/[pcre]/code/trunk/doc/pcrecompat.3
ViewVC logotype

Diff of /code/trunk/doc/pcrecompat.3

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 91 by nigel, Sat Feb 24 21:41:34 2007 UTC revision 459 by ph10, Sun Oct 4 09:21:39 2009 UTC
# Line 6  PCRE - Perl-compatible regular expressio Line 6  PCRE - Perl-compatible regular expressio
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 with respect to Perl
9  5.8.  5.10.
10  .P  .P
11  1. PCRE has only a subset of Perl's UTF-8 and Unicode support. Details of what  1. PCRE has only a subset of Perl's UTF-8 and Unicode support. Details of what
12  it does have are given in the  it does have are given in the
# Line 45  encountered by PCRE, an error is generat Line 45  encountered by PCRE, an error is generat
45  built with Unicode character property support. The properties that can be  built with Unicode character property support. The properties that can be
46  tested with \ep and \eP are limited to the general category properties such as  tested with \ep and \eP are limited to the general category properties such as
47  Lu and Nd, script names such as Greek or Han, and the derived properties Any  Lu and Nd, script names such as Greek or Han, and the derived properties Any
48  and L&.  and L&. PCRE does support the Cs (surrogate) property, which Perl does not; the
49    Perl documentation says "Because Perl hides the need for the user to understand
50    the internal representation of Unicode characters, there is no need to
51    implement the somewhat messy concept of surrogates."
52  .P  .P
53  7. PCRE does support the \eQ...\eE escape for quoting substrings. Characters in  7. PCRE does support the \eQ...\eE escape for quoting substrings. Characters in
54  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 $
# Line 63  following examples: Line 66  following examples:
66  .sp  .sp
67  The \eQ...\eE sequence is recognized both inside and outside character classes.  The \eQ...\eE sequence is recognized both inside and outside character classes.
68  .P  .P
69  8. Fairly obviously, PCRE does not support the (?{code}) and (?p{code})  8. Fairly obviously, PCRE does not support the (?{code}) and (??{code})
70  constructions. However, there is support for recursive patterns using the  constructions. However, there is support for recursive patterns. This is not
71  non-Perl items (?R), (?number), and (?P>name). Also, the PCRE "callout" feature  available in Perl 5.8, but it is in Perl 5.10. Also, the PCRE "callout"
72  allows an external function to be called during pattern matching. See the  feature allows an external function to be called during pattern matching. See
73    the
74  .\" HREF  .\" HREF
75  \fBpcrecallout\fP  \fBpcrecallout\fP
76  .\"  .\"
77  documentation for details.  documentation for details.
78  .P  .P
79  9. There are some differences that are concerned with the settings of captured  9. Subpatterns that are called recursively or as "subroutines" are always
80    treated as atomic groups in PCRE. This is like Python, but unlike Perl. There
81    is a discussion of an example that explains this in more detail in the
82    .\" HTML <a href="pcrepattern.html#recursiondifference">
83    .\" </a>
84    section on recursion differences from Perl
85    .\"
86    in the
87    .\" HREF
88    \fBpcrepattern\fP
89    .\"
90    page.
91    .P
92    10. There are some differences that are concerned with the settings of captured
93  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
94  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".
95  .P  .P
96  10. PCRE provides some extensions to the Perl regular expression facilities:  11. PCRE does support Perl 5.10's backtracking verbs (*ACCEPT), (*FAIL), (*F),
97  .sp  (*COMMIT), (*PRUNE), (*SKIP), and (*THEN), but only in the forms without an
98  (a) Although lookbehind assertions must match fixed length strings, each  argument. PCRE does not support (*MARK).
99  alternative branch of a lookbehind assertion can match a different length of  .P
100  string. Perl requires them all to have the same length.  12. PCRE's handling of duplicate subpattern numbers and duplicate subpattern
101    names is not as general as Perl's. This is a consequence of the fact the PCRE
102    works internally just with numbers, using an external table to translate
103    between numbers and names. In particular, a pattern such as (?|(?<a>A)|(?<b)B),
104    where the two capturing parentheses have the same number but different names,
105    is not supported, and causes an error at compile time. If it were allowed, it
106    would not be possible to distinguish which parentheses matched, because both
107    names map to capturing subpattern number 1. To avoid this confusing situation,
108    an error is given at compile time.
109    .P
110    13. PCRE provides some extensions to the Perl regular expression facilities.
111    Perl 5.10 includes new features that are not in earlier versions of Perl, some
112    of which (such as named parentheses) have been in PCRE for some time. This list
113    is with respect to Perl 5.10:
114    .sp
115    (a) Although lookbehind assertions in PCRE must match fixed length strings,
116    each alternative branch of a lookbehind assertion can match a different length
117    of string. Perl requires them all to have the same length.
118  .sp  .sp
119  (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 $
120  meta-character matches only at the very end of the string.  meta-character matches only at the very end of the string.
121  .sp  .sp
122  (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
123  meaning is faulted. Otherwise, like Perl, the backslash is ignored. (Perl can  meaning is faulted. Otherwise, like Perl, the backslash is quietly ignored.
124  be made to issue a warning.)  (Perl can be made to issue a warning.)
125  .sp  .sp
126  (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
127  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
# Line 96  question mark they are. Line 130  question mark they are.
130  (e) PCRE_ANCHORED can be used at matching time to force a pattern to be tried  (e) PCRE_ANCHORED can be used at matching time to force a pattern to be tried
131  only at the first matching position in the subject string.  only at the first matching position in the subject string.
132  .sp  .sp
133  (f) The PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, and PCRE_NO_AUTO_CAPTURE  (f) The PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NOTEMPTY_ATSTART, and
134  options for \fBpcre_exec()\fP have no Perl equivalents.  PCRE_NO_AUTO_CAPTURE options for \fBpcre_exec()\fP have no Perl equivalents.
 .sp  
 (g) The (?R), (?number), and (?P>name) constructs allows for recursive pattern  
 matching (Perl can do this using the (?p{code}) construct, which PCRE cannot  
 support.)  
 .sp  
 (h) PCRE supports named capturing substrings, using the Python syntax.  
135  .sp  .sp
136  (i) PCRE supports the possessive quantifier "++" syntax, taken from Sun's Java  (g) The \eR escape sequence can be restricted to match only CR, LF, or CRLF
137  package.  by the PCRE_BSR_ANYCRLF option.
138  .sp  .sp
139  (j) The (R) condition, for testing recursion, is a PCRE extension.  (h) The callout facility is PCRE-specific.
140  .sp  .sp
141  (k) The callout facility is PCRE-specific.  (i) The partial matching facility is PCRE-specific.
142  .sp  .sp
143  (l) The partial matching facility is PCRE-specific.  (j) Patterns compiled by PCRE can be saved and re-used at a later time, even on
 .sp  
 (m) Patterns compiled by PCRE can be saved and re-used at a later time, even on  
144  different hosts that have the other endianness.  different hosts that have the other endianness.
145  .sp  .sp
146  (n) The alternative matching function (\fBpcre_dfa_exec()\fP) matches in a  (k) The alternative matching function (\fBpcre_dfa_exec()\fP) matches in a
147  different way and is not Perl-compatible.  different way and is not Perl-compatible.
148  .P  .sp
149  .in 0  (l) PCRE recognizes some special sequences such as (*CR) at the start of
150  Last updated: 06 June 2006  a pattern that set overall options that cannot be changed within the pattern.
151  .br  .
152  Copyright (c) 1997-2006 University of Cambridge.  .
153    .SH AUTHOR
154    .rs
155    .sp
156    .nf
157    Philip Hazel
158    University Computing Service
159    Cambridge CB2 3QH, England.
160    .fi
161    .
162    .
163    .SH REVISION
164    .rs
165    .sp
166    .nf
167    Last updated: 04 October 2009
168    Copyright (c) 1997-2009 University of Cambridge.
169    .fi

Legend:
Removed from v.91  
changed lines
  Added in v.459

  ViewVC Help
Powered by ViewVC 1.1.5