Changes between Version 23 and Version 24 of AlternativeSelection

Timestamp:

Apr 15, 2007, 4:41:42 PM (19 years ago)

Author:

Dave Abrahams

Comment:

--

AlternativeSelection

@@ -163 +163 @@
 == Optional Extension to this Proposal ==
 
-Currently, selecting a target alternative (when it's not the only alternative) requires that ''all'' its requirements be matched.  It's not yet clear that the "require all requirements" is actually useful in real-world scenarios (I admit that not requiring requirements is a bit weird, but remember that we already don't require them for the single-alternative case, so maybe "requirements" is a misnomer anyway).  If we decide it is important to support alternatives where all requirements are actually required in order to be selected, we would need a new notation.  I suggest:
+Currently, sa target alternative (when it's not the only alternative) will only be selected when ''all'' its requirements are matched in the build request.  It's not yet clear that the rule "match all requirements" is actually useful in real-world scenarios (I admit that not matching requirements is a bit weird, but remember the rule of thumb: ''requirements describe how a target must be built, not exactly how it must be requested'').  If we decide it is important to support alternatives whose requirements must ''all'' be present in the build request in order to be selected, we would need a new notation.  I suggest:
 
 {{{