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

1 2 3

  /src/tests/usr.bin/xlint/lint1/
lex_char.c 82 * occur in practice though.
  /src/usr.bin/make/unit-tests/
cond-token-number.mk 11 # Even though -0 is a number and would be accepted by strtod, it is not
22 # Even though +0 is a number and would be accepted by strtod, it is not
33 # Even though -1 is a number and would be accepted by strtod, it is not
44 # Even though +1 is a number and would be accepted by strtod, it is not
55 # When the number comes from an expression though, it may be signed.
61 # When the number comes from an expression though, it may be signed.
76 # This is not a hexadecimal number, even though it has an x. It is
directive-undef.exp 4 make: directive-undef.mk:105: warning: UT_EXPORTED is still listed in .MAKE.EXPORTED even though spaceit is not exported anymore.
unexport.mk 12 # was not reachable though. At that point, backslash-newline has already
varname-dot-alltargets.mk 19 # The .ALLTARGETS variable is not about targets though, but
directive-export-impl.mk 38 # are not modified though, since the next time the :!...! modifier is
47 # These flags do not show up anywhere though, not even in the debug log.
53 # in the process of exporting the variable value, though.
counter-append.mk 7 # 6 words, even though the NEXT variable was only accessed 3 times.
counter.mk 7 # 4 words, even though the NEXT variable was only accessed 3 times.
cond-cmp-string.mk 73 # resulted in a "Malformed conditional", even though the string was
78 # Some other characters worked though, and some didn't.
93 # Adding another expression to the string literal works though.
98 # Adding a space at the beginning of the quoted expression works though.
directive-undef.mk 85 # As of var.c 1.762, this doesn't happen though because the error handling
104 # expect+1: warning: UT_EXPORTED is still listed in .MAKE.EXPORTED even though spaceit is not exported anymore.
105 . warning UT_EXPORTED is still listed in .MAKE.EXPORTED even though $\
123 # This applies to both variables, even though 'INDIRECT' is not actually
job-output-long-lines.mk 14 # beginning of a line, even though this is expected by anyone reading the log
opt-debug-lint.mk 30 # Even though the "@" variable is not defined at this point, this is not an
40 # well-known "Malformed conditional" error message, even though the
70 # variable modifier had to be separated by colons. This was wrong though
93 # compiled even though that was not necessary for checking the syntax at the
varmod-to-abs.mk 11 # a few restrictions though: The "redirected" path had to start with a slash,
var-eval-short.mk 58 # even though the whole expression should have only been parsed, not
153 # irrelevant right-hand side of the condition, even though this was not
165 # through, even though an empty string would suffice.
cond-token-string.mk 59 # expect+1: The string literal " " is not empty, even though it consists of whitespace only.
60 . info The string literal " " is not empty, even though it consists of $\
cond-func-defined.mk 58 # condition was evaluated even though it was irrelevant.
cond-op-and.mk 56 # The && operator may be abbreviated as &. This is not widely known though
cond-op-or.mk 56 # The || operator may be abbreviated as |. This is not widely known though
directive-for-break.mk 39 # No parse error, even though the .break occurs outside a .for loop, since
opt-env.mk 5 # the command line though.
posix-varassign.mk 69 # though it is not specified by POSIX, due to the differences in existing
varmod-shell.mk 19 # XXX: Processing continues as usual though.
varname-dot-parsedir.mk 40 # being parsed. Technically, it's possible though, but only if the file
varname-dot-parsefile.mk 35 # being parsed. Technically, it's possible though, but only if the file
  /src/sys/arch/x68k/stand/xxboot/
memcpy.S 77 | though it's pointless in

Completed in 235 milliseconds

1 2 3