| /src/tests/usr.bin/xlint/lint1/ |
| msg_326.c | 9 int variable __packed;
|
| msg_086.c | 8 extern double variable;
18 /* expect+1: warning: automatic 'variable' hides external declaration with type 'double' [86] */
19 int variable = 3; local
23 sink = variable;
|
| /src/tests/usr.bin/indent/ |
| opt_ts.c | 13 int variable; variable
24 int variable; variable
|
| opt_ut.c | 12 int variable; variable
29 int variable; variable
46 int variable; variable
|
| lex_ident.c | 44 int variable; variable
|
| /src/share/i18n/esdb/BIG5/ |
| Makefile.inc | 14 ${.CURDIR}/BIG5/Big5.variable
20 Big5-${i:S/:/@/}.src: Big5.src Big5.variable
23 -e 's/variable/${Big5_$i_variable}/' \
|
| /src/usr.bin/make/unit-tests/ |
| varname-dollar.mk | 3 # Tests for the expression "$$", which looks as if it referred to a variable,
6 # If there really were a special variable named '$', the expressions ${${DOLLAR}}
9 # Using the dollar sign in variable names is tricky and not recommended.
10 # To see that using this variable indeed affects the variable '$', run the
14 # At this point, the variable '$' is not defined. Therefore the second line
21 # Now overwrite the '$' variable to see whether '$$' really expands to that
22 # variable, or whether '$$' is handled by the parser.
25 # At this point, the variable '$' is defined, therefore its value is printed
|
| directive-export-impl.mk | 11 # VarFlags.exported (per variable)
12 # VarFlags.reexport (per variable)
19 # This is a variable that references another variable. At this point, the
20 # other variable is still undefined.
24 # variable value refers to another variable, ExportVar does not actually
25 # export the variable but only marks it as VarFlags.exported and
26 # VarFlags.reexport. After that, ExportVars registers the variable name in
36 # variables exported. Since this variable has both of the above-mentione
[all...] |
| var-op-append.mk | 3 # Tests for the '+=' variable assignment operator, which appends to a
4 # variable, creating it if necessary.
10 # The '+=' variable assignment operator is planned to be added in
17 # The '+=' variable assignment operator was added before 1993-03-21.
19 # Appending to an undefined variable is possible.
20 # The variable is created, and no extra space is added before the value.
26 # Appending to an existing variable adds a single space and the value.
38 # Variable names may contain '+', and this character is also part of the
48 # Before var.c 1.793 from 2021-02-03, the variable name of a newly created
49 # variable was expanded two times in a row, which was unexpected bu
[all...] |
| var-scope-cmdline.mk | 11 # variable name once for each lookup. Instead, when looking up the value of
12 # a variable, the search often starts in the global scope since that is where
15 # common case of finding a variable in the global scope, another lookup would
17 # variable there.
22 # Whenever a global variable is created, this creation is ignored if
23 # there is a cmdline variable of the same name.
25 # Whenever a cmdline variable is created, any global variable of the
28 # Whenever a global variable is deleted, nothing special happens.
30 # Deleting a cmdline variable is not possible
[all...] |
| varmod-loop-delete.mk | 3 # Tests for the variable modifier ':@', which as a side effect allows to
4 # delete an arbitrary variable.
6 # A side effect of the modifier ':@' is that the loop variable is created as
7 # an actual variable in the current evaluation scope (Command/Global/target),
8 # and at the end of the loop, this variable is deleted. Since var.c 1.204
9 # from 2016-02-18 and before var.c 1.963 from 2021-12-05, a variable could be
12 # See Var_Parse, comment 'the value of the variable must not change'.
15 ${MAKE} -f ${MAKEFILE} delete-active-variable || true
17 ${MAKE} -f ${MAKEFILE} delete-active-variable-in-target || true
23 delete-active-variable: .PHON
[all...] |
| var-op-default.mk | 3 # Tests for the ?= variable assignment operator, which only assigns
4 # if the variable is still undefined.
6 # The variable VAR is not defined yet. Therefore it gets the default value
7 # from the variable assignment.
13 # At this point, the variable 'VAR' is already defined. The '?=' therefore
14 # ignores the new variable value, preserving the previous "default value".
20 # The '?=' operator only checks whether the variable is defined or not.
21 # An empty variable is defined, therefore the '?=' operator does nothing.
32 # there is never an actual variable named 'i' involved.
34 # Because there is not really a variable named 'i', the '?=' operato
[all...] |
| counter-append.mk | 3 # Demonstrates how to let make count the number of times a variable
4 # is actually accessed, using the ::+= variable modifier.
7 # 6 words, even though the NEXT variable was only accessed 3 times.
8 # The cause for this surprising behavior was that the ::= variable modifiers
17 # This variable is first set to empty and then expanded.
|
| counter.mk | 3 # Demonstrates how to let make count the number of times a variable
4 # is actually accessed, using the ::= variable modifier.
7 # 4 words, even though the NEXT variable was only accessed 3 times.
8 # The cause for this surprising behavior was that the ::= variable modifiers
17 # This variable is first set to empty and then expanded.
|
| varname-dot-shell.mk | 3 # Tests for the special .SHELL variable, which contains the shell used for
6 # This variable is read-only.
17 # Trying to append to the variable.
24 # Trying to delete the variable.
25 # This has no effect since the variable is not defined in the global scope,
|
| directive-include-guard.mk | 18 # variable or the guard target is defined, the file is skipped completely, as
19 # including it would not have any effect, not even on the special variable
20 # '.MAKE.MAKEFILES', as that variable skips duplicate pathnames.
30 # This is the canonical form of a variable-based multiple-inclusion guard.
31 CASES+= variable-ifndef
32 LINES.variable-ifndef= \
36 # expect: Parse_PushInput: variable-ifndef.tmp:1
37 # expect: Skipping 'variable-ifndef.tmp' because 'VARIABLE_IFNDEF' is defined
42 CASES+= variable-ifndef-reuse
43 LINES.variable-ifndef-reuse=
[all...] |
| export-variants.mk | 12 . warning At this point, no variable should be exported.
16 . warning At this point, no variable should be exported.
20 . warning At this point, no variable should be exported.
28 . warning At this point, a single variable should be exported.
32 . warning At this point, a single variable should be exported.
36 . warning At this point, a single variable should be exported.
|
| opt-define.mk | 8 # The variable has the exact value "1", not "1.0".
13 # The variable can be overwritten by assigning another value to it. This
14 # would not be possible if the variable had been specified on the command line
21 # The variable can be undefined. If the variable had been defined in the
30 # behaves differently, it defines a variable with the name 'VAR=value' and the
|
| varmod-to-one-word.mk | 3 # Tests for the :tW variable modifier, which treats the variable value
15 # Protect against accidental freeing of the variable value.
|
| varmod-loop-varname.mk | 3 # Tests for the first part of the variable modifier ':@var@...@', which
4 # contains the variable name to use during the loop.
12 # Before 2021-04-04, the name of the loop variable could be generated
15 # variable name.
16 # expect+1: In the :@ modifier, the variable name "${:Ubar:S,b,v,}" must not contain a dollar
24 # ":::" is a very creative variable name, unlikely to occur in practice.
26 # be escaped in the modifiers, but not in the variable name, therefore
33 # "@@" is another creative variable name.
39 # In extreme cases, even the backslash can be used as variable name.
46 # The variable name can technically be empty, and in this situatio
[all...] |
| var-op-assign.mk | 3 # Tests for the = variable assignment operator, which overwrites an existing
4 # variable or creates it.
6 # This is a simple variable assignment.
7 # To the left of the assignment operator '=' there is the variable name,
8 # and to the right is the variable value. The variable value is stored as-is,
21 # The variable value can contain arbitrary characters.
28 # another variable.
38 # The variable value may contain references to other variables.
39 # In this example, the reference is to the variable with the empty name
[all...] |
| 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...] |
| 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,
|
| 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
|
| cond-token-var.mk | 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
[all...] |
