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

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

Parent Directory Parent Directory | Revision Log Revision Log


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

Properties

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

  ViewVC Help
Powered by ViewVC 1.1.5