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

1 2

  /src/usr.bin/make/unit-tests/
opt-debug-var.mk 26 # expect: Var_Parse: y(ASSIGNED) (eval)
32 # expect: Var_Parse: $U (eval-defined-loud)
38 # expect: Var_Parse: $< (eval-defined-loud)
dep-var.mk 11 # expect: Var_Parse: ${UNDEF1} (eval)
34 # Var_Parse, and this time, the result is the string "1-2-${INDIRECT_2}-2-1".
36 # This string is not expanded anymore by Var_Parse. But there is another
79 # calling Var_Parse.
80 # expect: Var_Parse: ${:U\$)}: (eval)
81 # expect: Var_Parse: $INDIRECT_2-2-1 $): (parse)
82 # expect: Var_Parse: $): (parse)
var-recursive.mk 38 # which takes a different code path in Var_Parse for parsing the variable
cond-token-var.mk 122 # expect: Var_Parse: ${VAR.param$U} (eval-defined-loud)
123 # expect: Var_Parse: $U} (eval)
opt-debug-lint.mk 37 # Since 2020-09-13, Var_Parse properly reports errors for undefined variables,
49 # observable from the outside of the function Var_Parse.
var-eval-short.mk 152 # Before var.c 1.875 from 2021-03-14, Var_Parse returned "${FAIL}else" for the
154 # necessary. Since the return value from Var_Parse is supposed to be ignored
varmod-defined.mk 50 # ApplyModifier_Defined calls Var_Parse, double dollars lead to a parse
95 # ApplyModifier_Defined passes the emode unmodified to Var_Parse, unlike
varparse-errors.mk 5 # This is the basis for redesigning the error handling in Var_Parse and
9 # Var_Parse
varmod-subst.mk 274 # calls Var_Parse to expand the variable. In all other places, the "$$"
275 # is handled outside of Var_Parse. Var_Parse therefore considers "$$"
280 # first part of the :S modifier. That code doesn't call Var_Parse but
varmod.mk 78 # See Var_Parse, where it calls Var_Subst.
86 # See Var_Parse, where it calls Var_Subst.
93 # See Var_Parse, where it calls Var_Subst.
cond-short.mk 11 # Var_Parse got a new parameter named 'wantit'. Since then it would have been
23 # it calls Var_Parse(condExpr, VAR_CMD, doEval,&varSpecLen,&doFree), but the
24 # definition of Var_Parse did not call the third parameter 'doEval', as would
170 # Var_Parse.
varmod-ifelse.mk 25 # Var_Parse and ParseVarname, it would be more useful and predictable
66 # conditional therefore returns a parse error from Var_Parse, and this parse
80 # XXX: The left-hand side is enclosed in quotes. This results in Var_Parse
82 # returns AMR_CLEANUP as result, Var_Parse returns varUndefined since the
varmod-loop-delete.mk 12 # See Var_Parse, comment 'the value of the variable must not change'.
directive-for-empty.mk 115 # Using a separate scope has the benefit that Var_Parse already allows for
118 # and these modifications happen in the scope that is passed to Var_Parse.
archive.mk 41 # that calls Var_Parse. It's an esoteric scenario since at the point where
directive-undef.mk 86 # in Var_Parse and Var_Subst is not done properly.
parse-var.mk 64 # everywhere else Var_Parse is called
cond-func-empty.mk 136 # to an empty string (see Var_Parse, varUndefined).
148 # and after the call to Var_Parse.
cond-token-plain.mk 194 # FIXME: In CondParser_String, Var_Parse returns var_Error without a
directive-for-escape.mk 134 # Var_Parse do all the parsing work.
var-scope-local.mk 91 # expressions like ${@}, ${.TARGET} ${VAR:Mpattern} (see Var_Parse,
  /src/usr.bin/make/
arch.c 212 result = Var_Parse(&nested_p, scope,
251 result = Var_Parse(&nested_p, scope,
cond.c 218 FStr nestedVal = Var_Parse(&p, SCOPE_CMDLINE, emode);
393 *out_str = Var_Parse(&p, SCOPE_CMDLINE, emode);
643 val = Var_Parse(&p, SCOPE_CMDLINE, doEval ? VARE_EVAL : VARE_PARSE);
make.h 602 * Value returned by Var_Parse when an error is encountered. It points to an
960 * TODO: Document what Var_Parse and Var_Subst return in this mode.
977 * Only for Var_Parse, not for Var_Subst or Var_Expand: Parse and
1050 FStr Var_Parse(const char **, GNode *, VarEvalMode);
var.c 100 * Var_Parse Parse an expression such as ${VAR:Mpattern}.
153 * as ${UNDEF:Ufallback} in Var_Parse and ApplyModifiers.
199 * The variable is currently being accessed by Var_Parse or Var_Subst.
289 * Special return value for Var_Parse, indicating a parse error. It may be
296 * Special return value for Var_Parse, indicating an undefined variable in
2147 FStr nested_val = Var_Parse(&p, ch->expr->scope,
2464 * XXX: This code is similar to the one in Var_Parse. See if
2482 FStr val = Var_Parse(&p, ch->expr->scope,
2746 * XXX: This code is similar to the one in Var_Parse.
3998 FStr mods = Var_Parse(&p, expr->scope, expr->emode)
    [all...]

Completed in 112 milliseconds

1 2