Changes between Version 22 and Version 23 of AlternativeSelection

Timestamp:

Apr 14, 2007, 12:37:09 PM (19 years ago)

Author:

Dave Abrahams

Comment:

--

AlternativeSelection

@@ -111 +111 @@
 == Why Not Separate Alternative Selection Criteria from Requirements? ==
 
-One might try to address these cases by asking the user to specify their criteria for selecting alternatives separately from their build requirements.  That would be a bad idea, for two reasons.
+One might try to address these cases by forcing the user to specify their criteria for selecting alternatives separately from the alternatives' build requirements.  That would be a bad idea, for two reasons.
 
 First, ''one usually wants a target to be built with properties that correspond to what the user explicitly requested!''  There's no reason to throw out that useful information just because occasionally one wants properties that aren't in the build request.  Certainly, when the build request turns out to match an alternative's requirements exactly, Boost.Build currently considers that to be unambiguous, and that has not caused any real difficulty.  This proposal is about expanding the cases that Boost.Build considers unambiguous, to better leverage the usual correspondence between requirements and build requests.