Commit | Line | Data |
---|---|---|
a0d0e21e | 1 | =head1 NAME |
d74e8afc | 2 | X<regular expression> X<regex> X<regexp> |
a0d0e21e LW |
3 | |
4 | perlre - Perl regular expressions | |
5 | ||
6 | =head1 DESCRIPTION | |
7 | ||
5d458dd8 | 8 | This page describes the syntax of regular expressions in Perl. |
91e0c79e | 9 | |
cc46d5f2 | 10 | If you haven't used regular expressions before, a quick-start |
91e0c79e MJD |
11 | introduction is available in L<perlrequick>, and a longer tutorial |
12 | introduction is available in L<perlretut>. | |
13 | ||
14 | For reference on how regular expressions are used in matching | |
15 | operations, plus various examples of the same, see discussions of | |
16 | C<m//>, C<s///>, C<qr//> and C<??> in L<perlop/"Regexp Quote-Like | |
17 | Operators">. | |
cb1a09d0 | 18 | |
0d017f4d WL |
19 | |
20 | =head2 Modifiers | |
21 | ||
19799a22 | 22 | Matching operations can have various modifiers. Modifiers |
5a964f20 | 23 | that relate to the interpretation of the regular expression inside |
19799a22 | 24 | are listed below. Modifiers that alter the way a regular expression |
5d458dd8 | 25 | is used by Perl are detailed in L<perlop/"Regexp Quote-Like Operators"> and |
1e66bd83 | 26 | L<perlop/"Gory details of parsing quoted constructs">. |
a0d0e21e | 27 | |
55497cff | 28 | =over 4 |
29 | ||
54310121 | 30 | =item m |
d74e8afc | 31 | X</m> X<regex, multiline> X<regexp, multiline> X<regular expression, multiline> |
55497cff | 32 | |
33 | Treat string as multiple lines. That is, change "^" and "$" from matching | |
14218588 | 34 | the start or end of the string to matching the start or end of any |
7f761169 | 35 | line anywhere within the string. |
55497cff | 36 | |
54310121 | 37 | =item s |
d74e8afc ITB |
38 | X</s> X<regex, single-line> X<regexp, single-line> |
39 | X<regular expression, single-line> | |
55497cff | 40 | |
41 | Treat string as single line. That is, change "." to match any character | |
19799a22 | 42 | whatsoever, even a newline, which normally it would not match. |
55497cff | 43 | |
f02c194e | 44 | Used together, as /ms, they let the "." match any character whatsoever, |
fb55449c | 45 | while still allowing "^" and "$" to match, respectively, just after |
19799a22 | 46 | and just before newlines within the string. |
7b8d334a | 47 | |
87e95b7f YO |
48 | =item i |
49 | X</i> X<regex, case-insensitive> X<regexp, case-insensitive> | |
50 | X<regular expression, case-insensitive> | |
51 | ||
52 | Do case-insensitive pattern matching. | |
53 | ||
54 | If C<use locale> is in effect, the case map is taken from the current | |
55 | locale. See L<perllocale>. | |
56 | ||
54310121 | 57 | =item x |
d74e8afc | 58 | X</x> |
55497cff | 59 | |
60 | Extend your pattern's legibility by permitting whitespace and comments. | |
61 | ||
87e95b7f YO |
62 | =item p |
63 | X</p> X<regex, preserve> X<regexp, preserve> | |
64 | ||
65 | Preserve the string matched such that ${^PREMATCH}, {$^MATCH}, and | |
66 | ${^POSTMATCH} are available for use after matching. | |
67 | ||
e2e6bec7 DN |
68 | =item g and c |
69 | X</g> X</c> | |
70 | ||
71 | Global matching, and keep the Current position after failed matching. | |
72 | Unlike i, m, s and x, these two flags affect the way the regex is used | |
73 | rather than the regex itself. See | |
74 | L<perlretut/"Using regular expressions in Perl"> for further explanation | |
75 | of the g and c modifiers. | |
76 | ||
55497cff | 77 | =back |
a0d0e21e LW |
78 | |
79 | These are usually written as "the C</x> modifier", even though the delimiter | |
14218588 | 80 | in question might not really be a slash. Any of these |
a0d0e21e | 81 | modifiers may also be embedded within the regular expression itself using |
14218588 | 82 | the C<(?...)> construct. See below. |
a0d0e21e | 83 | |
4633a7c4 | 84 | The C</x> modifier itself needs a little more explanation. It tells |
55497cff | 85 | the regular expression parser to ignore whitespace that is neither |
86 | backslashed nor within a character class. You can use this to break up | |
4633a7c4 | 87 | your regular expression into (slightly) more readable parts. The C<#> |
54310121 | 88 | character is also treated as a metacharacter introducing a comment, |
55497cff | 89 | just as in ordinary Perl code. This also means that if you want real |
14218588 | 90 | whitespace or C<#> characters in the pattern (outside a character |
f9a3ff1a RGS |
91 | class, where they are unaffected by C</x>), then you'll either have to |
92 | escape them (using backslashes or C<\Q...\E>) or encode them using octal | |
8933a740 RGS |
93 | or hex escapes. Taken together, these features go a long way towards |
94 | making Perl's regular expressions more readable. Note that you have to | |
95 | be careful not to include the pattern delimiter in the comment--perl has | |
96 | no way of knowing you did not intend to close the pattern early. See | |
97 | the C-comment deletion code in L<perlop>. Also note that anything inside | |
1031e5db | 98 | a C<\Q...\E> stays unaffected by C</x>. |
d74e8afc | 99 | X</x> |
a0d0e21e LW |
100 | |
101 | =head2 Regular Expressions | |
102 | ||
04838cea RGS |
103 | =head3 Metacharacters |
104 | ||
384f06ae | 105 | The patterns used in Perl pattern matching evolved from those supplied in |
14218588 | 106 | the Version 8 regex routines. (The routines are derived |
19799a22 GS |
107 | (distantly) from Henry Spencer's freely redistributable reimplementation |
108 | of the V8 routines.) See L<Version 8 Regular Expressions> for | |
109 | details. | |
a0d0e21e LW |
110 | |
111 | In particular the following metacharacters have their standard I<egrep>-ish | |
112 | meanings: | |
d74e8afc ITB |
113 | X<metacharacter> |
114 | X<\> X<^> X<.> X<$> X<|> X<(> X<()> X<[> X<[]> | |
115 | ||
a0d0e21e | 116 | |
54310121 | 117 | \ Quote the next metacharacter |
a0d0e21e LW |
118 | ^ Match the beginning of the line |
119 | . Match any character (except newline) | |
c07a80fd | 120 | $ Match the end of the line (or before newline at the end) |
a0d0e21e LW |
121 | | Alternation |
122 | () Grouping | |
123 | [] Character class | |
124 | ||
14218588 GS |
125 | By default, the "^" character is guaranteed to match only the |
126 | beginning of the string, the "$" character only the end (or before the | |
127 | newline at the end), and Perl does certain optimizations with the | |
a0d0e21e LW |
128 | assumption that the string contains only one line. Embedded newlines |
129 | will not be matched by "^" or "$". You may, however, wish to treat a | |
4a6725af | 130 | string as a multi-line buffer, such that the "^" will match after any |
0d520e8e YO |
131 | newline within the string (except if the newline is the last character in |
132 | the string), and "$" will match before any newline. At the | |
a0d0e21e LW |
133 | cost of a little more overhead, you can do this by using the /m modifier |
134 | on the pattern match operator. (Older programs did this by setting C<$*>, | |
f02c194e | 135 | but this practice has been removed in perl 5.9.) |
d74e8afc | 136 | X<^> X<$> X</m> |
a0d0e21e | 137 | |
14218588 | 138 | To simplify multi-line substitutions, the "." character never matches a |
55497cff | 139 | newline unless you use the C</s> modifier, which in effect tells Perl to pretend |
f02c194e | 140 | the string is a single line--even if it isn't. |
d74e8afc | 141 | X<.> X</s> |
a0d0e21e | 142 | |
04838cea RGS |
143 | =head3 Quantifiers |
144 | ||
a0d0e21e | 145 | The following standard quantifiers are recognized: |
d74e8afc | 146 | X<metacharacter> X<quantifier> X<*> X<+> X<?> X<{n}> X<{n,}> X<{n,m}> |
a0d0e21e LW |
147 | |
148 | * Match 0 or more times | |
149 | + Match 1 or more times | |
150 | ? Match 1 or 0 times | |
151 | {n} Match exactly n times | |
152 | {n,} Match at least n times | |
153 | {n,m} Match at least n but not more than m times | |
154 | ||
155 | (If a curly bracket occurs in any other context, it is treated | |
b975c076 | 156 | as a regular character. In particular, the lower bound |
527e91da BB |
157 | is not optional.) The "*" quantifier is equivalent to C<{0,}>, the "+" |
158 | quantifier to C<{1,}>, and the "?" quantifier to C<{0,1}>. n and m are limited | |
9c79236d GS |
159 | to integral values less than a preset limit defined when perl is built. |
160 | This is usually 32766 on the most common platforms. The actual limit can | |
161 | be seen in the error message generated by code such as this: | |
162 | ||
820475bd | 163 | $_ **= $_ , / {$_} / for 2 .. 42; |
a0d0e21e | 164 | |
54310121 | 165 | By default, a quantified subpattern is "greedy", that is, it will match as |
166 | many times as possible (given a particular starting location) while still | |
167 | allowing the rest of the pattern to match. If you want it to match the | |
168 | minimum number of times possible, follow the quantifier with a "?". Note | |
169 | that the meanings don't change, just the "greediness": | |
0d017f4d | 170 | X<metacharacter> X<greedy> X<greediness> |
d74e8afc | 171 | X<?> X<*?> X<+?> X<??> X<{n}?> X<{n,}?> X<{n,m}?> |
a0d0e21e | 172 | |
0d017f4d WL |
173 | *? Match 0 or more times, not greedily |
174 | +? Match 1 or more times, not greedily | |
175 | ?? Match 0 or 1 time, not greedily | |
176 | {n}? Match exactly n times, not greedily | |
177 | {n,}? Match at least n times, not greedily | |
178 | {n,m}? Match at least n but not more than m times, not greedily | |
a0d0e21e | 179 | |
b9b4dddf YO |
180 | By default, when a quantified subpattern does not allow the rest of the |
181 | overall pattern to match, Perl will backtrack. However, this behaviour is | |
0d017f4d | 182 | sometimes undesirable. Thus Perl provides the "possessive" quantifier form |
b9b4dddf YO |
183 | as well. |
184 | ||
0d017f4d WL |
185 | *+ Match 0 or more times and give nothing back |
186 | ++ Match 1 or more times and give nothing back | |
187 | ?+ Match 0 or 1 time and give nothing back | |
b9b4dddf | 188 | {n}+ Match exactly n times and give nothing back (redundant) |
04838cea RGS |
189 | {n,}+ Match at least n times and give nothing back |
190 | {n,m}+ Match at least n but not more than m times and give nothing back | |
b9b4dddf YO |
191 | |
192 | For instance, | |
193 | ||
194 | 'aaaa' =~ /a++a/ | |
195 | ||
196 | will never match, as the C<a++> will gobble up all the C<a>'s in the | |
197 | string and won't leave any for the remaining part of the pattern. This | |
198 | feature can be extremely useful to give perl hints about where it | |
199 | shouldn't backtrack. For instance, the typical "match a double-quoted | |
200 | string" problem can be most efficiently performed when written as: | |
201 | ||
202 | /"(?:[^"\\]++|\\.)*+"/ | |
203 | ||
0d017f4d | 204 | as we know that if the final quote does not match, backtracking will not |
b9b4dddf YO |
205 | help. See the independent subexpression C<< (?>...) >> for more details; |
206 | possessive quantifiers are just syntactic sugar for that construct. For | |
207 | instance the above example could also be written as follows: | |
208 | ||
209 | /"(?>(?:(?>[^"\\]+)|\\.)*)"/ | |
210 | ||
04838cea RGS |
211 | =head3 Escape sequences |
212 | ||
5f05dabc | 213 | Because patterns are processed as double quoted strings, the following |
a0d0e21e | 214 | also work: |
0d017f4d | 215 | X<\t> X<\n> X<\r> X<\f> X<\e> X<\a> X<\l> X<\u> X<\L> X<\U> X<\E> X<\Q> |
d74e8afc | 216 | X<\0> X<\c> X<\N> X<\x> |
a0d0e21e | 217 | |
0f36ee90 | 218 | \t tab (HT, TAB) |
219 | \n newline (LF, NL) | |
220 | \r return (CR) | |
221 | \f form feed (FF) | |
222 | \a alarm (bell) (BEL) | |
223 | \e escape (think troff) (ESC) | |
0d017f4d WL |
224 | \033 octal char (example: ESC) |
225 | \x1B hex char (example: ESC) | |
196ac2fc | 226 | \x{263a} long hex char (example: Unicode SMILEY) |
0d017f4d | 227 | \cK control char (example: VT) |
196ac2fc | 228 | \N{name} named Unicode character |
cb1a09d0 AD |
229 | \l lowercase next char (think vi) |
230 | \u uppercase next char (think vi) | |
231 | \L lowercase till \E (think vi) | |
232 | \U uppercase till \E (think vi) | |
233 | \E end case modification (think vi) | |
5a964f20 | 234 | \Q quote (disable) pattern metacharacters till \E |
a0d0e21e | 235 | |
a034a98d | 236 | If C<use locale> is in effect, the case map used by C<\l>, C<\L>, C<\u> |
423cee85 | 237 | and C<\U> is taken from the current locale. See L<perllocale>. For |
4a2d328f | 238 | documentation of C<\N{name}>, see L<charnames>. |
a034a98d | 239 | |
1d2dff63 GS |
240 | You cannot include a literal C<$> or C<@> within a C<\Q> sequence. |
241 | An unescaped C<$> or C<@> interpolates the corresponding variable, | |
242 | while escaping will cause the literal string C<\$> to be matched. | |
243 | You'll need to write something like C<m/\Quser\E\@\Qhost/>. | |
244 | ||
e1d1eefb | 245 | =head3 Character Classes and other Special Escapes |
04838cea | 246 | |
a0d0e21e | 247 | In addition, Perl defines the following: |
d74e8afc | 248 | X<\w> X<\W> X<\s> X<\S> X<\d> X<\D> X<\X> X<\p> X<\P> X<\C> |
f7819f85 | 249 | X<\g> X<\k> X<\N> X<\K> X<\v> X<\V> X<\h> X<\H> |
0d017f4d | 250 | X<word> X<whitespace> X<character class> X<backreference> |
a0d0e21e | 251 | |
81714fb9 YO |
252 | \w Match a "word" character (alphanumeric plus "_") |
253 | \W Match a non-"word" character | |
254 | \s Match a whitespace character | |
255 | \S Match a non-whitespace character | |
256 | \d Match a digit character | |
257 | \D Match a non-digit character | |
258 | \pP Match P, named property. Use \p{Prop} for longer names. | |
259 | \PP Match non-P | |
260 | \X Match eXtended Unicode "combining character sequence", | |
e1f17637 | 261 | equivalent to (?>\PM\pM*) |
81714fb9 YO |
262 | \C Match a single C char (octet) even under Unicode. |
263 | NOTE: breaks up characters into their UTF-8 bytes, | |
264 | so you may end up with malformed pieces of UTF-8. | |
265 | Unsupported in lookbehind. | |
5d458dd8 | 266 | \1 Backreference to a specific group. |
c74340f9 | 267 | '1' may actually be any positive integer. |
2bf803e2 YO |
268 | \g1 Backreference to a specific or previous group, |
269 | \g{-1} number may be negative indicating a previous buffer and may | |
270 | optionally be wrapped in curly brackets for safer parsing. | |
1f1031fe | 271 | \g{name} Named backreference |
81714fb9 | 272 | \k<name> Named backreference |
ee9b8eae | 273 | \K Keep the stuff left of the \K, don't include it in $& |
e1d1eefb YO |
274 | \v Vertical whitespace |
275 | \V Not vertical whitespace | |
276 | \h Horizontal whitespace | |
277 | \H Not horizontal whitespace | |
2ddf2931 | 278 | \R Linebreak |
a0d0e21e | 279 | |
08ce8fc6 JH |
280 | A C<\w> matches a single alphanumeric character (an alphabetic |
281 | character, or a decimal digit) or C<_>, not a whole word. Use C<\w+> | |
282 | to match a string of Perl-identifier characters (which isn't the same | |
283 | as matching an English word). If C<use locale> is in effect, the list | |
284 | of alphabetic characters generated by C<\w> is taken from the current | |
285 | locale. See L<perllocale>. You may use C<\w>, C<\W>, C<\s>, C<\S>, | |
0d017f4d WL |
286 | C<\d>, and C<\D> within character classes, but they aren't usable |
287 | as either end of a range. If any of them precedes or follows a "-", | |
288 | the "-" is understood literally. If Unicode is in effect, C<\s> matches | |
c62285ac | 289 | also "\x{85}", "\x{2028}", and "\x{2029}". See L<perlunicode> for more |
0d017f4d WL |
290 | details about C<\pP>, C<\PP>, C<\X> and the possibility of defining |
291 | your own C<\p> and C<\P> properties, and L<perluniintro> about Unicode | |
292 | in general. | |
d74e8afc | 293 | X<\w> X<\W> X<word> |
a0d0e21e | 294 | |
e1d1eefb | 295 | C<\R> will atomically match a linebreak, including the network line-ending |
e2cb52ee | 296 | "\x0D\x0A". Specifically, X<\R> is exactly equivalent to |
e1d1eefb YO |
297 | |
298 | (?>\x0D\x0A?|[\x0A-\x0C\x85\x{2028}\x{2029}]) | |
299 | ||
300 | B<Note:> C<\R> has no special meaning inside of a character class; | |
301 | use C<\v> instead (vertical whitespace). | |
302 | X<\R> | |
303 | ||
b8c5462f | 304 | The POSIX character class syntax |
d74e8afc | 305 | X<character class> |
b8c5462f | 306 | |
820475bd | 307 | [:class:] |
b8c5462f | 308 | |
0d017f4d | 309 | is also available. Note that the C<[> and C<]> brackets are I<literal>; |
5496314a SP |
310 | they must always be used within a character class expression. |
311 | ||
312 | # this is correct: | |
313 | $string =~ /[[:alpha:]]/; | |
314 | ||
315 | # this is not, and will generate a warning: | |
316 | $string =~ /[:alpha:]/; | |
317 | ||
318 | The available classes and their backslash equivalents (if available) are | |
319 | as follows: | |
d74e8afc ITB |
320 | X<character class> |
321 | X<alpha> X<alnum> X<ascii> X<blank> X<cntrl> X<digit> X<graph> | |
322 | X<lower> X<print> X<punct> X<space> X<upper> X<word> X<xdigit> | |
b8c5462f JH |
323 | |
324 | alpha | |
325 | alnum | |
326 | ascii | |
aaa51d5e | 327 | blank [1] |
b8c5462f JH |
328 | cntrl |
329 | digit \d | |
330 | graph | |
331 | lower | |
332 | ||
333 | punct | |
aaa51d5e | 334 | space \s [2] |
b8c5462f | 335 | upper |
aaa51d5e | 336 | word \w [3] |
b8c5462f JH |
337 | xdigit |
338 | ||
07698885 RGS |
339 | =over |
340 | ||
341 | =item [1] | |
342 | ||
b432a672 | 343 | A GNU extension equivalent to C<[ \t]>, "all horizontal whitespace". |
07698885 RGS |
344 | |
345 | =item [2] | |
346 | ||
347 | Not exactly equivalent to C<\s> since the C<[[:space:]]> includes | |
0d017f4d | 348 | also the (very rare) "vertical tabulator", "\cK" or chr(11) in ASCII. |
07698885 RGS |
349 | |
350 | =item [3] | |
351 | ||
08ce8fc6 | 352 | A Perl extension, see above. |
07698885 RGS |
353 | |
354 | =back | |
aaa51d5e | 355 | |
26b44a0a | 356 | For example use C<[:upper:]> to match all the uppercase characters. |
aaa51d5e JF |
357 | Note that the C<[]> are part of the C<[::]> construct, not part of the |
358 | whole character class. For example: | |
b8c5462f | 359 | |
820475bd | 360 | [01[:alpha:]%] |
b8c5462f | 361 | |
0d017f4d | 362 | matches zero, one, any alphabetic character, and the percent sign. |
b8c5462f | 363 | |
72ff2908 JH |
364 | The following equivalences to Unicode \p{} constructs and equivalent |
365 | backslash character classes (if available), will hold: | |
d74e8afc | 366 | X<character class> X<\p> X<\p{}> |
72ff2908 | 367 | |
5496314a | 368 | [[:...:]] \p{...} backslash |
b8c5462f JH |
369 | |
370 | alpha IsAlpha | |
371 | alnum IsAlnum | |
372 | ascii IsASCII | |
0d017f4d | 373 | blank |
b8c5462f | 374 | cntrl IsCntrl |
3bec3564 | 375 | digit IsDigit \d |
b8c5462f JH |
376 | graph IsGraph |
377 | lower IsLower | |
fdf0a293 RB |
378 | print IsPrint (but see [2] below) |
379 | punct IsPunct (but see [3] below) | |
b8c5462f | 380 | space IsSpace |
3bec3564 | 381 | IsSpacePerl \s |
b8c5462f | 382 | upper IsUpper |
fdf0a293 | 383 | word IsWord \w |
b8c5462f JH |
384 | xdigit IsXDigit |
385 | ||
5496314a | 386 | For example C<[[:lower:]]> and C<\p{IsLower}> are equivalent. |
b8c5462f | 387 | |
fdf0a293 RB |
388 | However, the equivalence between C<[[:xxxxx:]]> and C<\p{IsXxxxx}> |
389 | is not exact. | |
390 | ||
391 | =over 4 | |
392 | ||
393 | =item [1] | |
394 | ||
b8c5462f | 395 | If the C<utf8> pragma is not used but the C<locale> pragma is, the |
aaa51d5e | 396 | classes correlate with the usual isalpha(3) interface (except for |
b432a672 | 397 | "word" and "blank"). |
b8c5462f | 398 | |
fdf0a293 RB |
399 | But if the C<locale> or C<encoding> pragmas are not used and |
400 | the string is not C<utf8>, then C<[[:xxxxx:]]> (and C<\w>, etc.) | |
401 | will not match characters 0x80-0xff; whereas C<\p{IsXxxxx}> will | |
402 | force the string to C<utf8> and can match these characters | |
403 | (as Unicode). | |
404 | ||
405 | =item [2] | |
406 | ||
407 | C<\p{IsPrint}> matches characters 0x09-0x0d but C<[[:print:]]> does not. | |
408 | ||
409 | =item [3] | |
410 | ||
411 | C<[[:punct::]]> matches the following but C<\p{IsPunct}> does not, | |
412 | because they are classed as symbols (not punctuation) in Unicode. | |
413 | ||
414 | =over 4 | |
415 | ||
416 | =item C<$> | |
417 | ||
418 | Currency symbol | |
419 | ||
420 | =item C<+> C<< < >> C<=> C<< > >> C<|> C<~> | |
421 | ||
422 | Mathematical symbols | |
423 | ||
424 | =item C<^> C<`> | |
425 | ||
426 | Modifier symbols (accents) | |
427 | ||
428 | =back | |
429 | ||
430 | =back | |
431 | ||
353c6505 | 432 | The other named classes are: |
b8c5462f JH |
433 | |
434 | =over 4 | |
435 | ||
436 | =item cntrl | |
d74e8afc | 437 | X<cntrl> |
b8c5462f | 438 | |
820475bd GS |
439 | Any control character. Usually characters that don't produce output as |
440 | such but instead control the terminal somehow: for example newline and | |
441 | backspace are control characters. All characters with ord() less than | |
0d017f4d | 442 | 32 are usually classified as control characters (assuming ASCII, |
7be5a6cf JF |
443 | the ISO Latin character sets, and Unicode), as is the character with |
444 | the ord() value of 127 (C<DEL>). | |
b8c5462f JH |
445 | |
446 | =item graph | |
d74e8afc | 447 | X<graph> |
b8c5462f | 448 | |
f1cbbd6e | 449 | Any alphanumeric or punctuation (special) character. |
b8c5462f JH |
450 | |
451 | =item print | |
d74e8afc | 452 | X<print> |
b8c5462f | 453 | |
f79b3095 | 454 | Any alphanumeric or punctuation (special) character or the space character. |
b8c5462f JH |
455 | |
456 | =item punct | |
d74e8afc | 457 | X<punct> |
b8c5462f | 458 | |
f1cbbd6e | 459 | Any punctuation (special) character. |
b8c5462f JH |
460 | |
461 | =item xdigit | |
d74e8afc | 462 | X<xdigit> |
b8c5462f | 463 | |
593df60c | 464 | Any hexadecimal digit. Though this may feel silly ([0-9A-Fa-f] would |
820475bd | 465 | work just fine) it is included for completeness. |
b8c5462f | 466 | |
b8c5462f JH |
467 | =back |
468 | ||
469 | You can negate the [::] character classes by prefixing the class name | |
470 | with a '^'. This is a Perl extension. For example: | |
d74e8afc | 471 | X<character class, negation> |
b8c5462f | 472 | |
5496314a | 473 | POSIX traditional Unicode |
93733859 | 474 | |
5496314a SP |
475 | [[:^digit:]] \D \P{IsDigit} |
476 | [[:^space:]] \S \P{IsSpace} | |
477 | [[:^word:]] \W \P{IsWord} | |
b8c5462f | 478 | |
54c18d04 MK |
479 | Perl respects the POSIX standard in that POSIX character classes are |
480 | only supported within a character class. The POSIX character classes | |
481 | [.cc.] and [=cc=] are recognized but B<not> supported and trying to | |
482 | use them will cause an error. | |
b8c5462f | 483 | |
04838cea RGS |
484 | =head3 Assertions |
485 | ||
a0d0e21e | 486 | Perl defines the following zero-width assertions: |
d74e8afc ITB |
487 | X<zero-width assertion> X<assertion> X<regex, zero-width assertion> |
488 | X<regexp, zero-width assertion> | |
489 | X<regular expression, zero-width assertion> | |
490 | X<\b> X<\B> X<\A> X<\Z> X<\z> X<\G> | |
a0d0e21e LW |
491 | |
492 | \b Match a word boundary | |
0d017f4d | 493 | \B Match except at a word boundary |
b85d18e9 IZ |
494 | \A Match only at beginning of string |
495 | \Z Match only at end of string, or before newline at the end | |
496 | \z Match only at end of string | |
9da458fc IZ |
497 | \G Match only at pos() (e.g. at the end-of-match position |
498 | of prior m//g) | |
a0d0e21e | 499 | |
14218588 | 500 | A word boundary (C<\b>) is a spot between two characters |
19799a22 GS |
501 | that has a C<\w> on one side of it and a C<\W> on the other side |
502 | of it (in either order), counting the imaginary characters off the | |
503 | beginning and end of the string as matching a C<\W>. (Within | |
504 | character classes C<\b> represents backspace rather than a word | |
505 | boundary, just as it normally does in any double-quoted string.) | |
506 | The C<\A> and C<\Z> are just like "^" and "$", except that they | |
507 | won't match multiple times when the C</m> modifier is used, while | |
508 | "^" and "$" will match at every internal line boundary. To match | |
509 | the actual end of the string and not ignore an optional trailing | |
510 | newline, use C<\z>. | |
d74e8afc | 511 | X<\b> X<\A> X<\Z> X<\z> X</m> |
19799a22 GS |
512 | |
513 | The C<\G> assertion can be used to chain global matches (using | |
514 | C<m//g>), as described in L<perlop/"Regexp Quote-Like Operators">. | |
515 | It is also useful when writing C<lex>-like scanners, when you have | |
516 | several patterns that you want to match against consequent substrings | |
517 | of your string, see the previous reference. The actual location | |
518 | where C<\G> will match can also be influenced by using C<pos()> as | |
58e23c8d YO |
519 | an lvalue: see L<perlfunc/pos>. Note that the rule for zero-length |
520 | matches is modified somewhat, in that contents to the left of C<\G> is | |
521 | not counted when determining the length of the match. Thus the following | |
522 | will not match forever: | |
d74e8afc | 523 | X<\G> |
c47ff5f1 | 524 | |
58e23c8d YO |
525 | $str = 'ABC'; |
526 | pos($str) = 1; | |
527 | while (/.\G/g) { | |
528 | print $&; | |
529 | } | |
530 | ||
531 | It will print 'A' and then terminate, as it considers the match to | |
532 | be zero-width, and thus will not match at the same position twice in a | |
533 | row. | |
534 | ||
535 | It is worth noting that C<\G> improperly used can result in an infinite | |
536 | loop. Take care when using patterns that include C<\G> in an alternation. | |
537 | ||
04838cea RGS |
538 | =head3 Capture buffers |
539 | ||
0d017f4d WL |
540 | The bracketing construct C<( ... )> creates capture buffers. To refer |
541 | to the current contents of a buffer later on, within the same pattern, | |
542 | use \1 for the first, \2 for the second, and so on. | |
543 | Outside the match use "$" instead of "\". (The | |
81714fb9 | 544 | \<digit> notation works in certain circumstances outside |
14218588 GS |
545 | the match. See the warning below about \1 vs $1 for details.) |
546 | Referring back to another part of the match is called a | |
547 | I<backreference>. | |
d74e8afc ITB |
548 | X<regex, capture buffer> X<regexp, capture buffer> |
549 | X<regular expression, capture buffer> X<backreference> | |
14218588 GS |
550 | |
551 | There is no limit to the number of captured substrings that you may | |
552 | use. However Perl also uses \10, \11, etc. as aliases for \010, | |
fb55449c JH |
553 | \011, etc. (Recall that 0 means octal, so \011 is the character at |
554 | number 9 in your coded character set; which would be the 10th character, | |
81714fb9 YO |
555 | a horizontal tab under ASCII.) Perl resolves this |
556 | ambiguity by interpreting \10 as a backreference only if at least 10 | |
557 | left parentheses have opened before it. Likewise \11 is a | |
558 | backreference only if at least 11 left parentheses have opened | |
559 | before it. And so on. \1 through \9 are always interpreted as | |
5624f11d | 560 | backreferences. |
c74340f9 | 561 | |
1f1031fe | 562 | X<\g{1}> X<\g{-1}> X<\g{name}> X<relative backreference> X<named backreference> |
2bf803e2 | 563 | In order to provide a safer and easier way to construct patterns using |
99d59c4d RGS |
564 | backreferences, Perl provides the C<\g{N}> notation (starting with perl |
565 | 5.10.0). The curly brackets are optional, however omitting them is less | |
566 | safe as the meaning of the pattern can be changed by text (such as digits) | |
567 | following it. When N is a positive integer the C<\g{N}> notation is | |
568 | exactly equivalent to using normal backreferences. When N is a negative | |
569 | integer then it is a relative backreference referring to the previous N'th | |
570 | capturing group. When the bracket form is used and N is not an integer, it | |
571 | is treated as a reference to a named buffer. | |
2bf803e2 YO |
572 | |
573 | Thus C<\g{-1}> refers to the last buffer, C<\g{-2}> refers to the | |
574 | buffer before that. For example: | |
5624f11d YO |
575 | |
576 | / | |
577 | (Y) # buffer 1 | |
578 | ( # buffer 2 | |
579 | (X) # buffer 3 | |
2bf803e2 YO |
580 | \g{-1} # backref to buffer 3 |
581 | \g{-3} # backref to buffer 1 | |
5624f11d YO |
582 | ) |
583 | /x | |
584 | ||
2bf803e2 | 585 | and would match the same as C</(Y) ( (X) \3 \1 )/x>. |
14218588 | 586 | |
99d59c4d | 587 | Additionally, as of Perl 5.10.0 you may use named capture buffers and named |
1f1031fe | 588 | backreferences. The notation is C<< (?<name>...) >> to declare and C<< \k<name> >> |
0d017f4d WL |
589 | to reference. You may also use apostrophes instead of angle brackets to delimit the |
590 | name; and you may use the bracketed C<< \g{name} >> backreference syntax. | |
591 | It's possible to refer to a named capture buffer by absolute and relative number as well. | |
592 | Outside the pattern, a named capture buffer is available via the C<%+> hash. | |
593 | When different buffers within the same pattern have the same name, C<$+{name}> | |
594 | and C<< \k<name> >> refer to the leftmost defined group. (Thus it's possible | |
595 | to do things with named capture buffers that would otherwise require C<(??{})> | |
596 | code to accomplish.) | |
597 | X<named capture buffer> X<regular expression, named capture buffer> | |
64c5a566 | 598 | X<%+> X<$+{name}> X<< \k<name> >> |
81714fb9 | 599 | |
14218588 | 600 | Examples: |
a0d0e21e LW |
601 | |
602 | s/^([^ ]*) *([^ ]*)/$2 $1/; # swap first two words | |
603 | ||
81714fb9 YO |
604 | /(.)\1/ # find first doubled char |
605 | and print "'$1' is the first doubled character\n"; | |
606 | ||
607 | /(?<char>.)\k<char>/ # ... a different way | |
608 | and print "'$+{char}' is the first doubled character\n"; | |
609 | ||
0d017f4d | 610 | /(?'char'.)\1/ # ... mix and match |
81714fb9 | 611 | and print "'$1' is the first doubled character\n"; |
c47ff5f1 | 612 | |
14218588 | 613 | if (/Time: (..):(..):(..)/) { # parse out values |
a0d0e21e LW |
614 | $hours = $1; |
615 | $minutes = $2; | |
616 | $seconds = $3; | |
617 | } | |
c47ff5f1 | 618 | |
14218588 GS |
619 | Several special variables also refer back to portions of the previous |
620 | match. C<$+> returns whatever the last bracket match matched. | |
621 | C<$&> returns the entire matched string. (At one point C<$0> did | |
622 | also, but now it returns the name of the program.) C<$`> returns | |
77ea4f6d JV |
623 | everything before the matched string. C<$'> returns everything |
624 | after the matched string. And C<$^N> contains whatever was matched by | |
625 | the most-recently closed group (submatch). C<$^N> can be used in | |
626 | extended patterns (see below), for example to assign a submatch to a | |
81714fb9 | 627 | variable. |
d74e8afc | 628 | X<$+> X<$^N> X<$&> X<$`> X<$'> |
14218588 | 629 | |
665e98b9 | 630 | The numbered match variables ($1, $2, $3, etc.) and the related punctuation |
77ea4f6d | 631 | set (C<$+>, C<$&>, C<$`>, C<$'>, and C<$^N>) are all dynamically scoped |
14218588 GS |
632 | until the end of the enclosing block or until the next successful |
633 | match, whichever comes first. (See L<perlsyn/"Compound Statements">.) | |
d74e8afc ITB |
634 | X<$+> X<$^N> X<$&> X<$`> X<$'> |
635 | X<$1> X<$2> X<$3> X<$4> X<$5> X<$6> X<$7> X<$8> X<$9> | |
636 | ||
14218588 | 637 | |
0d017f4d | 638 | B<NOTE>: Failed matches in Perl do not reset the match variables, |
5146ce24 | 639 | which makes it easier to write code that tests for a series of more |
665e98b9 JH |
640 | specific cases and remembers the best match. |
641 | ||
14218588 GS |
642 | B<WARNING>: Once Perl sees that you need one of C<$&>, C<$`>, or |
643 | C<$'> anywhere in the program, it has to provide them for every | |
644 | pattern match. This may substantially slow your program. Perl | |
645 | uses the same mechanism to produce $1, $2, etc, so you also pay a | |
646 | price for each pattern that contains capturing parentheses. (To | |
647 | avoid this cost while retaining the grouping behaviour, use the | |
648 | extended regular expression C<(?: ... )> instead.) But if you never | |
649 | use C<$&>, C<$`> or C<$'>, then patterns I<without> capturing | |
650 | parentheses will not be penalized. So avoid C<$&>, C<$'>, and C<$`> | |
651 | if you can, but if you can't (and some algorithms really appreciate | |
652 | them), once you've used them once, use them at will, because you've | |
653 | already paid the price. As of 5.005, C<$&> is not so costly as the | |
654 | other two. | |
d74e8afc | 655 | X<$&> X<$`> X<$'> |
68dc0745 | 656 | |
99d59c4d | 657 | As a workaround for this problem, Perl 5.10.0 introduces C<${^PREMATCH}>, |
cde0cee5 YO |
658 | C<${^MATCH}> and C<${^POSTMATCH}>, which are equivalent to C<$`>, C<$&> |
659 | and C<$'>, B<except> that they are only guaranteed to be defined after a | |
87e95b7f | 660 | successful match that was executed with the C</p> (preserve) modifier. |
cde0cee5 YO |
661 | The use of these variables incurs no global performance penalty, unlike |
662 | their punctuation char equivalents, however at the trade-off that you | |
663 | have to tell perl when you want to use them. | |
87e95b7f | 664 | X</p> X<p modifier> |
cde0cee5 | 665 | |
19799a22 GS |
666 | Backslashed metacharacters in Perl are alphanumeric, such as C<\b>, |
667 | C<\w>, C<\n>. Unlike some other regular expression languages, there | |
668 | are no backslashed symbols that aren't alphanumeric. So anything | |
c47ff5f1 | 669 | that looks like \\, \(, \), \<, \>, \{, or \} is always |
19799a22 GS |
670 | interpreted as a literal character, not a metacharacter. This was |
671 | once used in a common idiom to disable or quote the special meanings | |
672 | of regular expression metacharacters in a string that you want to | |
36bbe248 | 673 | use for a pattern. Simply quote all non-"word" characters: |
a0d0e21e LW |
674 | |
675 | $pattern =~ s/(\W)/\\$1/g; | |
676 | ||
f1cbbd6e | 677 | (If C<use locale> is set, then this depends on the current locale.) |
14218588 GS |
678 | Today it is more common to use the quotemeta() function or the C<\Q> |
679 | metaquoting escape sequence to disable all metacharacters' special | |
680 | meanings like this: | |
a0d0e21e LW |
681 | |
682 | /$unquoted\Q$quoted\E$unquoted/ | |
683 | ||
9da458fc IZ |
684 | Beware that if you put literal backslashes (those not inside |
685 | interpolated variables) between C<\Q> and C<\E>, double-quotish | |
686 | backslash interpolation may lead to confusing results. If you | |
687 | I<need> to use literal backslashes within C<\Q...\E>, | |
688 | consult L<perlop/"Gory details of parsing quoted constructs">. | |
689 | ||
19799a22 GS |
690 | =head2 Extended Patterns |
691 | ||
14218588 GS |
692 | Perl also defines a consistent extension syntax for features not |
693 | found in standard tools like B<awk> and B<lex>. The syntax is a | |
694 | pair of parentheses with a question mark as the first thing within | |
695 | the parentheses. The character after the question mark indicates | |
696 | the extension. | |
19799a22 | 697 | |
14218588 GS |
698 | The stability of these extensions varies widely. Some have been |
699 | part of the core language for many years. Others are experimental | |
700 | and may change without warning or be completely removed. Check | |
701 | the documentation on an individual feature to verify its current | |
702 | status. | |
19799a22 | 703 | |
14218588 GS |
704 | A question mark was chosen for this and for the minimal-matching |
705 | construct because 1) question marks are rare in older regular | |
706 | expressions, and 2) whenever you see one, you should stop and | |
707 | "question" exactly what is going on. That's psychology... | |
a0d0e21e LW |
708 | |
709 | =over 10 | |
710 | ||
cc6b7395 | 711 | =item C<(?#text)> |
d74e8afc | 712 | X<(?#)> |
a0d0e21e | 713 | |
14218588 | 714 | A comment. The text is ignored. If the C</x> modifier enables |
19799a22 | 715 | whitespace formatting, a simple C<#> will suffice. Note that Perl closes |
259138e3 GS |
716 | the comment as soon as it sees a C<)>, so there is no way to put a literal |
717 | C<)> in the comment. | |
a0d0e21e | 718 | |
f7819f85 | 719 | =item C<(?pimsx-imsx)> |
d74e8afc | 720 | X<(?)> |
19799a22 | 721 | |
0b6d1084 JH |
722 | One or more embedded pattern-match modifiers, to be turned on (or |
723 | turned off, if preceded by C<->) for the remainder of the pattern or | |
724 | the remainder of the enclosing pattern group (if any). This is | |
725 | particularly useful for dynamic patterns, such as those read in from a | |
0d017f4d WL |
726 | configuration file, taken from an argument, or specified in a table |
727 | somewhere. Consider the case where some patterns want to be case | |
728 | sensitive and some do not: The case insensitive ones merely need to | |
729 | include C<(?i)> at the front of the pattern. For example: | |
19799a22 GS |
730 | |
731 | $pattern = "foobar"; | |
5d458dd8 | 732 | if ( /$pattern/i ) { } |
19799a22 GS |
733 | |
734 | # more flexible: | |
735 | ||
736 | $pattern = "(?i)foobar"; | |
5d458dd8 | 737 | if ( /$pattern/ ) { } |
19799a22 | 738 | |
0b6d1084 | 739 | These modifiers are restored at the end of the enclosing group. For example, |
19799a22 GS |
740 | |
741 | ( (?i) blah ) \s+ \1 | |
742 | ||
0d017f4d WL |
743 | will match C<blah> in any case, some spaces, and an exact (I<including the case>!) |
744 | repetition of the previous word, assuming the C</x> modifier, and no C</i> | |
745 | modifier outside this group. | |
19799a22 | 746 | |
5530442b | 747 | Note that the C<p> modifier is special in that it can only be enabled, |
cde0cee5 | 748 | not disabled, and that its presence anywhere in a pattern has a global |
5530442b | 749 | effect. Thus C<(?-p)> and C<(?-p:...)> are meaningless and will warn |
cde0cee5 YO |
750 | when executed under C<use warnings>. |
751 | ||
5a964f20 | 752 | =item C<(?:pattern)> |
d74e8afc | 753 | X<(?:)> |
a0d0e21e | 754 | |
ca9dfc88 IZ |
755 | =item C<(?imsx-imsx:pattern)> |
756 | ||
5a964f20 TC |
757 | This is for clustering, not capturing; it groups subexpressions like |
758 | "()", but doesn't make backreferences as "()" does. So | |
a0d0e21e | 759 | |
5a964f20 | 760 | @fields = split(/\b(?:a|b|c)\b/) |
a0d0e21e LW |
761 | |
762 | is like | |
763 | ||
5a964f20 | 764 | @fields = split(/\b(a|b|c)\b/) |
a0d0e21e | 765 | |
19799a22 GS |
766 | but doesn't spit out extra fields. It's also cheaper not to capture |
767 | characters if you don't need to. | |
a0d0e21e | 768 | |
19799a22 | 769 | Any letters between C<?> and C<:> act as flags modifiers as with |
5d458dd8 | 770 | C<(?imsx-imsx)>. For example, |
ca9dfc88 IZ |
771 | |
772 | /(?s-i:more.*than).*million/i | |
773 | ||
14218588 | 774 | is equivalent to the more verbose |
ca9dfc88 IZ |
775 | |
776 | /(?:(?s-i)more.*than).*million/i | |
777 | ||
594d7033 YO |
778 | =item C<(?|pattern)> |
779 | X<(?|)> X<Branch reset> | |
780 | ||
781 | This is the "branch reset" pattern, which has the special property | |
782 | that the capture buffers are numbered from the same starting point | |
99d59c4d | 783 | in each alternation branch. It is available starting from perl 5.10.0. |
4deaaa80 | 784 | |
693596a8 RGS |
785 | Capture buffers are numbered from left to right, but inside this |
786 | construct the numbering is restarted for each branch. | |
4deaaa80 PJ |
787 | |
788 | The numbering within each branch will be as normal, and any buffers | |
789 | following this construct will be numbered as though the construct | |
790 | contained only one branch, that being the one with the most capture | |
791 | buffers in it. | |
792 | ||
793 | This construct will be useful when you want to capture one of a | |
794 | number of alternative matches. | |
795 | ||
796 | Consider the following pattern. The numbers underneath show in | |
797 | which buffer the captured content will be stored. | |
594d7033 YO |
798 | |
799 | ||
800 | # before ---------------branch-reset----------- after | |
801 | / ( a ) (?| x ( y ) z | (p (q) r) | (t) u (v) ) ( z ) /x | |
802 | # 1 2 2 3 2 3 4 | |
803 | ||
90a18110 RGS |
804 | Note: as of Perl 5.10.0, branch resets interfere with the contents of |
805 | the C<%+> hash, that holds named captures. Consider using C<%-> instead. | |
806 | ||
ee9b8eae YO |
807 | =item Look-Around Assertions |
808 | X<look-around assertion> X<lookaround assertion> X<look-around> X<lookaround> | |
809 | ||
810 | Look-around assertions are zero width patterns which match a specific | |
811 | pattern without including it in C<$&>. Positive assertions match when | |
812 | their subpattern matches, negative assertions match when their subpattern | |
813 | fails. Look-behind matches text up to the current match position, | |
814 | look-ahead matches text following the current match position. | |
815 | ||
816 | =over 4 | |
817 | ||
5a964f20 | 818 | =item C<(?=pattern)> |
d74e8afc | 819 | X<(?=)> X<look-ahead, positive> X<lookahead, positive> |
a0d0e21e | 820 | |
19799a22 | 821 | A zero-width positive look-ahead assertion. For example, C</\w+(?=\t)/> |
a0d0e21e LW |
822 | matches a word followed by a tab, without including the tab in C<$&>. |
823 | ||
5a964f20 | 824 | =item C<(?!pattern)> |
d74e8afc | 825 | X<(?!)> X<look-ahead, negative> X<lookahead, negative> |
a0d0e21e | 826 | |
19799a22 | 827 | A zero-width negative look-ahead assertion. For example C</foo(?!bar)/> |
a0d0e21e | 828 | matches any occurrence of "foo" that isn't followed by "bar". Note |
19799a22 GS |
829 | however that look-ahead and look-behind are NOT the same thing. You cannot |
830 | use this for look-behind. | |
7b8d334a | 831 | |
5a964f20 | 832 | If you are looking for a "bar" that isn't preceded by a "foo", C</(?!foo)bar/> |
7b8d334a GS |
833 | will not do what you want. That's because the C<(?!foo)> is just saying that |
834 | the next thing cannot be "foo"--and it's not, it's a "bar", so "foobar" will | |
835 | match. You would have to do something like C</(?!foo)...bar/> for that. We | |
836 | say "like" because there's the case of your "bar" not having three characters | |
837 | before it. You could cover that this way: C</(?:(?!foo)...|^.{0,2})bar/>. | |
838 | Sometimes it's still easier just to say: | |
a0d0e21e | 839 | |
a3cb178b | 840 | if (/bar/ && $` !~ /foo$/) |
a0d0e21e | 841 | |
19799a22 | 842 | For look-behind see below. |
c277df42 | 843 | |
ee9b8eae YO |
844 | =item C<(?<=pattern)> C<\K> |
845 | X<(?<=)> X<look-behind, positive> X<lookbehind, positive> X<\K> | |
c277df42 | 846 | |
c47ff5f1 | 847 | A zero-width positive look-behind assertion. For example, C</(?<=\t)\w+/> |
19799a22 GS |
848 | matches a word that follows a tab, without including the tab in C<$&>. |
849 | Works only for fixed-width look-behind. | |
c277df42 | 850 | |
ee9b8eae YO |
851 | There is a special form of this construct, called C<\K>, which causes the |
852 | regex engine to "keep" everything it had matched prior to the C<\K> and | |
853 | not include it in C<$&>. This effectively provides variable length | |
854 | look-behind. The use of C<\K> inside of another look-around assertion | |
855 | is allowed, but the behaviour is currently not well defined. | |
856 | ||
c62285ac | 857 | For various reasons C<\K> may be significantly more efficient than the |
ee9b8eae YO |
858 | equivalent C<< (?<=...) >> construct, and it is especially useful in |
859 | situations where you want to efficiently remove something following | |
860 | something else in a string. For instance | |
861 | ||
862 | s/(foo)bar/$1/g; | |
863 | ||
864 | can be rewritten as the much more efficient | |
865 | ||
866 | s/foo\Kbar//g; | |
867 | ||
5a964f20 | 868 | =item C<(?<!pattern)> |
d74e8afc | 869 | X<(?<!)> X<look-behind, negative> X<lookbehind, negative> |
c277df42 | 870 | |
19799a22 GS |
871 | A zero-width negative look-behind assertion. For example C</(?<!bar)foo/> |
872 | matches any occurrence of "foo" that does not follow "bar". Works | |
873 | only for fixed-width look-behind. | |
c277df42 | 874 | |
ee9b8eae YO |
875 | =back |
876 | ||
81714fb9 YO |
877 | =item C<(?'NAME'pattern)> |
878 | ||
879 | =item C<< (?<NAME>pattern) >> | |
880 | X<< (?<NAME>) >> X<(?'NAME')> X<named capture> X<capture> | |
881 | ||
882 | A named capture buffer. Identical in every respect to normal capturing | |
90a18110 RGS |
883 | parentheses C<()> but for the additional fact that C<%+> or C<%-> may be |
884 | used after a successful match to refer to a named buffer. See C<perlvar> | |
885 | for more details on the C<%+> and C<%-> hashes. | |
81714fb9 YO |
886 | |
887 | If multiple distinct capture buffers have the same name then the | |
888 | $+{NAME} will refer to the leftmost defined buffer in the match. | |
889 | ||
0d017f4d | 890 | The forms C<(?'NAME'pattern)> and C<< (?<NAME>pattern) >> are equivalent. |
81714fb9 YO |
891 | |
892 | B<NOTE:> While the notation of this construct is the same as the similar | |
0d017f4d | 893 | function in .NET regexes, the behavior is not. In Perl the buffers are |
81714fb9 YO |
894 | numbered sequentially regardless of being named or not. Thus in the |
895 | pattern | |
896 | ||
897 | /(x)(?<foo>y)(z)/ | |
898 | ||
899 | $+{foo} will be the same as $2, and $3 will contain 'z' instead of | |
900 | the opposite which is what a .NET regex hacker might expect. | |
901 | ||
1f1031fe YO |
902 | Currently NAME is restricted to simple identifiers only. |
903 | In other words, it must match C</^[_A-Za-z][_A-Za-z0-9]*\z/> or | |
904 | its Unicode extension (see L<utf8>), | |
905 | though it isn't extended by the locale (see L<perllocale>). | |
81714fb9 | 906 | |
1f1031fe | 907 | B<NOTE:> In order to make things easier for programmers with experience |
ae5648b3 | 908 | with the Python or PCRE regex engines, the pattern C<< (?PE<lt>NAMEE<gt>pattern) >> |
0d017f4d | 909 | may be used instead of C<< (?<NAME>pattern) >>; however this form does not |
64c5a566 | 910 | support the use of single quotes as a delimiter for the name. |
81714fb9 | 911 | |
1f1031fe YO |
912 | =item C<< \k<NAME> >> |
913 | ||
914 | =item C<< \k'NAME' >> | |
81714fb9 YO |
915 | |
916 | Named backreference. Similar to numeric backreferences, except that | |
917 | the group is designated by name and not number. If multiple groups | |
918 | have the same name then it refers to the leftmost defined group in | |
919 | the current match. | |
920 | ||
0d017f4d | 921 | It is an error to refer to a name not defined by a C<< (?<NAME>) >> |
81714fb9 YO |
922 | earlier in the pattern. |
923 | ||
924 | Both forms are equivalent. | |
925 | ||
1f1031fe | 926 | B<NOTE:> In order to make things easier for programmers with experience |
0d017f4d | 927 | with the Python or PCRE regex engines, the pattern C<< (?P=NAME) >> |
64c5a566 | 928 | may be used instead of C<< \k<NAME> >>. |
1f1031fe | 929 | |
cc6b7395 | 930 | =item C<(?{ code })> |
d74e8afc | 931 | X<(?{})> X<regex, code in> X<regexp, code in> X<regular expression, code in> |
c277df42 | 932 | |
19799a22 | 933 | B<WARNING>: This extended regular expression feature is considered |
b9b4dddf YO |
934 | experimental, and may be changed without notice. Code executed that |
935 | has side effects may not perform identically from version to version | |
936 | due to the effect of future optimisations in the regex engine. | |
c277df42 | 937 | |
cc46d5f2 | 938 | This zero-width assertion evaluates any embedded Perl code. It |
19799a22 GS |
939 | always succeeds, and its C<code> is not interpolated. Currently, |
940 | the rules to determine where the C<code> ends are somewhat convoluted. | |
941 | ||
77ea4f6d JV |
942 | This feature can be used together with the special variable C<$^N> to |
943 | capture the results of submatches in variables without having to keep | |
944 | track of the number of nested parentheses. For example: | |
945 | ||
946 | $_ = "The brown fox jumps over the lazy dog"; | |
947 | /the (\S+)(?{ $color = $^N }) (\S+)(?{ $animal = $^N })/i; | |
948 | print "color = $color, animal = $animal\n"; | |
949 | ||
754091cb RGS |
950 | Inside the C<(?{...})> block, C<$_> refers to the string the regular |
951 | expression is matching against. You can also use C<pos()> to know what is | |
fa11829f | 952 | the current position of matching within this string. |
754091cb | 953 | |
19799a22 GS |
954 | The C<code> is properly scoped in the following sense: If the assertion |
955 | is backtracked (compare L<"Backtracking">), all changes introduced after | |
956 | C<local>ization are undone, so that | |
b9ac3b5b GS |
957 | |
958 | $_ = 'a' x 8; | |
5d458dd8 | 959 | m< |
b9ac3b5b GS |
960 | (?{ $cnt = 0 }) # Initialize $cnt. |
961 | ( | |
5d458dd8 | 962 | a |
b9ac3b5b GS |
963 | (?{ |
964 | local $cnt = $cnt + 1; # Update $cnt, backtracking-safe. | |
965 | }) | |
5d458dd8 | 966 | )* |
b9ac3b5b GS |
967 | aaaa |
968 | (?{ $res = $cnt }) # On success copy to non-localized | |
969 | # location. | |
970 | >x; | |
971 | ||
0d017f4d | 972 | will set C<$res = 4>. Note that after the match, C<$cnt> returns to the globally |
14218588 | 973 | introduced value, because the scopes that restrict C<local> operators |
b9ac3b5b GS |
974 | are unwound. |
975 | ||
19799a22 GS |
976 | This assertion may be used as a C<(?(condition)yes-pattern|no-pattern)> |
977 | switch. If I<not> used in this way, the result of evaluation of | |
978 | C<code> is put into the special variable C<$^R>. This happens | |
979 | immediately, so C<$^R> can be used from other C<(?{ code })> assertions | |
980 | inside the same regular expression. | |
b9ac3b5b | 981 | |
19799a22 GS |
982 | The assignment to C<$^R> above is properly localized, so the old |
983 | value of C<$^R> is restored if the assertion is backtracked; compare | |
984 | L<"Backtracking">. | |
b9ac3b5b | 985 | |
61528107 SP |
986 | Due to an unfortunate implementation issue, the Perl code contained in these |
987 | blocks is treated as a compile time closure that can have seemingly bizarre | |
6bda09f9 | 988 | consequences when used with lexically scoped variables inside of subroutines |
61528107 SP |
989 | or loops. There are various workarounds for this, including simply using |
990 | global variables instead. If you are using this construct and strange results | |
6bda09f9 YO |
991 | occur then check for the use of lexically scoped variables. |
992 | ||
19799a22 GS |
993 | For reasons of security, this construct is forbidden if the regular |
994 | expression involves run-time interpolation of variables, unless the | |
995 | perilous C<use re 'eval'> pragma has been used (see L<re>), or the | |
996 | variables contain results of C<qr//> operator (see | |
5d458dd8 | 997 | L<perlop/"qr/STRING/imosx">). |
871b0233 | 998 | |
0d017f4d | 999 | This restriction is due to the wide-spread and remarkably convenient |
19799a22 | 1000 | custom of using run-time determined strings as patterns. For example: |
871b0233 IZ |
1001 | |
1002 | $re = <>; | |
1003 | chomp $re; | |
1004 | $string =~ /$re/; | |
1005 | ||
14218588 GS |
1006 | Before Perl knew how to execute interpolated code within a pattern, |
1007 | this operation was completely safe from a security point of view, | |
1008 | although it could raise an exception from an illegal pattern. If | |
1009 | you turn on the C<use re 'eval'>, though, it is no longer secure, | |
1010 | so you should only do so if you are also using taint checking. | |
1011 | Better yet, use the carefully constrained evaluation within a Safe | |
cc46d5f2 | 1012 | compartment. See L<perlsec> for details about both these mechanisms. |
871b0233 | 1013 | |
0d017f4d | 1014 | Because Perl's regex engine is currently not re-entrant, interpolated |
8988a1bb DD |
1015 | code may not invoke the regex engine either directly with C<m//> or C<s///>), |
1016 | or indirectly with functions such as C<split>. | |
1017 | ||
14455d6c | 1018 | =item C<(??{ code })> |
d74e8afc ITB |
1019 | X<(??{})> |
1020 | X<regex, postponed> X<regexp, postponed> X<regular expression, postponed> | |
0f5d15d6 | 1021 | |
19799a22 | 1022 | B<WARNING>: This extended regular expression feature is considered |
b9b4dddf YO |
1023 | experimental, and may be changed without notice. Code executed that |
1024 | has side effects may not perform identically from version to version | |
1025 | due to the effect of future optimisations in the regex engine. | |
0f5d15d6 | 1026 | |
19799a22 GS |
1027 | This is a "postponed" regular subexpression. The C<code> is evaluated |
1028 | at run time, at the moment this subexpression may match. The result | |
1029 | of evaluation is considered as a regular expression and matched as | |
61528107 | 1030 | if it were inserted instead of this construct. Note that this means |
6bda09f9 YO |
1031 | that the contents of capture buffers defined inside an eval'ed pattern |
1032 | are not available outside of the pattern, and vice versa, there is no | |
1033 | way for the inner pattern to refer to a capture buffer defined outside. | |
1034 | Thus, | |
1035 | ||
1036 | ('a' x 100)=~/(??{'(.)' x 100})/ | |
1037 | ||
81714fb9 | 1038 | B<will> match, it will B<not> set $1. |
0f5d15d6 | 1039 | |
428594d9 | 1040 | The C<code> is not interpolated. As before, the rules to determine |
19799a22 GS |
1041 | where the C<code> ends are currently somewhat convoluted. |
1042 | ||
1043 | The following pattern matches a parenthesized group: | |
0f5d15d6 IZ |
1044 | |
1045 | $re = qr{ | |
1046 | \( | |
1047 | (?: | |
1048 | (?> [^()]+ ) # Non-parens without backtracking | |
1049 | | | |
14455d6c | 1050 | (??{ $re }) # Group with matching parens |
0f5d15d6 IZ |
1051 | )* |
1052 | \) | |
1053 | }x; | |
1054 | ||
6bda09f9 YO |
1055 | See also C<(?PARNO)> for a different, more efficient way to accomplish |
1056 | the same task. | |
1057 | ||
5d458dd8 | 1058 | Because perl's regex engine is not currently re-entrant, delayed |
8988a1bb DD |
1059 | code may not invoke the regex engine either directly with C<m//> or C<s///>), |
1060 | or indirectly with functions such as C<split>. | |
1061 | ||
5d458dd8 YO |
1062 | Recursing deeper than 50 times without consuming any input string will |
1063 | result in a fatal error. The maximum depth is compiled into perl, so | |
6bda09f9 YO |
1064 | changing it requires a custom build. |
1065 | ||
542fa716 YO |
1066 | =item C<(?PARNO)> C<(?-PARNO)> C<(?+PARNO)> C<(?R)> C<(?0)> |
1067 | X<(?PARNO)> X<(?1)> X<(?R)> X<(?0)> X<(?-1)> X<(?+1)> X<(?-PARNO)> X<(?+PARNO)> | |
6bda09f9 | 1068 | X<regex, recursive> X<regexp, recursive> X<regular expression, recursive> |
542fa716 | 1069 | X<regex, relative recursion> |
6bda09f9 | 1070 | |
81714fb9 YO |
1071 | Similar to C<(??{ code })> except it does not involve compiling any code, |
1072 | instead it treats the contents of a capture buffer as an independent | |
61528107 | 1073 | pattern that must match at the current position. Capture buffers |
81714fb9 | 1074 | contained by the pattern will have the value as determined by the |
6bda09f9 YO |
1075 | outermost recursion. |
1076 | ||
894be9b7 YO |
1077 | PARNO is a sequence of digits (not starting with 0) whose value reflects |
1078 | the paren-number of the capture buffer to recurse to. C<(?R)> recurses to | |
1079 | the beginning of the whole pattern. C<(?0)> is an alternate syntax for | |
542fa716 YO |
1080 | C<(?R)>. If PARNO is preceded by a plus or minus sign then it is assumed |
1081 | to be relative, with negative numbers indicating preceding capture buffers | |
1082 | and positive ones following. Thus C<(?-1)> refers to the most recently | |
1083 | declared buffer, and C<(?+1)> indicates the next buffer to be declared. | |
c74340f9 YO |
1084 | Note that the counting for relative recursion differs from that of |
1085 | relative backreferences, in that with recursion unclosed buffers B<are> | |
1086 | included. | |
6bda09f9 | 1087 | |
81714fb9 | 1088 | The following pattern matches a function foo() which may contain |
f145b7e9 | 1089 | balanced parentheses as the argument. |
6bda09f9 YO |
1090 | |
1091 | $re = qr{ ( # paren group 1 (full function) | |
81714fb9 | 1092 | foo |
6bda09f9 YO |
1093 | ( # paren group 2 (parens) |
1094 | \( | |
1095 | ( # paren group 3 (contents of parens) | |
1096 | (?: | |
1097 | (?> [^()]+ ) # Non-parens without backtracking | |
1098 | | | |
1099 | (?2) # Recurse to start of paren group 2 | |
1100 | )* | |
1101 | ) | |
1102 | \) | |
1103 | ) | |
1104 | ) | |
1105 | }x; | |
1106 | ||
1107 | If the pattern was used as follows | |
1108 | ||
1109 | 'foo(bar(baz)+baz(bop))'=~/$re/ | |
1110 | and print "\$1 = $1\n", | |
1111 | "\$2 = $2\n", | |
1112 | "\$3 = $3\n"; | |
1113 | ||
1114 | the output produced should be the following: | |
1115 | ||
1116 | $1 = foo(bar(baz)+baz(bop)) | |
1117 | $2 = (bar(baz)+baz(bop)) | |
81714fb9 | 1118 | $3 = bar(baz)+baz(bop) |
6bda09f9 | 1119 | |
81714fb9 | 1120 | If there is no corresponding capture buffer defined, then it is a |
61528107 | 1121 | fatal error. Recursing deeper than 50 times without consuming any input |
81714fb9 | 1122 | string will also result in a fatal error. The maximum depth is compiled |
6bda09f9 YO |
1123 | into perl, so changing it requires a custom build. |
1124 | ||
542fa716 YO |
1125 | The following shows how using negative indexing can make it |
1126 | easier to embed recursive patterns inside of a C<qr//> construct | |
1127 | for later use: | |
1128 | ||
1129 | my $parens = qr/(\((?:[^()]++|(?-1))*+\))/; | |
1130 | if (/foo $parens \s+ + \s+ bar $parens/x) { | |
1131 | # do something here... | |
1132 | } | |
1133 | ||
81714fb9 | 1134 | B<Note> that this pattern does not behave the same way as the equivalent |
0d017f4d | 1135 | PCRE or Python construct of the same form. In Perl you can backtrack into |
6bda09f9 | 1136 | a recursed group, in PCRE and Python the recursed into group is treated |
542fa716 YO |
1137 | as atomic. Also, modifiers are resolved at compile time, so constructs |
1138 | like (?i:(?1)) or (?:(?i)(?1)) do not affect how the sub-pattern will | |
1139 | be processed. | |
6bda09f9 | 1140 | |
894be9b7 YO |
1141 | =item C<(?&NAME)> |
1142 | X<(?&NAME)> | |
1143 | ||
0d017f4d WL |
1144 | Recurse to a named subpattern. Identical to C<(?PARNO)> except that the |
1145 | parenthesis to recurse to is determined by name. If multiple parentheses have | |
894be9b7 YO |
1146 | the same name, then it recurses to the leftmost. |
1147 | ||
1148 | It is an error to refer to a name that is not declared somewhere in the | |
1149 | pattern. | |
1150 | ||
1f1031fe YO |
1151 | B<NOTE:> In order to make things easier for programmers with experience |
1152 | with the Python or PCRE regex engines the pattern C<< (?P>NAME) >> | |
64c5a566 | 1153 | may be used instead of C<< (?&NAME) >>. |
1f1031fe | 1154 | |
e2e6a0f1 YO |
1155 | =item C<(?(condition)yes-pattern|no-pattern)> |
1156 | X<(?()> | |
286f584a | 1157 | |
e2e6a0f1 | 1158 | =item C<(?(condition)yes-pattern)> |
286f584a | 1159 | |
e2e6a0f1 YO |
1160 | Conditional expression. C<(condition)> should be either an integer in |
1161 | parentheses (which is valid if the corresponding pair of parentheses | |
1162 | matched), a look-ahead/look-behind/evaluate zero-width assertion, a | |
1163 | name in angle brackets or single quotes (which is valid if a buffer | |
1164 | with the given name matched), or the special symbol (R) (true when | |
1165 | evaluated inside of recursion or eval). Additionally the R may be | |
1166 | followed by a number, (which will be true when evaluated when recursing | |
1167 | inside of the appropriate group), or by C<&NAME>, in which case it will | |
1168 | be true only when evaluated during recursion in the named group. | |
1169 | ||
1170 | Here's a summary of the possible predicates: | |
1171 | ||
1172 | =over 4 | |
1173 | ||
1174 | =item (1) (2) ... | |
1175 | ||
1176 | Checks if the numbered capturing buffer has matched something. | |
1177 | ||
1178 | =item (<NAME>) ('NAME') | |
1179 | ||
1180 | Checks if a buffer with the given name has matched something. | |
1181 | ||
1182 | =item (?{ CODE }) | |
1183 | ||
1184 | Treats the code block as the condition. | |
1185 | ||
1186 | =item (R) | |
1187 | ||
1188 | Checks if the expression has been evaluated inside of recursion. | |
1189 | ||
1190 | =item (R1) (R2) ... | |
1191 | ||
1192 | Checks if the expression has been evaluated while executing directly | |
1193 | inside of the n-th capture group. This check is the regex equivalent of | |
1194 | ||
1195 | if ((caller(0))[3] eq 'subname') { ... } | |
1196 | ||
1197 | In other words, it does not check the full recursion stack. | |
1198 | ||
1199 | =item (R&NAME) | |
1200 | ||
1201 | Similar to C<(R1)>, this predicate checks to see if we're executing | |
1202 | directly inside of the leftmost group with a given name (this is the same | |
1203 | logic used by C<(?&NAME)> to disambiguate). It does not check the full | |
1204 | stack, but only the name of the innermost active recursion. | |
1205 | ||
1206 | =item (DEFINE) | |
1207 | ||
1208 | In this case, the yes-pattern is never directly executed, and no | |
1209 | no-pattern is allowed. Similar in spirit to C<(?{0})> but more efficient. | |
1210 | See below for details. | |
1211 | ||
1212 | =back | |
1213 | ||
1214 | For example: | |
1215 | ||
1216 | m{ ( \( )? | |
1217 | [^()]+ | |
1218 | (?(1) \) ) | |
1219 | }x | |
1220 | ||
1221 | matches a chunk of non-parentheses, possibly included in parentheses | |
1222 | themselves. | |
1223 | ||
1224 | A special form is the C<(DEFINE)> predicate, which never executes directly | |
1225 | its yes-pattern, and does not allow a no-pattern. This allows to define | |
1226 | subpatterns which will be executed only by using the recursion mechanism. | |
1227 | This way, you can define a set of regular expression rules that can be | |
1228 | bundled into any pattern you choose. | |
1229 | ||
1230 | It is recommended that for this usage you put the DEFINE block at the | |
1231 | end of the pattern, and that you name any subpatterns defined within it. | |
1232 | ||
1233 | Also, it's worth noting that patterns defined this way probably will | |
1234 | not be as efficient, as the optimiser is not very clever about | |
1235 | handling them. | |
1236 | ||
1237 | An example of how this might be used is as follows: | |
1238 | ||
2bf803e2 | 1239 | /(?<NAME>(?&NAME_PAT))(?<ADDR>(?&ADDRESS_PAT)) |
e2e6a0f1 | 1240 | (?(DEFINE) |
2bf803e2 YO |
1241 | (?<NAME_PAT>....) |
1242 | (?<ADRESS_PAT>....) | |
e2e6a0f1 YO |
1243 | )/x |
1244 | ||
1245 | Note that capture buffers matched inside of recursion are not accessible | |
0d017f4d | 1246 | after the recursion returns, so the extra layer of capturing buffers is |
e2e6a0f1 YO |
1247 | necessary. Thus C<$+{NAME_PAT}> would not be defined even though |
1248 | C<$+{NAME}> would be. | |
286f584a | 1249 | |
c47ff5f1 | 1250 | =item C<< (?>pattern) >> |
6bda09f9 | 1251 | X<backtrack> X<backtracking> X<atomic> X<possessive> |
5a964f20 | 1252 | |
19799a22 GS |
1253 | An "independent" subexpression, one which matches the substring |
1254 | that a I<standalone> C<pattern> would match if anchored at the given | |
9da458fc | 1255 | position, and it matches I<nothing other than this substring>. This |
19799a22 GS |
1256 | construct is useful for optimizations of what would otherwise be |
1257 | "eternal" matches, because it will not backtrack (see L<"Backtracking">). | |
9da458fc IZ |
1258 | It may also be useful in places where the "grab all you can, and do not |
1259 | give anything back" semantic is desirable. | |
19799a22 | 1260 | |
c47ff5f1 | 1261 | For example: C<< ^(?>a*)ab >> will never match, since C<< (?>a*) >> |
19799a22 GS |
1262 | (anchored at the beginning of string, as above) will match I<all> |
1263 | characters C<a> at the beginning of string, leaving no C<a> for | |
1264 | C<ab> to match. In contrast, C<a*ab> will match the same as C<a+b>, | |
1265 | since the match of the subgroup C<a*> is influenced by the following | |
1266 | group C<ab> (see L<"Backtracking">). In particular, C<a*> inside | |
1267 | C<a*ab> will match fewer characters than a standalone C<a*>, since | |
1268 | this makes the tail match. | |
1269 | ||
c47ff5f1 | 1270 | An effect similar to C<< (?>pattern) >> may be achieved by writing |
19799a22 GS |
1271 | C<(?=(pattern))\1>. This matches the same substring as a standalone |
1272 | C<a+>, and the following C<\1> eats the matched string; it therefore | |
c47ff5f1 | 1273 | makes a zero-length assertion into an analogue of C<< (?>...) >>. |
19799a22 GS |
1274 | (The difference between these two constructs is that the second one |
1275 | uses a capturing group, thus shifting ordinals of backreferences | |
1276 | in the rest of a regular expression.) | |
1277 | ||
1278 | Consider this pattern: | |
c277df42 | 1279 | |
871b0233 | 1280 | m{ \( |
e2e6a0f1 YO |
1281 | ( |
1282 | [^()]+ # x+ | |
1283 | | | |
871b0233 IZ |
1284 | \( [^()]* \) |
1285 | )+ | |
e2e6a0f1 | 1286 | \) |
871b0233 | 1287 | }x |
5a964f20 | 1288 | |
19799a22 GS |
1289 | That will efficiently match a nonempty group with matching parentheses |
1290 | two levels deep or less. However, if there is no such group, it | |
1291 | will take virtually forever on a long string. That's because there | |
1292 | are so many different ways to split a long string into several | |
1293 | substrings. This is what C<(.+)+> is doing, and C<(.+)+> is similar | |
1294 | to a subpattern of the above pattern. Consider how the pattern | |
1295 | above detects no-match on C<((()aaaaaaaaaaaaaaaaaa> in several | |
1296 | seconds, but that each extra letter doubles this time. This | |
1297 | exponential performance will make it appear that your program has | |
14218588 | 1298 | hung. However, a tiny change to this pattern |
5a964f20 | 1299 | |
e2e6a0f1 YO |
1300 | m{ \( |
1301 | ( | |
1302 | (?> [^()]+ ) # change x+ above to (?> x+ ) | |
1303 | | | |
871b0233 IZ |
1304 | \( [^()]* \) |
1305 | )+ | |
e2e6a0f1 | 1306 | \) |
871b0233 | 1307 | }x |
c277df42 | 1308 | |
c47ff5f1 | 1309 | which uses C<< (?>...) >> matches exactly when the one above does (verifying |
5a964f20 TC |
1310 | this yourself would be a productive exercise), but finishes in a fourth |
1311 | the time when used on a similar string with 1000000 C<a>s. Be aware, | |
1312 | however, that this pattern currently triggers a warning message under | |
9f1b1f2d | 1313 | the C<use warnings> pragma or B<-w> switch saying it |
6bab786b | 1314 | C<"matches null string many times in regex">. |
c277df42 | 1315 | |
c47ff5f1 | 1316 | On simple groups, such as the pattern C<< (?> [^()]+ ) >>, a comparable |
19799a22 | 1317 | effect may be achieved by negative look-ahead, as in C<[^()]+ (?! [^()] )>. |
c277df42 IZ |
1318 | This was only 4 times slower on a string with 1000000 C<a>s. |
1319 | ||
9da458fc IZ |
1320 | The "grab all you can, and do not give anything back" semantic is desirable |
1321 | in many situations where on the first sight a simple C<()*> looks like | |
1322 | the correct solution. Suppose we parse text with comments being delimited | |
1323 | by C<#> followed by some optional (horizontal) whitespace. Contrary to | |
4375e838 | 1324 | its appearance, C<#[ \t]*> I<is not> the correct subexpression to match |
9da458fc IZ |
1325 | the comment delimiter, because it may "give up" some whitespace if |
1326 | the remainder of the pattern can be made to match that way. The correct | |
1327 | answer is either one of these: | |
1328 | ||
1329 | (?>#[ \t]*) | |
1330 | #[ \t]*(?![ \t]) | |
1331 | ||
1332 | For example, to grab non-empty comments into $1, one should use either | |
1333 | one of these: | |
1334 | ||
1335 | / (?> \# [ \t]* ) ( .+ ) /x; | |
1336 | / \# [ \t]* ( [^ \t] .* ) /x; | |
1337 | ||
1338 | Which one you pick depends on which of these expressions better reflects | |
1339 | the above specification of comments. | |
1340 | ||
6bda09f9 YO |
1341 | In some literature this construct is called "atomic matching" or |
1342 | "possessive matching". | |
1343 | ||
b9b4dddf YO |
1344 | Possessive quantifiers are equivalent to putting the item they are applied |
1345 | to inside of one of these constructs. The following equivalences apply: | |
1346 | ||
1347 | Quantifier Form Bracketing Form | |
1348 | --------------- --------------- | |
1349 | PAT*+ (?>PAT*) | |
1350 | PAT++ (?>PAT+) | |
1351 | PAT?+ (?>PAT?) | |
1352 | PAT{min,max}+ (?>PAT{min,max}) | |
1353 | ||
e2e6a0f1 YO |
1354 | =back |
1355 | ||
1356 | =head2 Special Backtracking Control Verbs | |
1357 | ||
1358 | B<WARNING:> These patterns are experimental and subject to change or | |
0d017f4d | 1359 | removal in a future version of Perl. Their usage in production code should |
e2e6a0f1 YO |
1360 | be noted to avoid problems during upgrades. |
1361 | ||
1362 | These special patterns are generally of the form C<(*VERB:ARG)>. Unless | |
1363 | otherwise stated the ARG argument is optional; in some cases, it is | |
1364 | forbidden. | |
1365 | ||
1366 | Any pattern containing a special backtracking verb that allows an argument | |
1367 | has the special behaviour that when executed it sets the current packages' | |
5d458dd8 YO |
1368 | C<$REGERROR> and C<$REGMARK> variables. When doing so the following |
1369 | rules apply: | |
e2e6a0f1 | 1370 | |
5d458dd8 YO |
1371 | On failure, the C<$REGERROR> variable will be set to the ARG value of the |
1372 | verb pattern, if the verb was involved in the failure of the match. If the | |
1373 | ARG part of the pattern was omitted, then C<$REGERROR> will be set to the | |
1374 | name of the last C<(*MARK:NAME)> pattern executed, or to TRUE if there was | |
1375 | none. Also, the C<$REGMARK> variable will be set to FALSE. | |
e2e6a0f1 | 1376 | |
5d458dd8 YO |
1377 | On a successful match, the C<$REGERROR> variable will be set to FALSE, and |
1378 | the C<$REGMARK> variable will be set to the name of the last | |
1379 | C<(*MARK:NAME)> pattern executed. See the explanation for the | |
1380 | C<(*MARK:NAME)> verb below for more details. | |
e2e6a0f1 | 1381 | |
5d458dd8 YO |
1382 | B<NOTE:> C<$REGERROR> and C<$REGMARK> are not magic variables like C<$1> |
1383 | and most other regex related variables. They are not local to a scope, nor | |
1384 | readonly, but instead are volatile package variables similar to C<$AUTOLOAD>. | |
1385 | Use C<local> to localize changes to them to a specific scope if necessary. | |
e2e6a0f1 YO |
1386 | |
1387 | If a pattern does not contain a special backtracking verb that allows an | |
5d458dd8 | 1388 | argument, then C<$REGERROR> and C<$REGMARK> are not touched at all. |
e2e6a0f1 YO |
1389 | |
1390 | =over 4 | |
1391 | ||
1392 | =item Verbs that take an argument | |
1393 | ||
1394 | =over 4 | |
1395 | ||
5d458dd8 | 1396 | =item C<(*PRUNE)> C<(*PRUNE:NAME)> |
f7819f85 | 1397 | X<(*PRUNE)> X<(*PRUNE:NAME)> |
54612592 | 1398 | |
5d458dd8 YO |
1399 | This zero-width pattern prunes the backtracking tree at the current point |
1400 | when backtracked into on failure. Consider the pattern C<A (*PRUNE) B>, | |
1401 | where A and B are complex patterns. Until the C<(*PRUNE)> verb is reached, | |
1402 | A may backtrack as necessary to match. Once it is reached, matching | |
1403 | continues in B, which may also backtrack as necessary; however, should B | |
1404 | not match, then no further backtracking will take place, and the pattern | |
1405 | will fail outright at the current starting position. | |
54612592 YO |
1406 | |
1407 | The following example counts all the possible matching strings in a | |
1408 | pattern (without actually matching any of them). | |
1409 | ||
e2e6a0f1 | 1410 | 'aaab' =~ /a+b?(?{print "$&\n"; $count++})(*FAIL)/; |
54612592 YO |
1411 | print "Count=$count\n"; |
1412 | ||
1413 | which produces: | |
1414 | ||
1415 | aaab | |
1416 | aaa | |
1417 | aa | |
1418 | a | |
1419 | aab | |
1420 | aa | |
1421 | a | |
1422 | ab | |
1423 | a | |
1424 | Count=9 | |
1425 | ||
5d458dd8 | 1426 | If we add a C<(*PRUNE)> before the count like the following |
54612592 | 1427 | |
5d458dd8 | 1428 | 'aaab' =~ /a+b?(*PRUNE)(?{print "$&\n"; $count++})(*FAIL)/; |
54612592 YO |
1429 | print "Count=$count\n"; |
1430 | ||
1431 | we prevent backtracking and find the count of the longest matching | |
353c6505 | 1432 | at each matching starting point like so: |
54612592 YO |
1433 | |
1434 | aaab | |
1435 | aab | |
1436 | ab | |
1437 | Count=3 | |
1438 | ||
5d458dd8 | 1439 | Any number of C<(*PRUNE)> assertions may be used in a pattern. |
54612592 | 1440 | |
5d458dd8 YO |
1441 | See also C<< (?>pattern) >> and possessive quantifiers for other ways to |
1442 | control backtracking. In some cases, the use of C<(*PRUNE)> can be | |
1443 | replaced with a C<< (?>pattern) >> with no functional difference; however, | |
1444 | C<(*PRUNE)> can be used to handle cases that cannot be expressed using a | |
1445 | C<< (?>pattern) >> alone. | |
54612592 | 1446 | |
e2e6a0f1 | 1447 | |
5d458dd8 YO |
1448 | =item C<(*SKIP)> C<(*SKIP:NAME)> |
1449 | X<(*SKIP)> | |
e2e6a0f1 | 1450 | |
5d458dd8 | 1451 | This zero-width pattern is similar to C<(*PRUNE)>, except that on |
e2e6a0f1 | 1452 | failure it also signifies that whatever text that was matched leading up |
5d458dd8 YO |
1453 | to the C<(*SKIP)> pattern being executed cannot be part of I<any> match |
1454 | of this pattern. This effectively means that the regex engine "skips" forward | |
1455 | to this position on failure and tries to match again, (assuming that | |
1456 | there is sufficient room to match). | |
1457 | ||
1458 | The name of the C<(*SKIP:NAME)> pattern has special significance. If a | |
1459 | C<(*MARK:NAME)> was encountered while matching, then it is that position | |
1460 | which is used as the "skip point". If no C<(*MARK)> of that name was | |
1461 | encountered, then the C<(*SKIP)> operator has no effect. When used | |
1462 | without a name the "skip point" is where the match point was when | |
1463 | executing the (*SKIP) pattern. | |
1464 | ||
1465 | Compare the following to the examples in C<(*PRUNE)>, note the string | |
24b23f37 YO |
1466 | is twice as long: |
1467 | ||
5d458dd8 | 1468 | 'aaabaaab' =~ /a+b?(*SKIP)(?{print "$&\n"; $count++})(*FAIL)/; |
24b23f37 YO |
1469 | print "Count=$count\n"; |
1470 | ||
1471 | outputs | |
1472 | ||
1473 | aaab | |
1474 | aaab | |
1475 | Count=2 | |
1476 | ||
5d458dd8 | 1477 | Once the 'aaab' at the start of the string has matched, and the C<(*SKIP)> |
353c6505 | 1478 | executed, the next starting point will be where the cursor was when the |
5d458dd8 YO |
1479 | C<(*SKIP)> was executed. |
1480 | ||
5d458dd8 YO |
1481 | =item C<(*MARK:NAME)> C<(*:NAME)> |
1482 | X<(*MARK)> C<(*MARK:NAME)> C<(*:NAME)> | |
1483 | ||
1484 | This zero-width pattern can be used to mark the point reached in a string | |
1485 | when a certain part of the pattern has been successfully matched. This | |
1486 | mark may be given a name. A later C<(*SKIP)> pattern will then skip | |
1487 | forward to that point if backtracked into on failure. Any number of | |
1488 | C<(*MARK)> patterns are allowed, and the NAME portion is optional and may | |
1489 | be duplicated. | |
1490 | ||
1491 | In addition to interacting with the C<(*SKIP)> pattern, C<(*MARK:NAME)> | |
1492 | can be used to "label" a pattern branch, so that after matching, the | |
1493 | program can determine which branches of the pattern were involved in the | |
1494 | match. | |
1495 | ||
1496 | When a match is successful, the C<$REGMARK> variable will be set to the | |
1497 | name of the most recently executed C<(*MARK:NAME)> that was involved | |
1498 | in the match. | |
1499 | ||
1500 | This can be used to determine which branch of a pattern was matched | |
c62285ac | 1501 | without using a separate capture buffer for each branch, which in turn |
5d458dd8 YO |
1502 | can result in a performance improvement, as perl cannot optimize |
1503 | C</(?:(x)|(y)|(z))/> as efficiently as something like | |
1504 | C</(?:x(*MARK:x)|y(*MARK:y)|z(*MARK:z))/>. | |
1505 | ||
1506 | When a match has failed, and unless another verb has been involved in | |
1507 | failing the match and has provided its own name to use, the C<$REGERROR> | |
1508 | variable will be set to the name of the most recently executed | |
1509 | C<(*MARK:NAME)>. | |
1510 | ||
1511 | See C<(*SKIP)> for more details. | |
1512 | ||
b62d2d15 YO |
1513 | As a shortcut C<(*MARK:NAME)> can be written C<(*:NAME)>. |
1514 | ||
5d458dd8 YO |
1515 | =item C<(*THEN)> C<(*THEN:NAME)> |
1516 | ||
241e7389 | 1517 | This is similar to the "cut group" operator C<::> from Perl 6. Like |
5d458dd8 YO |
1518 | C<(*PRUNE)>, this verb always matches, and when backtracked into on |
1519 | failure, it causes the regex engine to try the next alternation in the | |
1520 | innermost enclosing group (capturing or otherwise). | |
1521 | ||
1522 | Its name comes from the observation that this operation combined with the | |
1523 | alternation operator (C<|>) can be used to create what is essentially a | |
1524 | pattern-based if/then/else block: | |
1525 | ||
1526 | ( COND (*THEN) FOO | COND2 (*THEN) BAR | COND3 (*THEN) BAZ ) | |
1527 | ||
1528 | Note that if this operator is used and NOT inside of an alternation then | |
1529 | it acts exactly like the C<(*PRUNE)> operator. | |
1530 | ||
1531 | / A (*PRUNE) B / | |
1532 | ||
1533 | is the same as | |
1534 | ||
1535 | / A (*THEN) B / | |
1536 | ||
1537 | but | |
1538 | ||
1539 | / ( A (*THEN) B | C (*THEN) D ) / | |
1540 | ||
1541 | is not the same as | |
1542 | ||
1543 | / ( A (*PRUNE) B | C (*PRUNE) D ) / | |
1544 | ||
1545 | as after matching the A but failing on the B the C<(*THEN)> verb will | |
1546 | backtrack and try C; but the C<(*PRUNE)> verb will simply fail. | |
24b23f37 | 1547 | |
e2e6a0f1 YO |
1548 | =item C<(*COMMIT)> |
1549 | X<(*COMMIT)> | |
24b23f37 | 1550 | |
241e7389 | 1551 | This is the Perl 6 "commit pattern" C<< <commit> >> or C<:::>. It's a |
5d458dd8 YO |
1552 | zero-width pattern similar to C<(*SKIP)>, except that when backtracked |
1553 | into on failure it causes the match to fail outright. No further attempts | |
1554 | to find a valid match by advancing the start pointer will occur again. | |
1555 | For example, | |
24b23f37 | 1556 | |
e2e6a0f1 | 1557 | 'aaabaaab' =~ /a+b?(*COMMIT)(?{print "$&\n"; $count++})(*FAIL)/; |
24b23f37 YO |
1558 | print "Count=$count\n"; |
1559 | ||
1560 | outputs | |
1561 | ||
1562 | aaab | |
1563 | Count=1 | |
1564 | ||
e2e6a0f1 YO |
1565 | In other words, once the C<(*COMMIT)> has been entered, and if the pattern |
1566 | does not match, the regex engine will not try any further matching on the | |
1567 | rest of the string. | |
c277df42 | 1568 | |
e2e6a0f1 | 1569 | =back |
9af228c6 | 1570 | |
e2e6a0f1 | 1571 | =item Verbs without an argument |
9af228c6 YO |
1572 | |
1573 | =over 4 | |
1574 | ||
e2e6a0f1 YO |
1575 | =item C<(*FAIL)> C<(*F)> |
1576 | X<(*FAIL)> X<(*F)> | |
9af228c6 | 1577 | |
e2e6a0f1 YO |
1578 | This pattern matches nothing and always fails. It can be used to force the |
1579 | engine to backtrack. It is equivalent to C<(?!)>, but easier to read. In | |
1580 | fact, C<(?!)> gets optimised into C<(*FAIL)> internally. | |
9af228c6 | 1581 | |
e2e6a0f1 | 1582 | It is probably useful only when combined with C<(?{})> or C<(??{})>. |
9af228c6 | 1583 | |
e2e6a0f1 YO |
1584 | =item C<(*ACCEPT)> |
1585 | X<(*ACCEPT)> | |
9af228c6 | 1586 | |
e2e6a0f1 YO |
1587 | B<WARNING:> This feature is highly experimental. It is not recommended |
1588 | for production code. | |
9af228c6 | 1589 | |
e2e6a0f1 YO |
1590 | This pattern matches nothing and causes the end of successful matching at |
1591 | the point at which the C<(*ACCEPT)> pattern was encountered, regardless of | |
1592 | whether there is actually more to match in the string. When inside of a | |
0d017f4d | 1593 | nested pattern, such as recursion, or in a subpattern dynamically generated |
e2e6a0f1 | 1594 | via C<(??{})>, only the innermost pattern is ended immediately. |
9af228c6 | 1595 | |
e2e6a0f1 YO |
1596 | If the C<(*ACCEPT)> is inside of capturing buffers then the buffers are |
1597 | marked as ended at the point at which the C<(*ACCEPT)> was encountered. | |
1598 | For instance: | |
9af228c6 | 1599 | |
e2e6a0f1 | 1600 | 'AB' =~ /(A (A|B(*ACCEPT)|C) D)(E)/x; |
9af228c6 | 1601 | |
e2e6a0f1 | 1602 | will match, and C<$1> will be C<AB> and C<$2> will be C<B>, C<$3> will not |
0d017f4d | 1603 | be set. If another branch in the inner parentheses were matched, such as in the |
e2e6a0f1 | 1604 | string 'ACDE', then the C<D> and C<E> would have to be matched as well. |
9af228c6 YO |
1605 | |
1606 | =back | |
c277df42 | 1607 | |
a0d0e21e LW |
1608 | =back |
1609 | ||
c07a80fd | 1610 | =head2 Backtracking |
d74e8afc | 1611 | X<backtrack> X<backtracking> |
c07a80fd | 1612 | |
35a734be IZ |
1613 | NOTE: This section presents an abstract approximation of regular |
1614 | expression behavior. For a more rigorous (and complicated) view of | |
1615 | the rules involved in selecting a match among possible alternatives, | |
0d017f4d | 1616 | see L<Combining RE Pieces>. |
35a734be | 1617 | |
c277df42 | 1618 | A fundamental feature of regular expression matching involves the |
5a964f20 | 1619 | notion called I<backtracking>, which is currently used (when needed) |
0d017f4d | 1620 | by all regular non-possessive expression quantifiers, namely C<*>, C<*?>, C<+>, |
9da458fc IZ |
1621 | C<+?>, C<{n,m}>, and C<{n,m}?>. Backtracking is often optimized |
1622 | internally, but the general principle outlined here is valid. | |
c07a80fd | 1623 | |
1624 | For a regular expression to match, the I<entire> regular expression must | |
1625 | match, not just part of it. So if the beginning of a pattern containing a | |
1626 | quantifier succeeds in a way that causes later parts in the pattern to | |
1627 | fail, the matching engine backs up and recalculates the beginning | |
1628 | part--that's why it's called backtracking. | |
1629 | ||
1630 | Here is an example of backtracking: Let's say you want to find the | |
1631 | word following "foo" in the string "Food is on the foo table.": | |
1632 | ||
1633 | $_ = "Food is on the foo table."; | |
1634 | if ( /\b(foo)\s+(\w+)/i ) { | |
1635 | print "$2 follows $1.\n"; | |
1636 | } | |
1637 | ||
1638 | When the match runs, the first part of the regular expression (C<\b(foo)>) | |
1639 | finds a possible match right at the beginning of the string, and loads up | |
1640 | $1 with "Foo". However, as soon as the matching engine sees that there's | |
1641 | no whitespace following the "Foo" that it had saved in $1, it realizes its | |
68dc0745 | 1642 | mistake and starts over again one character after where it had the |
c07a80fd | 1643 | tentative match. This time it goes all the way until the next occurrence |
1644 | of "foo". The complete regular expression matches this time, and you get | |
1645 | the expected output of "table follows foo." | |
1646 | ||
1647 | Sometimes minimal matching can help a lot. Imagine you'd like to match | |
1648 | everything between "foo" and "bar". Initially, you write something | |
1649 | like this: | |
1650 | ||
1651 | $_ = "The food is under the bar in the barn."; | |
1652 | if ( /foo(.*)bar/ ) { | |
1653 | print "got <$1>\n"; | |
1654 | } | |
1655 | ||
1656 | Which perhaps unexpectedly yields: | |
1657 | ||
1658 | got <d is under the bar in the > | |
1659 | ||
1660 | That's because C<.*> was greedy, so you get everything between the | |
14218588 | 1661 | I<first> "foo" and the I<last> "bar". Here it's more effective |
c07a80fd | 1662 | to use minimal matching to make sure you get the text between a "foo" |
1663 | and the first "bar" thereafter. | |
1664 | ||
1665 | if ( /foo(.*?)bar/ ) { print "got <$1>\n" } | |
1666 | got <d is under the > | |
1667 | ||
0d017f4d | 1668 | Here's another example. Let's say you'd like to match a number at the end |
b6e13d97 | 1669 | of a string, and you also want to keep the preceding part of the match. |
c07a80fd | 1670 | So you write this: |
1671 | ||
1672 | $_ = "I have 2 numbers: 53147"; | |
1673 | if ( /(.*)(\d*)/ ) { # Wrong! | |
1674 | print "Beginning is <$1>, number is <$2>.\n"; | |
1675 | } | |
1676 | ||
1677 | That won't work at all, because C<.*> was greedy and gobbled up the | |
1678 | whole string. As C<\d*> can match on an empty string the complete | |
1679 | regular expression matched successfully. | |
1680 | ||
8e1088bc | 1681 | Beginning is <I have 2 numbers: 53147>, number is <>. |
c07a80fd | 1682 | |
1683 | Here are some variants, most of which don't work: | |
1684 | ||
1685 | $_ = "I have 2 numbers: 53147"; | |
1686 | @pats = qw{ | |
1687 | (.*)(\d*) | |
1688 | (.*)(\d+) | |
1689 | (.*?)(\d*) | |
1690 | (.*?)(\d+) | |
1691 | (.*)(\d+)$ | |
1692 | (.*?)(\d+)$ | |
1693 | (.*)\b(\d+)$ | |
1694 | (.*\D)(\d+)$ | |
1695 | }; | |
1696 | ||
1697 | for $pat (@pats) { | |
1698 | printf "%-12s ", $pat; | |
1699 | if ( /$pat/ ) { | |
1700 | print "<$1> <$2>\n"; | |
1701 | } else { | |
1702 | print "FAIL\n"; | |
1703 | } | |
1704 | } | |
1705 | ||
1706 | That will print out: | |
1707 | ||
1708 | (.*)(\d*) <I have 2 numbers: 53147> <> | |
1709 | (.*)(\d+) <I have 2 numbers: 5314> <7> | |
1710 | (.*?)(\d*) <> <> | |
1711 | (.*?)(\d+) <I have > <2> | |
1712 | (.*)(\d+)$ <I have 2 numbers: 5314> <7> | |
1713 | (.*?)(\d+)$ <I have 2 numbers: > <53147> | |
1714 | (.*)\b(\d+)$ <I have 2 numbers: > <53147> | |
1715 | (.*\D)(\d+)$ <I have 2 numbers: > <53147> | |
1716 | ||
1717 | As you see, this can be a bit tricky. It's important to realize that a | |
1718 | regular expression is merely a set of assertions that gives a definition | |
1719 | of success. There may be 0, 1, or several different ways that the | |
1720 | definition might succeed against a particular string. And if there are | |
5a964f20 TC |
1721 | multiple ways it might succeed, you need to understand backtracking to |
1722 | know which variety of success you will achieve. | |
c07a80fd | 1723 | |
19799a22 | 1724 | When using look-ahead assertions and negations, this can all get even |
8b19b778 | 1725 | trickier. Imagine you'd like to find a sequence of non-digits not |
c07a80fd | 1726 | followed by "123". You might try to write that as |
1727 | ||
871b0233 IZ |
1728 | $_ = "ABC123"; |
1729 | if ( /^\D*(?!123)/ ) { # Wrong! | |
1730 | print "Yup, no 123 in $_\n"; | |
1731 | } | |
c07a80fd | 1732 | |
1733 | But that isn't going to match; at least, not the way you're hoping. It | |
1734 | claims that there is no 123 in the string. Here's a clearer picture of | |
9b9391b2 | 1735 | why that pattern matches, contrary to popular expectations: |
c07a80fd | 1736 | |
4358a253 SS |
1737 | $x = 'ABC123'; |
1738 | $y = 'ABC445'; | |
c07a80fd | 1739 | |
4358a253 SS |
1740 | print "1: got $1\n" if $x =~ /^(ABC)(?!123)/; |
1741 | print "2: got $1\n" if $y =~ /^(ABC)(?!123)/; | |
c07a80fd | 1742 | |
4358a253 SS |
1743 | print "3: got $1\n" if $x =~ /^(\D*)(?!123)/; |
1744 | print "4: got $1\n" if $y =~ /^(\D*)(?!123)/; | |
c07a80fd | 1745 | |
1746 | This prints | |
1747 | ||
1748 | 2: got ABC | |
1749 | 3: got AB | |
1750 | 4: got ABC | |
1751 | ||
5f05dabc | 1752 | You might have expected test 3 to fail because it seems to a more |
c07a80fd | 1753 | general purpose version of test 1. The important difference between |
1754 | them is that test 3 contains a quantifier (C<\D*>) and so can use | |
1755 | backtracking, whereas test 1 will not. What's happening is | |
1756 | that you've asked "Is it true that at the start of $x, following 0 or more | |
5f05dabc | 1757 | non-digits, you have something that's not 123?" If the pattern matcher had |
c07a80fd | 1758 | let C<\D*> expand to "ABC", this would have caused the whole pattern to |
54310121 | 1759 | fail. |
14218588 | 1760 | |
c07a80fd | 1761 | The search engine will initially match C<\D*> with "ABC". Then it will |
14218588 | 1762 | try to match C<(?!123> with "123", which fails. But because |
c07a80fd | 1763 | a quantifier (C<\D*>) has been used in the regular expression, the |
1764 | search engine can backtrack and retry the match differently | |
54310121 | 1765 | in the hope of matching the complete regular expression. |
c07a80fd | 1766 | |
5a964f20 TC |
1767 | The pattern really, I<really> wants to succeed, so it uses the |
1768 | standard pattern back-off-and-retry and lets C<\D*> expand to just "AB" this | |
c07a80fd | 1769 | time. Now there's indeed something following "AB" that is not |
14218588 | 1770 | "123". It's "C123", which suffices. |
c07a80fd | 1771 | |
14218588 GS |
1772 | We can deal with this by using both an assertion and a negation. |
1773 | We'll say that the first part in $1 must be followed both by a digit | |
1774 | and by something that's not "123". Remember that the look-aheads | |
1775 | are zero-width expressions--they only look, but don't consume any | |
1776 | of the string in their match. So rewriting this way produces what | |
c07a80fd | 1777 | you'd expect; that is, case 5 will fail, but case 6 succeeds: |
1778 | ||
4358a253 SS |
1779 | print "5: got $1\n" if $x =~ /^(\D*)(?=\d)(?!123)/; |
1780 | print "6: got $1\n" if $y =~ /^(\D*)(?=\d)(?!123)/; | |
c07a80fd | 1781 | |
1782 | 6: got ABC | |
1783 | ||
5a964f20 | 1784 | In other words, the two zero-width assertions next to each other work as though |
19799a22 | 1785 | they're ANDed together, just as you'd use any built-in assertions: C</^$/> |
c07a80fd | 1786 | matches only if you're at the beginning of the line AND the end of the |
1787 | line simultaneously. The deeper underlying truth is that juxtaposition in | |
1788 | regular expressions always means AND, except when you write an explicit OR | |
1789 | using the vertical bar. C</ab/> means match "a" AND (then) match "b", | |
1790 | although the attempted matches are made at different positions because "a" | |
1791 | is not a zero-width assertion, but a one-width assertion. | |
1792 | ||
0d017f4d | 1793 | B<WARNING>: Particularly complicated regular expressions can take |
14218588 | 1794 | exponential time to solve because of the immense number of possible |
0d017f4d | 1795 | ways they can use backtracking to try for a match. For example, without |
9da458fc IZ |
1796 | internal optimizations done by the regular expression engine, this will |
1797 | take a painfully long time to run: | |
c07a80fd | 1798 | |
e1901655 IZ |
1799 | 'aaaaaaaaaaaa' =~ /((a{0,5}){0,5})*[c]/ |
1800 | ||
1801 | And if you used C<*>'s in the internal groups instead of limiting them | |
1802 | to 0 through 5 matches, then it would take forever--or until you ran | |
1803 | out of stack space. Moreover, these internal optimizations are not | |
1804 | always applicable. For example, if you put C<{0,5}> instead of C<*> | |
1805 | on the external group, no current optimization is applicable, and the | |
1806 | match takes a long time to finish. | |
c07a80fd | 1807 | |
9da458fc IZ |
1808 | A powerful tool for optimizing such beasts is what is known as an |
1809 | "independent group", | |
c47ff5f1 | 1810 | which does not backtrack (see L<C<< (?>pattern) >>>). Note also that |
9da458fc | 1811 | zero-length look-ahead/look-behind assertions will not backtrack to make |
5d458dd8 | 1812 | the tail match, since they are in "logical" context: only |
14218588 | 1813 | whether they match is considered relevant. For an example |
9da458fc | 1814 | where side-effects of look-ahead I<might> have influenced the |
c47ff5f1 | 1815 | following match, see L<C<< (?>pattern) >>>. |
c277df42 | 1816 | |
a0d0e21e | 1817 | =head2 Version 8 Regular Expressions |
d74e8afc | 1818 | X<regular expression, version 8> X<regex, version 8> X<regexp, version 8> |
a0d0e21e | 1819 | |
5a964f20 | 1820 | In case you're not familiar with the "regular" Version 8 regex |
a0d0e21e LW |
1821 | routines, here are the pattern-matching rules not described above. |
1822 | ||
54310121 | 1823 | Any single character matches itself, unless it is a I<metacharacter> |
a0d0e21e | 1824 | with a special meaning described here or above. You can cause |
5a964f20 | 1825 | characters that normally function as metacharacters to be interpreted |
5f05dabc | 1826 | literally by prefixing them with a "\" (e.g., "\." matches a ".", not any |
0d017f4d WL |
1827 | character; "\\" matches a "\"). This escape mechanism is also required |
1828 | for the character used as the pattern delimiter. | |
1829 | ||
1830 | A series of characters matches that series of characters in the target | |
1831 | string, so the pattern C<blurfl> would match "blurfl" in the target | |
1832 | string. | |
a0d0e21e LW |
1833 | |
1834 | You can specify a character class, by enclosing a list of characters | |
5d458dd8 | 1835 | in C<[]>, which will match any character from the list. If the |
a0d0e21e | 1836 | first character after the "[" is "^", the class matches any character not |
14218588 | 1837 | in the list. Within a list, the "-" character specifies a |
5a964f20 | 1838 | range, so that C<a-z> represents all characters between "a" and "z", |
8a4f6ac2 GS |
1839 | inclusive. If you want either "-" or "]" itself to be a member of a |
1840 | class, put it at the start of the list (possibly after a "^"), or | |
1841 | escape it with a backslash. "-" is also taken literally when it is | |
1842 | at the end of the list, just before the closing "]". (The | |
84850974 DD |
1843 | following all specify the same class of three characters: C<[-az]>, |
1844 | C<[az-]>, and C<[a\-z]>. All are different from C<[a-z]>, which | |
5d458dd8 YO |
1845 | specifies a class containing twenty-six characters, even on EBCDIC-based |
1846 | character sets.) Also, if you try to use the character | |
1847 | classes C<\w>, C<\W>, C<\s>, C<\S>, C<\d>, or C<\D> as endpoints of | |
1848 | a range, the "-" is understood literally. | |
a0d0e21e | 1849 | |
8ada0baa JH |
1850 | Note also that the whole range idea is rather unportable between |
1851 | character sets--and even within character sets they may cause results | |
1852 | you probably didn't expect. A sound principle is to use only ranges | |
0d017f4d | 1853 | that begin from and end at either alphabetics of equal case ([a-e], |
8ada0baa JH |
1854 | [A-E]), or digits ([0-9]). Anything else is unsafe. If in doubt, |
1855 | spell out the character sets in full. | |
1856 | ||
54310121 | 1857 | Characters may be specified using a metacharacter syntax much like that |
a0d0e21e LW |
1858 | used in C: "\n" matches a newline, "\t" a tab, "\r" a carriage return, |
1859 | "\f" a form feed, etc. More generally, \I<nnn>, where I<nnn> is a string | |
5d458dd8 YO |
1860 | of octal digits, matches the character whose coded character set value |
1861 | is I<nnn>. Similarly, \xI<nn>, where I<nn> are hexadecimal digits, | |
1862 | matches the character whose numeric value is I<nn>. The expression \cI<x> | |
1863 | matches the character control-I<x>. Finally, the "." metacharacter | |
fb55449c | 1864 | matches any character except "\n" (unless you use C</s>). |
a0d0e21e LW |
1865 | |
1866 | You can specify a series of alternatives for a pattern using "|" to | |
1867 | separate them, so that C<fee|fie|foe> will match any of "fee", "fie", | |
5a964f20 | 1868 | or "foe" in the target string (as would C<f(e|i|o)e>). The |
a0d0e21e LW |
1869 | first alternative includes everything from the last pattern delimiter |
1870 | ("(", "[", or the beginning of the pattern) up to the first "|", and | |
1871 | the last alternative contains everything from the last "|" to the next | |
14218588 GS |
1872 | pattern delimiter. That's why it's common practice to include |
1873 | alternatives in parentheses: to minimize confusion about where they | |
a3cb178b GS |
1874 | start and end. |
1875 | ||
5a964f20 | 1876 | Alternatives are tried from left to right, so the first |
a3cb178b GS |
1877 | alternative found for which the entire expression matches, is the one that |
1878 | is chosen. This means that alternatives are not necessarily greedy. For | |
628afcb5 | 1879 | example: when matching C<foo|foot> against "barefoot", only the "foo" |
a3cb178b GS |
1880 | part will match, as that is the first alternative tried, and it successfully |
1881 | matches the target string. (This might not seem important, but it is | |
1882 | important when you are capturing matched text using parentheses.) | |
1883 | ||
5a964f20 | 1884 | Also remember that "|" is interpreted as a literal within square brackets, |
a3cb178b | 1885 | so if you write C<[fee|fie|foe]> you're really only matching C<[feio|]>. |
a0d0e21e | 1886 | |
14218588 GS |
1887 | Within a pattern, you may designate subpatterns for later reference |
1888 | by enclosing them in parentheses, and you may refer back to the | |
1889 | I<n>th subpattern later in the pattern using the metacharacter | |
1890 | \I<n>. Subpatterns are numbered based on the left to right order | |
1891 | of their opening parenthesis. A backreference matches whatever | |
1892 | actually matched the subpattern in the string being examined, not | |
1893 | the rules for that subpattern. Therefore, C<(0|0x)\d*\s\1\d*> will | |
1894 | match "0x1234 0x4321", but not "0x1234 01234", because subpattern | |
1895 | 1 matched "0x", even though the rule C<0|0x> could potentially match | |
1896 | the leading 0 in the second number. | |
cb1a09d0 | 1897 | |
0d017f4d | 1898 | =head2 Warning on \1 Instead of $1 |
cb1a09d0 | 1899 | |
5a964f20 | 1900 | Some people get too used to writing things like: |
cb1a09d0 AD |
1901 | |
1902 | $pattern =~ s/(\W)/\\\1/g; | |
1903 | ||
1904 | This is grandfathered for the RHS of a substitute to avoid shocking the | |
1905 | B<sed> addicts, but it's a dirty habit to get into. That's because in | |
d1be9408 | 1906 | PerlThink, the righthand side of an C<s///> is a double-quoted string. C<\1> in |
cb1a09d0 AD |
1907 | the usual double-quoted string means a control-A. The customary Unix |
1908 | meaning of C<\1> is kludged in for C<s///>. However, if you get into the habit | |
1909 | of doing that, you get yourself into trouble if you then add an C</e> | |
1910 | modifier. | |
1911 | ||
5a964f20 | 1912 | s/(\d+)/ \1 + 1 /eg; # causes warning under -w |
cb1a09d0 AD |
1913 | |
1914 | Or if you try to do | |
1915 | ||
1916 | s/(\d+)/\1000/; | |
1917 | ||
1918 | You can't disambiguate that by saying C<\{1}000>, whereas you can fix it with | |
14218588 | 1919 | C<${1}000>. The operation of interpolation should not be confused |
cb1a09d0 AD |
1920 | with the operation of matching a backreference. Certainly they mean two |
1921 | different things on the I<left> side of the C<s///>. | |
9fa51da4 | 1922 | |
0d017f4d | 1923 | =head2 Repeated Patterns Matching a Zero-length Substring |
c84d73f1 | 1924 | |
19799a22 | 1925 | B<WARNING>: Difficult material (and prose) ahead. This section needs a rewrite. |
c84d73f1 IZ |
1926 | |
1927 | Regular expressions provide a terse and powerful programming language. As | |
1928 | with most other power tools, power comes together with the ability | |
1929 | to wreak havoc. | |
1930 | ||
1931 | A common abuse of this power stems from the ability to make infinite | |
628afcb5 | 1932 | loops using regular expressions, with something as innocuous as: |
c84d73f1 IZ |
1933 | |
1934 | 'foo' =~ m{ ( o? )* }x; | |
1935 | ||
0d017f4d | 1936 | The C<o?> matches at the beginning of C<'foo'>, and since the position |
c84d73f1 | 1937 | in the string is not moved by the match, C<o?> would match again and again |
527e91da | 1938 | because of the C<*> quantifier. Another common way to create a similar cycle |
c84d73f1 IZ |
1939 | is with the looping modifier C<//g>: |
1940 | ||
1941 | @matches = ( 'foo' =~ m{ o? }xg ); | |
1942 | ||
1943 | or | |
1944 | ||
1945 | print "match: <$&>\n" while 'foo' =~ m{ o? }xg; | |
1946 | ||
1947 | or the loop implied by split(). | |
1948 | ||
1949 | However, long experience has shown that many programming tasks may | |
14218588 GS |
1950 | be significantly simplified by using repeated subexpressions that |
1951 | may match zero-length substrings. Here's a simple example being: | |
c84d73f1 IZ |
1952 | |
1953 | @chars = split //, $string; # // is not magic in split | |
1954 | ($whitewashed = $string) =~ s/()/ /g; # parens avoid magic s// / | |
1955 | ||
9da458fc | 1956 | Thus Perl allows such constructs, by I<forcefully breaking |
c84d73f1 | 1957 | the infinite loop>. The rules for this are different for lower-level |
527e91da | 1958 | loops given by the greedy quantifiers C<*+{}>, and for higher-level |
c84d73f1 IZ |
1959 | ones like the C</g> modifier or split() operator. |
1960 | ||
19799a22 GS |
1961 | The lower-level loops are I<interrupted> (that is, the loop is |
1962 | broken) when Perl detects that a repeated expression matched a | |
1963 | zero-length substring. Thus | |
c84d73f1 IZ |
1964 | |
1965 | m{ (?: NON_ZERO_LENGTH | ZERO_LENGTH )* }x; | |
1966 | ||
5d458dd8 | 1967 | is made equivalent to |
c84d73f1 | 1968 | |
5d458dd8 YO |
1969 | m{ (?: NON_ZERO_LENGTH )* |
1970 | | | |
1971 | (?: ZERO_LENGTH )? | |
c84d73f1 IZ |
1972 | }x; |
1973 | ||
1974 | The higher level-loops preserve an additional state between iterations: | |
5d458dd8 | 1975 | whether the last match was zero-length. To break the loop, the following |
c84d73f1 | 1976 | match after a zero-length match is prohibited to have a length of zero. |
5d458dd8 | 1977 | This prohibition interacts with backtracking (see L<"Backtracking">), |
c84d73f1 IZ |
1978 | and so the I<second best> match is chosen if the I<best> match is of |
1979 | zero length. | |
1980 | ||
19799a22 | 1981 | For example: |
c84d73f1 IZ |
1982 | |
1983 | $_ = 'bar'; | |
1984 | s/\w??/<$&>/g; | |
1985 | ||
20fb949f | 1986 | results in C<< <><b><><a><><r><> >>. At each position of the string the best |
5d458dd8 | 1987 | match given by non-greedy C<??> is the zero-length match, and the I<second |
c84d73f1 IZ |
1988 | best> match is what is matched by C<\w>. Thus zero-length matches |
1989 | alternate with one-character-long matches. | |
1990 | ||
5d458dd8 | 1991 | Similarly, for repeated C<m/()/g> the second-best match is the match at the |
c84d73f1 IZ |
1992 | position one notch further in the string. |
1993 | ||
19799a22 | 1994 | The additional state of being I<matched with zero-length> is associated with |
c84d73f1 | 1995 | the matched string, and is reset by each assignment to pos(). |
9da458fc IZ |
1996 | Zero-length matches at the end of the previous match are ignored |
1997 | during C<split>. | |
c84d73f1 | 1998 | |
0d017f4d | 1999 | =head2 Combining RE Pieces |
35a734be IZ |
2000 | |
2001 | Each of the elementary pieces of regular expressions which were described | |
2002 | before (such as C<ab> or C<\Z>) could match at most one substring | |
2003 | at the given position of the input string. However, in a typical regular | |
2004 | expression these elementary pieces are combined into more complicated | |
2005 | patterns using combining operators C<ST>, C<S|T>, C<S*> etc | |
2006 | (in these examples C<S> and C<T> are regular subexpressions). | |
2007 | ||
2008 | Such combinations can include alternatives, leading to a problem of choice: | |
2009 | if we match a regular expression C<a|ab> against C<"abc">, will it match | |
2010 | substring C<"a"> or C<"ab">? One way to describe which substring is | |
2011 | actually matched is the concept of backtracking (see L<"Backtracking">). | |
2012 | However, this description is too low-level and makes you think | |
2013 | in terms of a particular implementation. | |
2014 | ||
2015 | Another description starts with notions of "better"/"worse". All the | |
2016 | substrings which may be matched by the given regular expression can be | |
2017 | sorted from the "best" match to the "worst" match, and it is the "best" | |
2018 | match which is chosen. This substitutes the question of "what is chosen?" | |
2019 | by the question of "which matches are better, and which are worse?". | |
2020 | ||
2021 | Again, for elementary pieces there is no such question, since at most | |
2022 | one match at a given position is possible. This section describes the | |
2023 | notion of better/worse for combining operators. In the description | |
2024 | below C<S> and C<T> are regular subexpressions. | |
2025 | ||
13a2d996 | 2026 | =over 4 |
35a734be IZ |
2027 | |
2028 | =item C<ST> | |
2029 | ||
2030 | Consider two possible matches, C<AB> and C<A'B'>, C<A> and C<A'> are | |
2031 | substrings which can be matched by C<S>, C<B> and C<B'> are substrings | |
5d458dd8 | 2032 | which can be matched by C<T>. |
35a734be IZ |
2033 | |
2034 | If C<A> is better match for C<S> than C<A'>, C<AB> is a better | |
2035 | match than C<A'B'>. | |
2036 | ||
2037 | If C<A> and C<A'> coincide: C<AB> is a better match than C<AB'> if | |
2038 | C<B> is better match for C<T> than C<B'>. | |
2039 | ||
2040 | =item C<S|T> | |
2041 | ||
2042 | When C<S> can match, it is a better match than when only C<T> can match. | |
2043 | ||
2044 | Ordering of two matches for C<S> is the same as for C<S>. Similar for | |
2045 | two matches for C<T>. | |
2046 | ||
2047 | =item C<S{REPEAT_COUNT}> | |
2048 | ||
2049 | Matches as C<SSS...S> (repeated as many times as necessary). | |
2050 | ||
2051 | =item C<S{min,max}> | |
2052 | ||
2053 | Matches as C<S{max}|S{max-1}|...|S{min+1}|S{min}>. | |
2054 | ||
2055 | =item C<S{min,max}?> | |
2056 | ||
2057 | Matches as C<S{min}|S{min+1}|...|S{max-1}|S{max}>. | |
2058 | ||
2059 | =item C<S?>, C<S*>, C<S+> | |
2060 | ||
2061 | Same as C<S{0,1}>, C<S{0,BIG_NUMBER}>, C<S{1,BIG_NUMBER}> respectively. | |
2062 | ||
2063 | =item C<S??>, C<S*?>, C<S+?> | |
2064 | ||
2065 | Same as C<S{0,1}?>, C<S{0,BIG_NUMBER}?>, C<S{1,BIG_NUMBER}?> respectively. | |
2066 | ||
c47ff5f1 | 2067 | =item C<< (?>S) >> |
35a734be IZ |
2068 | |
2069 | Matches the best match for C<S> and only that. | |
2070 | ||
2071 | =item C<(?=S)>, C<(?<=S)> | |
2072 | ||
2073 | Only the best match for C<S> is considered. (This is important only if | |
2074 | C<S> has capturing parentheses, and backreferences are used somewhere | |
2075 | else in the whole regular expression.) | |
2076 | ||
2077 | =item C<(?!S)>, C<(?<!S)> | |
2078 | ||
2079 | For this grouping operator there is no need to describe the ordering, since | |
2080 | only whether or not C<S> can match is important. | |
2081 | ||
6bda09f9 | 2082 | =item C<(??{ EXPR })>, C<(?PARNO)> |
35a734be IZ |
2083 | |
2084 | The ordering is the same as for the regular expression which is | |
6bda09f9 | 2085 | the result of EXPR, or the pattern contained by capture buffer PARNO. |
35a734be IZ |
2086 | |
2087 | =item C<(?(condition)yes-pattern|no-pattern)> | |
2088 | ||
2089 | Recall that which of C<yes-pattern> or C<no-pattern> actually matches is | |
2090 | already determined. The ordering of the matches is the same as for the | |
2091 | chosen subexpression. | |
2092 | ||
2093 | =back | |
2094 | ||
2095 | The above recipes describe the ordering of matches I<at a given position>. | |
2096 | One more rule is needed to understand how a match is determined for the | |
2097 | whole regular expression: a match at an earlier position is always better | |
2098 | than a match at a later position. | |
2099 | ||
0d017f4d | 2100 | =head2 Creating Custom RE Engines |
c84d73f1 IZ |
2101 | |
2102 | Overloaded constants (see L<overload>) provide a simple way to extend | |
2103 | the functionality of the RE engine. | |
2104 | ||
2105 | Suppose that we want to enable a new RE escape-sequence C<\Y|> which | |
0d017f4d | 2106 | matches at a boundary between whitespace characters and non-whitespace |
c84d73f1 IZ |
2107 | characters. Note that C<(?=\S)(?<!\S)|(?!\S)(?<=\S)> matches exactly |
2108 | at these positions, so we want to have each C<\Y|> in the place of the | |
2109 | more complicated version. We can create a module C<customre> to do | |
2110 | this: | |
2111 | ||
2112 | package customre; | |
2113 | use overload; | |
2114 | ||
2115 | sub import { | |
2116 | shift; | |
2117 | die "No argument to customre::import allowed" if @_; | |
2118 | overload::constant 'qr' => \&convert; | |
2119 | } | |
2120 | ||
2121 | sub invalid { die "/$_[0]/: invalid escape '\\$_[1]'"} | |
2122 | ||
580a9fe1 RGS |
2123 | # We must also take care of not escaping the legitimate \\Y| |
2124 | # sequence, hence the presence of '\\' in the conversion rules. | |
5d458dd8 | 2125 | my %rules = ( '\\' => '\\\\', |
c84d73f1 IZ |
2126 | 'Y|' => qr/(?=\S)(?<!\S)|(?!\S)(?<=\S)/ ); |
2127 | sub convert { | |
2128 | my $re = shift; | |
5d458dd8 | 2129 | $re =~ s{ |
c84d73f1 IZ |
2130 | \\ ( \\ | Y . ) |
2131 | } | |
5d458dd8 | 2132 | { $rules{$1} or invalid($re,$1) }sgex; |
c84d73f1 IZ |
2133 | return $re; |
2134 | } | |
2135 | ||
2136 | Now C<use customre> enables the new escape in constant regular | |
2137 | expressions, i.e., those without any runtime variable interpolations. | |
2138 | As documented in L<overload>, this conversion will work only over | |
2139 | literal parts of regular expressions. For C<\Y|$re\Y|> the variable | |
2140 | part of this regular expression needs to be converted explicitly | |
2141 | (but only if the special meaning of C<\Y|> should be enabled inside $re): | |
2142 | ||
2143 | use customre; | |
2144 | $re = <>; | |
2145 | chomp $re; | |
2146 | $re = customre::convert $re; | |
2147 | /\Y|$re\Y|/; | |
2148 | ||
1f1031fe YO |
2149 | =head1 PCRE/Python Support |
2150 | ||
99d59c4d | 2151 | As of Perl 5.10.0, Perl supports several Python/PCRE specific extensions |
1f1031fe | 2152 | to the regex syntax. While Perl programmers are encouraged to use the |
99d59c4d | 2153 | Perl specific syntax, the following are also accepted: |
1f1031fe YO |
2154 | |
2155 | =over 4 | |
2156 | ||
ae5648b3 | 2157 | =item C<< (?PE<lt>NAMEE<gt>pattern) >> |
1f1031fe YO |
2158 | |
2159 | Define a named capture buffer. Equivalent to C<< (?<NAME>pattern) >>. | |
2160 | ||
2161 | =item C<< (?P=NAME) >> | |
2162 | ||
2163 | Backreference to a named capture buffer. Equivalent to C<< \g{NAME} >>. | |
2164 | ||
2165 | =item C<< (?P>NAME) >> | |
2166 | ||
2167 | Subroutine call to a named capture buffer. Equivalent to C<< (?&NAME) >>. | |
2168 | ||
ee9b8eae | 2169 | =back |
1f1031fe | 2170 | |
19799a22 GS |
2171 | =head1 BUGS |
2172 | ||
9da458fc IZ |
2173 | This document varies from difficult to understand to completely |
2174 | and utterly opaque. The wandering prose riddled with jargon is | |
2175 | hard to fathom in several places. | |
2176 | ||
2177 | This document needs a rewrite that separates the tutorial content | |
2178 | from the reference content. | |
19799a22 GS |
2179 | |
2180 | =head1 SEE ALSO | |
9fa51da4 | 2181 | |
91e0c79e MJD |
2182 | L<perlrequick>. |
2183 | ||
2184 | L<perlretut>. | |
2185 | ||
9b599b2a GS |
2186 | L<perlop/"Regexp Quote-Like Operators">. |
2187 | ||
1e66bd83 PP |
2188 | L<perlop/"Gory details of parsing quoted constructs">. |
2189 | ||
14218588 GS |
2190 | L<perlfaq6>. |
2191 | ||
9b599b2a GS |
2192 | L<perlfunc/pos>. |
2193 | ||
2194 | L<perllocale>. | |
2195 | ||
fb55449c JH |
2196 | L<perlebcdic>. |
2197 | ||
14218588 GS |
2198 | I<Mastering Regular Expressions> by Jeffrey Friedl, published |
2199 | by O'Reilly and Associates. |