Lines Matching refs:was
9 # Before 2020-06-28, the right-hand side of an && or || operator was always
10 # evaluated, which was wrong. In cond.c 1.69 and var.c 1.197 on 2015-10-11,
14 # relevant expressions was that in the irrelevant
17 # error message 'Malformed conditional', but the irrelevant expression was
22 # but that was wrong. The code in cond.c 1.1 from 1993-03-21 looks good since
53 # "VAR U11" is not evaluated; it was evaluated before 2020-07-02.
67 # Before 2020-07-02, it was wrongly evaluated.
154 # On the right-hand side of the '&&', the expression ${INDIR_UNDEF} was
155 # defined and had the value '${UNDEF}', but the nested variable UNDEF was
157 # and in parse-only mode, the "value" of the parsed expression was the
161 # numerically was not possible since the string '${UNDEF}' is not a number,
165 # This was fixed in cond.c 1.79 from 2020-07-09 by not evaluating irrelevant
168 # At that time, there was not enough debug logging to see the details in the
175 # expression was only parsed, not evaluated. The resulting literal string
176 # '${INDIR_UNDEF:U2}' was not numeric either, for the same reason as above.
187 # to occur in expressions. In this mode, the variable name 'VAR' was
189 # this expression, the variable name was 'VAR${:U1}', and of this variable
190 # name, only the fixed part 'VAR' was evaluated, without the part '${:U1}'.
204 # not evaluated, but that was wrong. These conditions were evaluated, the
205 # only difference was that undefined variables in them didn't trigger an
261 # already evaluates to false. Before cond.c 1.79 from 2020-07-09, it was
Indexes created Sun Feb 15 12:34:49 CET 2026