/[pcre]/code/trunk/doc/html/pcrepattern.html
ViewVC logotype

Contents of /code/trunk/doc/html/pcrepattern.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 959 - (show annotations)
Sat Apr 14 16:16:58 2012 UTC (7 years, 5 months ago) by ph10
File MIME type: text/html
File size: 124478 byte(s)
Error occurred while calculating annotation data.
Update documentation to clarify that UTF-8/16 checking is done on complete 
strings before any other processing.
1 <html>
2 <head>
3 <title>pcrepattern specification</title>
4 </head>
5 <body bgcolor="#FFFFFF" text="#00005A" link="#0066FF" alink="#3399FF" vlink="#2222BB">
6 <h1>pcrepattern man page</h1>
7 <p>
8 Return to the <a href="index.html">PCRE index page</a>.
9 </p>
10 <p>
11 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 <br>
15 <ul>
16 <li><a name="TOC1" href="#SEC1">PCRE REGULAR EXPRESSION DETAILS</a>
17 <li><a name="TOC2" href="#SEC2">NEWLINE CONVENTIONS</a>
18 <li><a name="TOC3" href="#SEC3">CHARACTERS AND METACHARACTERS</a>
19 <li><a name="TOC4" href="#SEC4">BACKSLASH</a>
20 <li><a name="TOC5" href="#SEC5">CIRCUMFLEX AND DOLLAR</a>
21 <li><a name="TOC6" href="#SEC6">FULL STOP (PERIOD, DOT) AND \N</a>
22 <li><a name="TOC7" href="#SEC7">MATCHING A SINGLE DATA UNIT</a>
23 <li><a name="TOC8" href="#SEC8">SQUARE BRACKETS AND CHARACTER CLASSES</a>
24 <li><a name="TOC9" href="#SEC9">POSIX CHARACTER CLASSES</a>
25 <li><a name="TOC10" href="#SEC10">VERTICAL BAR</a>
26 <li><a name="TOC11" href="#SEC11">INTERNAL OPTION SETTING</a>
27 <li><a name="TOC12" href="#SEC12">SUBPATTERNS</a>
28 <li><a name="TOC13" href="#SEC13">DUPLICATE SUBPATTERN NUMBERS</a>
29 <li><a name="TOC14" href="#SEC14">NAMED SUBPATTERNS</a>
30 <li><a name="TOC15" href="#SEC15">REPETITION</a>
31 <li><a name="TOC16" href="#SEC16">ATOMIC GROUPING AND POSSESSIVE QUANTIFIERS</a>
32 <li><a name="TOC17" href="#SEC17">BACK REFERENCES</a>
33 <li><a name="TOC18" href="#SEC18">ASSERTIONS</a>
34 <li><a name="TOC19" href="#SEC19">CONDITIONAL SUBPATTERNS</a>
35 <li><a name="TOC20" href="#SEC20">COMMENTS</a>
36 <li><a name="TOC21" href="#SEC21">RECURSIVE PATTERNS</a>
37 <li><a name="TOC22" href="#SEC22">SUBPATTERNS AS SUBROUTINES</a>
38 <li><a name="TOC23" href="#SEC23">ONIGURUMA SUBROUTINE SYNTAX</a>
39 <li><a name="TOC24" href="#SEC24">CALLOUTS</a>
40 <li><a name="TOC25" href="#SEC25">BACKTRACKING CONTROL</a>
41 <li><a name="TOC26" href="#SEC26">SEE ALSO</a>
42 <li><a name="TOC27" href="#SEC27">AUTHOR</a>
43 <li><a name="TOC28" href="#SEC28">REVISION</a>
44 </ul>
45 <br><a name="SEC1" href="#TOC1">PCRE REGULAR EXPRESSION DETAILS</a><br>
46 <P>
47 The syntax and semantics of the regular expressions that are supported by PCRE
48 are described in detail below. There is a quick-reference syntax summary in the
49 <a href="pcresyntax.html"><b>pcresyntax</b></a>
50 page. PCRE tries to match Perl syntax and semantics as closely as it can. PCRE
51 also supports some alternative regular expression syntax (which does not
52 conflict with the Perl syntax) in order to provide some compatibility with
53 regular expressions in Python, .NET, and Oniguruma.
54 </P>
55 <P>
56 Perl's regular expressions are described in its own documentation, and
57 regular expressions in general are covered in a number of books, some of which
58 have copious examples. Jeffrey Friedl's "Mastering Regular Expressions",
59 published by O'Reilly, covers regular expressions in great detail. This
60 description of PCRE's regular expressions is intended as reference material.
61 </P>
62 <P>
63 The original operation of PCRE was on strings of one-byte characters. However,
64 there is now also support for UTF-8 strings in the original library, and a
65 second library that supports 16-bit and UTF-16 character strings. To use these
66 features, PCRE must be built to include appropriate support. When using UTF
67 strings you must either call the compiling function with the PCRE_UTF8 or
68 PCRE_UTF16 option, or the pattern must start with one of these special
69 sequences:
70 <pre>
71 (*UTF8)
72 (*UTF16)
73 </pre>
74 Starting a pattern with such a sequence is equivalent to setting the relevant
75 option. This feature is not Perl-compatible. How setting a UTF mode affects
76 pattern matching is mentioned in several places below. There is also a summary
77 of features in the
78 <a href="pcreunicode.html"><b>pcreunicode</b></a>
79 page.
80 </P>
81 <P>
82 Another special sequence that may appear at the start of a pattern or in
83 combination with (*UTF8) or (*UTF16) is:
84 <pre>
85 (*UCP)
86 </pre>
87 This has the same effect as setting the PCRE_UCP option: it causes sequences
88 such as \d and \w to use Unicode properties to determine character types,
89 instead of recognizing only characters with codes less than 128 via a lookup
90 table.
91 </P>
92 <P>
93 If a pattern starts with (*NO_START_OPT), it has the same effect as setting the
94 PCRE_NO_START_OPTIMIZE option either at compile or matching time. There are
95 also some more of these special sequences that are concerned with the handling
96 of newlines; they are described below.
97 </P>
98 <P>
99 The remainder of this document discusses the patterns that are supported by
100 PCRE when one its main matching functions, <b>pcre_exec()</b> (8-bit) or
101 <b>pcre16_exec()</b> (16-bit), is used. PCRE also has alternative matching
102 functions, <b>pcre_dfa_exec()</b> and <b>pcre16_dfa_exec()</b>, which match using
103 a different algorithm that is not Perl-compatible. Some of the features
104 discussed below are not available when DFA matching is used. The advantages and
105 disadvantages of the alternative functions, and how they differ from the normal
106 functions, are discussed in the
107 <a href="pcrematching.html"><b>pcrematching</b></a>
108 page.
109 <a name="newlines"></a></P>
110 <br><a name="SEC2" href="#TOC1">NEWLINE CONVENTIONS</a><br>
111 <P>
112 PCRE supports five different conventions for indicating line breaks in
113 strings: a single CR (carriage return) character, a single LF (linefeed)
114 character, the two-character sequence CRLF, any of the three preceding, or any
115 Unicode newline sequence. The
116 <a href="pcreapi.html"><b>pcreapi</b></a>
117 page has
118 <a href="pcreapi.html#newlines">further discussion</a>
119 about newlines, and shows how to set the newline convention in the
120 <i>options</i> arguments for the compiling and matching functions.
121 </P>
122 <P>
123 It is also possible to specify a newline convention by starting a pattern
124 string with one of the following five sequences:
125 <pre>
126 (*CR) carriage return
127 (*LF) linefeed
128 (*CRLF) carriage return, followed by linefeed
129 (*ANYCRLF) any of the three above
130 (*ANY) all Unicode newline sequences
131 </pre>
132 These override the default and the options given to the compiling function. For
133 example, on a Unix system where LF is the default newline sequence, the pattern
134 <pre>
135 (*CR)a.b
136 </pre>
137 changes the convention to CR. That pattern matches "a\nb" because LF is no
138 longer a newline. Note that these special settings, which are not
139 Perl-compatible, are recognized only at the very start of a pattern, and that
140 they must be in upper case. If more than one of them is present, the last one
141 is used.
142 </P>
143 <P>
144 The newline convention affects the interpretation of the dot metacharacter when
145 PCRE_DOTALL is not set, and also the behaviour of \N. However, it does not
146 affect what the \R escape sequence matches. By default, this is any Unicode
147 newline sequence, for Perl compatibility. However, this can be changed; see the
148 description of \R in the section entitled
149 <a href="#newlineseq">"Newline sequences"</a>
150 below. A change of \R setting can be combined with a change of newline
151 convention.
152 </P>
153 <br><a name="SEC3" href="#TOC1">CHARACTERS AND METACHARACTERS</a><br>
154 <P>
155 A regular expression is a pattern that is matched against a subject string from
156 left to right. Most characters stand for themselves in a pattern, and match the
157 corresponding characters in the subject. As a trivial example, the pattern
158 <pre>
159 The quick brown fox
160 </pre>
161 matches a portion of a subject string that is identical to itself. When
162 caseless matching is specified (the PCRE_CASELESS option), letters are matched
163 independently of case. In a UTF mode, PCRE always understands the concept of
164 case for characters whose values are less than 128, so caseless matching is
165 always possible. For characters with higher values, the concept of case is
166 supported if PCRE is compiled with Unicode property support, but not otherwise.
167 If you want to use caseless matching for characters 128 and above, you must
168 ensure that PCRE is compiled with Unicode property support as well as with
169 UTF support.
170 </P>
171 <P>
172 The power of regular expressions comes from the ability to include alternatives
173 and repetitions in the pattern. These are encoded in the pattern by the use of
174 <i>metacharacters</i>, which do not stand for themselves but instead are
175 interpreted in some special way.
176 </P>
177 <P>
178 There are two different sets of metacharacters: those that are recognized
179 anywhere in the pattern except within square brackets, and those that are
180 recognized within square brackets. Outside square brackets, the metacharacters
181 are as follows:
182 <pre>
183 \ general escape character with several uses
184 ^ assert start of string (or line, in multiline mode)
185 $ assert end of string (or line, in multiline mode)
186 . match any character except newline (by default)
187 [ start character class definition
188 | start of alternative branch
189 ( start subpattern
190 ) end subpattern
191 ? extends the meaning of (
192 also 0 or 1 quantifier
193 also quantifier minimizer
194 * 0 or more quantifier
195 + 1 or more quantifier
196 also "possessive quantifier"
197 { start min/max quantifier
198 </pre>
199 Part of a pattern that is in square brackets is called a "character class". In
200 a character class the only metacharacters are:
201 <pre>
202 \ general escape character
203 ^ negate the class, but only if the first character
204 - indicates character range
205 [ POSIX character class (only if followed by POSIX syntax)
206 ] terminates the character class
207 </pre>
208 The following sections describe the use of each of the metacharacters.
209 </P>
210 <br><a name="SEC4" href="#TOC1">BACKSLASH</a><br>
211 <P>
212 The backslash character has several uses. Firstly, if it is followed by a
213 character that is not a number or a letter, it takes away any special meaning
214 that character may have. This use of backslash as an escape character applies
215 both inside and outside character classes.
216 </P>
217 <P>
218 For example, if you want to match a * character, you write \* in the pattern.
219 This escaping action applies whether or not the following character would
220 otherwise be interpreted as a metacharacter, so it is always safe to precede a
221 non-alphanumeric with backslash to specify that it stands for itself. In
222 particular, if you want to match a backslash, you write \\.
223 </P>
224 <P>
225 In a UTF mode, only ASCII numbers and letters have any special meaning after a
226 backslash. All other characters (in particular, those whose codepoints are
227 greater than 127) are treated as literals.
228 </P>
229 <P>
230 If a pattern is compiled with the PCRE_EXTENDED option, whitespace in the
231 pattern (other than in a character class) and characters between a # outside
232 a character class and the next newline are ignored. An escaping backslash can
233 be used to include a whitespace or # character as part of the pattern.
234 </P>
235 <P>
236 If you want to remove the special meaning from a sequence of characters, you
237 can do so by putting them between \Q and \E. This is different from Perl in
238 that $ and @ are handled as literals in \Q...\E sequences in PCRE, whereas in
239 Perl, $ and @ cause variable interpolation. Note the following examples:
240 <pre>
241 Pattern PCRE matches Perl matches
242
243 \Qabc$xyz\E abc$xyz abc followed by the contents of $xyz
244 \Qabc\$xyz\E abc\$xyz abc\$xyz
245 \Qabc\E\$\Qxyz\E abc$xyz abc$xyz
246 </pre>
247 The \Q...\E sequence is recognized both inside and outside character classes.
248 An isolated \E that is not preceded by \Q is ignored. If \Q is not followed
249 by \E later in the pattern, the literal interpretation continues to the end of
250 the pattern (that is, \E is assumed at the end). If the isolated \Q is inside
251 a character class, this causes an error, because the character class is not
252 terminated.
253 <a name="digitsafterbackslash"></a></P>
254 <br><b>
255 Non-printing characters
256 </b><br>
257 <P>
258 A second use of backslash provides a way of encoding non-printing characters
259 in patterns in a visible manner. There is no restriction on the appearance of
260 non-printing characters, apart from the binary zero that terminates a pattern,
261 but when a pattern is being prepared by text editing, it is often easier to use
262 one of the following escape sequences than the binary character it represents:
263 <pre>
264 \a alarm, that is, the BEL character (hex 07)
265 \cx "control-x", where x is any ASCII character
266 \e escape (hex 1B)
267 \f formfeed (hex 0C)
268 \n linefeed (hex 0A)
269 \r carriage return (hex 0D)
270 \t tab (hex 09)
271 \ddd character with octal code ddd, or back reference
272 \xhh character with hex code hh
273 \x{hhh..} character with hex code hhh.. (non-JavaScript mode)
274 \uhhhh character with hex code hhhh (JavaScript mode only)
275 </pre>
276 The precise effect of \cx is as follows: if x is a lower case letter, it
277 is converted to upper case. Then bit 6 of the character (hex 40) is inverted.
278 Thus \cz becomes hex 1A (z is 7A), but \c{ becomes hex 3B ({ is 7B), while
279 \c; becomes hex 7B (; is 3B). If the byte following \c has a value greater
280 than 127, a compile-time error occurs. This locks out non-ASCII characters in
281 all modes. (When PCRE is compiled in EBCDIC mode, all byte values are valid. A
282 lower case letter is converted to upper case, and then the 0xc0 bits are
283 flipped.)
284 </P>
285 <P>
286 By default, after \x, from zero to two hexadecimal digits are read (letters
287 can be in upper or lower case). Any number of hexadecimal digits may appear
288 between \x{ and }, but the character code is constrained as follows:
289 <pre>
290 8-bit non-UTF mode less than 0x100
291 8-bit UTF-8 mode less than 0x10ffff and a valid codepoint
292 16-bit non-UTF mode less than 0x10000
293 16-bit UTF-16 mode less than 0x10ffff and a valid codepoint
294 </pre>
295 Invalid Unicode codepoints are the range 0xd800 to 0xdfff (the so-called
296 "surrogate" codepoints).
297 </P>
298 <P>
299 If characters other than hexadecimal digits appear between \x{ and }, or if
300 there is no terminating }, this form of escape is not recognized. Instead, the
301 initial \x will be interpreted as a basic hexadecimal escape, with no
302 following digits, giving a character whose value is zero.
303 </P>
304 <P>
305 If the PCRE_JAVASCRIPT_COMPAT option is set, the interpretation of \x is
306 as just described only when it is followed by two hexadecimal digits.
307 Otherwise, it matches a literal "x" character. In JavaScript mode, support for
308 code points greater than 256 is provided by \u, which must be followed by
309 four hexadecimal digits; otherwise it matches a literal "u" character.
310 </P>
311 <P>
312 Characters whose value is less than 256 can be defined by either of the two
313 syntaxes for \x (or by \u in JavaScript mode). There is no difference in the
314 way they are handled. For example, \xdc is exactly the same as \x{dc} (or
315 \u00dc in JavaScript mode).
316 </P>
317 <P>
318 After \0 up to two further octal digits are read. If there are fewer than two
319 digits, just those that are present are used. Thus the sequence \0\x\07
320 specifies two binary zeros followed by a BEL character (code value 7). Make
321 sure you supply two digits after the initial zero if the pattern character that
322 follows is itself an octal digit.
323 </P>
324 <P>
325 The handling of a backslash followed by a digit other than 0 is complicated.
326 Outside a character class, PCRE reads it and any following digits as a decimal
327 number. If the number is less than 10, or if there have been at least that many
328 previous capturing left parentheses in the expression, the entire sequence is
329 taken as a <i>back reference</i>. A description of how this works is given
330 <a href="#backreferences">later,</a>
331 following the discussion of
332 <a href="#subpattern">parenthesized subpatterns.</a>
333 </P>
334 <P>
335 Inside a character class, or if the decimal number is greater than 9 and there
336 have not been that many capturing subpatterns, PCRE re-reads up to three octal
337 digits following the backslash, and uses them to generate a data character. Any
338 subsequent digits stand for themselves. The value of the character is
339 constrained in the same way as characters specified in hexadecimal.
340 For example:
341 <pre>
342 \040 is another way of writing a space
343 \40 is the same, provided there are fewer than 40 previous capturing subpatterns
344 \7 is always a back reference
345 \11 might be a back reference, or another way of writing a tab
346 \011 is always a tab
347 \0113 is a tab followed by the character "3"
348 \113 might be a back reference, otherwise the character with octal code 113
349 \377 might be a back reference, otherwise the value 255 (decimal)
350 \81 is either a back reference, or a binary zero followed by the two characters "8" and "1"
351 </pre>
352 Note that octal values of 100 or greater must not be introduced by a leading
353 zero, because no more than three octal digits are ever read.
354 </P>
355 <P>
356 All the sequences that define a single character value can be used both inside
357 and outside character classes. In addition, inside a character class, \b is
358 interpreted as the backspace character (hex 08).
359 </P>
360 <P>
361 \N is not allowed in a character class. \B, \R, and \X are not special
362 inside a character class. Like other unrecognized escape sequences, they are
363 treated as the literal characters "B", "R", and "X" by default, but cause an
364 error if the PCRE_EXTRA option is set. Outside a character class, these
365 sequences have different meanings.
366 </P>
367 <br><b>
368 Unsupported escape sequences
369 </b><br>
370 <P>
371 In Perl, the sequences \l, \L, \u, and \U are recognized by its string
372 handler and used to modify the case of following characters. By default, PCRE
373 does not support these escape sequences. However, if the PCRE_JAVASCRIPT_COMPAT
374 option is set, \U matches a "U" character, and \u can be used to define a
375 character by code point, as described in the previous section.
376 </P>
377 <br><b>
378 Absolute and relative back references
379 </b><br>
380 <P>
381 The sequence \g followed by an unsigned or a negative number, optionally
382 enclosed in braces, is an absolute or relative back reference. A named back
383 reference can be coded as \g{name}. Back references are discussed
384 <a href="#backreferences">later,</a>
385 following the discussion of
386 <a href="#subpattern">parenthesized subpatterns.</a>
387 </P>
388 <br><b>
389 Absolute and relative subroutine calls
390 </b><br>
391 <P>
392 For compatibility with Oniguruma, the non-Perl syntax \g followed by a name or
393 a number enclosed either in angle brackets or single quotes, is an alternative
394 syntax for referencing a subpattern as a "subroutine". Details are discussed
395 <a href="#onigurumasubroutines">later.</a>
396 Note that \g{...} (Perl syntax) and \g&#60;...&#62; (Oniguruma syntax) are <i>not</i>
397 synonymous. The former is a back reference; the latter is a
398 <a href="#subpatternsassubroutines">subroutine</a>
399 call.
400 <a name="genericchartypes"></a></P>
401 <br><b>
402 Generic character types
403 </b><br>
404 <P>
405 Another use of backslash is for specifying generic character types:
406 <pre>
407 \d any decimal digit
408 \D any character that is not a decimal digit
409 \h any horizontal whitespace character
410 \H any character that is not a horizontal whitespace character
411 \s any whitespace character
412 \S any character that is not a whitespace character
413 \v any vertical whitespace character
414 \V any character that is not a vertical whitespace character
415 \w any "word" character
416 \W any "non-word" character
417 </pre>
418 There is also the single sequence \N, which matches a non-newline character.
419 This is the same as
420 <a href="#fullstopdot">the "." metacharacter</a>
421 when PCRE_DOTALL is not set. Perl also uses \N to match characters by name;
422 PCRE does not support this.
423 </P>
424 <P>
425 Each pair of lower and upper case escape sequences partitions the complete set
426 of characters into two disjoint sets. Any given character matches one, and only
427 one, of each pair. The sequences can appear both inside and outside character
428 classes. They each match one character of the appropriate type. If the current
429 matching point is at the end of the subject string, all of them fail, because
430 there is no character to match.
431 </P>
432 <P>
433 For compatibility with Perl, \s does not match the VT character (code 11).
434 This makes it different from the the POSIX "space" class. The \s characters
435 are HT (9), LF (10), FF (12), CR (13), and space (32). If "use locale;" is
436 included in a Perl script, \s may match the VT character. In PCRE, it never
437 does.
438 </P>
439 <P>
440 A "word" character is an underscore or any character that is a letter or digit.
441 By default, the definition of letters and digits is controlled by PCRE's
442 low-valued character tables, and may vary if locale-specific matching is taking
443 place (see
444 <a href="pcreapi.html#localesupport">"Locale support"</a>
445 in the
446 <a href="pcreapi.html"><b>pcreapi</b></a>
447 page). For example, in a French locale such as "fr_FR" in Unix-like systems,
448 or "french" in Windows, some character codes greater than 128 are used for
449 accented letters, and these are then matched by \w. The use of locales with
450 Unicode is discouraged.
451 </P>
452 <P>
453 By default, in a UTF mode, characters with values greater than 128 never match
454 \d, \s, or \w, and always match \D, \S, and \W. These sequences retain
455 their original meanings from before UTF support was available, mainly for
456 efficiency reasons. However, if PCRE is compiled with Unicode property support,
457 and the PCRE_UCP option is set, the behaviour is changed so that Unicode
458 properties are used to determine character types, as follows:
459 <pre>
460 \d any character that \p{Nd} matches (decimal digit)
461 \s any character that \p{Z} matches, plus HT, LF, FF, CR
462 \w any character that \p{L} or \p{N} matches, plus underscore
463 </pre>
464 The upper case escapes match the inverse sets of characters. Note that \d
465 matches only decimal digits, whereas \w matches any Unicode digit, as well as
466 any Unicode letter, and underscore. Note also that PCRE_UCP affects \b, and
467 \B because they are defined in terms of \w and \W. Matching these sequences
468 is noticeably slower when PCRE_UCP is set.
469 </P>
470 <P>
471 The sequences \h, \H, \v, and \V are features that were added to Perl at
472 release 5.10. In contrast to the other sequences, which match only ASCII
473 characters by default, these always match certain high-valued codepoints,
474 whether or not PCRE_UCP is set. The horizontal space characters are:
475 <pre>
476 U+0009 Horizontal tab
477 U+0020 Space
478 U+00A0 Non-break space
479 U+1680 Ogham space mark
480 U+180E Mongolian vowel separator
481 U+2000 En quad
482 U+2001 Em quad
483 U+2002 En space
484 U+2003 Em space
485 U+2004 Three-per-em space
486 U+2005 Four-per-em space
487 U+2006 Six-per-em space
488 U+2007 Figure space
489 U+2008 Punctuation space
490 U+2009 Thin space
491 U+200A Hair space
492 U+202F Narrow no-break space
493 U+205F Medium mathematical space
494 U+3000 Ideographic space
495 </pre>
496 The vertical space characters are:
497 <pre>
498 U+000A Linefeed
499 U+000B Vertical tab
500 U+000C Formfeed
501 U+000D Carriage return
502 U+0085 Next line
503 U+2028 Line separator
504 U+2029 Paragraph separator
505 </pre>
506 In 8-bit, non-UTF-8 mode, only the characters with codepoints less than 256 are
507 relevant.
508 <a name="newlineseq"></a></P>
509 <br><b>
510 Newline sequences
511 </b><br>
512 <P>
513 Outside a character class, by default, the escape sequence \R matches any
514 Unicode newline sequence. In 8-bit non-UTF-8 mode \R is equivalent to the
515 following:
516 <pre>
517 (?&#62;\r\n|\n|\x0b|\f|\r|\x85)
518 </pre>
519 This is an example of an "atomic group", details of which are given
520 <a href="#atomicgroup">below.</a>
521 This particular group matches either the two-character sequence CR followed by
522 LF, or one of the single characters LF (linefeed, U+000A), VT (vertical tab,
523 U+000B), FF (formfeed, U+000C), CR (carriage return, U+000D), or NEL (next
524 line, U+0085). The two-character sequence is treated as a single unit that
525 cannot be split.
526 </P>
527 <P>
528 In other modes, two additional characters whose codepoints are greater than 255
529 are added: LS (line separator, U+2028) and PS (paragraph separator, U+2029).
530 Unicode character property support is not needed for these characters to be
531 recognized.
532 </P>
533 <P>
534 It is possible to restrict \R to match only CR, LF, or CRLF (instead of the
535 complete set of Unicode line endings) by setting the option PCRE_BSR_ANYCRLF
536 either at compile time or when the pattern is matched. (BSR is an abbrevation
537 for "backslash R".) This can be made the default when PCRE is built; if this is
538 the case, the other behaviour can be requested via the PCRE_BSR_UNICODE option.
539 It is also possible to specify these settings by starting a pattern string with
540 one of the following sequences:
541 <pre>
542 (*BSR_ANYCRLF) CR, LF, or CRLF only
543 (*BSR_UNICODE) any Unicode newline sequence
544 </pre>
545 These override the default and the options given to the compiling function, but
546 they can themselves be overridden by options given to a matching function. Note
547 that these special settings, which are not Perl-compatible, are recognized only
548 at the very start of a pattern, and that they must be in upper case. If more
549 than one of them is present, the last one is used. They can be combined with a
550 change of newline convention; for example, a pattern can start with:
551 <pre>
552 (*ANY)(*BSR_ANYCRLF)
553 </pre>
554 They can also be combined with the (*UTF8), (*UTF16), or (*UCP) special
555 sequences. Inside a character class, \R is treated as an unrecognized escape
556 sequence, and so matches the letter "R" by default, but causes an error if
557 PCRE_EXTRA is set.
558 <a name="uniextseq"></a></P>
559 <br><b>
560 Unicode character properties
561 </b><br>
562 <P>
563 When PCRE is built with Unicode character property support, three additional
564 escape sequences that match characters with specific properties are available.
565 When in 8-bit non-UTF-8 mode, these sequences are of course limited to testing
566 characters whose codepoints are less than 256, but they do work in this mode.
567 The extra escape sequences are:
568 <pre>
569 \p{<i>xx</i>} a character with the <i>xx</i> property
570 \P{<i>xx</i>} a character without the <i>xx</i> property
571 \X an extended Unicode sequence
572 </pre>
573 The property names represented by <i>xx</i> above are limited to the Unicode
574 script names, the general category properties, "Any", which matches any
575 character (including newline), and some special PCRE properties (described
576 in the
577 <a href="#extraprops">next section).</a>
578 Other Perl properties such as "InMusicalSymbols" are not currently supported by
579 PCRE. Note that \P{Any} does not match any characters, so always causes a
580 match failure.
581 </P>
582 <P>
583 Sets of Unicode characters are defined as belonging to certain scripts. A
584 character from one of these sets can be matched using a script name. For
585 example:
586 <pre>
587 \p{Greek}
588 \P{Han}
589 </pre>
590 Those that are not part of an identified script are lumped together as
591 "Common". The current list of scripts is:
592 </P>
593 <P>
594 Arabic,
595 Armenian,
596 Avestan,
597 Balinese,
598 Bamum,
599 Batak,
600 Bengali,
601 Bopomofo,
602 Brahmi,
603 Braille,
604 Buginese,
605 Buhid,
606 Canadian_Aboriginal,
607 Carian,
608 Chakma,
609 Cham,
610 Cherokee,
611 Common,
612 Coptic,
613 Cuneiform,
614 Cypriot,
615 Cyrillic,
616 Deseret,
617 Devanagari,
618 Egyptian_Hieroglyphs,
619 Ethiopic,
620 Georgian,
621 Glagolitic,
622 Gothic,
623 Greek,
624 Gujarati,
625 Gurmukhi,
626 Han,
627 Hangul,
628 Hanunoo,
629 Hebrew,
630 Hiragana,
631 Imperial_Aramaic,
632 Inherited,
633 Inscriptional_Pahlavi,
634 Inscriptional_Parthian,
635 Javanese,
636 Kaithi,
637 Kannada,
638 Katakana,
639 Kayah_Li,
640 Kharoshthi,
641 Khmer,
642 Lao,
643 Latin,
644 Lepcha,
645 Limbu,
646 Linear_B,
647 Lisu,
648 Lycian,
649 Lydian,
650 Malayalam,
651 Mandaic,
652 Meetei_Mayek,
653 Meroitic_Cursive,
654 Meroitic_Hieroglyphs,
655 Miao,
656 Mongolian,
657 Myanmar,
658 New_Tai_Lue,
659 Nko,
660 Ogham,
661 Old_Italic,
662 Old_Persian,
663 Old_South_Arabian,
664 Old_Turkic,
665 Ol_Chiki,
666 Oriya,
667 Osmanya,
668 Phags_Pa,
669 Phoenician,
670 Rejang,
671 Runic,
672 Samaritan,
673 Saurashtra,
674 Sharada,
675 Shavian,
676 Sinhala,
677 Sora_Sompeng,
678 Sundanese,
679 Syloti_Nagri,
680 Syriac,
681 Tagalog,
682 Tagbanwa,
683 Tai_Le,
684 Tai_Tham,
685 Tai_Viet,
686 Takri,
687 Tamil,
688 Telugu,
689 Thaana,
690 Thai,
691 Tibetan,
692 Tifinagh,
693 Ugaritic,
694 Vai,
695 Yi.
696 </P>
697 <P>
698 Each character has exactly one Unicode general category property, specified by
699 a two-letter abbreviation. For compatibility with Perl, negation can be
700 specified by including a circumflex between the opening brace and the property
701 name. For example, \p{^Lu} is the same as \P{Lu}.
702 </P>
703 <P>
704 If only one letter is specified with \p or \P, it includes all the general
705 category properties that start with that letter. In this case, in the absence
706 of negation, the curly brackets in the escape sequence are optional; these two
707 examples have the same effect:
708 <pre>
709 \p{L}
710 \pL
711 </pre>
712 The following general category property codes are supported:
713 <pre>
714 C Other
715 Cc Control
716 Cf Format
717 Cn Unassigned
718 Co Private use
719 Cs Surrogate
720
721 L Letter
722 Ll Lower case letter
723 Lm Modifier letter
724 Lo Other letter
725 Lt Title case letter
726 Lu Upper case letter
727
728 M Mark
729 Mc Spacing mark
730 Me Enclosing mark
731 Mn Non-spacing mark
732
733 N Number
734 Nd Decimal number
735 Nl Letter number
736 No Other number
737
738 P Punctuation
739 Pc Connector punctuation
740 Pd Dash punctuation
741 Pe Close punctuation
742 Pf Final punctuation
743 Pi Initial punctuation
744 Po Other punctuation
745 Ps Open punctuation
746
747 S Symbol
748 Sc Currency symbol
749 Sk Modifier symbol
750 Sm Mathematical symbol
751 So Other symbol
752
753 Z Separator
754 Zl Line separator
755 Zp Paragraph separator
756 Zs Space separator
757 </pre>
758 The special property L& is also supported: it matches a character that has
759 the Lu, Ll, or Lt property, in other words, a letter that is not classified as
760 a modifier or "other".
761 </P>
762 <P>
763 The Cs (Surrogate) property applies only to characters in the range U+D800 to
764 U+DFFF. Such characters are not valid in Unicode strings and so
765 cannot be tested by PCRE, unless UTF validity checking has been turned off
766 (see the discussion of PCRE_NO_UTF8_CHECK and PCRE_NO_UTF16_CHECK in the
767 <a href="pcreapi.html"><b>pcreapi</b></a>
768 page). Perl does not support the Cs property.
769 </P>
770 <P>
771 The long synonyms for property names that Perl supports (such as \p{Letter})
772 are not supported by PCRE, nor is it permitted to prefix any of these
773 properties with "Is".
774 </P>
775 <P>
776 No character that is in the Unicode table has the Cn (unassigned) property.
777 Instead, this property is assumed for any code point that is not in the
778 Unicode table.
779 </P>
780 <P>
781 Specifying caseless matching does not affect these escape sequences. For
782 example, \p{Lu} always matches only upper case letters.
783 </P>
784 <P>
785 The \X escape matches any number of Unicode characters that form an extended
786 Unicode sequence. \X is equivalent to
787 <pre>
788 (?&#62;\PM\pM*)
789 </pre>
790 That is, it matches a character without the "mark" property, followed by zero
791 or more characters with the "mark" property, and treats the sequence as an
792 atomic group
793 <a href="#atomicgroup">(see below).</a>
794 Characters with the "mark" property are typically accents that affect the
795 preceding character. None of them have codepoints less than 256, so in
796 8-bit non-UTF-8 mode \X matches any one character.
797 </P>
798 <P>
799 Note that recent versions of Perl have changed \X to match what Unicode calls
800 an "extended grapheme cluster", which has a more complicated definition.
801 </P>
802 <P>
803 Matching characters by Unicode property is not fast, because PCRE has to search
804 a structure that contains data for over fifteen thousand characters. That is
805 why the traditional escape sequences such as \d and \w do not use Unicode
806 properties in PCRE by default, though you can make them do so by setting the
807 PCRE_UCP option or by starting the pattern with (*UCP).
808 <a name="extraprops"></a></P>
809 <br><b>
810 PCRE's additional properties
811 </b><br>
812 <P>
813 As well as the standard Unicode properties described in the previous
814 section, PCRE supports four more that make it possible to convert traditional
815 escape sequences such as \w and \s and POSIX character classes to use Unicode
816 properties. PCRE uses these non-standard, non-Perl properties internally when
817 PCRE_UCP is set. They are:
818 <pre>
819 Xan Any alphanumeric character
820 Xps Any POSIX space character
821 Xsp Any Perl space character
822 Xwd Any Perl "word" character
823 </pre>
824 Xan matches characters that have either the L (letter) or the N (number)
825 property. Xps matches the characters tab, linefeed, vertical tab, formfeed, or
826 carriage return, and any other character that has the Z (separator) property.
827 Xsp is the same as Xps, except that vertical tab is excluded. Xwd matches the
828 same characters as Xan, plus underscore.
829 <a name="resetmatchstart"></a></P>
830 <br><b>
831 Resetting the match start
832 </b><br>
833 <P>
834 The escape sequence \K causes any previously matched characters not to be
835 included in the final matched sequence. For example, the pattern:
836 <pre>
837 foo\Kbar
838 </pre>
839 matches "foobar", but reports that it has matched "bar". This feature is
840 similar to a lookbehind assertion
841 <a href="#lookbehind">(described below).</a>
842 However, in this case, the part of the subject before the real match does not
843 have to be of fixed length, as lookbehind assertions do. The use of \K does
844 not interfere with the setting of
845 <a href="#subpattern">captured substrings.</a>
846 For example, when the pattern
847 <pre>
848 (foo)\Kbar
849 </pre>
850 matches "foobar", the first substring is still set to "foo".
851 </P>
852 <P>
853 Perl documents that the use of \K within assertions is "not well defined". In
854 PCRE, \K is acted upon when it occurs inside positive assertions, but is
855 ignored in negative assertions.
856 <a name="smallassertions"></a></P>
857 <br><b>
858 Simple assertions
859 </b><br>
860 <P>
861 The final use of backslash is for certain simple assertions. An assertion
862 specifies a condition that has to be met at a particular point in a match,
863 without consuming any characters from the subject string. The use of
864 subpatterns for more complicated assertions is described
865 <a href="#bigassertions">below.</a>
866 The backslashed assertions are:
867 <pre>
868 \b matches at a word boundary
869 \B matches when not at a word boundary
870 \A matches at the start of the subject
871 \Z matches at the end of the subject
872 also matches before a newline at the end of the subject
873 \z matches only at the end of the subject
874 \G matches at the first matching position in the subject
875 </pre>
876 Inside a character class, \b has a different meaning; it matches the backspace
877 character. If any other of these assertions appears in a character class, by
878 default it matches the corresponding literal character (for example, \B
879 matches the letter B). However, if the PCRE_EXTRA option is set, an "invalid
880 escape sequence" error is generated instead.
881 </P>
882 <P>
883 A word boundary is a position in the subject string where the current character
884 and the previous character do not both match \w or \W (i.e. one matches
885 \w and the other matches \W), or the start or end of the string if the
886 first or last character matches \w, respectively. In a UTF mode, the meanings
887 of \w and \W can be changed by setting the PCRE_UCP option. When this is
888 done, it also affects \b and \B. Neither PCRE nor Perl has a separate "start
889 of word" or "end of word" metasequence. However, whatever follows \b normally
890 determines which it is. For example, the fragment \ba matches "a" at the start
891 of a word.
892 </P>
893 <P>
894 The \A, \Z, and \z assertions differ from the traditional circumflex and
895 dollar (described in the next section) in that they only ever match at the very
896 start and end of the subject string, whatever options are set. Thus, they are
897 independent of multiline mode. These three assertions are not affected by the
898 PCRE_NOTBOL or PCRE_NOTEOL options, which affect only the behaviour of the
899 circumflex and dollar metacharacters. However, if the <i>startoffset</i>
900 argument of <b>pcre_exec()</b> is non-zero, indicating that matching is to start
901 at a point other than the beginning of the subject, \A can never match. The
902 difference between \Z and \z is that \Z matches before a newline at the end
903 of the string as well as at the very end, whereas \z matches only at the end.
904 </P>
905 <P>
906 The \G assertion is true only when the current matching position is at the
907 start point of the match, as specified by the <i>startoffset</i> argument of
908 <b>pcre_exec()</b>. It differs from \A when the value of <i>startoffset</i> is
909 non-zero. By calling <b>pcre_exec()</b> multiple times with appropriate
910 arguments, you can mimic Perl's /g option, and it is in this kind of
911 implementation where \G can be useful.
912 </P>
913 <P>
914 Note, however, that PCRE's interpretation of \G, as the start of the current
915 match, is subtly different from Perl's, which defines it as the end of the
916 previous match. In Perl, these can be different when the previously matched
917 string was empty. Because PCRE does just one match at a time, it cannot
918 reproduce this behaviour.
919 </P>
920 <P>
921 If all the alternatives of a pattern begin with \G, the expression is anchored
922 to the starting match position, and the "anchored" flag is set in the compiled
923 regular expression.
924 </P>
925 <br><a name="SEC5" href="#TOC1">CIRCUMFLEX AND DOLLAR</a><br>
926 <P>
927 Outside a character class, in the default matching mode, the circumflex
928 character is an assertion that is true only if the current matching point is
929 at the start of the subject string. If the <i>startoffset</i> argument of
930 <b>pcre_exec()</b> is non-zero, circumflex can never match if the PCRE_MULTILINE
931 option is unset. Inside a character class, circumflex has an entirely different
932 meaning
933 <a href="#characterclass">(see below).</a>
934 </P>
935 <P>
936 Circumflex need not be the first character of the pattern if a number of
937 alternatives are involved, but it should be the first thing in each alternative
938 in which it appears if the pattern is ever to match that branch. If all
939 possible alternatives start with a circumflex, that is, if the pattern is
940 constrained to match only at the start of the subject, it is said to be an
941 "anchored" pattern. (There are also other constructs that can cause a pattern
942 to be anchored.)
943 </P>
944 <P>
945 A dollar character is an assertion that is true only if the current matching
946 point is at the end of the subject string, or immediately before a newline
947 at the end of the string (by default). Dollar need not be the last character of
948 the pattern if a number of alternatives are involved, but it should be the last
949 item in any branch in which it appears. Dollar has no special meaning in a
950 character class.
951 </P>
952 <P>
953 The meaning of dollar can be changed so that it matches only at the very end of
954 the string, by setting the PCRE_DOLLAR_ENDONLY option at compile time. This
955 does not affect the \Z assertion.
956 </P>
957 <P>
958 The meanings of the circumflex and dollar characters are changed if the
959 PCRE_MULTILINE option is set. When this is the case, a circumflex matches
960 immediately after internal newlines as well as at the start of the subject
961 string. It does not match after a newline that ends the string. A dollar
962 matches before any newlines in the string, as well as at the very end, when
963 PCRE_MULTILINE is set. When newline is specified as the two-character
964 sequence CRLF, isolated CR and LF characters do not indicate newlines.
965 </P>
966 <P>
967 For example, the pattern /^abc$/ matches the subject string "def\nabc" (where
968 \n represents a newline) in multiline mode, but not otherwise. Consequently,
969 patterns that are anchored in single line mode because all branches start with
970 ^ are not anchored in multiline mode, and a match for circumflex is possible
971 when the <i>startoffset</i> argument of <b>pcre_exec()</b> is non-zero. The
972 PCRE_DOLLAR_ENDONLY option is ignored if PCRE_MULTILINE is set.
973 </P>
974 <P>
975 Note that the sequences \A, \Z, and \z can be used to match the start and
976 end of the subject in both modes, and if all branches of a pattern start with
977 \A it is always anchored, whether or not PCRE_MULTILINE is set.
978 <a name="fullstopdot"></a></P>
979 <br><a name="SEC6" href="#TOC1">FULL STOP (PERIOD, DOT) AND \N</a><br>
980 <P>
981 Outside a character class, a dot in the pattern matches any one character in
982 the subject string except (by default) a character that signifies the end of a
983 line.
984 </P>
985 <P>
986 When a line ending is defined as a single character, dot never matches that
987 character; when the two-character sequence CRLF is used, dot does not match CR
988 if it is immediately followed by LF, but otherwise it matches all characters
989 (including isolated CRs and LFs). When any Unicode line endings are being
990 recognized, dot does not match CR or LF or any of the other line ending
991 characters.
992 </P>
993 <P>
994 The behaviour of dot with regard to newlines can be changed. If the PCRE_DOTALL
995 option is set, a dot matches any one character, without exception. If the
996 two-character sequence CRLF is present in the subject string, it takes two dots
997 to match it.
998 </P>
999 <P>
1000 The handling of dot is entirely independent of the handling of circumflex and
1001 dollar, the only relationship being that they both involve newlines. Dot has no
1002 special meaning in a character class.
1003 </P>
1004 <P>
1005 The escape sequence \N behaves like a dot, except that it is not affected by
1006 the PCRE_DOTALL option. In other words, it matches any character except one
1007 that signifies the end of a line. Perl also uses \N to match characters by
1008 name; PCRE does not support this.
1009 </P>
1010 <br><a name="SEC7" href="#TOC1">MATCHING A SINGLE DATA UNIT</a><br>
1011 <P>
1012 Outside a character class, the escape sequence \C matches any one data unit,
1013 whether or not a UTF mode is set. In the 8-bit library, one data unit is one
1014 byte; in the 16-bit library it is a 16-bit unit. Unlike a dot, \C always
1015 matches line-ending characters. The feature is provided in Perl in order to
1016 match individual bytes in UTF-8 mode, but it is unclear how it can usefully be
1017 used. Because \C breaks up characters into individual data units, matching one
1018 unit with \C in a UTF mode means that the rest of the string may start with a
1019 malformed UTF character. This has undefined results, because PCRE assumes that
1020 it is dealing with valid UTF strings (and by default it checks this at the
1021 start of processing unless the PCRE_NO_UTF8_CHECK or PCRE_NO_UTF16_CHECK option
1022 is used).
1023 </P>
1024 <P>
1025 PCRE does not allow \C to appear in lookbehind assertions
1026 <a href="#lookbehind">(described below)</a>
1027 in a UTF mode, because this would make it impossible to calculate the length of
1028 the lookbehind.
1029 </P>
1030 <P>
1031 In general, the \C escape sequence is best avoided. However, one
1032 way of using it that avoids the problem of malformed UTF characters is to use a
1033 lookahead to check the length of the next character, as in this pattern, which
1034 could be used with a UTF-8 string (ignore white space and line breaks):
1035 <pre>
1036 (?| (?=[\x00-\x7f])(\C) |
1037 (?=[\x80-\x{7ff}])(\C)(\C) |
1038 (?=[\x{800}-\x{ffff}])(\C)(\C)(\C) |
1039 (?=[\x{10000}-\x{1fffff}])(\C)(\C)(\C)(\C))
1040 </pre>
1041 A group that starts with (?| resets the capturing parentheses numbers in each
1042 alternative (see
1043 <a href="#dupsubpatternnumber">"Duplicate Subpattern Numbers"</a>
1044 below). The assertions at the start of each branch check the next UTF-8
1045 character for values whose encoding uses 1, 2, 3, or 4 bytes, respectively. The
1046 character's individual bytes are then captured by the appropriate number of
1047 groups.
1048 <a name="characterclass"></a></P>
1049 <br><a name="SEC8" href="#TOC1">SQUARE BRACKETS AND CHARACTER CLASSES</a><br>
1050 <P>
1051 An opening square bracket introduces a character class, terminated by a closing
1052 square bracket. A closing square bracket on its own is not special by default.
1053 However, if the PCRE_JAVASCRIPT_COMPAT option is set, a lone closing square
1054 bracket causes a compile-time error. If a closing square bracket is required as
1055 a member of the class, it should be the first data character in the class
1056 (after an initial circumflex, if present) or escaped with a backslash.
1057 </P>
1058 <P>
1059 A character class matches a single character in the subject. In a UTF mode, the
1060 character may be more than one data unit long. A matched character must be in
1061 the set of characters defined by the class, unless the first character in the
1062 class definition is a circumflex, in which case the subject character must not
1063 be in the set defined by the class. If a circumflex is actually required as a
1064 member of the class, ensure it is not the first character, or escape it with a
1065 backslash.
1066 </P>
1067 <P>
1068 For example, the character class [aeiou] matches any lower case vowel, while
1069 [^aeiou] matches any character that is not a lower case vowel. Note that a
1070 circumflex is just a convenient notation for specifying the characters that
1071 are in the class by enumerating those that are not. A class that starts with a
1072 circumflex is not an assertion; it still consumes a character from the subject
1073 string, and therefore it fails if the current pointer is at the end of the
1074 string.
1075 </P>
1076 <P>
1077 In UTF-8 (UTF-16) mode, characters with values greater than 255 (0xffff) can be
1078 included in a class as a literal string of data units, or by using the \x{
1079 escaping mechanism.
1080 </P>
1081 <P>
1082 When caseless matching is set, any letters in a class represent both their
1083 upper case and lower case versions, so for example, a caseless [aeiou] matches
1084 "A" as well as "a", and a caseless [^aeiou] does not match "A", whereas a
1085 caseful version would. In a UTF mode, PCRE always understands the concept of
1086 case for characters whose values are less than 128, so caseless matching is
1087 always possible. For characters with higher values, the concept of case is
1088 supported if PCRE is compiled with Unicode property support, but not otherwise.
1089 If you want to use caseless matching in a UTF mode for characters 128 and
1090 above, you must ensure that PCRE is compiled with Unicode property support as
1091 well as with UTF support.
1092 </P>
1093 <P>
1094 Characters that might indicate line breaks are never treated in any special way
1095 when matching character classes, whatever line-ending sequence is in use, and
1096 whatever setting of the PCRE_DOTALL and PCRE_MULTILINE options is used. A class
1097 such as [^a] always matches one of these characters.
1098 </P>
1099 <P>
1100 The minus (hyphen) character can be used to specify a range of characters in a
1101 character class. For example, [d-m] matches any letter between d and m,
1102 inclusive. If a minus character is required in a class, it must be escaped with
1103 a backslash or appear in a position where it cannot be interpreted as
1104 indicating a range, typically as the first or last character in the class.
1105 </P>
1106 <P>
1107 It is not possible to have the literal character "]" as the end character of a
1108 range. A pattern such as [W-]46] is interpreted as a class of two characters
1109 ("W" and "-") followed by a literal string "46]", so it would match "W46]" or
1110 "-46]". However, if the "]" is escaped with a backslash it is interpreted as
1111 the end of range, so [W-\]46] is interpreted as a class containing a range
1112 followed by two other characters. The octal or hexadecimal representation of
1113 "]" can also be used to end a range.
1114 </P>
1115 <P>
1116 Ranges operate in the collating sequence of character values. They can also be
1117 used for characters specified numerically, for example [\000-\037]. Ranges
1118 can include any characters that are valid for the current mode.
1119 </P>
1120 <P>
1121 If a range that includes letters is used when caseless matching is set, it
1122 matches the letters in either case. For example, [W-c] is equivalent to
1123 [][\\^_`wxyzabc], matched caselessly, and in a non-UTF mode, if character
1124 tables for a French locale are in use, [\xc8-\xcb] matches accented E
1125 characters in both cases. In UTF modes, PCRE supports the concept of case for
1126 characters with values greater than 128 only when it is compiled with Unicode
1127 property support.
1128 </P>
1129 <P>
1130 The character escape sequences \d, \D, \h, \H, \p, \P, \s, \S, \v,
1131 \V, \w, and \W may appear in a character class, and add the characters that
1132 they match to the class. For example, [\dABCDEF] matches any hexadecimal
1133 digit. In UTF modes, the PCRE_UCP option affects the meanings of \d, \s, \w
1134 and their upper case partners, just as it does when they appear outside a
1135 character class, as described in the section entitled
1136 <a href="#genericchartypes">"Generic character types"</a>
1137 above. The escape sequence \b has a different meaning inside a character
1138 class; it matches the backspace character. The sequences \B, \N, \R, and \X
1139 are not special inside a character class. Like any other unrecognized escape
1140 sequences, they are treated as the literal characters "B", "N", "R", and "X" by
1141 default, but cause an error if the PCRE_EXTRA option is set.
1142 </P>
1143 <P>
1144 A circumflex can conveniently be used with the upper case character types to
1145 specify a more restricted set of characters than the matching lower case type.
1146 For example, the class [^\W_] matches any letter or digit, but not underscore,
1147 whereas [\w] includes underscore. A positive character class should be read as
1148 "something OR something OR ..." and a negative class as "NOT something AND NOT
1149 something AND NOT ...".
1150 </P>
1151 <P>
1152 The only metacharacters that are recognized in character classes are backslash,
1153 hyphen (only where it can be interpreted as specifying a range), circumflex
1154 (only at the start), opening square bracket (only when it can be interpreted as
1155 introducing a POSIX class name - see the next section), and the terminating
1156 closing square bracket. However, escaping other non-alphanumeric characters
1157 does no harm.
1158 </P>
1159 <br><a name="SEC9" href="#TOC1">POSIX CHARACTER CLASSES</a><br>
1160 <P>
1161 Perl supports the POSIX notation for character classes. This uses names
1162 enclosed by [: and :] within the enclosing square brackets. PCRE also supports
1163 this notation. For example,
1164 <pre>
1165 [01[:alpha:]%]
1166 </pre>
1167 matches "0", "1", any alphabetic character, or "%". The supported class names
1168 are:
1169 <pre>
1170 alnum letters and digits
1171 alpha letters
1172 ascii character codes 0 - 127
1173 blank space or tab only
1174 cntrl control characters
1175 digit decimal digits (same as \d)
1176 graph printing characters, excluding space
1177 lower lower case letters
1178 print printing characters, including space
1179 punct printing characters, excluding letters and digits and space
1180 space white space (not quite the same as \s)
1181 upper upper case letters
1182 word "word" characters (same as \w)
1183 xdigit hexadecimal digits
1184 </pre>
1185 The "space" characters are HT (9), LF (10), VT (11), FF (12), CR (13), and
1186 space (32). Notice that this list includes the VT character (code 11). This
1187 makes "space" different to \s, which does not include VT (for Perl
1188 compatibility).
1189 </P>
1190 <P>
1191 The name "word" is a Perl extension, and "blank" is a GNU extension from Perl
1192 5.8. Another Perl extension is negation, which is indicated by a ^ character
1193 after the colon. For example,
1194 <pre>
1195 [12[:^digit:]]
1196 </pre>
1197 matches "1", "2", or any non-digit. PCRE (and Perl) also recognize the POSIX
1198 syntax [.ch.] and [=ch=] where "ch" is a "collating element", but these are not
1199 supported, and an error is given if they are encountered.
1200 </P>
1201 <P>
1202 By default, in UTF modes, characters with values greater than 128 do not match
1203 any of the POSIX character classes. However, if the PCRE_UCP option is passed
1204 to <b>pcre_compile()</b>, some of the classes are changed so that Unicode
1205 character properties are used. This is achieved by replacing the POSIX classes
1206 by other sequences, as follows:
1207 <pre>
1208 [:alnum:] becomes \p{Xan}
1209 [:alpha:] becomes \p{L}
1210 [:blank:] becomes \h
1211 [:digit:] becomes \p{Nd}
1212 [:lower:] becomes \p{Ll}
1213 [:space:] becomes \p{Xps}
1214 [:upper:] becomes \p{Lu}
1215 [:word:] becomes \p{Xwd}
1216 </pre>
1217 Negated versions, such as [:^alpha:] use \P instead of \p. The other POSIX
1218 classes are unchanged, and match only characters with code points less than
1219 128.
1220 </P>
1221 <br><a name="SEC10" href="#TOC1">VERTICAL BAR</a><br>
1222 <P>
1223 Vertical bar characters are used to separate alternative patterns. For example,
1224 the pattern
1225 <pre>
1226 gilbert|sullivan
1227 </pre>
1228 matches either "gilbert" or "sullivan". Any number of alternatives may appear,
1229 and an empty alternative is permitted (matching the empty string). The matching
1230 process tries each alternative in turn, from left to right, and the first one
1231 that succeeds is used. If the alternatives are within a subpattern
1232 <a href="#subpattern">(defined below),</a>
1233 "succeeds" means matching the rest of the main pattern as well as the
1234 alternative in the subpattern.
1235 </P>
1236 <br><a name="SEC11" href="#TOC1">INTERNAL OPTION SETTING</a><br>
1237 <P>
1238 The settings of the PCRE_CASELESS, PCRE_MULTILINE, PCRE_DOTALL, and
1239 PCRE_EXTENDED options (which are Perl-compatible) can be changed from within
1240 the pattern by a sequence of Perl option letters enclosed between "(?" and ")".
1241 The option letters are
1242 <pre>
1243 i for PCRE_CASELESS
1244 m for PCRE_MULTILINE
1245 s for PCRE_DOTALL
1246 x for PCRE_EXTENDED
1247 </pre>
1248 For example, (?im) sets caseless, multiline matching. It is also possible to
1249 unset these options by preceding the letter with a hyphen, and a combined
1250 setting and unsetting such as (?im-sx), which sets PCRE_CASELESS and
1251 PCRE_MULTILINE while unsetting PCRE_DOTALL and PCRE_EXTENDED, is also
1252 permitted. If a letter appears both before and after the hyphen, the option is
1253 unset.
1254 </P>
1255 <P>
1256 The PCRE-specific options PCRE_DUPNAMES, PCRE_UNGREEDY, and PCRE_EXTRA can be
1257 changed in the same way as the Perl-compatible options by using the characters
1258 J, U and X respectively.
1259 </P>
1260 <P>
1261 When one of these option changes occurs at top level (that is, not inside
1262 subpattern parentheses), the change applies to the remainder of the pattern
1263 that follows. If the change is placed right at the start of a pattern, PCRE
1264 extracts it into the global options (and it will therefore show up in data
1265 extracted by the <b>pcre_fullinfo()</b> function).
1266 </P>
1267 <P>
1268 An option change within a subpattern (see below for a description of
1269 subpatterns) affects only that part of the subpattern that follows it, so
1270 <pre>
1271 (a(?i)b)c
1272 </pre>
1273 matches abc and aBc and no other strings (assuming PCRE_CASELESS is not used).
1274 By this means, options can be made to have different settings in different
1275 parts of the pattern. Any changes made in one alternative do carry on
1276 into subsequent branches within the same subpattern. For example,
1277 <pre>
1278 (a(?i)b|c)
1279 </pre>
1280 matches "ab", "aB", "c", and "C", even though when matching "C" the first
1281 branch is abandoned before the option setting. This is because the effects of
1282 option settings happen at compile time. There would be some very weird
1283 behaviour otherwise.
1284 </P>
1285 <P>
1286 <b>Note:</b> There are other PCRE-specific options that can be set by the
1287 application when the compiling or matching functions are called. In some cases
1288 the pattern can contain special leading sequences such as (*CRLF) to override
1289 what the application has set or what has been defaulted. Details are given in
1290 the section entitled
1291 <a href="#newlineseq">"Newline sequences"</a>
1292 above. There are also the (*UTF8), (*UTF16), and (*UCP) leading sequences that
1293 can be used to set UTF and Unicode property modes; they are equivalent to
1294 setting the PCRE_UTF8, PCRE_UTF16, and the PCRE_UCP options, respectively.
1295 <a name="subpattern"></a></P>
1296 <br><a name="SEC12" href="#TOC1">SUBPATTERNS</a><br>
1297 <P>
1298 Subpatterns are delimited by parentheses (round brackets), which can be nested.
1299 Turning part of a pattern into a subpattern does two things:
1300 <br>
1301 <br>
1302 1. It localizes a set of alternatives. For example, the pattern
1303 <pre>
1304 cat(aract|erpillar|)
1305 </pre>
1306 matches "cataract", "caterpillar", or "cat". Without the parentheses, it would
1307 match "cataract", "erpillar" or an empty string.
1308 <br>
1309 <br>
1310 2. It sets up the subpattern as a capturing subpattern. This means that, when
1311 the whole pattern matches, that portion of the subject string that matched the
1312 subpattern is passed back to the caller via the <i>ovector</i> argument of the
1313 matching function. (This applies only to the traditional matching functions;
1314 the DFA matching functions do not support capturing.)
1315 </P>
1316 <P>
1317 Opening parentheses are counted from left to right (starting from 1) to obtain
1318 numbers for the capturing subpatterns. For example, if the string "the red
1319 king" is matched against the pattern
1320 <pre>
1321 the ((red|white) (king|queen))
1322 </pre>
1323 the captured substrings are "red king", "red", and "king", and are numbered 1,
1324 2, and 3, respectively.
1325 </P>
1326 <P>
1327 The fact that plain parentheses fulfil two functions is not always helpful.
1328 There are often times when a grouping subpattern is required without a
1329 capturing requirement. If an opening parenthesis is followed by a question mark
1330 and a colon, the subpattern does not do any capturing, and is not counted when
1331 computing the number of any subsequent capturing subpatterns. For example, if
1332 the string "the white queen" is matched against the pattern
1333 <pre>
1334 the ((?:red|white) (king|queen))
1335 </pre>
1336 the captured substrings are "white queen" and "queen", and are numbered 1 and
1337 2. The maximum number of capturing subpatterns is 65535.
1338 </P>
1339 <P>
1340 As a convenient shorthand, if any option settings are required at the start of
1341 a non-capturing subpattern, the option letters may appear between the "?" and
1342 the ":". Thus the two patterns
1343 <pre>
1344 (?i:saturday|sunday)
1345 (?:(?i)saturday|sunday)
1346 </pre>
1347 match exactly the same set of strings. Because alternative branches are tried
1348 from left to right, and options are not reset until the end of the subpattern
1349 is reached, an option setting in one branch does affect subsequent branches, so
1350 the above patterns match "SUNDAY" as well as "Saturday".
1351 <a name="dupsubpatternnumber"></a></P>
1352 <br><a name="SEC13" href="#TOC1">DUPLICATE SUBPATTERN NUMBERS</a><br>
1353 <P>
1354 Perl 5.10 introduced a feature whereby each alternative in a subpattern uses
1355 the same numbers for its capturing parentheses. Such a subpattern starts with
1356 (?| and is itself a non-capturing subpattern. For example, consider this
1357 pattern:
1358 <pre>
1359 (?|(Sat)ur|(Sun))day
1360 </pre>
1361 Because the two alternatives are inside a (?| group, both sets of capturing
1362 parentheses are numbered one. Thus, when the pattern matches, you can look
1363 at captured substring number one, whichever alternative matched. This construct
1364 is useful when you want to capture part, but not all, of one of a number of
1365 alternatives. Inside a (?| group, parentheses are numbered as usual, but the
1366 number is reset at the start of each branch. The numbers of any capturing
1367 parentheses that follow the subpattern start after the highest number used in
1368 any branch. The following example is taken from the Perl documentation. The
1369 numbers underneath show in which buffer the captured content will be stored.
1370 <pre>
1371 # before ---------------branch-reset----------- after
1372 / ( a ) (?| x ( y ) z | (p (q) r) | (t) u (v) ) ( z ) /x
1373 # 1 2 2 3 2 3 4
1374 </pre>
1375 A back reference to a numbered subpattern uses the most recent value that is
1376 set for that number by any subpattern. The following pattern matches "abcabc"
1377 or "defdef":
1378 <pre>
1379 /(?|(abc)|(def))\1/
1380 </pre>
1381 In contrast, a subroutine call to a numbered subpattern always refers to the
1382 first one in the pattern with the given number. The following pattern matches
1383 "abcabc" or "defabc":
1384 <pre>
1385 /(?|(abc)|(def))(?1)/
1386 </pre>
1387 If a
1388 <a href="#conditions">condition test</a>
1389 for a subpattern's having matched refers to a non-unique number, the test is
1390 true if any of the subpatterns of that number have matched.
1391 </P>
1392 <P>
1393 An alternative approach to using this "branch reset" feature is to use
1394 duplicate named subpatterns, as described in the next section.
1395 </P>
1396 <br><a name="SEC14" href="#TOC1">NAMED SUBPATTERNS</a><br>
1397 <P>
1398 Identifying capturing parentheses by number is simple, but it can be very hard
1399 to keep track of the numbers in complicated regular expressions. Furthermore,
1400 if an expression is modified, the numbers may change. To help with this
1401 difficulty, PCRE supports the naming of subpatterns. This feature was not
1402 added to Perl until release 5.10. Python had the feature earlier, and PCRE
1403 introduced it at release 4.0, using the Python syntax. PCRE now supports both
1404 the Perl and the Python syntax. Perl allows identically numbered subpatterns to
1405 have different names, but PCRE does not.
1406 </P>
1407 <P>
1408 In PCRE, a subpattern can be named in one of three ways: (?&#60;name&#62;...) or
1409 (?'name'...) as in Perl, or (?P&#60;name&#62;...) as in Python. References to capturing
1410 parentheses from other parts of the pattern, such as
1411 <a href="#backreferences">back references,</a>
1412 <a href="#recursion">recursion,</a>
1413 and
1414 <a href="#conditions">conditions,</a>
1415 can be made by name as well as by number.
1416 </P>
1417 <P>
1418 Names consist of up to 32 alphanumeric characters and underscores. Named
1419 capturing parentheses are still allocated numbers as well as names, exactly as
1420 if the names were not present. The PCRE API provides function calls for
1421 extracting the name-to-number translation table from a compiled pattern. There
1422 is also a convenience function for extracting a captured substring by name.
1423 </P>
1424 <P>
1425 By default, a name must be unique within a pattern, but it is possible to relax
1426 this constraint by setting the PCRE_DUPNAMES option at compile time. (Duplicate
1427 names are also always permitted for subpatterns with the same number, set up as
1428 described in the previous section.) Duplicate names can be useful for patterns
1429 where only one instance of the named parentheses can match. Suppose you want to
1430 match the name of a weekday, either as a 3-letter abbreviation or as the full
1431 name, and in both cases you want to extract the abbreviation. This pattern
1432 (ignoring the line breaks) does the job:
1433 <pre>
1434 (?&#60;DN&#62;Mon|Fri|Sun)(?:day)?|
1435 (?&#60;DN&#62;Tue)(?:sday)?|
1436 (?&#60;DN&#62;Wed)(?:nesday)?|
1437 (?&#60;DN&#62;Thu)(?:rsday)?|
1438 (?&#60;DN&#62;Sat)(?:urday)?
1439 </pre>
1440 There are five capturing substrings, but only one is ever set after a match.
1441 (An alternative way of solving this problem is to use a "branch reset"
1442 subpattern, as described in the previous section.)
1443 </P>
1444 <P>
1445 The convenience function for extracting the data by name returns the substring
1446 for the first (and in this example, the only) subpattern of that name that
1447 matched. This saves searching to find which numbered subpattern it was.
1448 </P>
1449 <P>
1450 If you make a back reference to a non-unique named subpattern from elsewhere in
1451 the pattern, the one that corresponds to the first occurrence of the name is
1452 used. In the absence of duplicate numbers (see the previous section) this is
1453 the one with the lowest number. If you use a named reference in a condition
1454 test (see the
1455 <a href="#conditions">section about conditions</a>
1456 below), either to check whether a subpattern has matched, or to check for
1457 recursion, all subpatterns with the same name are tested. If the condition is
1458 true for any one of them, the overall condition is true. This is the same
1459 behaviour as testing by number. For further details of the interfaces for
1460 handling named subpatterns, see the
1461 <a href="pcreapi.html"><b>pcreapi</b></a>
1462 documentation.
1463 </P>
1464 <P>
1465 <b>Warning:</b> You cannot use different names to distinguish between two
1466 subpatterns with the same number because PCRE uses only the numbers when
1467 matching. For this reason, an error is given at compile time if different names
1468 are given to subpatterns with the same number. However, you can give the same
1469 name to subpatterns with the same number, even when PCRE_DUPNAMES is not set.
1470 </P>
1471 <br><a name="SEC15" href="#TOC1">REPETITION</a><br>
1472 <P>
1473 Repetition is specified by quantifiers, which can follow any of the following
1474 items:
1475 <pre>
1476 a literal data character
1477 the dot metacharacter
1478 the \C escape sequence
1479 the \X escape sequence
1480 the \R escape sequence
1481 an escape such as \d or \pL that matches a single character
1482 a character class
1483 a back reference (see next section)
1484 a parenthesized subpattern (including assertions)
1485 a subroutine call to a subpattern (recursive or otherwise)
1486 </pre>
1487 The general repetition quantifier specifies a minimum and maximum number of
1488 permitted matches, by giving the two numbers in curly brackets (braces),
1489 separated by a comma. The numbers must be less than 65536, and the first must
1490 be less than or equal to the second. For example:
1491 <pre>
1492 z{2,4}
1493 </pre>
1494 matches "zz", "zzz", or "zzzz". A closing brace on its own is not a special
1495 character. If the second number is omitted, but the comma is present, there is
1496 no upper limit; if the second number and the comma are both omitted, the
1497 quantifier specifies an exact number of required matches. Thus
1498 <pre>
1499 [aeiou]{3,}
1500 </pre>
1501 matches at least 3 successive vowels, but may match many more, while
1502 <pre>
1503 \d{8}
1504 </pre>
1505 matches exactly 8 digits. An opening curly bracket that appears in a position
1506 where a quantifier is not allowed, or one that does not match the syntax of a
1507 quantifier, is taken as a literal character. For example, {,6} is not a
1508 quantifier, but a literal string of four characters.
1509 </P>
1510 <P>
1511 In UTF modes, quantifiers apply to characters rather than to individual data
1512 units. Thus, for example, \x{100}{2} matches two characters, each of
1513 which is represented by a two-byte sequence in a UTF-8 string. Similarly,
1514 \X{3} matches three Unicode extended sequences, each of which may be several
1515 data units long (and they may be of different lengths).
1516 </P>
1517 <P>
1518 The quantifier {0} is permitted, causing the expression to behave as if the
1519 previous item and the quantifier were not present. This may be useful for
1520 subpatterns that are referenced as
1521 <a href="#subpatternsassubroutines">subroutines</a>
1522 from elsewhere in the pattern (but see also the section entitled
1523 <a href="#subdefine">"Defining subpatterns for use by reference only"</a>
1524 below). Items other than subpatterns that have a {0} quantifier are omitted
1525 from the compiled pattern.
1526 </P>
1527 <P>
1528 For convenience, the three most common quantifiers have single-character
1529 abbreviations:
1530 <pre>
1531 * is equivalent to {0,}
1532 + is equivalent to {1,}
1533 ? is equivalent to {0,1}
1534 </pre>
1535 It is possible to construct infinite loops by following a subpattern that can
1536 match no characters with a quantifier that has no upper limit, for example:
1537 <pre>
1538 (a?)*
1539 </pre>
1540 Earlier versions of Perl and PCRE used to give an error at compile time for
1541 such patterns. However, because there are cases where this can be useful, such
1542 patterns are now accepted, but if any repetition of the subpattern does in fact
1543 match no characters, the loop is forcibly broken.
1544 </P>
1545 <P>
1546 By default, the quantifiers are "greedy", that is, they match as much as
1547 possible (up to the maximum number of permitted times), without causing the
1548 rest of the pattern to fail. The classic example of where this gives problems
1549 is in trying to match comments in C programs. These appear between /* and */
1550 and within the comment, individual * and / characters may appear. An attempt to
1551 match C comments by applying the pattern
1552 <pre>
1553 /\*.*\*/
1554 </pre>
1555 to the string
1556 <pre>
1557 /* first comment */ not comment /* second comment */
1558 </pre>
1559 fails, because it matches the entire string owing to the greediness of the .*
1560 item.
1561 </P>
1562 <P>
1563 However, if a quantifier is followed by a question mark, it ceases to be
1564 greedy, and instead matches the minimum number of times possible, so the
1565 pattern
1566 <pre>
1567 /\*.*?\*/
1568 </pre>
1569 does the right thing with the C comments. The meaning of the various
1570 quantifiers is not otherwise changed, just the preferred number of matches.
1571 Do not confuse this use of question mark with its use as a quantifier in its
1572 own right. Because it has two uses, it can sometimes appear doubled, as in
1573 <pre>
1574 \d??\d
1575 </pre>
1576 which matches one digit by preference, but can match two if that is the only
1577 way the rest of the pattern matches.
1578 </P>
1579 <P>
1580 If the PCRE_UNGREEDY option is set (an option that is not available in Perl),
1581 the quantifiers are not greedy by default, but individual ones can be made
1582 greedy by following them with a question mark. In other words, it inverts the
1583 default behaviour.
1584 </P>
1585 <P>
1586 When a parenthesized subpattern is quantified with a minimum repeat count that
1587 is greater than 1 or with a limited maximum, more memory is required for the
1588 compiled pattern, in proportion to the size of the minimum or maximum.
1589 </P>
1590 <P>
1591 If a pattern starts with .* or .{0,} and the PCRE_DOTALL option (equivalent
1592 to Perl's /s) is set, thus allowing the dot to match newlines, the pattern is
1593 implicitly anchored, because whatever follows will be tried against every
1594 character position in the subject string, so there is no point in retrying the
1595 overall match at any position after the first. PCRE normally treats such a
1596 pattern as though it were preceded by \A.
1597 </P>
1598 <P>
1599 In cases where it is known that the subject string contains no newlines, it is
1600 worth setting PCRE_DOTALL in order to obtain this optimization, or
1601 alternatively using ^ to indicate anchoring explicitly.
1602 </P>
1603 <P>
1604 However, there is one situation where the optimization cannot be used. When .*
1605 is inside capturing parentheses that are the subject of a back reference
1606 elsewhere in the pattern, a match at the start may fail where a later one
1607 succeeds. Consider, for example:
1608 <pre>
1609 (.*)abc\1
1610 </pre>
1611 If the subject is "xyz123abc123" the match point is the fourth character. For
1612 this reason, such a pattern is not implicitly anchored.
1613 </P>
1614 <P>
1615 When a capturing subpattern is repeated, the value captured is the substring
1616 that matched the final iteration. For example, after
1617 <pre>
1618 (tweedle[dume]{3}\s*)+
1619 </pre>
1620 has matched "tweedledum tweedledee" the value of the captured substring is
1621 "tweedledee". However, if there are nested capturing subpatterns, the
1622 corresponding captured values may have been set in previous iterations. For
1623 example, after
1624 <pre>
1625 /(a|(b))+/
1626 </pre>
1627 matches "aba" the value of the second captured substring is "b".
1628 <a name="atomicgroup"></a></P>
1629 <br><a name="SEC16" href="#TOC1">ATOMIC GROUPING AND POSSESSIVE QUANTIFIERS</a><br>
1630 <P>
1631 With both maximizing ("greedy") and minimizing ("ungreedy" or "lazy")
1632 repetition, failure of what follows normally causes the repeated item to be
1633 re-evaluated to see if a different number of repeats allows the rest of the
1634 pattern to match. Sometimes it is useful to prevent this, either to change the
1635 nature of the match, or to cause it fail earlier than it otherwise might, when
1636 the author of the pattern knows there is no point in carrying on.
1637 </P>
1638 <P>
1639 Consider, for example, the pattern \d+foo when applied to the subject line
1640 <pre>
1641 123456bar
1642 </pre>
1643 After matching all 6 digits and then failing to match "foo", the normal
1644 action of the matcher is to try again with only 5 digits matching the \d+
1645 item, and then with 4, and so on, before ultimately failing. "Atomic grouping"
1646 (a term taken from Jeffrey Friedl's book) provides the means for specifying
1647 that once a subpattern has matched, it is not to be re-evaluated in this way.
1648 </P>
1649 <P>
1650 If we use atomic grouping for the previous example, the matcher gives up
1651 immediately on failing to match "foo" the first time. The notation is a kind of
1652 special parenthesis, starting with (?&#62; as in this example:
1653 <pre>
1654 (?&#62;\d+)foo
1655 </pre>
1656 This kind of parenthesis "locks up" the part of the pattern it contains once
1657 it has matched, and a failure further into the pattern is prevented from
1658 backtracking into it. Backtracking past it to previous items, however, works as
1659 normal.
1660 </P>
1661 <P>
1662 An alternative description is that a subpattern of this type matches the string
1663 of characters that an identical standalone pattern would match, if anchored at
1664 the current point in the subject string.
1665 </P>
1666 <P>
1667 Atomic grouping subpatterns are not capturing subpatterns. Simple cases such as
1668 the above example can be thought of as a maximizing repeat that must swallow
1669 everything it can. So, while both \d+ and \d+? are prepared to adjust the
1670 number of digits they match in order to make the rest of the pattern match,
1671 (?&#62;\d+) can only match an entire sequence of digits.
1672 </P>
1673 <P>
1674 Atomic groups in general can of course contain arbitrarily complicated
1675 subpatterns, and can be nested. However, when the subpattern for an atomic
1676 group is just a single repeated item, as in the example above, a simpler
1677 notation, called a "possessive quantifier" can be used. This consists of an
1678 additional + character following a quantifier. Using this notation, the
1679 previous example can be rewritten as
1680 <pre>
1681 \d++foo
1682 </pre>
1683 Note that a possessive quantifier can be used with an entire group, for
1684 example:
1685 <pre>
1686 (abc|xyz){2,3}+
1687 </pre>
1688 Possessive quantifiers are always greedy; the setting of the PCRE_UNGREEDY
1689 option is ignored. They are a convenient notation for the simpler forms of
1690 atomic group. However, there is no difference in the meaning of a possessive
1691 quantifier and the equivalent atomic group, though there may be a performance
1692 difference; possessive quantifiers should be slightly faster.
1693 </P>
1694 <P>
1695 The possessive quantifier syntax is an extension to the Perl 5.8 syntax.
1696 Jeffrey Friedl originated the idea (and the name) in the first edition of his
1697 book. Mike McCloskey liked it, so implemented it when he built Sun's Java
1698 package, and PCRE copied it from there. It ultimately found its way into Perl
1699 at release 5.10.
1700 </P>
1701 <P>
1702 PCRE has an optimization that automatically "possessifies" certain simple
1703 pattern constructs. For example, the sequence A+B is treated as A++B because
1704 there is no point in backtracking into a sequence of A's when B must follow.
1705 </P>
1706 <P>
1707 When a pattern contains an unlimited repeat inside a subpattern that can itself
1708 be repeated an unlimited number of times, the use of an atomic group is the
1709 only way to avoid some failing matches taking a very long time indeed. The
1710 pattern
1711 <pre>
1712 (\D+|&#60;\d+&#62;)*[!?]
1713 </pre>
1714 matches an unlimited number of substrings that either consist of non-digits, or
1715 digits enclosed in &#60;&#62;, followed by either ! or ?. When it matches, it runs
1716 quickly. However, if it is applied to
1717 <pre>
1718 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
1719 </pre>
1720 it takes a long time before reporting failure. This is because the string can
1721 be divided between the internal \D+ repeat and the external * repeat in a
1722 large number of ways, and all have to be tried. (The example uses [!?] rather
1723 than a single character at the end, because both PCRE and Perl have an
1724 optimization that allows for fast failure when a single character is used. They
1725 remember the last single character that is required for a match, and fail early
1726 if it is not present in the string.) If the pattern is changed so that it uses
1727 an atomic group, like this:
1728 <pre>
1729 ((?&#62;\D+)|&#60;\d+&#62;)*[!?]
1730 </pre>
1731 sequences of non-digits cannot be broken, and failure happens quickly.
1732 <a name="backreferences"></a></P>
1733 <br><a name="SEC17" href="#TOC1">BACK REFERENCES</a><br>
1734 <P>
1735 Outside a character class, a backslash followed by a digit greater than 0 (and
1736 possibly further digits) is a back reference to a capturing subpattern earlier
1737 (that is, to its left) in the pattern, provided there have been that many
1738 previous capturing left parentheses.
1739 </P>
1740 <P>
1741 However, if the decimal number following the backslash is less than 10, it is
1742 always taken as a back reference, and causes an error only if there are not
1743 that many capturing left parentheses in the entire pattern. In other words, the
1744 parentheses that are referenced need not be to the left of the reference for
1745 numbers less than 10. A "forward back reference" of this type can make sense
1746 when a repetition is involved and the subpattern to the right has participated
1747 in an earlier iteration.
1748 </P>
1749 <P>
1750 It is not possible to have a numerical "forward back reference" to a subpattern
1751 whose number is 10 or more using this syntax because a sequence such as \50 is
1752 interpreted as a character defined in octal. See the subsection entitled
1753 "Non-printing characters"
1754 <a href="#digitsafterbackslash">above</a>
1755 for further details of the handling of digits following a backslash. There is
1756 no such problem when named parentheses are used. A back reference to any
1757 subpattern is possible using named parentheses (see below).
1758 </P>
1759 <P>
1760 Another way of avoiding the ambiguity inherent in the use of digits following a
1761 backslash is to use the \g escape sequence. This escape must be followed by an
1762 unsigned number or a negative number, optionally enclosed in braces. These
1763 examples are all identical:
1764 <pre>
1765 (ring), \1
1766 (ring), \g1
1767 (ring), \g{1}
1768 </pre>
1769 An unsigned number specifies an absolute reference without the ambiguity that
1770 is present in the older syntax. It is also useful when literal digits follow
1771 the reference. A negative number is a relative reference. Consider this
1772 example:
1773 <pre>
1774 (abc(def)ghi)\g{-1}
1775 </pre>
1776 The sequence \g{-1} is a reference to the most recently started capturing
1777 subpattern before \g, that is, is it equivalent to \2 in this example.
1778 Similarly, \g{-2} would be equivalent to \1. The use of relative references
1779 can be helpful in long patterns, and also in patterns that are created by
1780 joining together fragments that contain references within themselves.
1781 </P>
1782 <P>
1783 A back reference matches whatever actually matched the capturing subpattern in
1784 the current subject string, rather than anything matching the subpattern
1785 itself (see
1786 <a href="#subpatternsassubroutines">"Subpatterns as subroutines"</a>
1787 below for a way of doing that). So the pattern
1788 <pre>
1789 (sens|respons)e and \1ibility
1790 </pre>
1791 matches "sense and sensibility" and "response and responsibility", but not
1792 "sense and responsibility". If caseful matching is in force at the time of the
1793 back reference, the case of letters is relevant. For example,
1794 <pre>
1795 ((?i)rah)\s+\1
1796 </pre>
1797 matches "rah rah" and "RAH RAH", but not "RAH rah", even though the original
1798 capturing subpattern is matched caselessly.
1799 </P>
1800 <P>
1801 There are several different ways of writing back references to named
1802 subpatterns. The .NET syntax \k{name} and the Perl syntax \k&#60;name&#62; or
1803 \k'name' are supported, as is the Python syntax (?P=name). Perl 5.10's unified
1804 back reference syntax, in which \g can be used for both numeric and named
1805 references, is also supported. We could rewrite the above example in any of
1806 the following ways:
1807 <pre>
1808 (?&#60;p1&#62;(?i)rah)\s+\k&#60;p1&#62;
1809 (?'p1'(?i)rah)\s+\k{p1}
1810 (?P&#60;p1&#62;(?i)rah)\s+(?P=p1)
1811 (?&#60;p1&#62;(?i)rah)\s+\g{p1}
1812 </pre>
1813 A subpattern that is referenced by name may appear in the pattern before or
1814 after the reference.
1815 </P>
1816 <P>
1817 There may be more than one back reference to the same subpattern. If a
1818 subpattern has not actually been used in a particular match, any back
1819 references to it always fail by default. For example, the pattern
1820 <pre>
1821 (a|(bc))\2
1822 </pre>
1823 always fails if it starts to match "a" rather than "bc". However, if the
1824 PCRE_JAVASCRIPT_COMPAT option is set at compile time, a back reference to an
1825 unset value matches an empty string.
1826 </P>
1827 <P>
1828 Because there may be many capturing parentheses in a pattern, all digits
1829 following a backslash are taken as part of a potential back reference number.
1830 If the pattern continues with a digit character, some delimiter must be used to
1831 terminate the back reference. If the PCRE_EXTENDED option is set, this can be
1832 whitespace. Otherwise, the \g{ syntax or an empty comment (see
1833 <a href="#comments">"Comments"</a>
1834 below) can be used.
1835 </P>
1836 <br><b>
1837 Recursive back references
1838 </b><br>
1839 <P>
1840 A back reference that occurs inside the parentheses to which it refers fails
1841 when the subpattern is first used, so, for example, (a\1) never matches.
1842 However, such references can be useful inside repeated subpatterns. For
1843 example, the pattern
1844 <pre>
1845 (a|b\1)+
1846 </pre>
1847 matches any number of "a"s and also "aba", "ababbaa" etc. At each iteration of
1848 the subpattern, the back reference matches the character string corresponding
1849 to the previous iteration. In order for this to work, the pattern must be such
1850 that the first iteration does not need to match the back reference. This can be
1851 done using alternation, as in the example above, or by a quantifier with a
1852 minimum of zero.
1853 </P>
1854 <P>
1855 Back references of this type cause the group that they reference to be treated
1856 as an
1857 <a href="#atomicgroup">atomic group.</a>
1858 Once the whole group has been matched, a subsequent matching failure cannot
1859 cause backtracking into the middle of the group.
1860 <a name="bigassertions"></a></P>
1861 <br><a name="SEC18" href="#TOC1">ASSERTIONS</a><br>
1862 <P>
1863 An assertion is a test on the characters following or preceding the current
1864 matching point that does not actually consume any characters. The simple
1865 assertions coded as \b, \B, \A, \G, \Z, \z, ^ and $ are described
1866 <a href="#smallassertions">above.</a>
1867 </P>
1868 <P>
1869 More complicated assertions are coded as subpatterns. There are two kinds:
1870 those that look ahead of the current position in the subject string, and those
1871 that look behind it. An assertion subpattern is matched in the normal way,
1872 except that it does not cause the current matching position to be changed.
1873 </P>
1874 <P>
1875 Assertion subpatterns are not capturing subpatterns. If such an assertion
1876 contains capturing subpatterns within it, these are counted for the purposes of
1877 numbering the capturing subpatterns in the whole pattern. However, substring
1878 capturing is carried out only for positive assertions, because it does not make
1879 sense for negative assertions.
1880 </P>
1881 <P>
1882 For compatibility with Perl, assertion subpatterns may be repeated; though
1883 it makes no sense to assert the same thing several times, the side effect of
1884 capturing parentheses may occasionally be useful. In practice, there only three
1885 cases:
1886 <br>
1887 <br>
1888 (1) If the quantifier is {0}, the assertion is never obeyed during matching.
1889 However, it may contain internal capturing parenthesized groups that are called
1890 from elsewhere via the
1891 <a href="#subpatternsassubroutines">subroutine mechanism.</a>
1892 <br>
1893 <br>
1894 (2) If quantifier is {0,n} where n is greater than zero, it is treated as if it
1895 were {0,1}. At run time, the rest of the pattern match is tried with and
1896 without the assertion, the order depending on the greediness of the quantifier.
1897 <br>
1898 <br>
1899 (3) If the minimum repetition is greater than zero, the quantifier is ignored.
1900 The assertion is obeyed just once when encountered during matching.
1901 </P>
1902 <br><b>
1903 Lookahead assertions
1904 </b><br>
1905 <P>
1906 Lookahead assertions start with (?= for positive assertions and (?! for
1907 negative assertions. For example,
1908 <pre>
1909 \w+(?=;)
1910 </pre>
1911 matches a word followed by a semicolon, but does not include the semicolon in
1912 the match, and
1913 <pre>
1914 foo(?!bar)
1915 </pre>
1916 matches any occurrence of "foo" that is not followed by "bar". Note that the
1917 apparently similar pattern
1918 <pre>
1919 (?!foo)bar
1920 </pre>
1921 does not find an occurrence of "bar" that is preceded by something other than
1922 "foo"; it finds any occurrence of "bar" whatsoever, because the assertion
1923 (?!foo) is always true when the next three characters are "bar". A
1924 lookbehind assertion is needed to achieve the other effect.
1925 </P>
1926 <P>
1927 If you want to force a matching failure at some point in a pattern, the most
1928 convenient way to do it is with (?!) because an empty string always matches, so
1929 an assertion that requires there not to be an empty string must always fail.
1930 The backtracking control verb (*FAIL) or (*F) is a synonym for (?!).
1931 <a name="lookbehind"></a></P>
1932 <br><b>
1933 Lookbehind assertions
1934 </b><br>
1935 <P>
1936 Lookbehind assertions start with (?&#60;= for positive assertions and (?&#60;! for
1937 negative assertions. For example,
1938 <pre>
1939 (?&#60;!foo)bar
1940 </pre>
1941 does find an occurrence of "bar" that is not preceded by "foo". The contents of
1942 a lookbehind assertion are restricted such that all the strings it matches must
1943 have a fixed length. However, if there are several top-level alternatives, they
1944 do not all have to have the same fixed length. Thus
1945 <pre>
1946 (?&#60;=bullock|donkey)
1947 </pre>
1948 is permitted, but
1949 <pre>
1950 (?&#60;!dogs?|cats?)
1951 </pre>
1952 causes an error at compile time. Branches that match different length strings
1953 are permitted only at the top level of a lookbehind assertion. This is an
1954 extension compared with Perl, which requires all branches to match the same
1955 length of string. An assertion such as
1956 <pre>
1957 (?&#60;=ab(c|de))
1958 </pre>
1959 is not permitted, because its single top-level branch can match two different
1960 lengths, but it is acceptable to PCRE if rewritten to use two top-level
1961 branches:
1962 <pre>
1963 (?&#60;=abc|abde)
1964 </pre>
1965 In some cases, the escape sequence \K
1966 <a href="#resetmatchstart">(see above)</a>
1967 can be used instead of a lookbehind assertion to get round the fixed-length
1968 restriction.
1969 </P>
1970 <P>
1971 The implementation of lookbehind assertions is, for each alternative, to
1972 temporarily move the current position back by the fixed length and then try to
1973 match. If there are insufficient characters before the current position, the
1974 assertion fails.
1975 </P>
1976 <P>
1977 In a UTF mode, PCRE does not allow the \C escape (which matches a single data
1978 unit even in a UTF mode) to appear in lookbehind assertions, because it makes
1979 it impossible to calculate the length of the lookbehind. The \X and \R
1980 escapes, which can match different numbers of data units, are also not
1981 permitted.
1982 </P>
1983 <P>
1984 <a href="#subpatternsassubroutines">"Subroutine"</a>
1985 calls (see below) such as (?2) or (?&X) are permitted in lookbehinds, as long
1986 as the subpattern matches a fixed-length string.
1987 <a href="#recursion">Recursion,</a>
1988 however, is not supported.
1989 </P>
1990 <P>
1991 Possessive quantifiers can be used in conjunction with lookbehind assertions to
1992 specify efficient matching of fixed-length strings at the end of subject
1993 strings. Consider a simple pattern such as
1994 <pre>
1995 abcd$
1996 </pre>
1997 when applied to a long string that does not match. Because matching proceeds
1998 from left to right, PCRE will look for each "a" in the subject and then see if
1999 what follows matches the rest of the pattern. If the pattern is specified as
2000 <pre>
2001 ^.*abcd$
2002 </pre>
2003 the initial .* matches the entire string at first, but when this fails (because
2004 there is no following "a"), it backtracks to match all but the last character,
2005 then all but the last two characters, and so on. Once again the search for "a"
2006 covers the entire string, from right to left, so we are no better off. However,
2007 if the pattern is written as
2008 <pre>
2009 ^.*+(?&#60;=abcd)
2010 </pre>
2011 there can be no backtracking for the .*+ item; it can match only the entire
2012 string. The subsequent lookbehind assertion does a single test on the last four
2013 characters. If it fails, the match fails immediately. For long strings, this
2014 approach makes a significant difference to the processing time.
2015 </P>
2016 <br><b>
2017 Using multiple assertions
2018 </b><br>
2019 <P>
2020 Several assertions (of any sort) may occur in succession. For example,
2021 <pre>
2022 (?&#60;=\d{3})(?&#60;!999)foo
2023 </pre>
2024 matches "foo" preceded by three digits that are not "999". Notice that each of
2025 the assertions is applied independently at the same point in the subject
2026 string. First there is a check that the previous three characters are all
2027 digits, and then there is a check that the same three characters are not "999".
2028 This pattern does <i>not</i> match "foo" preceded by six characters, the first
2029 of which are digits and the last three of which are not "999". For example, it
2030 doesn't match "123abcfoo". A pattern to do that is
2031 <pre>
2032 (?&#60;=\d{3}...)(?&#60;!999)foo
2033 </pre>
2034 This time the first assertion looks at the preceding six characters, checking
2035 that the first three are digits, and then the second assertion checks that the
2036 preceding three characters are not "999".
2037 </P>
2038 <P>
2039 Assertions can be nested in any combination. For example,
2040 <pre>
2041 (?&#60;=(?&#60;!foo)bar)baz
2042 </pre>
2043 matches an occurrence of "baz" that is preceded by "bar" which in turn is not
2044 preceded by "foo", while
2045 <pre>
2046 (?&#60;=\d{3}(?!999)...)foo
2047 </pre>
2048 is another pattern that matches "foo" preceded by three digits and any three
2049 characters that are not "999".
2050 <a name="conditions"></a></P>
2051 <br><a name="SEC19" href="#TOC1">CONDITIONAL SUBPATTERNS</a><br>
2052 <P>
2053 It is possible to cause the matching process to obey a subpattern
2054 conditionally or to choose between two alternative subpatterns, depending on
2055 the result of an assertion, or whether a specific capturing subpattern has
2056 already been matched. The two possible forms of conditional subpattern are:
2057 <pre>
2058 (?(condition)yes-pattern)
2059 (?(condition)yes-pattern|no-pattern)
2060 </pre>
2061 If the condition is satisfied, the yes-pattern is used; otherwise the
2062 no-pattern (if present) is used. If there are more than two alternatives in the
2063 subpattern, a compile-time error occurs. Each of the two alternatives may
2064 itself contain nested subpatterns of any form, including conditional
2065 subpatterns; the restriction to two alternatives applies only at the level of
2066 the condition. This pattern fragment is an example where the alternatives are
2067 complex:
2068 <pre>
2069 (?(1) (A|B|C) | (D | (?(2)E|F) | E) )
2070
2071 </PRE>
2072 </P>
2073 <P>
2074 There are four kinds of condition: references to subpatterns, references to
2075 recursion, a pseudo-condition called DEFINE, and assertions.
2076 </P>
2077 <br><b>
2078 Checking for a used subpattern by number
2079 </b><br>
2080 <P>
2081 If the text between the parentheses consists of a sequence of digits, the
2082 condition is true if a capturing subpattern of that number has previously
2083 matched. If there is more than one capturing subpattern with the same number
2084 (see the earlier
2085 <a href="#recursion">section about duplicate subpattern numbers),</a>
2086 the condition is true if any of them have matched. An alternative notation is
2087 to precede the digits with a plus or minus sign. In this case, the subpattern
2088 number is relative rather than absolute. The most recently opened parentheses
2089 can be referenced by (?(-1), the next most recent by (?(-2), and so on. Inside
2090 loops it can also make sense to refer to subsequent groups. The next
2091 parentheses to be opened can be referenced as (?(+1), and so on. (The value
2092 zero in any of these forms is not used; it provokes a compile-time error.)
2093 </P>
2094 <P>
2095 Consider the following pattern, which contains non-significant white space to
2096 make it more readable (assume the PCRE_EXTENDED option) and to divide it into
2097 three parts for ease of discussion:
2098 <pre>
2099 ( \( )? [^()]+ (?(1) \) )
2100 </pre>
2101 The first part matches an optional opening parenthesis, and if that
2102 character is present, sets it as the first captured substring. The second part
2103 matches one or more characters that are not parentheses. The third part is a
2104 conditional subpattern that tests whether or not the first set of parentheses
2105 matched. If they did, that is, if subject started with an opening parenthesis,
2106 the condition is true, and so the yes-pattern is executed and a closing
2107 parenthesis is required. Otherwise, since no-pattern is not present, the
2108 subpattern matches nothing. In other words, this pattern matches a sequence of
2109 non-parentheses, optionally enclosed in parentheses.
2110 </P>
2111 <P>
2112 If you were embedding this pattern in a larger one, you could use a relative
2113 reference:
2114 <pre>
2115 ...other stuff... ( \( )? [^()]+ (?(-1) \) ) ...
2116 </pre>
2117 This makes the fragment independent of the parentheses in the larger pattern.
2118 </P>
2119 <br><b>
2120 Checking for a used subpattern by name
2121 </b><br>
2122 <P>
2123 Perl uses the syntax (?(&#60;name&#62;)...) or (?('name')...) to test for a used
2124 subpattern by name. For compatibility with earlier versions of PCRE, which had
2125 this facility before Perl, the syntax (?(name)...) is also recognized. However,
2126 there is a possible ambiguity with this syntax, because subpattern names may
2127 consist entirely of digits. PCRE looks first for a named subpattern; if it
2128 cannot find one and the name consists entirely of digits, PCRE looks for a
2129 subpattern of that number, which must be greater than zero. Using subpattern
2130 names that consist entirely of digits is not recommended.
2131 </P>
2132 <P>
2133 Rewriting the above example to use a named subpattern gives this:
2134 <pre>
2135 (?&#60;OPEN&#62; \( )? [^()]+ (?(&#60;OPEN&#62;) \) )
2136 </pre>
2137 If the name used in a condition of this kind is a duplicate, the test is
2138 applied to all subpatterns of the same name, and is true if any one of them has
2139 matched.
2140 </P>
2141 <br><b>
2142 Checking for pattern recursion
2143 </b><br>
2144 <P>
2145 If the condition is the string (R), and there is no subpattern with the name R,
2146 the condition is true if a recursive call to the whole pattern or any
2147 subpattern has been made. If digits or a name preceded by ampersand follow the
2148 letter R, for example:
2149 <pre>
2150 (?(R3)...) or (?(R&name)...)
2151 </pre>
2152 the condition is true if the most recent recursion is into a subpattern whose
2153 number or name is given. This condition does not check the entire recursion
2154 stack. If the name used in a condition of this kind is a duplicate, the test is
2155 applied to all subpatterns of the same name, and is true if any one of them is
2156 the most recent recursion.
2157 </P>
2158 <P>
2159 At "top level", all these recursion test conditions are false.
2160 <a href="#recursion">The syntax for recursive patterns</a>
2161 is described below.
2162 <a name="subdefine"></a></P>
2163 <br><b>
2164 Defining subpatterns for use by reference only
2165 </b><br>
2166 <P>
2167 If the condition is the string (DEFINE), and there is no subpattern with the
2168 name DEFINE, the condition is always false. In this case, there may be only one
2169 alternative in the subpattern. It is always skipped if control reaches this
2170 point in the pattern; the idea of DEFINE is that it can be used to define
2171 subroutines that can be referenced from elsewhere. (The use of
2172 <a href="#subpatternsassubroutines">subroutines</a>
2173 is described below.) For example, a pattern to match an IPv4 address such as
2174 "192.168.23.245" could be written like this (ignore whitespace and line
2175 breaks):
2176 <pre>
2177 (?(DEFINE) (?&#60;byte&#62; 2[0-4]\d | 25[0-5] | 1\d\d | [1-9]?\d) )
2178 \b (?&byte) (\.(?&byte)){3} \b
2179 </pre>
2180 The first part of the pattern is a DEFINE group inside which a another group
2181 named "byte" is defined. This matches an individual component of an IPv4
2182 address (a number less than 256). When matching takes place, this part of the
2183 pattern is skipped because DEFINE acts like a false condition. The rest of the
2184 pattern uses references to the named group to match the four dot-separated
2185 components of an IPv4 address, insisting on a word boundary at each end.
2186 </P>
2187 <br><b>
2188 Assertion conditions
2189 </b><br>
2190 <P>
2191 If the condition is not in any of the above formats, it must be an assertion.
2192 This may be a positive or negative lookahead or lookbehind assertion. Consider
2193 this pattern, again containing non-significant white space, and with the two
2194 alternatives on the second line:
2195 <pre>
2196 (?(?=[^a-z]*[a-z])
2197 \d{2}-[a-z]{3}-\d{2} | \d{2}-\d{2}-\d{2} )
2198 </pre>
2199 The condition is a positive lookahead assertion that matches an optional
2200 sequence of non-letters followed by a letter. In other words, it tests for the
2201 presence of at least one letter in the subject. If a letter is found, the
2202 subject is matched against the first alternative; otherwise it is matched
2203 against the second. This pattern matches strings in one of the two forms
2204 dd-aaa-dd or dd-dd-dd, where aaa are letters and dd are digits.
2205 <a name="comments"></a></P>
2206 <br><a name="SEC20" href="#TOC1">COMMENTS</a><br>
2207 <P>
2208 There are two ways of including comments in patterns that are processed by
2209 PCRE. In both cases, the start of the comment must not be in a character class,
2210 nor in the middle of any other sequence of related characters such as (?: or a
2211 subpattern name or number. The characters that make up a comment play no part
2212 in the pattern matching.
2213 </P>
2214 <P>
2215 The sequence (?# marks the start of a comment that continues up to the next
2216 closing parenthesis. Nested parentheses are not permitted. If the PCRE_EXTENDED
2217 option is set, an unescaped # character also introduces a comment, which in
2218 this case continues to immediately after the next newline character or
2219 character sequence in the pattern. Which characters are interpreted as newlines
2220 is controlled by the options passed to a compiling function or by a special
2221 sequence at the start of the pattern, as described in the section entitled
2222 <a href="#newlines">"Newline conventions"</a>
2223 above. Note that the end of this type of comment is a literal newline sequence
2224 in the pattern; escape sequences that happen to represent a newline do not
2225 count. For example, consider this pattern when PCRE_EXTENDED is set, and the
2226 default newline convention is in force:
2227 <pre>
2228 abc #comment \n still comment
2229 </pre>
2230 On encountering the # character, <b>pcre_compile()</b> skips along, looking for
2231 a newline in the pattern. The sequence \n is still literal at this stage, so
2232 it does not terminate the comment. Only an actual character with the code value
2233 0x0a (the default newline) does so.
2234 <a name="recursion"></a></P>
2235 <br><a name="SEC21" href="#TOC1">RECURSIVE PATTERNS</a><br>
2236 <P>
2237 Consider the problem of matching a string in parentheses, allowing for
2238 unlimited nested parentheses. Without the use of recursion, the best that can
2239 be done is to use a pattern that matches up to some fixed depth of nesting. It
2240 is not possible to handle an arbitrary nesting depth.
2241 </P>
2242 <P>
2243 For some time, Perl has provided a facility that allows regular expressions to
2244 recurse (amongst other things). It does this by interpolating Perl code in the
2245 expression at run time, and the code can refer to the expression itself. A Perl
2246 pattern using code interpolation to solve the parentheses problem can be
2247 created like this:
2248 <pre>
2249 $re = qr{\( (?: (?&#62;[^()]+) | (?p{$re}) )* \)}x;
2250 </pre>
2251 The (?p{...}) item interpolates Perl code at run time, and in this case refers
2252 recursively to the pattern in which it appears.
2253 </P>
2254 <P>
2255 Obviously, PCRE cannot support the interpolation of Perl code. Instead, it
2256 supports special syntax for recursion of the entire pattern, and also for
2257 individual subpattern recursion. After its introduction in PCRE and Python,
2258 this kind of recursion was subsequently introduced into Perl at release 5.10.
2259 </P>
2260 <P>
2261 A special item that consists of (? followed by a number greater than zero and a
2262 closing parenthesis is a recursive subroutine call of the subpattern of the
2263 given number, provided that it occurs inside that subpattern. (If not, it is a
2264 <a href="#subpatternsassubroutines">non-recursive subroutine</a>
2265 call, which is described in the next section.) The special item (?R) or (?0) is
2266 a recursive call of the entire regular expression.
2267 </P>
2268 <P>
2269 This PCRE pattern solves the nested parentheses problem (assume the
2270 PCRE_EXTENDED option is set so that white space is ignored):
2271 <pre>
2272 \( ( [^()]++ | (?R) )* \)
2273 </pre>
2274 First it matches an opening parenthesis. Then it matches any number of
2275 substrings which can either be a sequence of non-parentheses, or a recursive
2276 match of the pattern itself (that is, a correctly parenthesized substring).
2277 Finally there is a closing parenthesis. Note the use of a possessive quantifier
2278 to avoid backtracking into sequences of non-parentheses.
2279 </P>
2280 <P>
2281 If this were part of a larger pattern, you would not want to recurse the entire
2282 pattern, so instead you could use this:
2283 <pre>
2284 ( \( ( [^()]++ | (?1) )* \) )
2285 </pre>
2286 We have put the pattern into parentheses, and caused the recursion to refer to
2287 them instead of the whole pattern.
2288 </P>
2289 <P>
2290 In a larger pattern, keeping track of parenthesis numbers can be tricky. This
2291 is made easier by the use of relative references. Instead of (?1) in the
2292 pattern above you can write (?-2) to refer to the second most recently opened
2293 parentheses preceding the recursion. In other words, a negative number counts
2294 capturing parentheses leftwards from the point at which it is encountered.
2295 </P>
2296 <P>
2297 It is also possible to refer to subsequently opened parentheses, by writing
2298 references such as (?+2). However, these cannot be recursive because the
2299 reference is not inside the parentheses that are referenced. They are always
2300 <a href="#subpatternsassubroutines">non-recursive subroutine</a>
2301 calls, as described in the next section.
2302 </P>
2303 <P>
2304 An alternative approach is to use named parentheses instead. The Perl syntax
2305 for this is (?&name); PCRE's earlier syntax (?P&#62;name) is also supported. We
2306 could rewrite the above example as follows:
2307 <pre>
2308 (?&#60;pn&#62; \( ( [^()]++ | (?&pn) )* \) )
2309 </pre>
2310 If there is more than one subpattern with the same name, the earliest one is
2311 used.
2312 </P>
2313 <P>
2314 This particular example pattern that we have been looking at contains nested
2315 unlimited repeats, and so the use of a possessive quantifier for matching
2316 strings of non-parentheses is important when applying the pattern to strings
2317 that do not match. For example, when this pattern is applied to
2318 <pre>
2319 (aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa()
2320 </pre>
2321 it yields "no match" quickly. However, if a possessive quantifier is not used,
2322 the match runs for a very long time indeed because there are so many different
2323 ways the + and * repeats can carve up the subject, and all have to be tested
2324 before failure can be reported.
2325 </P>
2326 <P>
2327 At the end of a match, the values of capturing parentheses are those from
2328 the outermost level. If you want to obtain intermediate values, a callout
2329 function can be used (see below and the
2330 <a href="pcrecallout.html"><b>pcrecallout</b></a>
2331 documentation). If the pattern above is matched against
2332 <pre>
2333 (ab(cd)ef)
2334 </pre>
2335 the value for the inner capturing parentheses (numbered 2) is "ef", which is
2336 the last value taken on at the top level. If a capturing subpattern is not
2337 matched at the top level, its final captured value is unset, even if it was
2338 (temporarily) set at a deeper level during the matching process.
2339 </P>
2340 <P>
2341 If there are more than 15 capturing parentheses in a pattern, PCRE has to
2342 obtain extra memory to store data during a recursion, which it does by using
2343 <b>pcre_malloc</b>, freeing it via <b>pcre_free</b> afterwards. If no memory can
2344 be obtained, the match fails with the PCRE_ERROR_NOMEMORY error.
2345 </P>
2346 <P>
2347 Do not confuse the (?R) item with the condition (R), which tests for recursion.
2348 Consider this pattern, which matches text in angle brackets, allowing for
2349 arbitrary nesting. Only digits are allowed in nested brackets (that is, when
2350 recursing), whereas any characters are permitted at the outer level.
2351 <pre>
2352 &#60; (?: (?(R) \d++ | [^&#60;&#62;]*+) | (?R)) * &#62;
2353 </pre>
2354 In this pattern, (?(R) is the start of a conditional subpattern, with two
2355 different alternatives for the recursive and non-recursive cases. The (?R) item
2356 is the actual recursive call.
2357 <a name="recursiondifference"></a></P>
2358 <br><b>
2359 Differences in recursion processing between PCRE and Perl
2360 </b><br>
2361 <P>
2362 Recursion processing in PCRE differs from Perl in two important ways. In PCRE
2363 (like Python, but unlike Perl), a recursive subpattern call is always treated
2364 as an atomic group. That is, once it has matched some of the subject string, it
2365 is never re-entered, even if it contains untried alternatives and there is a
2366 subsequent matching failure. This can be illustrated by the following pattern,
2367 which purports to match a palindromic string that contains an odd number of
2368 characters (for example, "a", "aba", "abcba", "abcdcba"):
2369 <pre>
2370 ^(.|(.)(?1)\2)$
2371 </pre>
2372 The idea is that it either matches a single character, or two identical
2373 characters surrounding a sub-palindrome. In Perl, this pattern works; in PCRE
2374 it does not if the pattern is longer than three characters. Consider the
2375 subject string "abcba":
2376 </P>
2377 <P>
2378 At the top level, the first character is matched, but as it is not at the end
2379 of the string, the first alternative fails; the second alternative is taken
2380 and the recursion kicks in. The recursive call to subpattern 1 successfully
2381 matches the next character ("b"). (Note that the beginning and end of line
2382 tests are not part of the recursion).
2383 </P>
2384 <P>
2385 Back at the top level, the next character ("c") is compared with what
2386 subpattern 2 matched, which was "a". This fails. Because the recursion is
2387 treated as an atomic group, there are now no backtracking points, and so the
2388 entire match fails. (Perl is able, at this point, to re-enter the recursion and
2389 try the second alternative.) However, if the pattern is written with the
2390 alternatives in the other order, things are different:
2391 <pre>
2392 ^((.)(?1)\2|.)$
2393 </pre>
2394 This time, the recursing alternative is tried first, and continues to recurse
2395 until it runs out of characters, at which point the recursion fails. But this
2396 time we do have another alternative to try at the higher level. That is the big
2397 difference: in the previous case the remaining alternative is at a deeper
2398 recursion level, which PCRE cannot use.
2399 </P>
2400 <P>
2401 To change the pattern so that it matches all palindromic strings, not just
2402 those with an odd number of characters, it is tempting to change the pattern to
2403 this:
2404 <pre>
2405 ^((.)(?1)\2|.?)$
2406 </pre>
2407 Again, this works in Perl, but not in PCRE, and for the same reason. When a
2408 deeper recursion has matched a single character, it cannot be entered again in
2409 order to match an empty string. The solution is to separate the two cases, and
2410 write out the odd and even cases as alternatives at the higher level:
2411 <pre>
2412 ^(?:((.)(?1)\2|)|((.)(?3)\4|.))
2413 </pre>
2414 If you want to match typical palindromic phrases, the pattern has to ignore all
2415 non-word characters, which can be done like this:
2416 <pre>
2417 ^\W*+(?:((.)\W*+(?1)\W*+\2|)|((.)\W*+(?3)\W*+\4|\W*+.\W*+))\W*+$
2418 </pre>
2419 If run with the PCRE_CASELESS option, this pattern matches phrases such as "A
2420 man, a plan, a canal: Panama!" and it works well in both PCRE and Perl. Note
2421 the use of the possessive quantifier *+ to avoid backtracking into sequences of
2422 non-word characters. Without this, PCRE takes a great deal longer (ten times or
2423 more) to match typical phrases, and Perl takes so long that you think it has
2424 gone into a loop.
2425 </P>
2426 <P>
2427 <b>WARNING</b>: The palindrome-matching patterns above work only if the subject
2428 string does not start with a palindrome that is shorter than the entire string.
2429 For example, although "abcba" is correctly matched, if the subject is "ababa",
2430 PCRE finds the palindrome "aba" at the start, then fails at top level because
2431 the end of the string does not follow. Once again, it cannot jump back into the
2432 recursion to try other alternatives, so the entire match fails.
2433 </P>
2434 <P>
2435 The second way in which PCRE and Perl differ in their recursion processing is
2436 in the handling of captured values. In Perl, when a subpattern is called
2437 recursively or as a subpattern (see the next section), it has no access to any
2438 values that were captured outside the recursion, whereas in PCRE these values
2439 can be referenced. Consider this pattern:
2440 <pre>
2441 ^(.)(\1|a(?2))
2442 </pre>
2443 In PCRE, this pattern matches "bab". The first capturing parentheses match "b",
2444 then in the second group, when the back reference \1 fails to match "b", the
2445 second alternative matches "a" and then recurses. In the recursion, \1 does
2446 now match "b" and so the whole match succeeds. In Perl, the pattern fails to
2447 match because inside the recursive call \1 cannot access the externally set
2448 value.
2449 <a name="subpatternsassubroutines"></a></P>
2450 <br><a name="SEC22" href="#TOC1">SUBPATTERNS AS SUBROUTINES</a><br>
2451 <P>
2452 If the syntax for a recursive subpattern call (either by number or by
2453 name) is used outside the parentheses to which it refers, it operates like a
2454 subroutine in a programming language. The called subpattern may be defined
2455 before or after the reference. A numbered reference can be absolute or
2456 relative, as in these examples:
2457 <pre>
2458 (...(absolute)...)...(?2)...
2459 (...(relative)...)...(?-1)...
2460 (...(?+1)...(relative)...
2461 </pre>
2462 An earlier example pointed out that the pattern
2463 <pre>
2464 (sens|respons)e and \1ibility
2465 </pre>
2466 matches "sense and sensibility" and "response and responsibility", but not
2467 "sense and responsibility". If instead the pattern
2468 <pre>
2469 (sens|respons)e and (?1)ibility
2470 </pre>
2471 is used, it does match "sense and responsibility" as well as the other two
2472 strings. Another example is given in the discussion of DEFINE above.
2473 </P>
2474 <P>
2475 All subroutine calls, whether recursive or not, are always treated as atomic
2476 groups. That is, once a subroutine has matched some of the subject string, it
2477 is never re-entered, even if it contains untried alternatives and there is a
2478 subsequent matching failure. Any capturing parentheses that are set during the
2479 subroutine call revert to their previous values afterwards.
2480 </P>
2481 <P>
2482 Processing options such as case-independence are fixed when a subpattern is
2483 defined, so if it is used as a subroutine, such options cannot be changed for
2484 different calls. For example, consider this pattern:
2485 <pre>
2486 (abc)(?i:(?-1))
2487 </pre>
2488 It matches "abcabc". It does not match "abcABC" because the change of
2489 processing option does not affect the called subpattern.
2490 <a name="onigurumasubroutines"></a></P>
2491 <br><a name="SEC23" href="#TOC1">ONIGURUMA SUBROUTINE SYNTAX</a><br>
2492 <P>
2493 For compatibility with Oniguruma, the non-Perl syntax \g followed by a name or
2494 a number enclosed either in angle brackets or single quotes, is an alternative
2495 syntax for referencing a subpattern as a subroutine, possibly recursively. Here
2496 are two of the examples used above, rewritten using this syntax:
2497 <pre>
2498 (?&#60;pn&#62; \( ( (?&#62;[^()]+) | \g&#60;pn&#62; )* \) )
2499 (sens|respons)e and \g'1'ibility
2500 </pre>
2501 PCRE supports an extension to Oniguruma: if a number is preceded by a
2502 plus or a minus sign it is taken as a relative reference. For example:
2503 <pre>
2504 (abc)(?i:\g&#60;-1&#62;)
2505 </pre>
2506 Note that \g{...} (Perl syntax) and \g&#60;...&#62; (Oniguruma syntax) are <i>not</i>
2507 synonymous. The former is a back reference; the latter is a subroutine call.
2508 </P>
2509 <br><a name="SEC24" href="#TOC1">CALLOUTS</a><br>
2510 <P>
2511 Perl has a feature whereby using the sequence (?{...}) causes arbitrary Perl
2512 code to be obeyed in the middle of matching a regular expression. This makes it
2513 possible, amongst other things, to extract different substrings that match the
2514 same pair of parentheses when there is a repetition.
2515 </P>
2516 <P>
2517 PCRE provides a similar feature, but of course it cannot obey arbitrary Perl
2518 code. The feature is called "callout". The caller of PCRE provides an external
2519 function by putting its entry point in the global variable <i>pcre_callout</i>
2520 (8-bit library) or <i>pcre16_callout</i> (16-bit library). By default, this
2521 variable contains NULL, which disables all calling out.
2522 </P>
2523 <P>
2524 Within a regular expression, (?C) indicates the points at which the external
2525 function is to be called. If you want to identify different callout points, you
2526 can put a number less than 256 after the letter C. The default value is zero.
2527 For example, this pattern has two callout points:
2528 <pre>
2529 (?C1)abc(?C2)def
2530 </pre>
2531 If the PCRE_AUTO_CALLOUT flag is passed to a compiling function, callouts are
2532 automatically installed before each item in the pattern. They are all numbered
2533 255.
2534 </P>
2535 <P>
2536 During matching, when PCRE reaches a callout point, the external function is
2537 called. It is provided with the number of the callout, the position in the
2538 pattern, and, optionally, one item of data originally supplied by the caller of
2539 the matching function. The callout function may cause matching to proceed, to
2540 backtrack, or to fail altogether. A complete description of the interface to
2541 the callout function is given in the
2542 <a href="pcrecallout.html"><b>pcrecallout</b></a>
2543 documentation.
2544 <a name="backtrackcontrol"></a></P>
2545 <br><a name="SEC25" href="#TOC1">BACKTRACKING CONTROL</a><br>
2546 <P>
2547 Perl 5.10 introduced a number of "Special Backtracking Control Verbs", which
2548 are described in the Perl documentation as "experimental and subject to change
2549 or removal in a future version of Perl". It goes on to say: "Their usage in
2550 production code should be noted to avoid problems during upgrades." The same
2551 remarks apply to the PCRE features described in this section.
2552 </P>
2553 <P>
2554 Since these verbs are specifically related to backtracking, most of them can be
2555 used only when the pattern is to be matched using one of the traditional
2556 matching functions, which use a backtracking algorithm. With the exception of
2557 (*FAIL), which behaves like a failing negative assertion, they cause an error
2558 if encountered by a DFA matching function.
2559 </P>
2560 <P>
2561 If any of these verbs are used in an assertion or in a subpattern that is
2562 called as a subroutine (whether or not recursively), their effect is confined
2563 to that subpattern; it does not extend to the surrounding pattern, with one
2564 exception: the name from a *(MARK), (*PRUNE), or (*THEN) that is encountered in
2565 a successful positive assertion <i>is</i> passed back when a match succeeds
2566 (compare capturing parentheses in assertions). Note that such subpatterns are
2567 processed as anchored at the point where they are tested. Note also that Perl's
2568 treatment of subroutines is different in some cases.
2569 </P>
2570 <P>
2571 The new verbs make use of what was previously invalid syntax: an opening
2572 parenthesis followed by an asterisk. They are generally of the form
2573 (*VERB) or (*VERB:NAME). Some may take either form, with differing behaviour,
2574 depending on whether or not an argument is present. A name is any sequence of
2575 characters that does not include a closing parenthesis. If the name is empty,
2576 that is, if the closing parenthesis immediately follows the colon, the effect
2577 is as if the colon were not there. Any number of these verbs may occur in a
2578 pattern.
2579 <a name="nooptimize"></a></P>
2580 <br><b>
2581 Optimizations that affect backtracking verbs
2582 </b><br>
2583 <P>
2584 PCRE contains some optimizations that are used to speed up matching by running
2585 some checks at the start of each match attempt. For example, it may know the
2586 minimum length of matching subject, or that a particular character must be
2587 present. When one of these optimizations suppresses the running of a match, any
2588 included backtracking verbs will not, of course, be processed. You can suppress
2589 the start-of-match optimizations by setting the PCRE_NO_START_OPTIMIZE option
2590 when calling <b>pcre_compile()</b> or <b>pcre_exec()</b>, or by starting the
2591 pattern with (*NO_START_OPT). There is more discussion of this option in the
2592 section entitled
2593 <a href="pcreapi.html#execoptions">"Option bits for <b>pcre_exec()</b>"</a>
2594 in the
2595 <a href="pcreapi.html"><b>pcreapi</b></a>
2596 documentation.
2597 </P>
2598 <P>
2599 Experiments with Perl suggest that it too has similar optimizations, sometimes
2600 leading to anomalous results.
2601 </P>
2602 <br><b>
2603 Verbs that act immediately
2604 </b><br>
2605 <P>
2606 The following verbs act as soon as they are encountered. They may not be
2607 followed by a name.
2608 <pre>
2609 (*ACCEPT)
2610 </pre>
2611 This verb causes the match to end successfully, skipping the remainder of the
2612 pattern. However, when it is inside a subpattern that is called as a
2613 subroutine, only that subpattern is ended successfully. Matching then continues
2614 at the outer level. If (*ACCEPT) is inside capturing parentheses, the data so
2615 far is captured. For example:
2616 <pre>
2617 A((?:A|B(*ACCEPT)|C)D)
2618 </pre>
2619 This matches "AB", "AAD", or "ACD"; when it matches "AB", "B" is captured by
2620 the outer parentheses.
2621 <pre>
2622 (*FAIL) or (*F)
2623 </pre>
2624 This verb causes a matching failure, forcing backtracking to occur. It is
2625 equivalent to (?!) but easier to read. The Perl documentation notes that it is
2626 probably useful only when combined with (?{}) or (??{}). Those are, of course,
2627 Perl features that are not present in PCRE. The nearest equivalent is the
2628 callout feature, as for example in this pattern:
2629 <pre>
2630 a+(?C)(*FAIL)
2631 </pre>
2632 A match with the string "aaaa" always fails, but the callout is taken before
2633 each backtrack happens (in this example, 10 times).
2634 </P>
2635 <br><b>
2636 Recording which path was taken
2637 </b><br>
2638 <P>
2639 There is one verb whose main purpose is to track how a match was arrived at,
2640 though it also has a secondary use in conjunction with advancing the match
2641 starting point (see (*SKIP) below).
2642 <pre>
2643 (*MARK:NAME) or (*:NAME)
2644 </pre>
2645 A name is always required with this verb. There may be as many instances of
2646 (*MARK) as you like in a pattern, and their names do not have to be unique.
2647 </P>
2648 <P>
2649 When a match succeeds, the name of the last-encountered (*MARK) on the matching
2650 path is passed back to the caller as described in the section entitled
2651 <a href="pcreapi.html#extradata">"Extra data for <b>pcre_exec()</b>"</a>
2652 in the
2653 <a href="pcreapi.html"><b>pcreapi</b></a>
2654 documentation. Here is an example of <b>pcretest</b> output, where the /K
2655 modifier requests the retrieval and outputting of (*MARK) data:
2656 <pre>
2657 re&#62; /X(*MARK:A)Y|X(*MARK:B)Z/K
2658 data&#62; XY
2659 0: XY
2660 MK: A
2661 XZ
2662 0: XZ
2663 MK: B
2664 </pre>
2665 The (*MARK) name is tagged with "MK:" in this output, and in this example it
2666 indicates which of the two alternatives matched. This is a more efficient way
2667 of obtaining this information than putting each alternative in its own
2668 capturing parentheses.
2669 </P>
2670 <P>
2671 If (*MARK) is encountered in a positive assertion, its name is recorded and
2672 passed back if it is the last-encountered. This does not happen for negative
2673 assertions.
2674 </P>
2675 <P>
2676 After a partial match or a failed match, the name of the last encountered
2677 (*MARK) in the entire match process is returned. For example:
2678 <pre>
2679 re&#62; /X(*MARK:A)Y|X(*MARK:B)Z/K
2680 data&#62; XP
2681 No match, mark = B
2682 </pre>
2683 Note that in this unanchored example the mark is retained from the match
2684 attempt that started at the letter "X" in the subject. Subsequent match
2685 attempts starting at "P" and then with an empty string do not get as far as the
2686 (*MARK) item, but nevertheless do not reset it.
2687 </P>
2688 <P>
2689 If you are interested in (*MARK) values after failed matches, you should
2690 probably set the PCRE_NO_START_OPTIMIZE option
2691 <a href="#nooptimize">(see above)</a>
2692 to ensure that the match is always attempted.
2693 </P>
2694 <br><b>
2695 Verbs that act after backtracking
2696 </b><br>
2697 <P>
2698 The following verbs do nothing when they are encountered. Matching continues
2699 with what follows, but if there is no subsequent match, causing a backtrack to
2700 the verb, a failure is forced. That is, backtracking cannot pass to the left of
2701 the verb. However, when one of these verbs appears inside an atomic group, its
2702 effect is confined to that group, because once the group has been matched,
2703 there is never any backtracking into it. In this situation, backtracking can
2704 "jump back" to the left of the entire atomic group. (Remember also, as stated
2705 above, that this localization also applies in subroutine calls and assertions.)
2706 </P>
2707 <P>
2708 These verbs differ in exactly what kind of failure occurs when backtracking
2709 reaches them.
2710 <pre>
2711 (*COMMIT)
2712 </pre>
2713 This verb, which may not be followed by a name, causes the whole match to fail
2714 outright if the rest of the pattern does not match. Even if the pattern is
2715 unanchored, no further attempts to find a match by advancing the starting point
2716 take place. Once (*COMMIT) has been passed, <b>pcre_exec()</b> is committed to
2717 finding a match at the current starting point, or not at all. For example:
2718 <pre>
2719 a+(*COMMIT)b
2720 </pre>
2721 This matches "xxaab" but not "aacaab". It can be thought of as a kind of
2722 dynamic anchor, or "I've started, so I must finish." The name of the most
2723 recently passed (*MARK) in the path is passed back when (*COMMIT) forces a
2724 match failure.
2725 </P>
2726 <P>
2727 Note that (*COMMIT) at the start of a pattern is not the same as an anchor,
2728 unless PCRE's start-of-match optimizations are turned off, as shown in this
2729 <b>pcretest</b> example:
2730 <pre>
2731 re&#62; /(*COMMIT)abc/
2732 data&#62; xyzabc
2733 0: abc
2734 xyzabc\Y
2735 No match
2736 </pre>
2737 PCRE knows that any match must start with "a", so the optimization skips along
2738 the subject to "a" before running the first match attempt, which succeeds. When
2739 the optimization is disabled by the \Y escape in the second subject, the match
2740 starts at "x" and so the (*COMMIT) causes it to fail without trying any other
2741 starting points.
2742 <pre>
2743 (*PRUNE) or (*PRUNE:NAME)
2744 </pre>
2745 This verb causes the match to fail at the current starting position in the
2746 subject if the rest of the pattern does not match. If the pattern is
2747 unanchored, the normal "bumpalong" advance to the next starting character then
2748 happens. Backtracking can occur as usual to the left of (*PRUNE), before it is
2749 reached, or when matching to the right of (*PRUNE), but if there is no match to
2750 the right, backtracking cannot cross (*PRUNE). In simple cases, the use of
2751 (*PRUNE) is just an alternative to an atomic group or possessive quantifier,
2752 but there are some uses of (*PRUNE) that cannot be expressed in any other way.
2753 The behaviour of (*PRUNE:NAME) is the same as (*MARK:NAME)(*PRUNE). In an
2754 anchored pattern (*PRUNE) has the same effect as (*COMMIT).
2755 <pre>
2756 (*SKIP)
2757 </pre>
2758 This verb, when given without a name, is like (*PRUNE), except that if the
2759 pattern is unanchored, the "bumpalong" advance is not to the next character,
2760 but to the position in the subject where (*SKIP) was encountered. (*SKIP)
2761 signifies that whatever text was matched leading up to it cannot be part of a
2762 successful match. Consider:
2763 <pre>
2764 a+(*SKIP)b
2765 </pre>
2766 If the subject is "aaaac...", after the first match attempt fails (starting at
2767 the first character in the string), the starting point skips on to start the
2768 next attempt at "c". Note that a possessive quantifer does not have the same
2769 effect as this example; although it would suppress backtracking during the
2770 first match attempt, the second attempt would start at the second character
2771 instead of skipping on to "c".
2772 <pre>
2773 (*SKIP:NAME)
2774 </pre>
2775 When (*SKIP) has an associated name, its behaviour is modified. If the
2776 following pattern fails to match, the previous path through the pattern is
2777 searched for the most recent (*MARK) that has the same name. If one is found,
2778 the "bumpalong" advance is to the subject position that corresponds to that
2779 (*MARK) instead of to where (*SKIP) was encountered. If no (*MARK) with a
2780 matching name is found, the (*SKIP) is ignored.
2781 <pre>
2782 (*THEN) or (*THEN:NAME)
2783 </pre>
2784 This verb causes a skip to the next innermost alternative if the rest of the
2785 pattern does not match. That is, it cancels pending backtracking, but only
2786 within the current alternative. Its name comes from the observation that it can
2787 be used for a pattern-based if-then-else block:
2788 <pre>
2789 ( COND1 (*THEN) FOO | COND2 (*THEN) BAR | COND3 (*THEN) BAZ ) ...
2790 </pre>
2791 If the COND1 pattern matches, FOO is tried (and possibly further items after
2792 the end of the group if FOO succeeds); on failure, the matcher skips to the
2793 second alternative and tries COND2, without backtracking into COND1. The
2794 behaviour of (*THEN:NAME) is exactly the same as (*MARK:NAME)(*THEN).
2795 If (*THEN) is not inside an alternation, it acts like (*PRUNE).
2796 </P>
2797 <P>
2798 Note that a subpattern that does not contain a | character is just a part of
2799 the enclosing alternative; it is not a nested alternation with only one
2800 alternative. The effect of (*THEN) extends beyond such a subpattern to the
2801 enclosing alternative. Consider this pattern, where A, B, etc. are complex
2802 pattern fragments that do not contain any | characters at this level:
2803 <pre>
2804 A (B(*THEN)C) | D
2805 </pre>
2806 If A and B are matched, but there is a failure in C, matching does not
2807 backtrack into A; instead it moves to the next alternative, that is, D.
2808 However, if the subpattern containing (*THEN) is given an alternative, it
2809 behaves differently:
2810 <pre>
2811 A (B(*THEN)C | (*FAIL)) | D
2812 </pre>
2813 The effect of (*THEN) is now confined to the inner subpattern. After a failure
2814 in C, matching moves to (*FAIL), which causes the whole subpattern to fail
2815 because there are no more alternatives to try. In this case, matching does now
2816 backtrack into A.
2817 </P>
2818 <P>
2819 Note also that a conditional subpattern is not considered as having two
2820 alternatives, because only one is ever used. In other words, the | character in
2821 a conditional subpattern has a different meaning. Ignoring white space,
2822 consider:
2823 <pre>
2824 ^.*? (?(?=a) a | b(*THEN)c )
2825 </pre>
2826 If the subject is "ba", this pattern does not match. Because .*? is ungreedy,
2827 it initially matches zero characters. The condition (?=a) then fails, the
2828 character "b" is matched, but "c" is not. At this point, matching does not
2829 backtrack to .*? as might perhaps be expected from the presence of the |
2830 character. The conditional subpattern is part of the single alternative that
2831 comprises the whole pattern, and so the match fails. (If there was a backtrack
2832 into .*?, allowing it to match "b", the match would succeed.)
2833 </P>
2834 <P>
2835 The verbs just described provide four different "strengths" of control when
2836 subsequent matching fails. (*THEN) is the weakest, carrying on the match at the
2837 next alternative. (*PRUNE) comes next, failing the match at the current
2838 starting position, but allowing an advance to the next character (for an
2839 unanchored pattern). (*SKIP) is similar, except that the advance may be more
2840 than one character. (*COMMIT) is the strongest, causing the entire match to
2841 fail.
2842 </P>
2843 <P>
2844 If more than one such verb is present in a pattern, the "strongest" one wins.
2845 For example, consider this pattern, where A, B, etc. are complex pattern
2846 fragments:
2847 <pre>
2848 (A(*COMMIT)B(*THEN)C|D)
2849 </pre>
2850 Once A has matched, PCRE is committed to this match, at the current starting
2851 position. If subsequently B matches, but C does not, the normal (*THEN) action
2852 of trying the next alternative (that is, D) does not happen because (*COMMIT)
2853 overrides.
2854 </P>
2855 <br><a name="SEC26" href="#TOC1">SEE ALSO</a><br>
2856 <P>
2857 <b>pcreapi</b>(3), <b>pcrecallout</b>(3), <b>pcrematching</b>(3),
2858 <b>pcresyntax</b>(3), <b>pcre</b>(3), <b>pcre16(3)</b>.
2859 </P>
2860 <br><a name="SEC27" href="#TOC1">AUTHOR</a><br>
2861 <P>
2862 Philip Hazel
2863 <br>
2864 University Computing Service
2865 <br>
2866 Cambridge CB2 3QH, England.
2867 <br>
2868 </P>
2869 <br><a name="SEC28" href="#TOC1">REVISION</a><br>
2870 <P>
2871 Last updated: 14 April 2012
2872 <br>
2873 Copyright &copy; 1997-2012 University of Cambridge.
2874 <br>
2875 <p>
2876 Return to the <a href="index.html">PCRE index page</a>.
2877 </p>

Properties

Name Value
svn:eol-style native
svn:keywords "Author Date Id Revision Url"

  ViewVC Help
Powered by ViewVC 1.1.5