Lines Matching full:posix

25 This set of functions provides a POSIX-style API for the PCRE2 regular
26 expression 8-bit library. There are no POSIX-style wrappers for PCRE2's 16-bit
42 standard POSIX names such \fBregcomp()\fP into \fBpcre2_regcomp()\fP etc. This
43 means that a program can use the usual POSIX names without running the risk of
44 accidentally linking with POSIX functions from a different library.
46 On Unix-like systems the PCRE2 POSIX library is called \fBlibpcre2-posix\fP, so
47 can be accessed by adding \fB-lpcre2-posix\fP to the command for linking an
48 application. Because the POSIX functions call the native ones, it is also
57 10.33 to 10.36 of the library contained functions with the POSIX names
60 earlier versions of PCRE2, which had only POSIX names. However, this has proved
62 which use PCRE2's POSIX interface while others use the real POSIX functions.
63 For this reason, the POSIX names have been removed since release 10.37.
65 Calling the header file \fBpcre2posix.h\fP avoids any conflict with other POSIX
73 .SH "USING THE POSIX FUNCTIONS"
76 Note that these functions are just POSIX-style wrappers for PCRE2's native API.
77 They do not give POSIX regular expression behaviour, and they are not
78 thread-safe or even POSIX compatible.
80 Those POSIX option bits that can reasonably be mapped to PCRE2 native options
83 POSIX interface often use it, this makes it easier to slot in PCRE2 as a
84 replacement library. Other POSIX options are not even defined.
86 There are also some options that are not defined by POSIX. These have been
88 features via the POSIX calling interface or to add BSD or GNU functionality.
90 When PCRE2 is called via these functions, it is only the API that is POSIX-like
93 described below. "POSIX-like in style" means that the API approximates to the
94 POSIX definition; it is not fully POSIX-compatible, and in multi-unit encoding
98 above, the standard POSIX names (without the \fBpcre2_\fP prefix) may also be
112 that provide POSIX-style matching.
121 POSIX standard.
132 defined POSIX behaviour for REG_NEWLINE (see the following section).
140 REG_UTF. Note that REG_NOSPEC is not part of the POSIX standard.
157 ignored. This is a GNU extension to the POSIX standard and should be used with
165 that REG_UCP is not part of the POSIX standard.
171 POSIX standard.
178 is not part of the POSIX standard.
183 Perl way, not the POSIX way. Note that setting PCRE2_MULTILINE has only
203 This area is not simple, because POSIX and Perl take different views of things.
204 It is not possible to get PCRE2 to obey POSIX semantics, but then PCRE2 was
205 never intended to be a POSIX engine. The following table lists the different
216 This is the equivalent table for a POSIX-compatible pattern matcher:
226 This behaviour is not what happens when PCRE2 is called via its POSIX
231 Default POSIX newline handling can be obtained by setting PCRE2_DOTALL and
234 the POSIX API, passing REG_NEWLINE to PCRE2's \fBpcre2_regcomp()\fP function
255 function. Note that REG_NOTEMPTY is not part of the POSIX standard. However,
256 setting this option can give more POSIX-like behaviour in some situations.
278 1003.2 (POSIX.2), and should be used with caution in software intended to be
304 similarly named types from other libraries that provide POSIX-style matching.