Re: [jamboost] Progress on issue 578618: Leave jamfile modules for user.

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-08-08 02:15:16

Rene Rivera wrote:

> >> Acceptable, but also (I think) unneccessary. Assuming you have a module
>
> to
>
> >> work with (e.g. jamfile.jam), you could store the __attributes__ for a
> >> given jamfile in $(jamfile-name).__attributes__ in that module. You
> >> could also implement a jamfile.get-attribute ( jamfile attribute) rule
> >> which extracts the value of a given attribute for a particular jamfile.

> While having to implement the same thing for project-root I came up with a
> somewhat less anoying syntax for these uses. Instead of having to get the
> object, then make calls on the object. I just pass along what call I want
> to make to the single access function and it makes the call. For project
> root one use looks like:
>
> ECHO [ project-root get-location ] ;

That's convenient in fact. Only you have to be in a scope where 
"project-root" is defined.

> It sould replace the above with:
>
> local requirements = [ project.attribute get requirements ] ;

I could not understand this sentence. What is "It" and why replace the above? 

Sorry,
Volodya