| 77 |
documentation for details. |
documentation for details. |
| 78 |
.P |
.P |
| 79 |
9. Subpatterns that are called recursively or as "subroutines" are always |
9. Subpatterns that are called recursively or as "subroutines" are always |
| 80 |
treated as atomic groups in PCRE. This is like Python, but unlike Perl. There |
treated as atomic groups in PCRE. This is like Python, but unlike Perl. There |
| 81 |
is a discussion of an example that explains this in more detail in the |
is a discussion of an example that explains this in more detail in the |
| 82 |
.\" HTML <a href="pcrepattern.html#recursiondifference"> |
.\" HTML <a href="pcrepattern.html#recursiondifference"> |
| 83 |
.\" </a> |
.\" </a> |
| 97 |
(*COMMIT), (*PRUNE), (*SKIP), and (*THEN), but only in the forms without an |
(*COMMIT), (*PRUNE), (*SKIP), and (*THEN), but only in the forms without an |
| 98 |
argument. PCRE does not support (*MARK). |
argument. PCRE does not support (*MARK). |
| 99 |
.P |
.P |
| 100 |
12. PCRE's handling of duplicate subpattern numbers and duplicate subpattern |
12. PCRE's handling of duplicate subpattern numbers and duplicate subpattern |
| 101 |
names is not as general as Perl's. This is a consequence of the fact the PCRE |
names is not as general as Perl's. This is a consequence of the fact the PCRE |
| 102 |
works internally just with numbers, using an external table to translate |
works internally just with numbers, using an external table to translate |
| 103 |
between numbers and names. In particular, a pattern such as (?|(?<a>A)|(?<b)B), |
between numbers and names. In particular, a pattern such as (?|(?<a>A)|(?<b)B), |