From: David Abrahams (gclbb-jamboost_at_[hidden])
Date: 2003-05-16 07:55:18
Vladimir Prus <ghost_at_[hidden]> writes:
> David Abrahams wrote:
>> Vladimir Prus <ghost_at_[hidden]> writes:
>> > David Abrahams wrote:
>> >> Because the project-rules module gets "cloned" into the user's
>> >> projects, and because its rules import path and project, these
>> >> modules will be automatically available in the user's project. Is
>> >> that what we want?
>> > No, we don't want that. I wonder if "import" should import the rules as
>> > *local* names, so that cloning don't pick them....
>> I'm not sure what you're asking, exactly.
>> import foo ;
>> does bring in foo's names as qualified names local to the invoking module.
> Will those names be listed as result of RULENAME rule?
> If not, then clone-rules won't import them.
That's not the problem. The problem is that the rules from
project-rules (which *do* get cloned) are performing module imports,
and since those rules are localized, they are invoked from the module
into which they're cloned.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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