Lines Matching refs:the
3 # When an undefined variable is expanded in a ':=' assignment, only the
4 # initial '$' of the expression is skipped by the parser, while
5 # the remaining expression is evaluated. In edge cases this can lead to
6 # a completely different interpretation of the partially expanded text.
12 # The expression ${VAR.${PARAM}} refers to the variable named "VAR.:Q",
13 # with the ":Q" being part of the name. This variable is not defined,
14 # therefore the initial '$' of that whole expression is skipped by the parser
15 # (see VarSubstExpr) and the rest of the expression is expanded as usual.
17 # The resulting expression is ${VAR.:Q}, which means that the
18 # interpretation of the ":Q" has changed from being part of the variable
25 # Define the possible outcomes, to see which of them gets expanded.
29 # At this point, the variable "VAR." is defined, therefore the expression
30 # ${VAR.:Q} is expanded, consisting of the variable name "VAR." and the
36 # In contrast to the previous line, evaluating the original LIST again now
37 # produces a different result since the variable named "VAR.:Q" is now
38 # defined. It is expanded as usual, interpreting the ":Q" as part of the
39 # variable name, as would be expected from reading the expression.
45 # It's difficult to decide what the best behavior is in this situation.
46 # Should the whole expression be skipped for now, or should the inner
52 # The variable COMPILER typically contains an identifier and the variable is
53 # not modified later. In this practical case, it does not matter whether the
54 # expression is expanded early, or whether the whole ${COPTS.${COMPILER}} is
55 # expanded as soon as the variable COPTS.${COMPILER} becomes defined. The
Indexes created Sun Feb 15 12:34:49 CET 2026