Re: target references

From: David Abrahams (dave_at_[hidden])
Date: 2004-07-14 16:11:34

"Mark Elston" <m.elston_at_[hidden]> writes:

>> 2.2. The part before "//" can identify a project in two ways: by specifying
>> directory of Jamfile, or by specifying project id previously passed to the
>> invocation of the 'project' rule. There's no syntantic differences between
>> those two ways: we first look if project with such id exists. If not, we
>> interpret the part before "//" as path to Jamfile.
>
> This, I think, is the rub. Sure, the build system can make a clear
> determination by looking for the ID then looking for the path.
> However, I think that the problem is that users will be trying to
> read this and would like a little visual distinction between the
> two. Otherwise, users would have to read every Jamfile in an entire
> build tree to find out whether or not a target reference referred to
> a project id or a path.
>
> Is that your point, David?

Only part of it. See my reply to Volodya.

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com