Re: [jamboost] Re: This appears to be a general boost.build problem

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-11-14 23:13:35

[2003-11-14] David Abrahams wrote:

>Rene Rivera <grafik666_at_[hidden]> writes:
>
>> [2003-11-14] David Abrahams wrote:
>>
>>>David Abrahams <dave_at_[hidden]> writes:
>>>
>>>> ..., not just one with the regex lib.
>>>>
>>>>
>>>
>>>Looks like I have a fix for this. Rene, I feel I should object to
>>>breaking the regularity of properties with these
>>><tag><more><grist><elements> properties. That was what was killing
>>>us. The fix is a patch to normalize-paths which special-cases <tag>.
>>
>> You have any other syntax in mind?? 
>
>
><tag-more-elements> for example, might work.
>
>> Or am I missunderstanding your question??
>
>I don't think so.
>
>> -- Thruthfully I don't understand what you mean on the second sentence
:-(
>
>All other properties were <feature>value, and only ever appeared with
>more gristed elements as <variant><feature>value or
><toolset><variant><feature>value, where <toolset> or <variant> might
>be <*>.

Well then, I guess this would make more sense..

<toolset|*><variant|*><tag>...
<toolset|*><variant|*><tag-prefix>...
<toolset|*><variant|*><tag-postfix>...

Don't know if it's worth changing in the very near future, or after the
release.

>Having properties with multiple gristed elements breaks a lot of code
>unless you account for it with special cases in normalize-paths.

Which wasn't a problem initially when the tag code was only part of stage.

-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq