From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-09-12 16:24:57
[2003-09-12] David Abrahams wrote:
>Vladimir Prus <ghost_at_[hidden]> writes:
>> David Abrahams wrote:
>>> > Hmm... IIRC, it was discussed between Ali, myself, and *you* some time
>>> > ago. In short, it was decided that @ does not add anything.
>>> Yes, but now some crazy "//" notation which I don't understand has
>>> shown up. Where did that come from and why do we have it?
>> Well, the motivation is explained by Ali at the very end of
>> Some followups are in
>> "//" is the separator between project-id and target-id.
>Oh. We never discussed using that notation, which may explain my
>confusion. Well, it's minimal and complete, but:
> 1. I am concerned that on some systems // is used to write remote
> 2. People read paths left-to-right. I thought it was helpful to
> have an @ at the beginning to say "this is a project path".
> 3. It seems to me that using "//" for the usual case is syntactic
> overkill. Should it be reserved for the case where you are
> specifying a multi-component path w.r.t. a project, i.e.
I have a simple question. What is the need for the "//"? Or perhaps what
does it delineate? Because I fail to see the need for it.
-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq
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