Lines Matching full:posix

18 <li><a name="TOC3" href="#SEC3">USING THE POSIX FUNCTIONS</a>
48 This set of functions provides a POSIX-style API for the PCRE2 regular
49 expression 8-bit library. There are no POSIX-style wrappers for PCRE2's 16-bit
60 standard POSIX names such <b>regcomp()</b> into <b>pcre2_regcomp()</b> etc. This
61 means that a program can use the usual POSIX names without running the risk of
62 accidentally linking with POSIX functions from a different library.
65 On Unix-like systems the PCRE2 POSIX library is called <b>libpcre2-posix</b>, so
66 can be accessed by adding <b>-lpcre2-posix</b> to the command for linking an
67 application. Because the POSIX functions call the native ones, it is also
72 10.33 to 10.36 of the library contained functions with the POSIX names
75 earlier versions of PCRE2, which had only POSIX names. However, this has proved
77 which use PCRE2's POSIX interface while others use the real POSIX functions.
78 For this reason, the POSIX names have been removed since release 10.37.
81 Calling the header file <b>pcre2posix.h</b> avoids any conflict with other POSIX
88 <br><a name="SEC3" href="#TOC1">USING THE POSIX FUNCTIONS</a><br>
90 Those POSIX option bits that can reasonably be mapped to PCRE2 native options
93 POSIX interface often use it, this makes it easier to slot in PCRE2 as a
94 replacement library. Other POSIX options are not even defined.
97 There are also some options that are not defined by POSIX. These have been
99 features via the POSIX calling interface or to add BSD or GNU functionality.
102 When PCRE2 is called via these functions, it is only the API that is POSIX-like
105 described below. "POSIX-like in style" means that the API approximates to the
106 POSIX definition; it is not fully POSIX-compatible, and in multi-unit encoding
111 above, the standard POSIX names (without the <b>pcre2_</b> prefix) may also be
131 POSIX standard.
142 defined POSIX behaviour for REG_NEWLINE (see the following section).
150 REG_UTF. Note that REG_NOSPEC is not part of the POSIX standard.
167 ignored. This is a GNU extension to the POSIX standard and should be used with
175 that REG_UCP is not part of the POSIX standard.
181 POSIX standard.
188 is not part of the POSIX standard.
194 Perl way, not the POSIX way. Note that setting PCRE2_MULTILINE has only
214 This area is not simple, because POSIX and Perl take different views of things.
215 It is not possible to get PCRE2 to obey POSIX semantics, but then PCRE2 was
216 never intended to be a POSIX engine. The following table lists the different
227 This is the equivalent table for a POSIX-compatible pattern matcher:
237 This behaviour is not what happens when PCRE2 is called via its POSIX
243 Default POSIX newline handling can be obtained by setting PCRE2_DOTALL and
246 the POSIX API, passing REG_NEWLINE to PCRE2's <b>pcre2_regcomp()</b> function
265 function. Note that REG_NOTEMPTY is not part of the POSIX standard. However,
266 setting this option can give more POSIX-like behaviour in some situations.
290 1003.2 (POSIX.2), and should be used with caution in software intended to be