HomeSort by: relevance | last modified time | path
    Searched refs:braces (Results 1 - 25 of 25) sorted by relevancy

  /src/usr.bin/make/unit-tests/
varname-dollar.exp 2 make: varname-dollar.mk:19: dollar in braces is .
4 make: varname-dollar.mk:30: dollar in braces is dollar.
varname-dollar.mk 18 # expect+1: dollar in braces is .
19 .info dollar in braces is ${${DOLLAR}}.
29 # expect+1: dollar in braces is dollar.
30 .info dollar in braces is ${${DOLLAR}}.
varname.exp 1 Global: VAR{{{}}} = 3 braces
2 Var_Parse: ${VAR{{{}}}}" != "3 braces" (eval)
var-op-assign.mk 62 # But if the whitespace appears inside parentheses or braces, everything is
66 # neither contain parentheses nor braces. This is only a side-effect from
68 # name. It only counts parentheses and braces instead of properly parsing
72 VAR{spaces in braces}= {}
79 VARNAME_BRACES= VAR{spaces in braces}
varmod-undefined.mk 32 # The nested expressions may contain braces, and these braces don't
35 # and closing braces don't match anymore. It's syntactically valid though.
parse-var.mk 9 # long form with braces endc == '}'
101 # braces.
104 # Keep these braces outside the conditions below, to keep them simple to
121 # only counted the braces, and since the inner expression '${BRACE_PAIR:...}'
var-op-sunsh.mk 97 # Since the parser just counts braces and parentheses instead of properly
100 # be enclosed in braces or parentheses.
109 # The unintended comment can include multiple levels of nested braces and
110 # parentheses. Braces and parentheses are interchangeable, that is, a '(' can
111 # be closed by either ')' or '}'. These braces and parentheses are only
113 VAR :sh{Put}((((a}{comment}}}}{here}= comment in braces
114 .if ${VAR} != "comment in braces"
varname.mk 7 # In a variable assignment, braces are allowed in the variable name, but they
8 # must be balanced. Parentheses and braces may be mixed.
9 VAR{{{}}}= 3 braces
10 .if "${VAR{{{}}}}" != "3 braces"
15 # braces and parentheses equally, therefore the first closing brace already
26 # This is not a variable assignment since the parentheses and braces are not
cond-func.mk 14 ${:UVAR{value}}= variable name with balanced braces
17 # so that no unbalanced braces appear in the top-level expression.
19 ${VARNAME_UNBALANCED_BRACES}= variable name with unbalanced braces
67 # Braces do not have any special meaning when parsing arguments.
72 # Braces do not have any special meaning when parsing arguments.
moderrs.mk 57 # In ParseModifierPart, braces and parentheses don't have to be balanced.
59 # braces must be balanced.
61 # used delimiter (either braces or parentheses) must be balanced.
varmod-edge.mk 13 INP= (parentheses) {braces} (opening closing) ()
50 # parentheses and braces are counted. This leads to a parse error since
65 # In contrast to parentheses and braces, the brackets are not counted
char-005c-reverse-solidus.mk 108 # all other places, but instead counts the braces and tries to decode the
varmod-ifelse.mk 209 # especially when one of the branches contains unbalanced '{}' braces.
220 # unbalanced braces in the ':S' modifiers into account. This change was not
300 # braces instead of proper subexpressions, which meant that unbalanced braces
302 BRACES= }}}
303 NO= ${0:?${BRACES:S,}}},yes,}:${BRACES:S,}}},no,}}
304 YES= ${1:?${BRACES:S,}}},yes,}:${BRACES:S,}}},no,}}
cond-token-var.mk 55 # The same as above, for single-letter variables without braces or
dep-var.mk 37 # effect. Now DirExpandCurly comes into play and expands the curly braces
varmod-defined.mk 59 # to the :M modifier, parentheses and braces do not need to be nested.
directive-for-escape.mk 132 # expressions, braces and parentheses. (Compare ':M', ':S', and
160 # could contain braces, which allowed to replace sequences of
varmod.mk 252 # When an expression has the usual form ${...} with braces,
directive-for.mk 142 # Ensure that braces and parentheses are properly escaped by the .for loop.
var-scope-local.mk 95 # '$(.TARGET)'; note that the alias is not written with braces, as would be
directive-include-guard.mk 191 # where parentheses or braces are handled inconsistently to make this naming
  /src/sys/external/bsd/compiler_rt/dist/lib/sanitizer_common/scripts/
check_lint.sh 21 -build/namespaces,-readability/braces
cpplint.py 126 Examples: --filter=-whitespace,+whitespace/braces
178 'readability/braces',
208 'whitespace/braces',
1496 """Holds states related to parsing braces."""
1499 # Stack for tracking all braces. An object is pushed whenever we
1684 # Consume braces or semicolons from what's left of the line
2448 # braces. And since you should never have braces at the beginning of a line,
2451 error(filename, linenum, 'whitespace/braces', 5,
2456 error(filename, linenum, 'whitespace/braces', 5
    [all...]
  /src/usr.bin/make/
dir.c 592 * See if the given name has any wildcard characters in it and all braces and
604 int braces = 0, brackets = 0; local
609 braces++;
613 braces--;
630 return wild && brackets == 0 && braces == 0;
687 /* Find the next closing brace in 'p', taking nested braces into account. */
705 * Find the next closing brace or comma in the string, taking nested braces
753 * Expand curly braces like the C shell. Brace expansion by itself is purely
test-variants.mk 176 CFLAGS.gcc-warn+= -Wmissing-braces

Completed in 32 milliseconds