Lines Matching +full:use +full:- +full:external +full:- +full:names
3 PCRE - Perl-compatible regular expressions (original API)
7 This document relates to PCRE releases that use the original API,
8 with library names libpcre, libpcre16, and libpcre32. January 2015 saw the
10 10.00 and library names libpcre2-8, libpcre2-16, and libpcre2-32. The old
12 there will be no new development. New projects are advised to use the new PCRE2
27 libraries: the original, which supports 8-bit character strings (including
28 UTF-8 strings), and a second library that supports 16-bit character strings
29 (including UTF-16 strings). The build process allows either one or both to be
34 library that supports 32-bit character strings (including UTF-32 strings). The
35 build process allows any combination of the 8-, 16- and 32-bit libraries. The
38 The three libraries contain identical sets of functions, except that the names
39 in the 16-bit library start with \fBpcre16_\fP instead of \fBpcre_\fP, and the
40 names in the 32-bit library start with \fBpcre32_\fP instead of \fBpcre_\fP. To
41 avoid over-complication and reduce the documentation maintenance load, most of
42 the documentation describes the 8-bit library, with the differences for the
43 16-bit and 32-bit libraries described separately in the
51 should be read as meaning "\fIpcre_xxx\fP when using the 8-bit library,
52 \fIpcre16_xxx\fP when using the 16-bit library, or \fIpcre32_xxx\fP when using
53 the 32-bit library".
56 including support for UTF-8/16/32 encoded strings and Unicode general category
57 properties. However, UTF-8/16/32 and Unicode support has to be explicitly
61 In addition to the Perl-compatible matching function, PCRE contains an
72 have provided a comprehensive C++ wrapper for the 8-bit library. This is now
117 .\" HTML <a href="NON-AUTOTOOLS-BUILD.txt">
119 \fBNON-AUTOTOOLS_BUILD\fP
124 tables that are used by more than one of the exported external functions, but
125 which are not intended for use by external callers. Their names all begin with
127 clashes. In some environments, it is possible to control which external symbols
135 If you are using PCRE in a non-UTF application that permits users to supply
138 was built with UTF support. For example, an 8-bit pattern that begins with
139 "(*UTF8)" or "(*UTF)" turns on UTF-8 mode, which interprets patterns and
140 subjects as strings of UTF-8 characters instead of individual 8-bit characters.
142 checked for UTF-8 validity. If the data string is very long, such a check might
146 One way of guarding against this possibility is to use the
150 UTF-setting sequence.
153 can take time. If the same data string is to be matched many times, you can use
180 pcre-config show PCRE installation configuration information
181 pcre16 details of the 16-bit library
182 pcre32 details of the 32-bit library
187 pcrecpp details of the C++ wrapper for the 8-bit library
189 pcregrep description of the \fBpcregrep\fP command (8-bit only)
190 pcrejit discussion of the just-in-time optimization support
198 pcreposix the POSIX-compatible C API for the 8-bit library
199 pcreprecompile details of saving and re-using precompiled patterns
204 pcreunicode discussion of Unicode and UTF-8/16/32 support
220 taken it away. If you want to email me, use my two initials, followed by the
229 Copyright (c) 1997-2015 University of Cambridge.