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

Lines Matching defs:not

19 # including it would not have any effect, not even on the special variable
41 # Its content is skipped, therefore the syntax error is not detected.
69 # Comments and empty lines do not affect the multiple-inclusion guard.
84 # not commonly used.
95 # Its content is skipped, therefore the syntax error is not detected.
104 # Triple negation is so uncommon that it's not recognized, even though it has
114 # If the guard variable is enclosed in spaces, it does not have an effect, as
115 # that form is not common in practice.
124 # If the guard variable condition is enclosed in parentheses, it does not have
125 # an effect, as that form is not common in practice.
134 # A conditional other than '.if' or '.ifndef' does not guard the file, even if
153 # If the guard variable condition is enclosed in parentheses, it does not have
154 # an effect, as that form is not common in practice.
180 # '!' is not supported in any place, though.
192 # choice a bad idea, therefore these characters are not allowed in guard
222 # The variable name in an '.ifndef' guard must be given directly, it must not
232 # The variable name in an '.if' guard must be given directly, it must not
307 # The whole file content must be guarded by a single '.if' conditional, not by
309 # This case is not expected to occur in practice, as the two parts would
358 # time, the guard does not have an effect, and the file is included again.
368 # If the file does not define the guard variable, the guard does not have an
370 CASES+= variable-not-defined
371 LINES.variable-not-defined= \
374 # expect: Parse_PushInput: variable-not-defined.tmp:1
375 # expect: Parse_PushInput: variable-not-defined.tmp:1
377 # The outermost '.if' must not have an '.elif' branch.
398 # The outermost '.if' must not have an '.else' branch.
469 # and once for determining the guard name. This double evaluation should not
483 # This form does not work when the basename contains whitespace characters, as
484 # it is not possible to define a target with whitespace, not even by cheating.
505 # guard name only contains the basename but not the directory name. So even
538 # If the guard target is not defined when including the file the next time,
584 # If the guard target name has leading spaces, it does not have an effect,
585 # as that form is not common in practice.
594 # If the guard target name has trailing spaces, it does not have an effect,
595 # as that form is not common in practice.
604 # If the guard target condition is enclosed in parentheses, it does not have
605 # an effect, as that form is not common in practice.