| /openbsd-src/regress/lib/libcrypto/x509/bettertls/scripts/ |
| H A D | expects.json | 1 …implementations will fail to validate the certificate."]},"dns":{"expect":"ERROR","descriptions":[…
|
| /openbsd-src/usr.bin/sed/ |
| H A D | POSIX | 19 1. 32V and BSD derived implementations of sed strip the text
76 (e.g. /foo/!!!p). Historic implementations allow any number of
103 11. Historical implementations do not output the change text of a c
121 Historic implementations, and this implementation, do not output
126 13. Historical implementations allow an output suppressing #n at the
135 command. Historic sed implementations behave differently for "ls |
150 As historic sed implementations always discarded the backslash,
155 is not true for historic implementations or this implementation
160 Historic implementations of sed assigned different locations to
178 22. Historic implementations of sed ignore the RE delimiter characters
[all …]
|
| /openbsd-src/gnu/llvm/llvm/docs/ |
| H A D | AliasAnalysis.rst | 23 primary interface used by clients and implementations of alias analyses in the
25 analysis information and the implementations providing it, and is designed to
26 support a wide range of implementations and clients (but currently all clients
28 information, this class exposes Mod/Ref information from those implementations
40 class defines the interface that the various alias analysis implementations
162 analysis implementations and can be put to good use by various clients.
209 There are already several implementations that you can use for examples, and the
211 look at the `various alias analysis implementations`_ included with LLVM.
323 communicate program changes from the clients to the analysis implementations.
324 Various alias analysis implementations should use these methods to ensure that
[all …]
|
| /openbsd-src/gnu/gcc/libstdc++-v3/docs/html/ext/pb_ds/ |
| H A D | pq_design.html | 65 explained further in <a href="#pq_imp">Implementations</a>.</p>
83 implementations which are described in <a href=
84 "#pq_imp">Implementations</a>; <a href="#pq_traits">Traits</a>
86 different implementations.</p>
177 <h2><a name="pq_imp" id="pq_imp">Implementations</a></h2>
179 <p>There are three main implementations of priority queues: the
206 <p>Most implementations do
231 <tt>std::string</tt>). This implementations is relatively
243 Data-Structures</a> B. This implementations too is relatively
255 Data-Structures</a> B. This implementations is more
[all …]
|
| /openbsd-src/share/man/man4/man4.i386/ |
| H A D | pcibios.4 | 63 Some BIOS implementations don't allocate I/O space and
77 Although many BIOS implementations leave CardBus bridges'
87 But some BIOS implementations don't assign a bus number
89 And many BIOS implementations don't assign a bus number for CardBuses.
114 Some BIOS implementations don't assign an interrupt for
140 Some buggy BIOS implementations provide inconsistent information between
|
| /openbsd-src/lib/libcurses/ |
| H A D | curs_getstr.3 | 185 SVr3 and early SVr4 curses implementations did not reject function keys;
194 string by those implementations was predictable but not useful
206 As of 2018, some implementations count it, some do not:
222 however most implementations
266 Other implementations differ in their treatment of special characters:
269 other implementations do not modify the \fIraw\fP mode,
283 where other implementations allow one to enter those characters in the buffer.
|
| H A D | curs_getyx.3 | 86 many implementations provide members of the WINDOW structure
89 since some implementations make WINDOW opaque (do not allow
94 different implementations.
97 other implementations.
|
| H A D | curs_clear.3 | 114 Some historic curses implementations had, as an undocumented feature, the
123 That fact is not documented in other implementations,
124 and may not be true of implementations
128 most implementations clear the screen after \fBwclear\fP
|
| H A D | default_colors.3 | 60 For example, there are several implementations of the \fBls\fP program
91 For other curses implementations, color
95 Other curses implementations do not allow an application to modify color pair 0.
139 Version 7, BSD or System V implementations.
|
| H A D | curs_util.3 | 129 which some implementations return rather than null.
309 They were not supported on Version 7, BSD or System V implementations.
327 Most implementations simply dump the binary \fBWINDOW\fP structure to the file.
334 The implementations which use binary dumps use block-I/O
370 Other implementations have different conventions.
395 Other implementations may not do that.
402 is not provided by other implementations of curses.
|
| H A D | curs_addch.3 | 213 Some implementations are problematic:
215 Some implementations define the ACS symbols to a constant
231 and the various implementations use \fBi\fP (lowercase).
280 The other implementations do not do this;
296 For portability to other implementations,
310 This is true of other implementations, but is not documented.
|
| H A D | curs_legacy.3 | 100 These functions were supported on Version 7, BSD or System V implementations.
101 None of those implementations checked the window parameter.
104 for compatibility with those implementations
|
| H A D | curs_add_wch.3 | 255 A few implementations are problematic:
266 SVr4 curses implementations defined their line-drawing symbols in
269 which are not in the SVr4 implementations.
276 Existing implementations of Unix curses (AIX, HPUX, Solaris)
278 As a result, those implementations can only use single-byte line-drawing
|
| H A D | term_variables.3 | 180 Other implementations may have comparable variables.
181 Some implementations provide the variables in their libraries,
184 All implementations which provide terminfo interfaces add definitions
|
| /openbsd-src/gnu/llvm/compiler-rt/include/xray/ |
| H A D | xray_log_interface.h | 68 /// // after we've finalized the log. Some implementations may not actually
77 /// // relying on the implementations' flushing semantics (if the
89 /// implementation first. Some implementations might stay in an "off" state when
107 /// Some implementations support multi-stage init (or asynchronous init), and
110 /// implementations to support concurrent threads attempting to initialize,
120 /// Some implementations might support multi-stage finalization (or
123 /// This allows implementations to support concurrent threads attempting to
129 /// semantics of a finalized implementation is. Some implementations might
180 /// The 0-argument function call handler. XRay logging implementations MUST
203 /// existing implementations*. It does NOT patch the instrumentation points.
[all …]
|
| /openbsd-src/gnu/usr.bin/perl/cpan/Digest/lib/Digest/ |
| H A D | base.pm | 88 The C<Digest::base> class provide implementations of the methods
92 Digest implementations might want to inherit from this class to get
93 this implementations of the alternative I<add> and I<digest> methods.
|
| /openbsd-src/usr.bin/gprof/PSD.doc/ |
| H A D | intro.me | 54 of abstraction implementations
62 help the user evaluate alternative implementations
74 various implementations.
|
| /openbsd-src/lib/libssl/man/ |
| H A D | SSL_read_early_data.3 | 89 If these functions are used, other TLS implementations
145 can occur with other implementations, but not with LibreSSL.
151 With other implementations, it might also return
|
| /openbsd-src/gnu/llvm/llvm/lib/Target/WebAssembly/ |
| H A D | WebAssemblyTargetTransformInfo.h | 15 /// implementations handle the rest.
44 /// \name Scalar TTI Implementations
57 /// \name Vector TTI Implementations
|
| /openbsd-src/lib/libc/sys/ |
| H A D | mprotect.2 | 77 Not all implementations will guarantee protection on a page basis;
79 Nor will all implementations guarantee to give exactly the requested
145 although other implementations may.
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/doc/ |
| H A D | standards.texi | 112 required for freestanding implementations. The standard also defines
114 required of all implementations and which may not have library
115 facilities beyond those required of freestanding implementations,
140 implementations, nor yet all the facilities required by C99 of
141 freestanding implementations; to use the facilities of a hosted
|
| /openbsd-src/gnu/gcc/gcc/doc/ |
| H A D | standards.texi | 112 required for freestanding implementations. The standard also defines
114 required of all implementations and which may not have library
115 facilities beyond those required of freestanding implementations,
140 implementations, nor yet all the facilities required by C99 of
141 freestanding implementations; to use the facilities of a hosted
|
| /openbsd-src/lib/libcrypto/man/ |
| H A D | DH_set_method.3 | 92 By selecting another method, alternative implementations
119 implementations,
150 /* compute r = a ^ p mod m (May be NULL for some implementations) */
|
| /openbsd-src/gnu/usr.bin/perl/cpan/CPAN-Meta-YAML/t/tml-spec/ |
| H A D | unicode.tml | 30 # \z is the other YAML "null" encoding. Most implementations (including
281 # Some implementations think N means false. This should not be the case in a
296 # Some implementations think Y means true. This should not be the case in a
355 # Some implementations think n means false. This should not be the case in a
363 # Some implementations think y means true. This should not be the case in a
|
| /openbsd-src/gnu/llvm/llvm/lib/CodeGen/LiveDebugValues/ |
| H A D | LiveDebugValues.h | 19 // LiveDebugValues implementations.
35 // Factory functions for LiveDebugValues implementations.
|