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
65 standard POSIX names such <b>regcomp()</b> into <b>pcre2_regcomp()</b> etc. This
66 means that a program can use the usual POSIX names without running the risk of
67 accidentally linking with POSIX functions from a different library.
70 On Unix-like systems the PCRE2 POSIX library is called <b>libpcre2-posix</b>, so
71 can be accessed by adding <b>-lpcre2-posix</b> to the command for linking an
72 application. Because the POSIX functions call the native ones, it is also
83 10.33 to 10.36 of the library contained functions with the POSIX names
86 earlier versions of PCRE2, which had only POSIX names. However, this has proved
88 which use PCRE2's POSIX interface while others use the real POSIX functions.
89 For this reason, the POSIX names have been removed since release 10.37.
92 Calling the header file <b>pcre2posix.h</b> avoids any conflict with other POSIX
99 <br><a name="SEC3" href="#TOC1">USING THE POSIX FUNCTIONS</a><br>
101 Note that these functions are just POSIX-style wrappers for PCRE2's native API.
102 They do not give POSIX regular expression behaviour, and they are not
103 thread-safe or even POSIX compatible.
106 Those POSIX option bits that can reasonably be mapped to PCRE2 native options
109 POSIX interface often use it, this makes it easier to slot in PCRE2 as a
110 replacement library. Other POSIX options are not even defined.
113 There are also some options that are not defined by POSIX. These have been
115 features via the POSIX calling interface or to add BSD or GNU functionality.
118 When PCRE2 is called via these functions, it is only the API that is POSIX-like
121 described below. "POSIX-like in style" means that the API approximates to the
122 POSIX definition; it is not fully POSIX-compatible, and in multi-unit encoding
127 above, the standard POSIX names (without the <b>pcre2_</b> prefix) may also be
139 that provide POSIX-style matching.
149 POSIX standard.
160 defined POSIX behaviour for REG_NEWLINE (see the following section).
168 REG_UTF. Note that REG_NOSPEC is not part of the POSIX standard.
185 ignored. This is a GNU extension to the POSIX standard and should be used with
193 that REG_UCP is not part of the POSIX standard.
199 POSIX standard.
206 is not part of the POSIX standard.
212 Perl way, not the POSIX way. Note that setting PCRE2_MULTILINE has only
232 This area is not simple, because POSIX and Perl take different views of things.
233 It is not possible to get PCRE2 to obey POSIX semantics, but then PCRE2 was
234 never intended to be a POSIX engine. The following table lists the different
245 This is the equivalent table for a POSIX-compatible pattern matcher:
255 This behaviour is not what happens when PCRE2 is called via its POSIX
261 Default POSIX newline handling can be obtained by setting PCRE2_DOTALL and
264 the POSIX API, passing REG_NEWLINE to PCRE2's <b>pcre2_regcomp()</b> function
283 function. Note that REG_NOTEMPTY is not part of the POSIX standard. However,
284 setting this option can give more POSIX-like behaviour in some situations.
308 1003.2 (POSIX.2), and should be used with caution in software intended to be
338 similarly named types from other libraries that provide POSIX-style matching.