Lines Matching +full:use +full:- +full:external +full:- +full:names
25 This document relates to PCRE releases that use the original API,
26 with library names libpcre, libpcre16, and libpcre32. January 2015 saw the
28 10.00 and library names libpcre2-8, libpcre2-16, and libpcre2-32. The old
30 there will be no new development. New projects are advised to use the new PCRE2
44 libraries: the original, which supports 8-bit character strings (including
45 UTF-8 strings), and a second library that supports 16-bit character strings
46 (including UTF-16 strings). The build process allows either one or both to be
52 library that supports 32-bit character strings (including UTF-32 strings). The
53 build process allows any combination of the 8-, 16- and 32-bit libraries. The
57 The three libraries contain identical sets of functions, except that the names
58 in the 16-bit library start with <b>pcre16_</b> instead of <b>pcre_</b>, and the
59 names in the 32-bit library start with <b>pcre32_</b> instead of <b>pcre_</b>. To
60 avoid over-complication and reduce the documentation maintenance load, most of
61 the documentation describes the 8-bit library, with the differences for the
62 16-bit and 32-bit libraries described separately in the
67 should be read as meaning "<i>pcre_xxx</i> when using the 8-bit library,
68 <i>pcre16_xxx</i> when using the 16-bit library, or <i>pcre32_xxx</i> when using
69 the 32-bit library".
73 including support for UTF-8/16/32 encoded strings and Unicode general category
74 properties. However, UTF-8/16/32 and Unicode support has to be explicitly
79 In addition to the Perl-compatible matching function, PCRE contains an
89 have provided a comprehensive C++ wrapper for the 8-bit library. This is now
117 <a href="NON-AUTOTOOLS-BUILD.txt"><b>NON-AUTOTOOLS_BUILD</b></a>
122 tables that are used by more than one of the exported external functions, but
123 which are not intended for use by external callers. Their names all begin with
125 clashes. In some environments, it is possible to control which external symbols
131 If you are using PCRE in a non-UTF application that permits users to supply
134 was built with UTF support. For example, an 8-bit pattern that begins with
135 "(*UTF8)" or "(*UTF)" turns on UTF-8 mode, which interprets patterns and
136 subjects as strings of UTF-8 characters instead of individual 8-bit characters.
138 checked for UTF-8 validity. If the data string is very long, such a check might
139 use sufficiently many resources as to cause your application to lose
143 One way of guarding against this possibility is to use the
147 UTF-setting sequence.
151 can take time. If the same data string is to be matched many times, you can use
175 pcre-config show PCRE installation configuration information
176 pcre16 details of the 16-bit library
177 pcre32 details of the 32-bit library
182 pcrecpp details of the C++ wrapper for the 8-bit library
184 pcregrep description of the <b>pcregrep</b> command (8-bit only)
185 pcrejit discussion of the just-in-time optimization support
191 pcreposix the POSIX-compatible C API for the 8-bit library
192 pcreprecompile details of saving and re-using precompiled patterns
197 pcreunicode discussion of Unicode and UTF-8/16/32 support
213 taken it away. If you want to email me, use my two initials, followed by the
220 Copyright © 1997-2015 University of Cambridge.