Home | History | Annotate | Download | only in unit-tests

Lines Matching refs:And

5 # This is called 'short-circuit evaluation' and is the usual evaluation
7 # distinguishes between the operators 'And', 'And Then', 'Or', 'Or Else'.
10 # evaluated, which was wrong.  In cond.c 1.69 and var.c 1.197 on 2015-10-11,
12 # possible to skip evaluation of irrelevant expressions and only
27 # evaluate at all' and 'allow undefined variables' led to the unexpected
35 .if 0 && ${echo "unexpected and" 1>&2 :L:sh}
38 .if 1 && ${echo "expected and" 1>&2 :L:sh}
41 .if 0 && exists(nonexistent${echo "unexpected and exists" 1>&2 :L:sh})
44 .if 1 && exists(nonexistent${echo "expected and exists" 1>&2 :L:sh})
47 .if 0 && empty(${echo "unexpected and empty" 1>&2 :L:sh})
50 .if 1 && empty(${echo "expected and empty" 1>&2 :L:sh})
54 # The whole !empty condition is only parsed and then discarded.
130 .  if ${echo "unexpected nested and" 1>&2 :L:sh}
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
158 # uninterpreted variable value, in this case '${UNDEF}'.  And even though the
160 # the comparison were still parsed and evaluated.  Comparing these two values
166 # comparisons.  Instead, they are only parsed and then discarded.
169 # -dA log.  To actually see it, add debug logging at the beginning and end of
182 # Since cond.c 1.76 from 2020.06.28 and before var.c 1.225 from 2020.07.01,
189 # this expression, the variable name was 'VAR${:U1}', and of this variable
200 # expressions based on undefined variables are allowed and evaluate to an
208 # matches or equality comparisons worked fine and never produced error
230 # expect+1: Comparison with "<" requires both operands "" and "42" to be numeric
237 # The right-hand side of '||' is irrelevant and thus not evaluated.
243 # The right-hand side of '||' is relevant and thus evaluated normally.
271 # evaluated to true (see CondParser_FuncCall and CondParser_FuncCallEmpty), an