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

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

Parent Directory | Revision Log | View Patch Patch

-revision 572 by ph10,
Wed Nov 17 17:55:57 2010 UTC
+revision 835 by ph10,
Wed Dec 28 16:10:09 2011 UTC
 Line 32 
 Starting a pattern with this sequence is
  option. This feature is not Perl-compatible. How setting UTF-8 mode affects
  pattern matching is mentioned in several places below. There is also a summary
  of UTF-8 features in the
- .\" HTML <a href="pcre.html#utf8support">
- .\" </a>
- section on UTF-8 support
- .\"
- in the main
  .\" HREF
- \fBpcre\fP
+ \fBpcreunicode\fP
  .\"
  page.
  .P
-Line 52 
 such as \ed and \ew to use Unicode prope
+Line 47 
 such as \ed and \ew to use Unicode prope
  instead of recognizing only characters with codes less than 128 via a lookup
  table.
  .P
+ If a pattern starts with (*NO_START_OPT), it has the same effect as setting the
+ PCRE_NO_START_OPTIMIZE option either at compile or matching time. There are
+ also some more of these special sequences that are concerned with the handling
+ of newlines; they are described below.
+ .P
  The remainder of this document discusses the patterns that are supported by
  PCRE when its main matching function, \fBpcre_exec()\fP, is used.
  From release 6.0, PCRE offers a second matching function,
 Line 182 
 The following sections describe the use
  .rs
  .sp
  The backslash character has several uses. Firstly, if it is followed by a
- non-alphanumeric character, it takes away any special meaning that character
+ character that is not a number or a letter, it takes away any special meaning
- may have. This use of backslash as an escape character applies both inside and
+ that character may have. This use of backslash as an escape character applies
- outside character classes.
+ both inside and outside character classes.
  .P
  For example, if you want to match a * character, you write \e* in the pattern.
  This escaping action applies whether or not the following character would
 Line 192 
 otherwise be interpreted as a metacharac
  non-alphanumeric with backslash to specify that it stands for itself. In
  particular, if you want to match a backslash, you write \e\e.
  .P
+ In UTF-8 mode, only ASCII numbers and letters have any special meaning after a
+ backslash. All other characters (in particular, those whose codepoints are
+ greater than 127) are treated as literals.
+ .P
  If a pattern is compiled with the PCRE_EXTENDED option, whitespace in the
  pattern (other than in a character class) and characters between a # outside
  a character class and the next newline are ignored. An escaping backslash can
-Line 211 
 Perl, $ and @ cause variable interpolati
+Line 215 
 Perl, $ and @ cause variable interpolati
    \eQabc\eE\e$\eQxyz\eE   abc$xyz        abc$xyz
  .sp
  The \eQ...\eE sequence is recognized both inside and outside character classes.
- An isolated \eE that is not preceded by \eQ is ignored.
+ An isolated \eE that is not preceded by \eQ is ignored. If \eQ is not followed
+ by \eE later in the pattern, the literal interpretation continues to the end of
+ the pattern (that is, \eE is assumed at the end). If the isolated \eQ is inside
+ a character class, this causes an error, because the character class is not
+ terminated.
  .
  .
  .\" HTML <a name="digitsafterbackslash"></a>
-Line 225 
 but when a pattern is being prepared by
+Line 233 
 but when a pattern is being prepared by
  one of the following escape sequences than the binary character it represents:
  .sp
    \ea        alarm, that is, the BEL character (hex 07)
-   \ecx       "control-x", where x is any character
+   \ecx       "control-x", where x is any ASCII character
    \ee        escape (hex 1B)
    \ef        formfeed (hex 0C)
    \en        linefeed (hex 0A)
-Line 233 
 one of the following escape sequences th
+Line 241 
 one of the following escape sequences th
    \et        tab (hex 09)
    \eddd      character with octal code ddd, or back reference
    \exhh      character with hex code hh
-   \ex{hhh..} character with hex code hhh..
+   \ex{hhh..} character with hex code hhh.. (non-JavaScript mode)
+   \euhhhh    character with hex code hhhh (JavaScript mode only)
  .sp
  The precise effect of \ecx is as follows: if x is a lower case letter, it
  is converted to upper case. Then bit 6 of the character (hex 40) is inverted.
