doc/html/pcre.html

<html>
<head>
<title>pcre specification</title>
</head>
<body bgcolor="#FFFFFF" text="#00005A" link="#0066FF" alink="#3399FF" vlink="#2222BB">
<h1>pcre man page</h1>
<p>
Return to the <a href="index.html">PCRE index page</a>.
</p>
<p>
This page is part of the PCRE HTML documentation. It was generated automatically
from the original man page. If there is any nonsense in it, please consult the
man page, in case the conversion went wrong.
<br>
<ul>
<li><a name="TOC1" href="#SEC1">INTRODUCTION</a>
<li><a name="TOC2" href="#SEC2">USER DOCUMENTATION</a>
<li><a name="TOC3" href="#SEC3">LIMITATIONS</a>
<li><a name="TOC4" href="#SEC4">UTF-8 AND UNICODE PROPERTY SUPPORT</a>
<li><a name="TOC5" href="#SEC5">AUTHOR</a>
<li><a name="TOC6" href="#SEC6">REVISION</a>
</ul>
<br><a name="SEC1" href="#TOC1">INTRODUCTION</a><br>
<P>
The PCRE library is a set of functions that implement regular expression
pattern matching using the same syntax and semantics as Perl, with just a few
differences. (Certain features that appeared in Python and PCRE before they
appeared in Perl are also available using the Python syntax.)
</P>
<P>
The current implementation of PCRE (release 7.x) corresponds approximately with
Perl 5.10, including support for UTF-8 encoded strings and Unicode general
category properties. However, UTF-8 and Unicode support has to be explicitly
enabled; it is not the default. The Unicode tables correspond to Unicode
release 5.0.0.
</P>
<P>
In addition to the Perl-compatible matching function, PCRE contains an
alternative matching function that matches the same compiled patterns in a
different way. In certain circumstances, the alternative function has some
advantages. For a discussion of the two matching algorithms, see the
<a href="pcrematching.html"><b>pcrematching</b></a>
page.
</P>
<P>
PCRE is written in C and released as a C library. A number of people have
written wrappers and interfaces of various kinds. In particular, Google Inc.
have provided a comprehensive C++ wrapper. This is now included as part of the
PCRE distribution. The
<a href="pcrecpp.html"><b>pcrecpp</b></a>
page has details of this interface. Other people's contributions can be found
in the <i>Contrib</i> directory at the primary FTP site, which is:
<a href="ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre">ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre</a>
</P>
<P>
Details of exactly which Perl regular expression features are and are not
supported by PCRE are given in separate documents. See the
<a href="pcrepattern.html"><b>pcrepattern</b></a>
and
<a href="pcrecompat.html"><b>pcrecompat</b></a>
pages. There is a syntax summary in the
<a href="pcresyntax.html"><b>pcresyntax</b></a>
page.
</P>
<P>
Some features of PCRE can be included, excluded, or changed when the library is
built. The
<a href="pcre_config.html"><b>pcre_config()</b></a>
function makes it possible for a client to discover which features are
available. The features themselves are described in the
<a href="pcrebuild.html"><b>pcrebuild</b></a>
page. Documentation about building PCRE for various operating systems can be
found in the <b>README</b> file in the source distribution.
</P>
<P>
The library contains a number of undocumented internal functions and data
tables that are used by more than one of the exported external functions, but
which are not intended for use by external callers. Their names all begin with
"_pcre_", which hopefully will not provoke any name clashes. In some
environments, it is possible to control which external symbols are exported
when a shared library is built, and in these cases the undocumented symbols are
not exported.
</P>
<br><a name="SEC2" href="#TOC1">USER DOCUMENTATION</a><br>
<P>
The user documentation for PCRE comprises a number of different sections. In
the "man" format, each of these is a separate "man page". In the HTML format,
each is a separate page, linked from the index page. In the plain text format,
all the sections are concatenated, for ease of searching. The sections are as
follows:
<pre>
  pcre              this document
  pcre-config       show PCRE installation configuration information
  pcreapi           details of PCRE's native C API
  pcrebuild         options for building PCRE
  pcrecallout       details of the callout feature
  pcrecompat        discussion of Perl compatibility
  pcrecpp           details of the C++ wrapper
  pcregrep          description of the <b>pcregrep</b> command
  pcrematching      discussion of the two matching algorithms
  pcrepartial       details of the partial matching facility
  pcrepattern       syntax and semantics of supported regular expressions
  pcresyntax        quick syntax reference
  pcreperform       discussion of performance issues
  pcreposix         the POSIX-compatible C API
  pcreprecompile    details of saving and re-using precompiled patterns
  pcresample        discussion of the sample program
  pcrestack         discussion of stack usage
  pcretest          description of the <b>pcretest</b> testing command
