1 |
.TH PCRE 3 |
.TH PCRECOMPAT 3 |
2 |
.SH NAME |
.SH NAME |
3 |
PCRE - Perl-compatible regular expressions |
PCRE - Perl-compatible regular expressions |
4 |
.SH DIFFERENCES FROM PERL |
.SH "DIFFERENCES BETWEEN PCRE AND PERL" |
5 |
.rs |
.rs |
6 |
.sp |
.sp |
7 |
This document describes the differences in the ways that PCRE and Perl handle |
This document describes the differences in the ways that PCRE and Perl handle |
8 |
regular expressions. The differences described here are with respect to Perl |
regular expressions. The differences described here are mainly with respect to |
9 |
5.8. |
Perl 5.8, though PCRE version 7.0 contains some features that are expected to |
10 |
|
be in the forthcoming Perl 5.10. |
11 |
1. PCRE does not allow repeat quantifiers on lookahead assertions. Perl permits |
.P |
12 |
|
1. PCRE has only a subset of Perl's UTF-8 and Unicode support. Details of what |
13 |
|
it does have are given in the |
14 |
|
.\" HTML <a href="pcre.html#utf8support"> |
15 |
|
.\" </a> |
16 |
|
section on UTF-8 support |
17 |
|
.\" |
18 |
|
in the main |
19 |
|
.\" HREF |
20 |
|
\fBpcre\fP |
21 |
|
.\" |
22 |
|
page. |
23 |
|
.P |
24 |
|
2. PCRE does not allow repeat quantifiers on lookahead assertions. Perl permits |
25 |
them, but they do not mean what you might think. For example, (?!a){3} does |
them, but they do not mean what you might think. For example, (?!a){3} does |
26 |
not assert that the next three characters are not "a". It just asserts that the |
not assert that the next three characters are not "a". It just asserts that the |
27 |
next character is not "a" three times. |
next character is not "a" three times. |
28 |
|
.P |
29 |
2. Capturing subpatterns that occur inside negative lookahead assertions are |
3. Capturing subpatterns that occur inside negative lookahead assertions are |
30 |
counted, but their entries in the offsets vector are never set. Perl sets its |
counted, but their entries in the offsets vector are never set. Perl sets its |
31 |
numerical variables from any such patterns that are matched before the |
numerical variables from any such patterns that are matched before the |
32 |
assertion fails to match something (thereby succeeding), but only if the |
assertion fails to match something (thereby succeeding), but only if the |
33 |
negative lookahead assertion contains just one branch. |
negative lookahead assertion contains just one branch. |
34 |
|
.P |
35 |
3. Though binary zero characters are supported in the subject string, they are |
4. Though binary zero characters are supported in the subject string, they are |
36 |
not allowed in a pattern string because it is passed as a normal C string, |
not allowed in a pattern string because it is passed as a normal C string, |
37 |
terminated by zero. The escape sequence "\\0" can be used in the pattern to |
terminated by zero. The escape sequence \e0 can be used in the pattern to |
38 |
represent a binary zero. |
represent a binary zero. |
39 |
|
.P |
40 |
4. The following Perl escape sequences are not supported: \\l, \\u, \\L, |
5. The following Perl escape sequences are not supported: \el, \eu, \eL, |
41 |
\\U, \\P, \\p, \N, and \\X. In fact these are implemented by Perl's general |
\eU, and \eN. In fact these are implemented by Perl's general string-handling |
42 |
string-handling and are not part of its pattern matching engine. If any of |
and are not part of its pattern matching engine. If any of these are |
43 |
these are encountered by PCRE, an error is generated. |
encountered by PCRE, an error is generated. |
44 |
|
.P |
45 |
5. PCRE does support the \\Q...\\E escape for quoting substrings. Characters in |
6. The Perl escape sequences \ep, \eP, and \eX are supported only if PCRE is |
46 |
|
built with Unicode character property support. The properties that can be |
47 |
|
tested with \ep and \eP are limited to the general category properties such as |
48 |
|
Lu and Nd, script names such as Greek or Han, and the derived properties Any |
49 |
|
and L&. |
50 |
|
.P |
51 |
|
7. PCRE does support the \eQ...\eE escape for quoting substrings. Characters in |
52 |
between are treated as literals. This is slightly different from Perl in that $ |
between are treated as literals. This is slightly different from Perl in that $ |
53 |
and @ are also handled as literals inside the quotes. In Perl, they cause |
and @ are also handled as literals inside the quotes. In Perl, they cause |
54 |
variable interpolation (but of course PCRE does not have variables). Note the |
variable interpolation (but of course PCRE does not have variables). Note the |
55 |
following examples: |
following examples: |
56 |
|
.sp |
57 |
Pattern PCRE matches Perl matches |
Pattern PCRE matches Perl matches |
58 |
|
.sp |
59 |
\\Qabc$xyz\\E abc$xyz abc followed by the |
.\" JOIN |
60 |
|
\eQabc$xyz\eE abc$xyz abc followed by the |
61 |
contents of $xyz |
contents of $xyz |
62 |
\\Qabc\\$xyz\\E abc\\$xyz abc\\$xyz |
\eQabc\e$xyz\eE abc\e$xyz abc\e$xyz |
63 |
\\Qabc\\E\\$\\Qxyz\\E abc$xyz abc$xyz |
\eQabc\eE\e$\eQxyz\eE abc$xyz abc$xyz |
64 |
|
.sp |
65 |
In PCRE, the \\Q...\\E mechanism is not recognized inside a character class. |
The \eQ...\eE sequence is recognized both inside and outside character classes. |
66 |
|
.P |
67 |
8. Fairly obviously, PCRE does not support the (?{code}) and (?p{code}) |
8. Fairly obviously, PCRE does not support the (?{code}) and (??{code}) |
68 |
constructions. However, there is some experimental support for recursive |
constructions. However, there is support for recursive patterns. This is not |
69 |
patterns using the non-Perl items (?R), (?number) and (?P>name). Also, the PCRE |
available in Perl 5.8, but will be in Perl 5.10. Also, the PCRE "callout" |
70 |
"callout" feature allows an external function to be called during pattern |
feature allows an external function to be called during pattern matching. See |
71 |
matching. |
the |
72 |
|
.\" HREF |
73 |
9. There are some differences that are concerned with the settings of captured |
\fBpcrecallout\fP |
74 |
|
.\" |
75 |
|
documentation for details. |
76 |
|
.P |
77 |
|
9. Subpatterns that are called recursively or as "subroutines" are always |
78 |
|
treated as atomic groups in PCRE. This is like Python, but unlike Perl. |
79 |
|
.P |
80 |
|
10. There are some differences that are concerned with the settings of captured |
81 |
strings when part of a pattern is repeated. For example, matching "aba" against |
strings when part of a pattern is repeated. For example, matching "aba" against |
82 |
the pattern /^(a(b)?)+$/ in Perl leaves $2 unset, but in PCRE it is set to "b". |
the pattern /^(a(b)?)+$/ in Perl leaves $2 unset, but in PCRE it is set to "b". |
83 |
|
.P |
84 |
10. PCRE provides some extensions to the Perl regular expression facilities: |
11. PCRE provides some extensions to the Perl regular expression facilities. |
85 |
|
Perl 5.10 will include new features that are not in earlier versions, some of |
86 |
|
which (such as named parentheses) have been in PCRE for some time. This list is |
87 |
|
with respect to Perl 5.10: |
88 |
|
.sp |
89 |
(a) Although lookbehind assertions must match fixed length strings, each |
(a) Although lookbehind assertions must match fixed length strings, each |
90 |
alternative branch of a lookbehind assertion can match a different length of |
alternative branch of a lookbehind assertion can match a different length of |
91 |
string. Perl requires them all to have the same length. |
string. Perl requires them all to have the same length. |
92 |
|
.sp |
93 |
(b) If PCRE_DOLLAR_ENDONLY is set and PCRE_MULTILINE is not set, the $ |
(b) If PCRE_DOLLAR_ENDONLY is set and PCRE_MULTILINE is not set, the $ |
94 |
meta-character matches only at the very end of the string. |
meta-character matches only at the very end of the string. |
95 |
|
.sp |
96 |
(c) If PCRE_EXTRA is set, a backslash followed by a letter with no special |
(c) If PCRE_EXTRA is set, a backslash followed by a letter with no special |
97 |
meaning is faulted. |
meaning is faulted. Otherwise, like Perl, the backslash is ignored. (Perl can |
98 |
|
be made to issue a warning.) |
99 |
|
.sp |
100 |
(d) If PCRE_UNGREEDY is set, the greediness of the repetition quantifiers is |
(d) If PCRE_UNGREEDY is set, the greediness of the repetition quantifiers is |
101 |
inverted, that is, by default they are not greedy, but if followed by a |
inverted, that is, by default they are not greedy, but if followed by a |
102 |
question mark they are. |
question mark they are. |
103 |
|
.sp |
104 |
(e) PCRE_ANCHORED can be used to force a pattern to be tried only at the first |
(e) PCRE_ANCHORED can be used at matching time to force a pattern to be tried |
105 |
matching position in the subject string. |
only at the first matching position in the subject string. |
106 |
|
.sp |
107 |
(f) The PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, and PCRE_NO_AUTO_CAPTURE |
(f) The PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, and PCRE_NO_AUTO_CAPTURE |
108 |
options for \fBpcre_exec()\fR have no Perl equivalents. |
options for \fBpcre_exec()\fP have no Perl equivalents. |
109 |
|
.sp |
110 |
(g) The (?R), (?number), and (?P>name) constructs allows for recursive pattern |
(g) The callout facility is PCRE-specific. |
111 |
matching (Perl can do this using the (?p{code}) construct, which PCRE cannot |
.sp |
112 |
support.) |
(h) The partial matching facility is PCRE-specific. |
113 |
|
.sp |
114 |
(h) PCRE supports named capturing substrings, using the Python syntax. |
(i) Patterns compiled by PCRE can be saved and re-used at a later time, even on |
115 |
|
different hosts that have the other endianness. |
116 |
(i) PCRE supports the possessive quantifier "++" syntax, taken from Sun's Java |
.sp |
117 |
package. |
(j) The alternative matching function (\fBpcre_dfa_exec()\fP) matches in a |
118 |
|
different way and is not Perl-compatible. |
119 |
(j) The (R) condition, for testing recursion, is a PCRE extension. |
. |
120 |
|
. |
121 |
(k) The callout facility is PCRE-specific. |
.SH AUTHOR |
122 |
|
.rs |
123 |
.in 0 |
.sp |
124 |
Last updated: 03 February 2003 |
.nf |
125 |
.br |
Philip Hazel |
126 |
Copyright (c) 1997-2003 University of Cambridge. |
University Computing Service |
127 |
|
Cambridge CB2 3QH, England. |
128 |
|
.fi |
129 |
|
. |
130 |
|
. |
131 |
|
.SH REVISION |
132 |
|
.rs |
133 |
|
.sp |
134 |
|
.nf |
135 |
|
Last updated: 06 March 2007 |
136 |
|
Copyright (c) 1997-2007 University of Cambridge. |
137 |
|
.fi |