Searched refs:variable (Results 1 - 25 of 337) sorted by relevance

1234567891011>>

/freebsd-current/contrib/ncurses/misc/
H A Dshlib35 # libraries on systems that use the $LD_LIBRARY_PATH variable and don't embed
42 # variable has to be set to run the programs within this directory tree.
53 # variable, and on some systems (IRIX) you can even run the resulting binaries
91 # Set the environment variable.
124 variable=PATH
127 variable=LIBRARY_PATH
130 variable=DYLD_LIBRARY_PATH
133 variable=LD_LIBRARY_PATH
137 eval 'test -z "$'$variable'" && '$variable'
[all...]
/freebsd-current/crypto/heimdal/lib/asn1/
H A Dgen_length.c41 const char *variable)
43 fprintf (codefile, "%s += der_length_%s(%s);\n", variable, typename, name);
64 const char *variable, const char *tmpstr)
72 variable, t->symbol->gen_name, name);
79 length_primitive ("integer", "&enumint", variable);
82 length_primitive ("heim_integer", name, variable);
84 length_primitive ("integer64", name, variable);
86 length_primitive ("unsigned64", name, variable);
88 length_primitive ("integer", name, variable);
90 length_primitive ("unsigned", name, variable);
39 length_primitive(const char *typename, const char *name, const char *variable) argument
63 length_type(const char *name, const Type *t, const char *variable, const char *tmpstr) argument
[all...]
/freebsd-current/contrib/bmake/unit-tests/
H A Dvarname-dollar.mk3 # 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
H A Ddirective-export-impl.mk11 # 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 ha
[all...]
H A Dvar-op-append.mk3 # 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.
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 but
50 # irrelevant in practice since variable name
[all...]
H A Dvar-scope-cmdline.mk11 # 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 i
[all...]
H A Dvarmod-loop-delete.mk3 # 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'.
14 # Set up the variable that deletes itself when it is evaluated.
17 # In an assignment, the scope is 'Global'. Since the variable 'VAR' is
19 # expect+1: while evaluating variable "VA
[all...]
H A Dvar-op-default.mk3 # 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 name
[all...]
H A Dvarname-dot-shell.mk3 # 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,
H A Dcounter.mk3 # 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.
H A Dcounter-append.mk3 # 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.
H A Dvarmod-loop-varname.mk3 # 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+2: while evaluating "${:Uone two three:@${:Ubar:S,b,v,}@+${var}+@} != "+one+ +two+ +three+"": In the :@ modifier, the variable name "${:Ubar:S,b,v,}" must not contain a dollar
25 # ":::" is a very creative variable name, unlikely to occur in practice.
27 # be escaped in the modifiers, but not in the variable name, therefore
34 # "@@" is another creative variable name.
40 # In extreme cases, even the backslash can be used as variable name.
47 # The variable nam
[all...]
H A Ddirective-include-guard.mk18 # 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: file variable-ifndef.tmp, line 1
37 # expect: Skipping 'variable-ifndef.tmp' because 'VARIABLE_IFNDEF' is defined
42 CASES+= variable-ifndef-reuse
43 LINES.variable
[all...]
H A Dexport-variants.mk12 . 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.
H A Dopt-define.mk8 # 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
H A Dvarmod-to-one-word.mk3 # Tests for the :tW variable modifier, which treats the variable value
15 # Protect against accidental freeing of the variable value.
H A Dvar-op-assign.mk3 # 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 wit
[all...]
H A Dvarname.mk4 # And for variable names in general.
8 # In variable names, braces are allowed, but they must be balanced.
17 # marks the end of the variable name.
24 # In the above test, the variable name is constructed indirectly. Neither
27 # This is not a variable assignment since the parentheses and braces are not
29 # means the variable name is not finished.
33 # On the left-hand side of a variable assignments, the backslash is not parsed
36 # variable assignment as well.
39 # To assign to a variable with an arbitrary name, the variable nam
[all...]
H A Dcond-token-var.mk5 # 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.
18 # A defined variable may appear on either side of the comparison.
26 # A variable that appears on the left-hand side must be defined.
32 # A variable that appears on the right-hand side must be defined.
38 # A defined variable ma
[all...]
H A Dvarmod-assign-shell.mk3 # Tests for the variable modifier '::!=', which assigns the output of a shell
4 # command to the variable, but only if the command exited successfully. This
6 # command (variable assignment operator '!=', expression modifier ':sh',
10 # The variable modifier '::!=' and its close relatives have been around since
13 # Before 2020.08.25.21.16.53, the variable modifier '::!=' had a bug for
14 # unsuccessful commands, it put the previous value of the variable into the
20 # Even though the variable modifier '::!=' produces an error message,
23 # Having an error message instead of a warning like for the variable
/freebsd-current/share/i18n/esdb/BIG5/
H A DMakefile12 ${.CURDIR}/Big5.variable
16 Big5-${i:S/:/@/}.src: Big5.src Big5.variable
18 -e 's/variable/${Big5_${i:S/@/:/}_variable}/' \
/freebsd-current/lib/libc/locale/
H A Drune.c64 void *variable; local
99 variable = frl + 1;
105 runetype_ext_ranges = (_FileRuneEntry *)variable;
106 variable = runetype_ext_ranges + frl->runetype_ext_nranges;
107 if (variable > lastp) {
111 maplower_ext_ranges = (_FileRuneEntry *)variable;
112 variable = maplower_ext_ranges + frl->maplower_ext_nranges;
113 if (variable > lastp) {
117 mapupper_ext_ranges = (_FileRuneEntry *)variable;
118 variable
[all...]
/freebsd-current/contrib/llvm-project/llvm/lib/TargetParser/Windows/
H A DHost.inc27 // Override the default target with an environment variable named by
/freebsd-current/sbin/veriexec/
H A DMakefile17 XCFLAGS.manifest_lexer+= -Wno-missing-variable-declarations \
19 XCFLAGS.manifest_parser+= -Wno-missing-variable-declarations
/freebsd-current/usr.sbin/bsdconfig/share/
H A DMakefile7 sysrc.subr variable.subr

Completed in 266 milliseconds

1234567891011>>