</pre>
In addition, in the "man" and HTML formats, there is a short page for each
C library function, listing its arguments and results.
</P>
<br><a name="SEC3" href="#TOC1">LIMITATIONS</a><br>
<P>
There are some size limitations in PCRE but it is hoped that they will never in
practice be relevant.
</P>
<P>
The maximum length of a compiled pattern is 65539 (sic) bytes if PCRE is
compiled with the default internal linkage size of 2. If you want to process
regular expressions that are truly enormous, you can compile PCRE with an
internal linkage size of 3 or 4 (see the <b>README</b> file in the source
distribution and the
<a href="pcrebuild.html"><b>pcrebuild</b></a>
documentation for details). In these cases the limit is substantially larger.
However, the speed of execution is slower.
</P>
<P>
All values in repeating quantifiers must be less than 65536.
</P>
<P>
There is no limit to the number of parenthesized subpatterns, but there can be
no more than 65535 capturing subpatterns.
</P>
<P>
The maximum length of name for a named subpattern is 32 characters, and the
maximum number of named subpatterns is 10000.
</P>
<P>
The maximum length of a subject string is the largest positive number that an
integer variable can hold. However, when using the traditional matching
function, PCRE uses recursion to handle subpatterns and indefinite repetition.
This means that the available stack space may limit the size of a subject
string that can be processed by certain patterns. For a discussion of stack
issues, see the
<a href="pcrestack.html"><b>pcrestack</b></a>
documentation.
<a name="utf8support"></a></P>
<br><a name="SEC4" href="#TOC1">UTF-8 AND UNICODE PROPERTY SUPPORT</a><br>
<P>
From release 3.3, PCRE has had some support for character strings encoded in
the UTF-8 format. For release 4.0 this was greatly extended to cover most
common requirements, and in release 5.0 additional support for Unicode general
category properties was added.
</P>
<P>
In order process UTF-8 strings, you must build PCRE to include UTF-8 support in
the code, and, in addition, you must call
<a href="pcre_compile.html"><b>pcre_compile()</b></a>
with the PCRE_UTF8 option flag. When you do this, both the pattern and any
subject strings that are matched against it are treated as UTF-8 strings
instead of just strings of bytes.
</P>
<P>
If you compile PCRE with UTF-8 support, but do not use it at run time, the
library will be a bit bigger, but the additional run time overhead is limited
to testing the PCRE_UTF8 flag occasionally, so should not be very big.
</P>
<P>
If PCRE is built with Unicode character property support (which implies UTF-8
support), the escape sequences \p{..}, \P{..}, and \X are supported.
The available properties that can be tested are limited to the general
category properties such as Lu for an upper case letter or Nd for a decimal
number, the Unicode script names such as Arabic or Han, and the derived
properties Any and L&. A full list is given in the
<a href="pcrepattern.html"><b>pcrepattern</b></a>
documentation. Only the short names for properties are supported. For example,
\p{L} matches a letter. Its Perl synonym, \p{Letter}, is not supported.
Furthermore, in Perl, many properties may optionally be prefixed by "Is", for
compatibility with Perl 5.6. PCRE does not support this.
</P>
<P>
The following comments apply when PCRE is running in UTF-8 mode:
</P>
<P>
1. When you set the PCRE_UTF8 flag, the strings passed as patterns and subjects
are checked for validity on entry to the relevant functions. If an invalid
UTF-8 string is passed, an error return is given. In some situations, you may
already know that your strings are valid, and therefore want to skip these
checks in order to improve performance. If you set the PCRE_NO_UTF8_CHECK flag
at compile time or at run time, PCRE assumes that the pattern or subject it
is given (respectively) contains only valid UTF-8 codes. In this case, it does
not diagnose an invalid UTF-8 string. If you pass an invalid UTF-8 string to
PCRE when PCRE_NO_UTF8_CHECK is set, the results are undefined. Your program
may crash.
</P>
<P>
2. An unbraced hexadecimal escape sequence (such as \xb3) matches a two-byte
UTF-8 character if the value is greater than 127.
</P>
<P>
3. Octal numbers up to \777 are recognized, and match two-byte UTF-8
characters for values greater than \177.
</P>
<P>
4. Repeat quantifiers apply to complete UTF-8 characters, not to individual
bytes, for example: \x{100}{3}.
</P>
<P>
5. The dot metacharacter matches one UTF-8 character instead of a single byte.
</P>
<P>
6. The escape sequence \C can be used to match a single byte in UTF-8 mode,
but its use can lead to some strange effects. This facility is not available in
the alternative matching function, <b>pcre_dfa_exec()</b>.
</P>
<P>
7. The character escapes \b, \B, \d, \D, \s, \S, \w, and \W correctly
test characters of any code value, but the characters that PCRE recognizes as
digits, spaces, or word characters remain the same set as before, all with
values less than 256. This remains true even when PCRE includes Unicode
property support, because to do otherwise would slow down PCRE in many common
cases. If you really want to test for a wider sense of, say, "digit", you
must use Unicode property tests such as \p{Nd}.
</P>
<P>
8. Similarly, characters that match the POSIX named character classes are all
low-valued characters.
</P>
<P>
9. However, the Perl 5.10 horizontal and vertical whitespace matching escapes
(\h, \H, \v, and \V) do match all the appropriate Unicode characters.
</P>
<P>
10. Case-insensitive matching applies only to characters whose values are less
than 128, unless PCRE is built with Unicode property support. Even when Unicode
property support is available, PCRE still uses its own character tables when
checking the case of low-valued characters, so as not to degrade performance.
The Unicode property information is used only for characters with higher
values. Even when Unicode property support is available, PCRE supports
case-insensitive matching only when there is a one-to-one mapping between a
letter's cases. There are a small number of many-to-one mappings in Unicode;
these are not supported by PCRE.
</P>
<br><a name="SEC5" href="#TOC1">AUTHOR</a><br>
<P>
Philip Hazel
<br>
University Computing Service
<br>
Cambridge CB2 3QH, England.
<br>
</P>
<P>
Putting an actual email address here seems to have been a spam magnet, so I've
taken it away. If you want to email me, use my two initials, followed by the
two digits 10, at the domain cam.ac.uk.
</P>
<br><a name="SEC6" href="#TOC1">REVISION</a><br>
<P>
Last updated: 06 August 2007
<br>
Copyright &copy; 1997-2007 University of Cambridge.
<br>
<p>
Return to the <a href="index.html">PCRE index page</a>.
</p>
1	nigel	63	<html>
2			<head>
3			<title>pcre specification</title>
4			</head>
5			<body bgcolor="#FFFFFF" text="#00005A" link="#0066FF" alink="#3399FF" vlink="#2222BB">
6	nigel	75	<h1>pcre man page</h1>
7			<p>
8			Return to the <a href="index.html">PCRE index page</a>.
9			</p>
10	ph10	111	<p>
11	nigel	75	This page is part of the PCRE HTML documentation. It was generated automatically
12			from the original man page. If there is any nonsense in it, please consult the
13			man page, in case the conversion went wrong.
14	ph10	111	<br>
15	nigel	63	<ul>
16	nigel	75	<li><a name="TOC1" href="#SEC1">INTRODUCTION</a>
17	nigel	63	<li><a name="TOC2" href="#SEC2">USER DOCUMENTATION</a>
18			<li><a name="TOC3" href="#SEC3">LIMITATIONS</a>
19	nigel	75	<li><a name="TOC4" href="#SEC4">UTF-8 AND UNICODE PROPERTY SUPPORT</a>
20	nigel	63	<li><a name="TOC5" href="#SEC5">AUTHOR</a>
21	ph10	99	<li><a name="TOC6" href="#SEC6">REVISION</a>
22	nigel	63	</ul>
23	nigel	75	<br><a name="SEC1" href="#TOC1">INTRODUCTION</a><br>
24	nigel	63	<P>
25			The PCRE library is a set of functions that implement regular expression
26			pattern matching using the same syntax and semantics as Perl, with just a few
27	nigel	93	differences. (Certain features that appeared in Python and PCRE before they
28			appeared in Perl are also available using the Python syntax.)
29	nigel	63	</P>
30			<P>
31	nigel	93	The current implementation of PCRE (release 7.x) corresponds approximately with
32			Perl 5.10, including support for UTF-8 encoded strings and Unicode general
33			category properties. However, UTF-8 and Unicode support has to be explicitly
34			enabled; it is not the default. The Unicode tables correspond to Unicode
35			release 5.0.0.
36			</P>
37			<P>
38			In addition to the Perl-compatible matching function, PCRE contains an
39	nigel	77	alternative matching function that matches the same compiled patterns in a
40			different way. In certain circumstances, the alternative function has some
41			advantages. For a discussion of the two matching algorithms, see the
42			<a href="pcrematching.html"><b>pcrematching</b></a>
43			page.
44			</P>
45			<P>
46	nigel	75	PCRE is written in C and released as a C library. A number of people have
47	nigel	77	written wrappers and interfaces of various kinds. In particular, Google Inc.
48			have provided a comprehensive C++ wrapper. This is now included as part of the
49			PCRE distribution. The
50			<a href="pcrecpp.html"><b>pcrecpp</b></a>
51			page has details of this interface. Other people's contributions can be found
52			in the <i>Contrib</i> directory at the primary FTP site, which is:
53	nigel	75	<a href="ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre">ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre</a>
54	nigel	63	</P>
55			<P>
56			Details of exactly which Perl regular expression features are and are not
57			supported by PCRE are given in separate documents. See the
58			<a href="pcrepattern.html"><b>pcrepattern</b></a>
59			and
60			<a href="pcrecompat.html"><b>pcrecompat</b></a>
61	ph10	208	pages. There is a syntax summary in the
62			<a href="pcresyntax.html"><b>pcresyntax</b></a>
63			page.
64	nigel	63	</P>
65			<P>
66			Some features of PCRE can be included, excluded, or changed when the library is
67			built. The
68			<a href="pcre_config.html"><b>pcre_config()</b></a>
69			function makes it possible for a client to discover which features are
70	nigel	75	available. The features themselves are described in the
71			<a href="pcrebuild.html"><b>pcrebuild</b></a>
72			page. Documentation about building PCRE for various operating systems can be
73			found in the <b>README</b> file in the source distribution.
74	nigel	63	</P>
75	nigel	77	<P>
76			The library contains a number of undocumented internal functions and data
77			tables that are used by more than one of the exported external functions, but
78			which are not intended for use by external callers. Their names all begin with
79	nigel	83	"_pcre_", which hopefully will not provoke any name clashes. In some
80			environments, it is possible to control which external symbols are exported
81			when a shared library is built, and in these cases the undocumented symbols are
82			not exported.
83	nigel	77	</P>
84	nigel	63	<br><a name="SEC2" href="#TOC1">USER DOCUMENTATION</a><br>
85			<P>
86	nigel	75	The user documentation for PCRE comprises a number of different sections. In
87			the "man" format, each of these is a separate "man page". In the HTML format,
88			each is a separate page, linked from the index page. In the plain text format,
89			all the sections are concatenated, for ease of searching. The sections are as
90			follows:
91	nigel	63	<pre>
92			pcre this document
93	ph10	153	pcre-config show PCRE installation configuration information
94	nigel	77	pcreapi details of PCRE's native C API
95	nigel	63	pcrebuild options for building PCRE
96			pcrecallout details of the callout feature
97			pcrecompat discussion of Perl compatibility
98	nigel	77	pcrecpp details of the C++ wrapper
99	nigel	63	pcregrep description of the <b>pcregrep</b> command
100	nigel	77	pcrematching discussion of the two matching algorithms
101	nigel	75	pcrepartial details of the partial matching facility
102			pcrepattern syntax and semantics of supported regular expressions
103	ph10	208	pcresyntax quick syntax reference
104	nigel	63	pcreperform discussion of performance issues
105	nigel	77	pcreposix the POSIX-compatible C API
106	nigel	75	pcreprecompile details of saving and re-using precompiled patterns
107	nigel	63	pcresample discussion of the sample program
108	nigel	91	pcrestack discussion of stack usage
109	nigel	75	pcretest description of the <b>pcretest</b> testing command
110			</pre>
111	nigel	63	In addition, in the "man" and HTML formats, there is a short page for each
112	nigel	77	C library function, listing its arguments and results.
113	nigel	63	</P>
114			<br><a name="SEC3" href="#TOC1">LIMITATIONS</a><br>
115			<P>
116			There are some size limitations in PCRE but it is hoped that they will never in
117			practice be relevant.
118			</P>
119			<P>
120			The maximum length of a compiled pattern is 65539 (sic) bytes if PCRE is
121			compiled with the default internal linkage size of 2. If you want to process
122			regular expressions that are truly enormous, you can compile PCRE with an
123			internal linkage size of 3 or 4 (see the <b>README</b> file in the source
124			distribution and the
125			<a href="pcrebuild.html"><b>pcrebuild</b></a>
126	nigel	75	documentation for details). In these cases the limit is substantially larger.
127	nigel	93	However, the speed of execution is slower.
128	nigel	63	</P>
129			<P>
130	ph10	208	All values in repeating quantifiers must be less than 65536.
131	nigel	63	</P>
132			<P>
133	nigel	93	There is no limit to the number of parenthesized subpatterns, but there can be
134			no more than 65535 capturing subpatterns.
135	nigel	63	</P>
136			<P>
137	nigel	93	The maximum length of name for a named subpattern is 32 characters, and the
138			maximum number of named subpatterns is 10000.
139	nigel	91	</P>
140			<P>
141	nigel	63	The maximum length of a subject string is the largest positive number that an
142	nigel	77	integer variable can hold. However, when using the traditional matching
143			function, PCRE uses recursion to handle subpatterns and indefinite repetition.
144			This means that the available stack space may limit the size of a subject
145	nigel	91	string that can be processed by certain patterns. For a discussion of stack
146			issues, see the
147			<a href="pcrestack.html"><b>pcrestack</b></a>
148			documentation.
149	nigel	75	<a name="utf8support"></a></P>
150			<br><a name="SEC4" href="#TOC1">UTF-8 AND UNICODE PROPERTY SUPPORT</a><br>
151	nigel	63	<P>
152	nigel	75	From release 3.3, PCRE has had some support for character strings encoded in
153			the UTF-8 format. For release 4.0 this was greatly extended to cover most
154			common requirements, and in release 5.0 additional support for Unicode general
155			category properties was added.
156	nigel	63	</P>
157			<P>
158			In order process UTF-8 strings, you must build PCRE to include UTF-8 support in
159			the code, and, in addition, you must call
160			<a href="pcre_compile.html"><b>pcre_compile()</b></a>
161			with the PCRE_UTF8 option flag. When you do this, both the pattern and any
162			subject strings that are matched against it are treated as UTF-8 strings
163			instead of just strings of bytes.
164			</P>
165			<P>
166			If you compile PCRE with UTF-8 support, but do not use it at run time, the
167			library will be a bit bigger, but the additional run time overhead is limited
168	nigel	93	to testing the PCRE_UTF8 flag occasionally, so should not be very big.
169	nigel	63	</P>
170			<P>
171	nigel	75	If PCRE is built with Unicode character property support (which implies UTF-8
172			support), the escape sequences \p{..}, \P{..}, and \X are supported.
173			The available properties that can be tested are limited to the general
174			category properties such as Lu for an upper case letter or Nd for a decimal
175	nigel	87	number, the Unicode script names such as Arabic or Han, and the derived
176			properties Any and L&. A full list is given in the
177	nigel	75	<a href="pcrepattern.html"><b>pcrepattern</b></a>
178	nigel	87	documentation. Only the short names for properties are supported. For example,
179			\p{L} matches a letter. Its Perl synonym, \p{Letter}, is not supported.
180			Furthermore, in Perl, many properties may optionally be prefixed by "Is", for
181			compatibility with Perl 5.6. PCRE does not support this.
182	nigel	75	</P>
183			<P>
184	nigel	63	The following comments apply when PCRE is running in UTF-8 mode:
185			</P>
186			<P>
187	nigel	71	1. When you set the PCRE_UTF8 flag, the strings passed as patterns and subjects
188			are checked for validity on entry to the relevant functions. If an invalid
189			UTF-8 string is passed, an error return is given. In some situations, you may
190			already know that your strings are valid, and therefore want to skip these
191			checks in order to improve performance. If you set the PCRE_NO_UTF8_CHECK flag
192			at compile time or at run time, PCRE assumes that the pattern or subject it
193			is given (respectively) contains only valid UTF-8 codes. In this case, it does
194			not diagnose an invalid UTF-8 string. If you pass an invalid UTF-8 string to
195			PCRE when PCRE_NO_UTF8_CHECK is set, the results are undefined. Your program
196			may crash.
197	nigel	63	</P>
198			<P>
199	nigel	87	2. An unbraced hexadecimal escape sequence (such as \xb3) matches a two-byte
200			UTF-8 character if the value is greater than 127.
201	nigel	63	</P>
202			<P>
203	nigel	91	3. Octal numbers up to \777 are recognized, and match two-byte UTF-8
204			characters for values greater than \177.
205			</P>
206			<P>
207			4. Repeat quantifiers apply to complete UTF-8 characters, not to individual
208	nigel	63	bytes, for example: \x{100}{3}.
209			</P>
210			<P>
211	nigel	91	5. The dot metacharacter matches one UTF-8 character instead of a single byte.
212	nigel	63	</P>
213			<P>
214	nigel	91	6. The escape sequence \C can be used to match a single byte in UTF-8 mode,
215	nigel	77	but its use can lead to some strange effects. This facility is not available in
216			the alternative matching function, <b>pcre_dfa_exec()</b>.
217	nigel	63	</P>
218			<P>
219	nigel	91	7. The character escapes \b, \B, \d, \D, \s, \S, \w, and \W correctly
220	nigel	63	test characters of any code value, but the characters that PCRE recognizes as
221			digits, spaces, or word characters remain the same set as before, all with
222	nigel	75	values less than 256. This remains true even when PCRE includes Unicode
223			property support, because to do otherwise would slow down PCRE in many common
224			cases. If you really want to test for a wider sense of, say, "digit", you
225			must use Unicode property tests such as \p{Nd}.
226	nigel	63	</P>
227			<P>
228	nigel	91	8. Similarly, characters that match the POSIX named character classes are all
229	nigel	75	low-valued characters.
230	nigel	63	</P>
231			<P>
232	ph10	182	9. However, the Perl 5.10 horizontal and vertical whitespace matching escapes
233			(\h, \H, \v, and \V) do match all the appropriate Unicode characters.
234			</P>
235			<P>
236			10. Case-insensitive matching applies only to characters whose values are less
237	nigel	75	than 128, unless PCRE is built with Unicode property support. Even when Unicode
238			property support is available, PCRE still uses its own character tables when
239			checking the case of low-valued characters, so as not to degrade performance.
240			The Unicode property information is used only for characters with higher
241	nigel	87	values. Even when Unicode property support is available, PCRE supports
242			case-insensitive matching only when there is a one-to-one mapping between a
243			letter's cases. There are a small number of many-to-one mappings in Unicode;
244			these are not supported by PCRE.
245	nigel	63	</P>
246			<br><a name="SEC5" href="#TOC1">AUTHOR</a><br>
247			<P>
248	nigel	77	Philip Hazel
249	nigel	63	<br>
250	ph10	99	University Computing Service
251	nigel	63	<br>
252	nigel	93	Cambridge CB2 3QH, England.
253	ph10	99	<br>
254	nigel	77	</P>
255			<P>
256			Putting an actual email address here seems to have been a spam magnet, so I've
257	ph10	153	taken it away. If you want to email me, use my two initials, followed by the
258			two digits 10, at the domain cam.ac.uk.
259	ph10	99	</P>
260			<br><a name="SEC6" href="#TOC1">REVISION</a><br>
261			<P>
262	ph10	208	Last updated: 06 August 2007
263	nigel	63	<br>
264	ph10	99	Copyright © 1997-2007 University of Cambridge.
265			<br>
266	nigel	75	<p>
267			Return to the <a href="index.html">PCRE index page</a>.
268			</p>
Name	Value
svn:eol-style	native
svn:keywords	"Author Date Id Revision Url"