| /freebsd/contrib/bmake/unit-tests/ |
| H A D | 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
|
| H A D | deptgt-begin.mk | 12 # though, since the ':' dependency operator prevents that any other place may
29 # For the .BEGIN target, .USE dependencies do not work though, since in
39 # For the .BEGIN target, .USEBEFORE dependencies do not work though, since in
|
| H A D | 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
|
| H A D | 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.
|
| H A D | 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.
|
| H A D | 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 expor…
105 . warning UT_EXPORTED is still listed in .MAKE.EXPORTED even though $\
123 # This applies to both variables, even though 'INDIRECT' is not actually
|
| H A D | cond-op-parentheses.mk | 5 # used to form arithmetic expressions such as '(3+4)' though.
35 # about this number though, much higher numbers work as well, at least on
53 # even though the documentation of that function promised to only ever return
|
| H A D | varmod-range.mk | 28 # An empty expression results in a sequence of a single number, even though
40 # expression into a defined one, even though it does not depend on the value
50 # As of 2020-11-01, they are accepted though, using up all available memory.
|
| H A D | directive-for-errors.mk | 18 # XXX: The error message is misleading though. As of 2020-12-31, it says
39 # expression" ${$} got replaced though, even though this would be a parse
|
| H A D | varmod-to-separator.mk | 39 # quote though, or other special characters like dollar or backslash.
116 # Not all modifiers use the separator from the previous modifier ':ts' though.
124 # Adding a final :M* modifier applies the :ts separator again, though.
150 # for an unsigned character though.
195 # The digit '8' is not an octal digit though.
|
| H A D | suff-rebuild.mk | 29 # message "don't know how to make suff-rebuild-example" though.
34 # this global list of targets though.
|
| H A D | sh-dots.mk | 11 # The ${.TARGET} correctly expands to the target name, even though the
47 # The "..." can appear more than once, even though that doesn't make sense.
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_inject_net_dgram.pod | 5 SSL_inject_net_dgram - inject a datagram as though received from the network
19 object. The payload is processed as though it was received from the network.
28 describing the remote and local UDP endpoint addresses for the packet. Though
30 OpenSSL, the packet will be processed as though the received datagram had the
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_inject_net_dgram.3 | 64 SSL_inject_net_dgram \- inject a datagram as though received from the network
78 object. The payload is processed as though it was received from the network.
87 describing the remote and local UDP endpoint addresses for the packet. Though
89 OpenSSL, the packet will be processed as though the received datagram had the
|
| /freebsd/contrib/netbsd-tests/usr.bin/grep/ |
| H A D | d_context_b.out | 1 Though mountains may topple and tilt.
4 Though you may be thrown over by Tabby and Rover,
|
| H A D | d_context_a.out | 2 Though mountains may topple and tilt.
5 Though you may be thrown over by Tabby and Rover,
|
| H A D | d_context_a.in | 4 Though mountains may topple and tilt.
7 Though you may be thrown over by Tabby and Rover,
|
| H A D | d_context_d.out | 4 d_context_a.in-Though mountains may topple and tilt.
6 d_context_a.in-Though you may be thrown over by Tabby and Rover,
|
| /freebsd/usr.sbin/cron/doc/ |
| H A D | INSTALL | 32 run if they don't exist. You do need to have a /var, though -- just "mkdir
47 to be /usr/bin/sendmail even though sendmail is installed in /usr/lib.
74 under most BSD's, `crontab' will still think of you as yourself even though
|
| H A D | THANKS | 10 answer even though it made me clean up some really awful things in the code.
16 ability with System V, though without at(1) capabilities, this cron isn't going
|
| /freebsd/sys/teken/libteken/ |
| H A D | teken.3 | 110 All callbacks must be provided, though unimplemented callbacks may some
127 Even though the cursor position is normally controlled by input of data
224 though it was only available and used inside the kernel.
|
| /freebsd/contrib/bc/manuals/bc/ |
| H A D | HN.1 | 155 Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
1297 string assigned to it, the statement acts as though it had received a
1341 as though the string had appeared as its own statement.
1347 The result is then printed as though \f[B]obase\f[R] is \f[B]256\f[R]
1820 as though it has the same number of bytes as the truncated absolute
1830 though it has \f[B]8\f[R] binary digits (\f[B]1\f[R] unsigned byte).
1839 though it has \f[B]16\f[R] binary digits (\f[B]2\f[R] unsigned bytes).
1848 though it has \f[B]32\f[R] binary digits (\f[B]4\f[R] unsigned bytes).
1857 though it has \f[B]64\f[R] binary digits (\f[B]8\f[R] unsigned bytes).
1866 though it has the minimum number of power of two unsigned bytes.
[all …]
|
| H A D | A.1 | 155 Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
1297 string assigned to it, the statement acts as though it had received a
1341 as though the string had appeared as its own statement.
1347 The result is then printed as though \f[B]obase\f[R] is \f[B]256\f[R]
1820 as though it has the same number of bytes as the truncated absolute
1830 though it has \f[B]8\f[R] binary digits (\f[B]1\f[R] unsigned byte).
1839 though it has \f[B]16\f[R] binary digits (\f[B]2\f[R] unsigned bytes).
1848 though it has \f[B]32\f[R] binary digits (\f[B]4\f[R] unsigned bytes).
1857 though it has \f[B]64\f[R] binary digits (\f[B]8\f[R] unsigned bytes).
1866 though it has the minimum number of power of two unsigned bytes.
[all …]
|
| H A D | H.1 | 155 Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
1297 string assigned to it, the statement acts as though it had received a
1341 as though the string had appeared as its own statement.
1347 The result is then printed as though \f[B]obase\f[R] is \f[B]256\f[R]
1820 as though it has the same number of bytes as the truncated absolute
1830 though it has \f[B]8\f[R] binary digits (\f[B]1\f[R] unsigned byte).
1839 though it has \f[B]16\f[R] binary digits (\f[B]2\f[R] unsigned bytes).
1848 though it has \f[B]32\f[R] binary digits (\f[B]4\f[R] unsigned bytes).
1857 though it has \f[B]64\f[R] binary digits (\f[B]8\f[R] unsigned bytes).
1866 though it has the minimum number of power of two unsigned bytes.
[all …]
|
| H A D | N.1 | 155 Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
1297 string assigned to it, the statement acts as though it had received a
1341 as though the string had appeared as its own statement.
1347 The result is then printed as though \f[B]obase\f[R] is \f[B]256\f[R]
1820 as though it has the same number of bytes as the truncated absolute
1830 though it has \f[B]8\f[R] binary digits (\f[B]1\f[R] unsigned byte).
1839 though it has \f[B]16\f[R] binary digits (\f[B]2\f[R] unsigned bytes).
1848 though it has \f[B]32\f[R] binary digits (\f[B]4\f[R] unsigned bytes).
1857 though it has \f[B]64\f[R] binary digits (\f[B]8\f[R] unsigned bytes).
1866 though it has the minimum number of power of two unsigned bytes.
[all …]
|