Re: Conditional requirements

From: pal.tw (pal.tw_at_[hidden])
Date: 2003-07-19 03:46:02

--- In jamboost_at_[hidden], David Abrahams <gclbb-jamboost_at_m...> 
wrote:
> Vladimir Prus <ghost_at_c...> writes:
> > I think the simplest solution is to declare that in conditional
> > property, part after ":" can be only free or incidental
> 
> Why would you want to impose that limitation?
> 
> > and that free/incidental features cannot be present before
> > ":". Opinions? Anybody using non-free conditional properties?
> 
> I don't know; this sounds terribly limiting to me.

But I think it sounds a good idea to prevent users from
misusing the rule. If the properties with other attributes
want to be combined, they can be declared by a "variant".

I will mention another thing about conditional property.
It might be a bug. One time I used conditional property like this
------------------------------------------------------------------
<link>shared:<linkflags>-DEF:$(SOURCE_ROOT)/curl-
7.10.5/lib/libcurl.def
-------------------------------------------------------------------
It parses in error because of two colons in this token.
The colon sign is used very often in msvc toolset options.
Is there any way to escape the colon sign ?