- Thus \ecz becomes hex 1A, but \ec{ becomes hex 3B, while \ec; becomes hex
+ Thus \ecz becomes hex 1A (z is 7A), but \ec{ becomes hex 3B ({ is 7B), while
-B.
+ \ec; becomes hex 7B (; is 3B). If the byte following \ec has a value greater
- .P
+ than 127, a compile-time error occurs. This locks out non-ASCII characters in
- After \ex, from zero to two hexadecimal digits are read (letters can be in
+ both byte mode and UTF-8 mode. (When PCRE is compiled in EBCDIC mode, all byte
- upper or lower case). Any number of hexadecimal digits may appear between \ex{
+ values are valid. A lower case letter is converted to upper case, and then the
- and }, but the value of the character code must be less than 256 in non-UTF-8
+xc0 bits are flipped.)
- mode, and less than 2**31 in UTF-8 mode. That is, the maximum value in
+ .P
- hexadecimal is 7FFFFFFF. Note that this is bigger than the largest Unicode code
+ By default, after \ex, from zero to two hexadecimal digits are read (letters
- point, which is 10FFFF.
+ can be in upper or lower case). Any number of hexadecimal digits may appear
+ between \ex{ and }, but the value of the character code must be less than 256
+ in non-UTF-8 mode, and less than 2**31 in UTF-8 mode. That is, the maximum
+ value in hexadecimal is 7FFFFFFF. Note that this is bigger than the largest
+ Unicode code point, which is 10FFFF.
  .P
  If characters other than hexadecimal digits appear between \ex{ and }, or if
  there is no terminating }, this form of escape is not recognized. Instead, the
  initial \ex will be interpreted as a basic hexadecimal escape, with no
  following digits, giving a character whose value is zero.
  .P
+ If the PCRE_JAVASCRIPT_COMPAT option is set, the interpretation of \ex is
+ as just described only when it is followed by two hexadecimal digits.
+ Otherwise, it matches a literal "x" character. In JavaScript mode, support for
+ code points greater than 256 is provided by \eu, which must be followed by
+ four hexadecimal digits; otherwise it matches a literal "u" character.
+ .P
  Characters whose value is less than 256 can be defined by either of the two
- syntaxes for \ex. There is no difference in the way they are handled. For
+ syntaxes for \ex (or by \eu in JavaScript mode). There is no difference in the
- example, \exdc is exactly the same as \ex{dc}.
+ way they are handled. For example, \exdc is exactly the same as \ex{dc} (or
+ \eu00dc in JavaScript mode).
  .P
  After \e0 up to two further octal digits are read. If there are fewer than two
  digits, just those that are present are used. Thus the sequence \e0\ex\e07
-Line 316 
 unrecognized escape sequences, they are
+Line 336 
 unrecognized escape sequences, they are
  set. Outside a character class, these sequences have different meanings.
  .
  .
+ .SS "Unsupported escape sequences"
+ .rs
+ .sp
+ In Perl, the sequences \el, \eL, \eu, and \eU are recognized by its string
+ handler and used to modify the case of following characters. By default, PCRE
+ does not support these escape sequences. However, if the PCRE_JAVASCRIPT_COMPAT
+ option is set, \eU matches a "U" character, and \eu can be used to define a
+ character by code point, as described in the previous section.
+ .
+ .
  .SS "Absolute and relative back references"
  .rs
  .sp
-Line 375 
 This is the same as
+Line 405 
 This is the same as
  .\" </a>
  the "." metacharacter
  .\"
- when PCRE_DOTALL is not set.
+ when PCRE_DOTALL is not set. Perl also uses \eN to match characters by name;
+ PCRE does not support this.
  .P
  Each pair of lower and upper case escape sequences partitions the complete set
  of characters into two disjoint sets. Any given character matches one, and only
-Line 424 
 any Unicode letter, and underscore. Note
+Line 455 
 any Unicode letter, and underscore. Note
  \eB because they are defined in terms of \ew and \eW. Matching these sequences
  is noticeably slower when PCRE_UCP is set.
  .P
  The sequences \eh, \eH, \ev, and \eV are features that were added to Perl at
  release 5.10. In contrast to the other sequences, which match only ASCII
  characters by default, these always match certain high-valued codepoints in
  UTF-8 mode, whether or not PCRE_UCP is set. The horizontal space characters
-Line 740 
 Characters with the "mark" property are
+Line 771 
 Characters with the "mark" property are
  preceding character. None of them have codepoints less than 256, so in
  non-UTF-8 mode \eX matches any one character.
  .P
+ Note that recent versions of Perl have changed \eX to match what Unicode calls
+ an "extended grapheme cluster", which has a more complicated definition.
+ .P
  Matching characters by Unicode property is not fast, because PCRE has to search
  a structure that contains data for over fifteen thousand characters. That is
  why the traditional escape sequences such as \ed and \ew do not use Unicode
-Line 947 
 The handling of dot is entirely independ
+Line 981 
 The handling of dot is entirely independ
  dollar, the only relationship being that they both involve newlines. Dot has no
  special meaning in a character class.
  .P
  The escape sequence \eN behaves like a dot, except that it is not affected by
  the PCRE_DOTALL option. In other words, it matches any character except one
- that signifies the end of a line.
+ that signifies the end of a line. Perl also uses \eN to match characters by
+ name; PCRE does not support this.
  .
  .
  .SH "MATCHING A SINGLE BYTE"
  .rs
  .sp
  Outside a character class, the escape sequence \eC matches any one byte, both
- in and out of UTF-8 mode. Unlike a dot, it always matches any line-ending
+ in and out of UTF-8 mode. Unlike a dot, it always matches line-ending
  characters. The feature is provided in Perl in order to match individual bytes
- in UTF-8 mode. Because it breaks up UTF-8 characters into individual bytes, the
+ in UTF-8 mode, but it is unclear how it can usefully be used. Because \eC
- rest of the string may start with a malformed UTF-8 character. For this reason,
+ breaks up characters into individual bytes, matching one byte with \eC in UTF-8
- the \eC escape sequence is best avoided.
+ mode means that the rest of the string may start with a malformed UTF-8
+ character. This has undefined results, because PCRE assumes that it is dealing
+ with valid UTF-8 strings (and by default it checks this at the start of
+ processing unless the PCRE_NO_UTF8_CHECK option is used).
  .P
  PCRE does not allow \eC to appear in lookbehind assertions
  .\" HTML <a href="#lookbehind">
  .\" </a>
- (described below),
+ (described below)
  .\"
- because in UTF-8 mode this would make it impossible to calculate the length of
+ in UTF-8 mode, because this would make it impossible to calculate the length of
  the lookbehind.
+ .P
+ In general, the \eC escape sequence is best avoided in UTF-8 mode. However, one
+ way of using it that avoids the problem of malformed UTF-8 characters is to
+ use a lookahead to check the length of the next character, as in this pattern
+ (ignore white space and line breaks):
+ .sp
+   (?| (?=[\ex00-\ex7f])(\eC) |
+       (?=[\ex80-\ex{7ff}])(\eC)(\eC) |
+       (?=[\ex{800}-\ex{ffff}])(\eC)(\eC)(\eC) |
+       (?=[\ex{10000}-\ex{1fffff}])(\eC)(\eC)(\eC)(\eC))
+ .sp
+ A group that starts with (?| resets the capturing parentheses numbers in each
+ alternative (see
+ .\" HTML <a href="#dupsubpatternnumber">
+ .\" </a>
+ "Duplicate Subpattern Numbers"
+ .\"
+ below). The assertions at the start of each branch check the next UTF-8
+ character for values whose encoding uses 1, 2, 3, or 4 bytes, respectively. The
+ character's individual bytes are then captured by the appropriate number of
+ groups.
  .
  .
  .\" HTML <a name="characterclass"></a>
-Line 1044 
 characters in both cases. In UTF-8 mode,
+Line 1103 
 characters in both cases. In UTF-8 mode,
  characters with values greater than 128 only when it is compiled with Unicode
  property support.
  .P
- The character types \ed, \eD, \eh, \eH, \ep, \eP, \es, \eS, \ev, \eV, \ew, and
+ The character escape sequences \ed, \eD, \eh, \eH, \ep, \eP, \es, \eS, \ev,
- \eW may also appear in a character class, and add the characters that they
+ \eV, \ew, and \eW may appear in a character class, and add the characters that
- match to the class. For example, [\edABCDEF] matches any hexadecimal digit. A
+ they match to the class. For example, [\edABCDEF] matches any hexadecimal
- circumflex can conveniently be used with the upper case character types to
+ digit. In UTF-8 mode, the PCRE_UCP option affects the meanings of \ed, \es, \ew
+ and their upper case partners, just as it does when they appear outside a
+ character class, as described in the section entitled
+ .\" HTML <a href="#genericchartypes">
+ .\" </a>
+ "Generic character types"
+ .\"
+ above. The escape sequence \eb has a different meaning inside a character
+ class; it matches the backspace character. The sequences \eB, \eN, \eR, and \eX
+ are not special inside a character class. Like any other unrecognized escape
+ sequences, they are treated as the literal characters "B", "N", "R", and "X" by
+ default, but cause an error if the PCRE_EXTRA option is set.
+ .P
+ A circumflex can conveniently be used with the upper case character types to
  specify a more restricted set of characters than the matching lower case type.
- For example, the class [^\eW_] matches any letter or digit, but not underscore.
+ For example, the class [^\eW_] matches any letter or digit, but not underscore,
+ whereas [\ew] includes underscore. A positive character class should be read as
+ "something OR something OR ..." and a negative class as "NOT something AND NOT
+ something AND NOT ...".
  .P
  The only metacharacters that are recognized in character classes are backslash,
  hyphen (only where it can be interpreted as specifying a range), circumflex
-Line 1284 
 or "defdef":
+Line 1359 
 or "defdef":
  .sp
    /(?|(abc)|(def))\e1/
  .sp
- In contrast, a recursive or "subroutine" call to a numbered subpattern always
+ In contrast, a subroutine call to a numbered subpattern always refers to the
- refers to the first one in the pattern with the given number. The following
+ first one in the pattern with the given number. The following pattern matches
- pattern matches "abcabc" or "defabc":
+ "abcabc" or "defabc":
  .sp
    /(?|(abc)|(def))(?1)/
  .sp
-Line 1402 
 items:
+Line 1477 
 items:
    an escape such as \ed or \epL that matches a single character
    a character class
    a back reference (see next section)
-   a parenthesized subpattern (unless it is an assertion)
+   a parenthesized subpattern (including assertions)
-   a recursive or "subroutine" call to a subpattern
+   a subroutine call to a subpattern (recursive or otherwise)
  .sp
  The general repetition quantifier specifies a minimum and maximum number of
  permitted matches, by giving the two numbers in curly brackets (braces),
-Line 1793 
 those that look ahead of the current pos
+Line 1868 
 those that look ahead of the current pos
  that look behind it. An assertion subpattern is matched in the normal way,
  except that it does not cause the current matching position to be changed.
  .P
- Assertion subpatterns are not capturing subpatterns, and may not be repeated,
+ Assertion subpatterns are not capturing subpatterns. If such an assertion
- because it makes no sense to assert the same thing several times. If any kind
+ contains capturing subpatterns within it, these are counted for the purposes of
- of assertion contains capturing subpatterns within it, these are counted for
+ numbering the capturing subpatterns in the whole pattern. However, substring
- the purposes of numbering the capturing subpatterns in the whole pattern.
+ capturing is carried out only for positive assertions, because it does not make
- However, substring capturing is carried out only for positive assertions,
+ sense for negative assertions.
- because it does not make sense for negative assertions.
+ .P
+ For compatibility with Perl, assertion subpatterns may be repeated; though
+ it makes no sense to assert the same thing several times, the side effect of
+ capturing parentheses may occasionally be useful. In practice, there only three
+ cases:
+ .sp
+ (1) If the quantifier is {0}, the assertion is never obeyed during matching.
+ However, it may contain internal capturing parenthesized groups that are called
+ from elsewhere via the
+ .\" HTML <a href="#subpatternsassubroutines">
+ .\" </a>
+ subroutine mechanism.
+ .\"
+ .sp
+ (2) If quantifier is {0,n} where n is greater than zero, it is treated as if it
+ were {0,1}. At run time, the rest of the pattern match is tried with and
+ without the assertion, the order depending on the greediness of the quantifier.
+ .sp
+ (3) If the minimum repetition is greater than zero, the quantifier is ignored.
+ The assertion is obeyed just once when encountered during matching.
  .
  .
  .SS "Lookahead assertions"
-Line 1876 
 temporarily move the current position ba
+Line 1970 
 temporarily move the current position ba
  match. If there are insufficient characters before the current position, the
  assertion fails.
  .P
- PCRE does not allow the \eC escape (which matches a single byte in UTF-8 mode)
+ In UTF-8 mode, PCRE does not allow the \eC escape (which matches a single byte,
- to appear in lookbehind assertions, because it makes it impossible to calculate
+ even in UTF-8 mode) to appear in lookbehind assertions, because it makes it
- the length of the lookbehind. The \eX and \eR escapes, which can match
+ impossible to calculate the length of the lookbehind. The \eX and \eR escapes,
- different numbers of bytes, are also not permitted.
+ which can match different numbers of bytes, are also not permitted.
  .P
  .\" HTML <a href="#subpatternsassubroutines">
  .\" </a>
-Line 1968 
 already been matched. The two possible f
+Line 2062 
 already been matched. The two possible f
  If the condition is satisfied, the yes-pattern is used; otherwise the
  no-pattern (if present) is used. If there are more than two alternatives in the
  subpattern, a compile-time error occurs. Each of the two alternatives may
  itself contain nested subpatterns of any form, including conditional
  subpatterns; the restriction to two alternatives applies only at the level of
  the condition. This pattern fragment is an example where the alternatives are
  complex:
  .sp
    (?(1) (A|B|C) | (D | (?(2)E|F) | E) )
-Line 1995 
 the condition is true if any of them hav
+Line 2089 
 the condition is true if any of them hav
  to precede the digits with a plus or minus sign. In this case, the subpattern
  number is relative rather than absolute. The most recently opened parentheses
  can be referenced by (?(-1), the next most recent by (?(-2), and so on. Inside
  loops it can also make sense to refer to subsequent groups. The next
  parentheses to be opened can be referenced as (?(+1), and so on. (The value
  zero in any of these forms is not used; it provokes a compile-time error.)
  .P
-Line 2073 
 If the condition is the string (DEFINE),
+Line 2167 
 If the condition is the string (DEFINE),
  name DEFINE, the condition is always false. In this case, there may be only one
  alternative in the subpattern. It is always skipped if control reaches this
  point in the pattern; the idea of DEFINE is that it can be used to define
- "subroutines" that can be referenced from elsewhere. (The use of
+ subroutines that can be referenced from elsewhere. (The use of
  .\" HTML <a href="#subpatternsassubroutines">
  .\" </a>
- "subroutines"
+ subroutines
  .\"
  is described below.) For example, a pattern to match an IPv4 address such as
  "192.168.23.245" could be written like this (ignore whitespace and line
-Line 2115 
 dd-aaa-dd or dd-dd-dd, where aaa are let
+Line 2209 
 dd-aaa-dd or dd-dd-dd, where aaa are let
  .SH COMMENTS
  .rs
  .sp
  There are two ways of including comments in patterns that are processed by
  PCRE. In both cases, the start of the comment must not be in a character class,
  nor in the middle of any other sequence of related characters such as (?: or a
  subpattern name or number. The characters that make up a comment play no part
-Line 2139 
 default newline convention is in force:
+Line 2233 
 default newline convention is in force:
  .sp
    abc #comment \en still comment
  .sp
  On encountering the # character, \fBpcre_compile()\fP skips along, looking for
  a newline in the pattern. The sequence \en is still literal at this stage, so
  it does not terminate the comment. Only an actual character with the code value
 x0a (the default newline) does so.
-Line 2171 
 individual subpattern recursion. After i
+Line 2265 
 individual subpattern recursion. After i
  this kind of recursion was subsequently introduced into Perl at release 5.10.
  .P
  A special item that consists of (? followed by a number greater than zero and a
- closing parenthesis is a recursive call of the subpattern of the given number,
+ closing parenthesis is a recursive subroutine call of the subpattern of the
- provided that it occurs inside that subpattern. (If not, it is a
+ given number, provided that it occurs inside that subpattern. (If not, it is a
  .\" HTML <a href="#subpatternsassubroutines">
  .\" </a>
- "subroutine"
+ non-recursive subroutine
  .\"
  call, which is described in the next section.) The special item (?R) or (?0) is
  a recursive call of the entire regular expression.
-Line 2210 
 references such as (?+2). However, these
+Line 2304 
 references such as (?+2). However, these
  reference is not inside the parentheses that are referenced. They are always
  .\" HTML <a href="#subpatternsassubroutines">
  .\" </a>
- "subroutine"
+ non-recursive subroutine
  .\"
  calls, as described in the next section.
  .P
-Line 2247 
 documentation). If the pattern above is
+Line 2341 
 documentation). If the pattern above is
  .sp
  the value for the inner capturing parentheses (numbered 2) is "ef", which is
  the last value taken on at the top level. If a capturing subpattern is not
- matched at the top level, its final value is unset, even if it is (temporarily)
+ matched at the top level, its final captured value is unset, even if it was
- set at a deeper level.
+ (temporarily) set at a deeper level during the matching process.
  .P
  If there are more than 15 capturing parentheses in a pattern, PCRE has to
  obtain extra memory to store data during a recursion, which it does by using
-Line 2268 
 is the actual recursive call.
+Line 2362 
 is the actual recursive call.
  .
  .
  .\" HTML <a name="recursiondifference"></a>
- .SS "Recursion difference from Perl"
+ .SS "Differences in recursion processing between PCRE and Perl"
  .rs
  .sp
- In PCRE (like Python, but unlike Perl), a recursive subpattern call is always
+ Recursion processing in PCRE differs from Perl in two important ways. In PCRE
- treated as an atomic group. That is, once it has matched some of the subject
+ (like Python, but unlike Perl), a recursive subpattern call is always treated
- string, it is never re-entered, even if it contains untried alternatives and
+ as an atomic group. That is, once it has matched some of the subject string, it
- there is a subsequent matching failure. This can be illustrated by the
+ is never re-entered, even if it contains untried alternatives and there is a
- following pattern, which purports to match a palindromic string that contains
+ subsequent matching failure. This can be illustrated by the following pattern,
- an odd number of characters (for example, "a", "aba", "abcba", "abcdcba"):
+ which purports to match a palindromic string that contains an odd number of
+ characters (for example, "a", "aba", "abcba", "abcdcba"):
  .sp
    ^(.|(.)(?1)\e2)$
  .sp
-Line 2337 
 For example, although "abcba" is correct
+Line 2432 
 For example, although "abcba" is correct
  PCRE finds the palindrome "aba" at the start, then fails at top level because
  the end of the string does not follow. Once again, it cannot jump back into the
  recursion to try other alternatives, so the entire match fails.
+ .P
+ The second way in which PCRE and Perl differ in their recursion processing is
+ in the handling of captured values. In Perl, when a subpattern is called
+ recursively or as a subpattern (see the next section), it has no access to any
+ values that were captured outside the recursion, whereas in PCRE these values
+ can be referenced. Consider this pattern:
+ .sp
+   ^(.)(\e1|a(?2))
+ .sp
+ In PCRE, this pattern matches "bab". The first capturing parentheses match "b",
+ then in the second group, when the back reference \e1 fails to match "b", the
+ second alternative matches "a" and then recurses. In the recursion, \e1 does
+ now match "b" and so the whole match succeeds. In Perl, the pattern fails to
+ match because inside the recursive call \e1 cannot access the externally set
+ value.
  .
  .
  .\" HTML <a name="subpatternsassubroutines"></a>
  .SH "SUBPATTERNS AS SUBROUTINES"
  .rs
  .sp
- If the syntax for a recursive subpattern reference (either by number or by
+ If the syntax for a recursive subpattern call (either by number or by
  name) is used outside the parentheses to which it refers, it operates like a
- subroutine in a programming language. The "called" subpattern may be defined
+ subroutine in a programming language. The called subpattern may be defined
  before or after the reference. A numbered reference can be absolute or
  relative, as in these examples:
  .sp
-Line 2365 
 matches "sense and sensibility" and "res
+Line 2475 
 matches "sense and sensibility" and "res
  is used, it does match "sense and responsibility" as well as the other two
  strings. Another example is given in the discussion of DEFINE above.
  .P
- Like recursive subpatterns, a subroutine call is always treated as an atomic
+ All subroutine calls, whether recursive or not, are always treated as atomic
- group. That is, once it has matched some of the subject string, it is never
+ groups. That is, once a subroutine has matched some of the subject string, it
- re-entered, even if it contains untried alternatives and there is a subsequent
+ is never re-entered, even if it contains untried alternatives and there is a
- matching failure. Any capturing parentheses that are set during the subroutine
+ subsequent matching failure. Any capturing parentheses that are set during the
- call revert to their previous values afterwards.
+ subroutine call revert to their previous values afterwards.
  .P
- When a subpattern is used as a subroutine, processing options such as
+ Processing options such as case-independence are fixed when a subpattern is
- case-independence are fixed when the subpattern is defined. They cannot be
+ defined, so if it is used as a subroutine, such options cannot be changed for
- changed for different calls. For example, consider this pattern:
+ different calls. For example, consider this pattern:
  .sp
    (abc)(?i:(?-1))
  .sp
-Line 2454 
 a backtracking algorithm. With the excep
+Line 2564 
 a backtracking algorithm. With the excep
  failing negative assertion, they cause an error if encountered by
  \fBpcre_dfa_exec()\fP.
  .P
- If any of these verbs are used in an assertion or subroutine subpattern
+ If any of these verbs are used in an assertion or in a subpattern that is
- (including recursive subpatterns), their effect is confined to that subpattern;
+ called as a subroutine (whether or not recursively), their effect is confined
- it does not extend to the surrounding pattern. Note that such subpatterns are
+ to that subpattern; it does not extend to the surrounding pattern, with one
- processed as anchored at the point where they are tested.
+ exception: a *MARK that is encountered in a positive assertion \fIis\fP passed
+ back (compare capturing parentheses in assertions). Note that such subpatterns
+ are processed as anchored at the point where they are tested. Note also that
+ Perl's treatment of subroutines is different in some cases.
  .P
  The new verbs make use of what was previously invalid syntax: an opening
  parenthesis followed by an asterisk. They are generally of the form
  (*VERB) or (*VERB:NAME). Some may take either form, with differing behaviour,
- depending on whether or not an argument is present. An name is a sequence of
+ depending on whether or not an argument is present. A name is any sequence of
- letters, digits, and underscores. If the name is empty, that is, if the closing
+ characters that does not include a closing parenthesis. If the name is empty,
- parenthesis immediately follows the colon, the effect is as if the colon were
+ that is, if the closing parenthesis immediately follows the colon, the effect
- not there. Any number of these verbs may occur in a pattern.
+ is as if the colon were not there. Any number of these verbs may occur in a
+ pattern.
  .P
  PCRE contains some optimizations that are used to speed up matching by running
  some checks at the start of each match attempt. For example, it may know the
-Line 2473 
 minimum length of matching subject, or t
+Line 2587 
 minimum length of matching subject, or t
  present. When one of these optimizations suppresses the running of a match, any
  included backtracking verbs will not, of course, be processed. You can suppress
  the start-of-match optimizations by setting the PCRE_NO_START_OPTIMIZE option
- when calling \fBpcre_exec()\fP.
+ when calling \fBpcre_compile()\fP or \fBpcre_exec()\fP, or by starting the
+ pattern with (*NO_START_OPT).
  .
  .
  .SS "Verbs that act immediately"
-Line 2485 
 followed by a name.
+Line 2600 
 followed by a name.
     (*ACCEPT)
  .sp
  This verb causes the match to end successfully, skipping the remainder of the
- pattern. When inside a recursion, only the innermost pattern is ended
+ pattern. However, when it is inside a subpattern that is called as a
- immediately. If (*ACCEPT) is inside capturing parentheses, the data so far is
+ subroutine, only that subpattern is ended successfully. Matching then continues
- captured. (This feature was added to PCRE at release 8.00.) For example:
+ at the outer level. If (*ACCEPT) is inside capturing parentheses, the data so
+ far is captured. For example:
  .sp
    A((?:A|B(*ACCEPT)|C)D)
  .sp
-Line 2496 
 the outer parentheses.
+Line 2612 
 the outer parentheses.
  .sp
    (*FAIL) or (*F)
  .sp
- This verb causes the match to fail, forcing backtracking to occur. It is
+ This verb causes a matching failure, forcing backtracking to occur. It is
  equivalent to (?!) but easier to read. The Perl documentation notes that it is
  probably useful only when combined with (?{}) or (??{}). Those are, of course,
  Perl features that are not present in PCRE. The nearest equivalent is the
-Line 2547 
 indicates which of the two alternatives
+Line 2663 
 indicates which of the two alternatives
  of obtaining this information than putting each alternative in its own
  capturing parentheses.
  .P
+ If (*MARK) is encountered in a positive assertion, its name is recorded and
+ passed back if it is the last-encountered. This does not happen for negative
+ assertions.
+ .P
  A name may also be returned after a failed match if the final path through the
  pattern involves (*MARK). However, unless (*MARK) used in conjunction with
  (*COMMIT), this is unlikely to happen for an unanchored pattern because, as the
-Line 2659 
 following pattern fails to match, the pr
+Line 2779 
 following pattern fails to match, the pr
  searched for the most recent (*MARK) that has the same name. If one is found,
  the "bumpalong" advance is to the subject position that corresponds to that
  (*MARK) instead of to where (*SKIP) was encountered. If no (*MARK) with a
- matching name is found, normal "bumpalong" of one character happens (the
+ matching name is found, normal "bumpalong" of one character happens (that is,
- (*SKIP) is ignored).
+ the (*SKIP) is ignored).
  .sp
    (*THEN) or (*THEN:NAME)
  .sp
- This verb causes a skip to the next alternation in the innermost enclosing
+ This verb causes a skip to the next innermost alternative if the rest of the
- group if the rest of the pattern does not match. That is, it cancels pending
+ pattern does not match. That is, it cancels pending backtracking, but only
- backtracking, but only within the current alternation. Its name comes from the
+ within the current alternative. Its name comes from the observation that it can
- observation that it can be used for a pattern-based if-then-else block:
+ be used for a pattern-based if-then-else block:
  .sp
    ( COND1 (*THEN) FOO | COND2 (*THEN) BAR | COND3 (*THEN) BAZ ) ...
  .sp
  If the COND1 pattern matches, FOO is tried (and possibly further items after
- the end of the group if FOO succeeds); on failure the matcher skips to the
+ the end of the group if FOO succeeds); on failure, the matcher skips to the
  second alternative and tries COND2, without backtracking into COND1. The
  behaviour of (*THEN:NAME) is exactly the same as (*MARK:NAME)(*THEN) if the
- overall match fails. If (*THEN) is not directly inside an alternation, it acts
+ overall match fails. If (*THEN) is not inside an alternation, it acts like
- like (*PRUNE).
+ (*PRUNE).
- .
- .P
- The above verbs provide four different "strengths" of control when subsequent
- matching fails. (*THEN) is the weakest, carrying on the match at the next
- alternation. (*PRUNE) comes next, failing the match at the current starting
- position, but allowing an advance to the next character (for an unanchored
- pattern). (*SKIP) is similar, except that the advance may be more than one
- character. (*COMMIT) is the strongest, causing the entire match to fail.
  .P
- If more than one is present in a pattern, the "stongest" one wins. For example,
+ Note that a subpattern that does not contain a | character is just a part of
- consider this pattern, where A, B, etc. are complex pattern fragments:
+ the enclosing alternative; it is not a nested alternation with only one
+ alternative. The effect of (*THEN) extends beyond such a subpattern to the
+ enclosing alternative. Consider this pattern, where A, B, etc. are complex
+ pattern fragments that do not contain any | characters at this level:
+ .sp
+   A (B(*THEN)C) | D
+ .sp
+ If A and B are matched, but there is a failure in C, matching does not
+ backtrack into A; instead it moves to the next alternative, that is, D.
+ However, if the subpattern containing (*THEN) is given an alternative, it
+ behaves differently:
+ .sp
+   A (B(*THEN)C | (*FAIL)) | D
+ .sp
+ The effect of (*THEN) is now confined to the inner subpattern. After a failure
+ in C, matching moves to (*FAIL), which causes the whole subpattern to fail
+ because there are no more alternatives to try. In this case, matching does now
+ backtrack into A.
+ .P
+ Note also that a conditional subpattern is not considered as having two
+ alternatives, because only one is ever used. In other words, the | character in
+ a conditional subpattern has a different meaning. Ignoring white space,
+ consider:
+ .sp
+   ^.*? (?(?=a) a | b(*THEN)c )
+ .sp
+ If the subject is "ba", this pattern does not match. Because .*? is ungreedy,
+ it initially matches zero characters. The condition (?=a) then fails, the
+ character "b" is matched, but "c" is not. At this point, matching does not
+ backtrack to .*? as might perhaps be expected from the presence of the |
+ character. The conditional subpattern is part of the single alternative that
+ comprises the whole pattern, and so the match fails. (If there was a backtrack
+ into .*?, allowing it to match "b", the match would succeed.)
+ .P
+ The verbs just described provide four different "strengths" of control when
+ subsequent matching fails. (*THEN) is the weakest, carrying on the match at the
+ next alternative. (*PRUNE) comes next, failing the match at the current
+ starting position, but allowing an advance to the next character (for an
+ unanchored pattern). (*SKIP) is similar, except that the advance may be more
+ than one character. (*COMMIT) is the strongest, causing the entire match to
+ fail.
+ .P
+ If more than one such verb is present in a pattern, the "strongest" one wins.
+ For example, consider this pattern, where A, B, etc. are complex pattern
+ fragments:
  .sp
    (A(*COMMIT)B(*THEN)C|D)
  .sp
  Once A has matched, PCRE is committed to this match, at the current starting
  position. If subsequently B matches, but C does not, the normal (*THEN) action
- of trying the next alternation (that is, D) does not happen because (*COMMIT)
+ of trying the next alternative (that is, D) does not happen because (*COMMIT)
  overrides.
  .
  .
-Line 2718 
 Cambridge CB2 3QH, England.
+Line 2874 
 Cambridge CB2 3QH, England.
  .rs
  .sp
  .nf
- Last updated: 17 November 2010
+ Last updated: 19 November 2011
- Copyright (c) 1997-2010 University of Cambridge.
+ Copyright (c) 1997-2011 University of Cambridge.
  .fi

 Legend:



Removed from v.572
 


changed lines


 
Added in v.835
 Legend:



Removed from v.572
 


changed lines


 
Added in v.835
-Removed from v.572
+Added in v.835

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12