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

Lines Matching refs:Variable

5 # Note the fine distinction between a variable and an expression.
6 # A variable has a name and a value. To access the value, one writes an
9 # variable modifiers such as in ${VAR:Mpattern}.
11 # XXX: Strictly speaking, variable modifiers should be called expression
12 # modifiers instead since they only modify the expression, not the variable.
14 # of the variable.
20 # A defined variable may appear on either side of the comparison.
28 # A variable that appears on the left-hand side must be defined.
29 # expect+1: Variable "UNDEF" is undefined
34 # A variable that appears on the right-hand side must be defined.
35 # expect+1: Variable "UNDEF" is undefined
40 # A defined variable may appear as an expression of its own.
44 # An undefined variable on its own generates a parse error.
45 # expect+1: Variable "UNDEF" is undefined
58 # A defined variable may appear on either side of the comparison.
62 # A variable on the left-hand side must be defined.
63 # expect+1: Variable "U" is undefined
67 # A variable on the right-hand side must be defined.
68 # expect+1: Variable "U" is undefined
72 # A defined variable may appear as an expression of its own.
76 # An undefined variable without a comparison operator generates a parse error.
77 # expect+1: Variable "U" is undefined
119 # An expression in a condition must not be based on an undefined variable,
120 # but undefined variables may occur in the variable name or in modifiers.
132 # expect+1: Variable "UNDEF" is undefined
141 # expect+1: Variable "UNDEF" is undefined
150 # expect+1: Variable "UNDEF" is undefined