/freebsd-current/usr.sbin/flowctl/ |
H A D | Makefile | 19 CFLAGS+= -Wno-error=unused-but-set-variable
|
/freebsd-current/contrib/bmake/unit-tests/ |
H A D | varmod-remember.mk | 4 # in the _ variable or another, to be used later again. 9 # cases, the value of the expression is saved in the temporary variable '_', 24 # Before var.c 1.1040 from 2023-02-09, the temporary variable '_' was placed 27 # evaluations in global scope could not overwrite the variable '_' anymore, 37 # In the parameterized form, having the variable name on the right side of 39 # the variable name is on the left-hand side of the = operator, therefore 49 # The ':_' modifier takes a variable name as optional argument. Before var.c 50 # 1.867 from 2021-03-14, this variable name could refer to other variables, 53 # '${...:_=VAR.${param}}' is that the variable name is parsed in an ad-hoc 56 # are possible but long expressions aren't, the name of the temporary variable [all...] |
H A D | make-exported.mk | 4 # directive and the .MAKE.EXPORTED variable. This leads to non-obvious 5 # behavior for certain variable assignments. 13 # export the variable named "-env", but that is rejected because the 14 # variable name starts with a hyphen. 20 # Since 2020-10-03, the "variable" named "-literal" is not exported anymore,
|
H A D | varname-dot-makeflags.mk | 3 # Tests for the special .MAKEFLAGS variable, which collects almost all 5 # the environment variable MAKEFLAGS (without leading '.'). 17 # Append an option with argument, a plain option and a variable assignment. 27 # The environment variable 'MAKEFLAGS' is not available to child processes 34 # After parsing, the environment variable 'MAKEFLAGS' is set based on the
|
H A D | varparse-errors.mk | 18 REF_UNDEF= A reference to an ${UNDEF}undefined variable. 28 # The variable itself must be defined. 30 .if ${REF_UNDEF} != "A reference to an undefined variable." 34 # As of 2020-12-01, errors in the variable name are silently ignored. 38 VAR.${:U:Z}= unknown modifier in the variable name 39 .if ${VAR.} != "unknown modifier in the variable name" 43 # As of 2020-12-01, errors in the variable name are silently ignored. 47 VAR.${:U:Z}post= unknown modifier with text in the variable name 48 .if ${VAR.post} != "unknown modifier with text in the variable name" 58 # To trigger this difference, the variable assignmen [all...] |
H A D | varname-makefile.mk | 3 # Tests for the special MAKEFILE variable, which contains the current 6 # When there are multiple -f options, the variable MAKEFILE is set 9 # variable though. 15 # This variable lives in the "Internal" namespace. 18 # Deleting the variable does not work since this variable does not live in 27 # Overwriting this variable is possible since the "Internal" namespace
|
H A D | recursive.mk | 3 # In -dL mode, a variable may get expanded before it makes sense. 7 # The purpose of evaluating that variable early was just to detect 8 # whether there are unclosed variables. The variable value is therefore 30 # can be achieved by just parsing the variable and not evaluating it. 32 # When the variable is only parsed but not evaluated, bugs in nested 37 # expect+1: Unclosed variable "MISSING_PAREN" 39 # expect+1: Unclosed variable "MISSING_BRACE"
|
H A D | cmdline.mk | 20 # The .OBJDIR can be set via the MAKEOBJDIR command line variable. 21 # It must be a command line variable; an environment variable would not work. 26 # The .OBJDIR can be set via the MAKEOBJDIR command line variable, 27 # and expressions based on that variable can contain the usual modifiers. 29 # the SUB2 variable in the modifier is not defined yet and is therefore empty. 30 # The SUB1 in the resulting path comes from the environment variable TMPBASE, 41 # variable assignments in makefiles. In the command line, trailing whitespace 47 # Leading whitespace in the variable value is discarded though, which makes
|
H A D | varparse-undef-partial.mk | 3 # When an undefined variable is expanded in a ':=' assignment, only the 12 # The expression ${VAR.${PARAM}} refers to the variable named "VAR.:Q", 13 # with the ":Q" being part of the name. This variable is not defined, 18 # interpretation of the ":Q" has changed from being part of the variable 19 # name to being a variable modifier. This is a classical code injection. 29 # At this point, the variable "VAR." is defined, therefore the expression 30 # ${VAR.:Q} is expanded, consisting of the variable name "VAR." and the 37 # produces a different result since the variable named "VAR.:Q" is now 39 # variable name, as would be expected from reading the expression. 52 # The variable COMPILE [all...] |
H A D | var-op-expand.mk | 3 # Tests for the := variable assignment operator, which expands its 28 # the variable named "", which is guaranteed to be never defined, but at the 40 # reference to a variable containing literal dollar signs 49 # reference to an undefined variable 61 # reference to a variable whose name is computed from another variable 71 # expression with an indirect modifier referring to an undefined variable 83 # expression with an indirect modifier referring to another variable that 84 # in turn refers to an undefined variable 87 # the variable modifie [all...] |
H A D | directive-export-literal.mk | 3 # Tests for the .export-literal directive, which exports a variable value
|
H A D | directive-undef.mk | 9 # variable, silently skipping all further variable names. 14 # Since var.c 1.761 from 2020-12-22, .undef handles multiple variable names 26 # to delete the variable with the empty name, which never exists; see 33 # Trying to delete the variable with the empty name is ok, it just won't 34 # ever do anything since that variable is never defined. 56 # A variable named " " cannot be undefined. There's no practical use case 69 # A variable named "$" can be undefined since the argument to .undef is 87 # expect+1: while evaluating variable "VARNAMES": Unknown modifier "Z" 110 # When an exported variable i [all...] |
H A D | varmod-order.mk | 3 # Tests for the :O variable modifier and its variants, which either sort the 15 # expect+1: Undefined variable "${WORDS:OX" 20 # expect+1: Undefined variable "${WORDS:Ox" 31 # expect: make: Bad modifier ":Oxn" for variable "NUMBERS" 42 # expect: make: Bad modifier ":On_typo" for variable "NUMBERS" 52 # expect: make: Bad modifier ":Onr_typo" for variable "NUMBERS" 62 # expect: make: Bad modifier ":Orn_typo" for variable "NUMBERS" 74 # expect: make: Bad modifier ":Onn" for variable "NUMBERS" 84 # expect: make: Bad modifier ":Onrr" for variable "NUMBERS" 94 # expect: make: Bad modifier ":Orrn" for variable "NUMBER [all...] |
H A D | varmod-to-many-words.mk | 3 # Tests for the :tw modifier, which treats the variable as many words, 15 # Protect against accidental freeing of the variable value.
|
H A D | varname-dot-alltargets.mk | 3 # Tests for the special .ALLTARGETS variable. 19 # The .ALLTARGETS variable is not about targets though, but
|
H A D | varmod-sun-shell.mk | 3 # Tests for the :sh variable modifier, which runs the shell command 4 # given by the variable value and returns its output.
|
H A D | varmod-quote-dollar.mk | 3 # Tests for the :q variable modifier, which quotes the string for the shell 8 # to the child make. When the child make parses the variable assignment, it
|
H A D | opt-x-reduce-exported.mk | 6 # The variable 'BEFORE' is exported, the variable 'AFTER' isn't.
|
H A D | var-recursive.mk | 19 DIRECT= ${DIRECT} # Defining a recursive variable is not yet an error. 22 . info ${DIRECT} # But expanding the variable is an error. 33 # The variable refers to itself, but only in the branch of a condition that 41 # Short variable names can be expanded using the short-hand $V notation, 42 # which takes a different code path in Var_Parse for parsing the variable 49 # If a recursive variable is accessed in a command of a target, the makefiles
|
H A D | cond-func-empty.mk | 6 # Note that the argument in the parentheses is a variable name, not an 16 # An undefined variable counts as empty. 21 # An undefined variable has the empty string as the value, and the :M 22 # variable modifier does not change that. 30 # no longer empty, but it is still based on an undefined variable. There are 51 # When an expression is based on an undefined variable, its modifiers interact 54 # is based on an undefined variable. The :U modifier that follows only looks 55 # at the definedness state to decide whether the variable is defined or not. 59 # Since the variable was undefined to begin with, the fallback value from the 67 # The variable EMPT [all...] |
H A D | varmod-loop.mk | 5 # variable 'var'. For example, '${1 2 3:L:@word@<${word}>@}' encloses each 8 # The variable name can be chosen freely, except that it must not contain a 9 # '$'. For simplicity and readability, variable names should only use the 17 # '$' are interpreted as expressions, like when evaluating a regular variable. 28 # Even "@" works as a variable name since the variable is installed 40 # since the $@ at the end could have been interpreted as a variable, which 51 # for the loop variable. These modifiers influence each other. 54 # variable in the scope of the expression and deleting it again after the 59 # loop variable t [all...] |
H A D | varmod-assign.mk | 3 # Tests for the obscure ::= variable modifiers, which perform variable 14 # operator '?=' only has an effect for the first time, therefore the variable 22 # operator '=' overwrites the previous value, therefore the variable LAST ends 30 # operator '+=' appends 3 times to the variable, therefore the variable 38 # with the modifier '::=', the last value is stored in the RAN variable. 75 # Assigning to the empty variable would obviously not work since that 76 # variable is write-protected. Therefore it is rejected early with a 85 # The :L modifier sets the value of the expression to its variable [all...] |
/freebsd-current/crypto/heimdal/lib/hx509/ |
H A D | sel-gram.y | 63 %type <expr> variable variables 92 | word kw_IN variable { $$ = _hx509_make_expr(comp_IN, $1, $3); } 98 | variable { $$ = $1; } 107 variable: '%' '{' variables '}' { $$ = $3; } label
|
/freebsd-current/crypto/heimdal/lib/wind/ |
H A D | gen-bidi.py | 78 def printTable(file, table, variable): 79 """print table to file named as variable""" 80 file.write("const struct range_entry %s[] = {\n" % variable) 96 file.write("const size_t %s_size = %u;\n\n" % (variable, count))
|
/freebsd-current/lib/libc/iconv/ |
H A D | citrus_mapper.c | 128 size_t linebufsize, const char **module, const char **variable) 166 /* get variable */ 167 *variable = p; 205 const char * __restrict variable) 260 (const void *)variable, strlen(variable) + 1, 281 const char * __restrict module, const char * __restrict variable) 284 return (mapper_open(ma, rcm, module, variable)); 318 const char *module, *variable; local 321 variable 127 lookup_mapper_entry(const char *dir, const char *mapname, void *linebuf, size_t linebufsize, const char **module, const char **variable) argument 202 mapper_open(struct _citrus_mapper_area *__restrict ma, struct _citrus_mapper * __restrict * __restrict rcm, const char * __restrict module, const char * __restrict variable) argument 279 _citrus_mapper_open_direct(struct _citrus_mapper_area *__restrict ma, struct _citrus_mapper * __restrict * __restrict rcm, const char * __restrict module, const char * __restrict variable) argument [all...] |