Re: target references

From: David Abrahams (dave_at_[hidden])
Date: 2004-07-09 13:37:18

Rene Rivera <grafik.list_at_[hidden]> writes:

>> @other_project/lib1@<link>static
>> 
>> Though I guess I prefer the colon. 
>
> Reusing the "@" would be another source of confusion. 

You mean the 2nd one. OK.

> Overloading 
> semantics for the same syntax is just asking for trouble -- yes I 
> include Perl and C++ in that ;-)

OK.

>
> Thinking very far ahead.. My suggestion would be:
>
> @other_project/lib1?<link>static
>
> This follows what is becoming the expected practice of URIs. Which means 
> that in a far future we might be able to map that to things like:
>
> http://some_project.org/bb/lib1?
>static

> cvs://cvs.sf.net/some_project/lib1?<link>static
>
> I know, it's far fetched, but it doesn't hurt to hope :-)

Ouch. I don't think we should choose our syntax based on a
far-fetched hope.

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

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

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