Re: [jamboost] Re: target references

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-07-10 01:22:07

David Abrahams wrote:

> Since I understand Christopher Currie's issue with target names that
> need to contain a slash, I suggest using a path separator character:
>
> @other_project:lib1:<link>static

IOW, the problem you have with the current syntax is that "/" is too heavily 
overloaded? I'm accustomed to this syntax, so it's naturally fine with me. 
What others think?

About "@" -- why do we need it? Is it really desired to indicate if we refer 
to target or a file? BTW, IIRC the original proposal by Ali was that

/some/other/project//foobar.cpp

could refer *either* to target foorbar.cpp or file foobar.cpp in that other 
project. I'm not really sure "@" is good -- you need to know what 
'foobar.cpp' is really is.

> Somehow I have no trouble with the colon separating these sections of
> the target reference.

There might be troubles when you refer to a target in requirements:

<variant>release:<source>/other/lib:target1

There's a lot of colons here.

- Volodya