Subject: Re: [Boost-build] prototyping alternative Boost.Build syntax
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-11-07 10:34:29
On 11/06/2016 11:07 PM, Stefan Seefeld wrote:
> On 04.11.2016 11:18, Steven Watanabe wrote:
>> On 11/04/2016 07:29 AM, Stefan Seefeld wrote:
>>> * what is a "module" and how is it used in the engine ?
>> See modules.h. Also
> Thanks. I have been reading that document, and am a little confused as
> it seems the rules are slightly inconsistent, so I wonder whether I have
> merely misunderstood...
> The document explains how rules defined in one module can be accessed
> (by qname) from within another. But it seems that concept (of qualified
> naming) doesn't apply to anything else, such as action, variable, or
> target names. Am I reading that right ? And if so, why is that so ?
Modules are a bit of a hack for historical
reasons. In practice it isn't much of a problem.
- Actions and rules are accessed in the same way.
Thus, actions can be called from other modules.
- Targets refer to the file system which is
global. Scoping them by module would be
- Most variables shouldn't be accessed from
other modules anyway.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk