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

1 2

  /src/usr.bin/make/unit-tests/
directive-ifdef.mk 8 # There is no variable named 'UNDEF', therefore the condition evaluates to
38 # they evaluate to true if they are not empty, therefore this particular
varname-dot-alltargets.mk 20 # about all nodes, therefore source is also included.
recursive.mk 8 # whether there are unclosed variables. The variable value is therefore
34 # therefore that's acceptable. In most practical cases, the missing
varmod-assign.mk 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
49 # Tests for nested assignments, which are hard to read and therefore seldom
52 # The condition "1" is true, therefore THEN1 gets assigned a value,
58 # The condition "0" is false, therefore ELSE2 gets assigned a value,
94 # name. The name of the expression is "VAR", therefore assigning to
deptgt-delete_on_error.mk 43 # The following line is therefore misleading but does not generate any
varname-dollar.mk 14 # At this point, the variable '$' is not defined. Therefore the second line
25 # At this point, the variable '$' is defined, therefore its value is printed
var-op-default.mk 6 # The variable VAR is not defined yet. Therefore it gets the default value
13 # At this point, the variable 'VAR' is already defined. The '?=' therefore
21 # An empty variable is defined, therefore the '?=' operator does nothing.
44 # it expands the variable name exactly once. Therefore both 'VAR.param'
varmod-remember.mk 29 # The expression ${GHI} therefore evaluated to '1=D 2=E 3=F', reusing the
39 # the variable name is on the left-hand side of the = operator, therefore
varparse-undef-partial.mk 14 # therefore the initial '$' of that whole expression is skipped by the parser
29 # At this point, the variable "VAR." is defined, therefore the expression
cond-cmp-numeric-eq.mk 45 # typically 16 or 17 significant digits, therefore these two numbers seem to
directive.mk 21 # There is no directive called '.target', therefore this is parsed as a
var-scope-local-legacy.mk 30 # The variable '.MEMBER' is undefined, therefore '%D' and '%F' are
varname-dot-curdir.mk 37 # Appending to .CURDIR does not make sense, therefore it doesn't matter that
varname-dot-parsedir.mk 14 # The .PARSEDIR may be absolute or relative, therefore there is not much that
dep-var.mk 50 # therefore this feature is probably not widely used.
68 # fully expanded before parsing, therefore any ':' in a target or source name
var-op-assign.mk 42 # This alone would not produce any side-effects, therefore the variable has
58 # The following line therefore generates a parse error.
93 # Therefore, just output an info message.
cmdline.mk 30 # the SUB2 variable in the modifier is not defined yet and is therefore empty.
comment.mk 43 # not count as a line continuation, therefore the variable assignment that
directive-export-impl.mk 39 # evaluated, the referenced variables could have changed, therefore the
varmod-order.mk 64 # criteria are fixed, not computed, therefore allowing this redundancy does
varmod-edge.mk 93 # Therefore, the second backslash escapes the parenthesis.
101 # the pattern, therefore (} would match.
110 # The backslash in \( does not escape the parenthesis, therefore it
115 # The second :M in the pattern is nested between ( and }, therefore it
varname-dot-make-save_dollars.mk 65 # in the value of an expression, therefore .MAKE.SAVE_DOLLARS doesn't apply
varname.mk 15 # braces and parentheses equally, therefore the first closing brace already
33 # as an escape character, therefore the parentheses still count to the nesting
34 # level, which at the end of the line is still 3. Therefore this is not a
varmod-ifelse.mk 66 # conditional therefore returns a parse error from Var_Parse, and this parse
86 # string. The left-hand side of the comparison is therefore just an empty
145 # therefore parsing stopped at the '>', producing the 'Bad conditional
  /src/distrib/sets/
fmt-list 241 -- The entries are nicely aligned, therefore there is no need to change
251 -- The entries are currently not aligned, therefore they are aligned
260 -- The entries are already aligned, therefore the current alignment is

Completed in 259 milliseconds

1 2