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:
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
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:
There's a lot of colons here.
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