Changes between Version 18 and Version 19 of AlternativeSelection

Timestamp:

Mar 28, 2007, 9:04:59 PM (19 years ago)

Author:

Dave Abrahams

Comment:

Change emphasis so claim is not specious.

AlternativeSelection

@@ -169 +169 @@
 == Summary ==
 
-This proposal would make several problematic cases into non-problems, would make the handling of multiple alternatives more uniform with the handling of "single alternatives," would make the syntax/semantics of specifying conditions for alternatives more consistent with that of build requests, and would make some currently-"ambiguous" bjam invocations into well-defined commands.  
+This proposal would make several problematic cases into non-problems, would make the handling of multiple alternatives more uniform with the handling of "single alternatives," ''could'' make the syntax/semantics of specifying conditions for alternatives more consistent with that of build requests, and would make some currently-"ambiguous" bjam invocations into well-defined commands.  
 Admittedly, it would change the semantics of a common class of configurations when combined with what appears to be an uncommon class of bjam invocations.  So far, we don't have a use case for the current semantics that isn't equally well-covered by this proposal.  However, should we find such a use case, the "optional extension" detailed here would allow us to recover the current semantics (with a different syntax, of course).