Lines Matching refs:expression
4 # the then-expression or the else-expression, depending on the condition.
13 # The variable name of the expression is expanded and then taken as the
19 # word "expression". If the name were expanded lazily, everything would be
43 # context, an undefined expression is not an error. The "variable name" then
65 # expression" by ApplyModifier_IfElse. The expression containing that
83 # value of the expression is still undefined. CondParser_String is
103 # expression in the condition to be evaluated at exactly the right point,
105 # expression ${:U\$}. Because of this escaping, the variable "VAR" and thus
110 # Making the '$' of the '${VAR}' expression indirect hides this expression
122 # make: Bad conditional expression 'string == "literal" && no >= 10'
131 # of the expression, and in an expression, the variable name is always
134 # expression, it already looks like this:
138 # When parsing such an expression, the parser used to be strict. It first
146 # expression'.
148 # Ideally, the conditional expression would not be expanded before parsing
204 # 1. The whole expression is only parsed.
205 # 2. The expression is parsed and the 'then' branch is evaluated.
206 # 3. The expression is parsed and the 'else' branch is evaluated.
208 # In all of these cases, the expression must be parsed in the same way,
219 # that in both cases the expression is parsed in the same way, taking the
246 # At 2020-01-07, the expression evaluated to 'then0,,}}', even though it was
254 # At 2020-01-07, the whole expression evaluated to 'then2,,}}' instead of the
260 # and the whole expression. This left the trailing ',,}}', which together
266 # Since the condition is taken from the variable name of the expression, not
Indexes created Sat Oct 11 14:09:46 GMT 2025