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

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

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 247 by ph10, Mon Sep 17 09:38:32 2007 UTC revision 459 by ph10, Sun Oct 4 09:21:39 2009 UTC
# Line 9  are described in detail below. There is Line 9  are described in detail below. There is
9  .\" HREF  .\" HREF
10  \fBpcresyntax\fP  \fBpcresyntax\fP
11  .\"  .\"
12  page. Perl's regular expressions are described in its own documentation, and  page. PCRE tries to match Perl syntax and semantics as closely as it can. PCRE
13    also supports some alternative regular expression syntax (which does not
14    conflict with the Perl syntax) in order to provide some compatibility with
15    regular expressions in Python, .NET, and Oniguruma.
16    .P
17    Perl's regular expressions are described in its own documentation, and
18  regular expressions in general are covered in a number of books, some of which  regular expressions in general are covered in a number of books, some of which
19  have copious examples. Jeffrey Friedl's "Mastering Regular Expressions",  have copious examples. Jeffrey Friedl's "Mastering Regular Expressions",
20  published by O'Reilly, covers regular expressions in great detail. This  published by O'Reilly, covers regular expressions in great detail. This
21  description of PCRE's regular expressions is intended as reference material.  description of PCRE's regular expressions is intended as reference material.
22  .P  .P
23  The original operation of PCRE was on strings of one-byte characters. However,  The original operation of PCRE was on strings of one-byte characters. However,
24  there is now also support for UTF-8 character strings. To use this, you must  there is now also support for UTF-8 character strings. To use this,
25  build PCRE to include UTF-8 support, and then call \fBpcre_compile()\fP with  PCRE must be built to include UTF-8 support, and you must call
26  the PCRE_UTF8 option. How this affects pattern matching is mentioned in several  \fBpcre_compile()\fP or \fBpcre_compile2()\fP with the PCRE_UTF8 option. There
27  places below. There is also a summary of UTF-8 features in the  is also a special sequence that can be given at the start of a pattern:
28    .sp
29      (*UTF8)
30    .sp
31    Starting a pattern with this sequence is equivalent to setting the PCRE_UTF8
32    option. This feature is not Perl-compatible. How setting UTF-8 mode affects
33    pattern matching is mentioned in several places below. There is also a summary
34    of UTF-8 features in the
35  .\" HTML <a href="pcre.html#utf8support">  .\" HTML <a href="pcre.html#utf8support">
36  .\" </a>  .\" </a>
37  section on UTF-8 support  section on UTF-8 support
# Line 71  string with one of the following five se Line 83  string with one of the following five se
83    (*ANYCRLF)   any of the three above    (*ANYCRLF)   any of the three above
84    (*ANY)       all Unicode newline sequences    (*ANY)       all Unicode newline sequences
85  .sp  .sp
86  These override the default and the options given to \fBpcre_compile()\fP. For  These override the default and the options given to \fBpcre_compile()\fP or
87  example, on a Unix system where LF is the default newline sequence, the pattern  \fBpcre_compile2()\fP. For example, on a Unix system where LF is the default
88    newline sequence, the pattern
89  .sp  .sp
90    (*CR)a.b    (*CR)a.b
91  .sp  .sp
# Line 194  The \eQ...\eE sequence is recognized bot Line 207  The \eQ...\eE sequence is recognized bot
207  A second use of backslash provides a way of encoding non-printing characters  A second use of backslash provides a way of encoding non-printing characters
208  in patterns in a visible manner. There is no restriction on the appearance of  in patterns in a visible manner. There is no restriction on the appearance of
209  non-printing characters, apart from the binary zero that terminates a pattern,  non-printing characters, apart from the binary zero that terminates a pattern,
210  but when a pattern is being prepared by text editing, it is usually easier to  but when a pattern is being prepared by text editing, it is often easier to use
211  use one of the following escape sequences than the binary character it  one of the following escape sequences than the binary character it represents:
 represents:  
212  .sp  .sp
213    \ea        alarm, that is, the BEL character (hex 07)    \ea        alarm, that is, the BEL character (hex 07)
214    \ecx       "control-x", where x is any character    \ecx       "control-x", where x is any character
# Line 310  parenthesized subpatterns. Line 322  parenthesized subpatterns.
322  .\"  .\"
323  .  .
324  .  .
325    .SS "Absolute and relative subroutine calls"
326    .rs
327    .sp
328    For compatibility with Oniguruma, the non-Perl syntax \eg followed by a name or
329    a number enclosed either in angle brackets or single quotes, is an alternative
330    syntax for referencing a subpattern as a "subroutine". Details are discussed
331    .\" HTML <a href="#onigurumasubroutines">
332    .\" </a>
333    later.
334    .\"
335    Note that \eg{...} (Perl syntax) and \eg<...> (Oniguruma syntax) are \fInot\fP
336    synonymous. The former is a back reference; the latter is a
337    .\" HTML <a href="#subpatternsassubroutines">
338    .\" </a>
339    subroutine
340    .\"
341    call.
342    .
343    .
344  .SS "Generic character types"  .SS "Generic character types"
345  .rs  .rs
346  .sp  .sp
# Line 345  In UTF-8 mode, characters with values gr Line 376  In UTF-8 mode, characters with values gr
376  \ew, and always match \eD, \eS, and \eW. This is true even when Unicode  \ew, and always match \eD, \eS, and \eW. This is true even when Unicode
377  character property support is available. These sequences retain their original  character property support is available. These sequences retain their original
378  meanings from before UTF-8 support was available, mainly for efficiency  meanings from before UTF-8 support was available, mainly for efficiency
379  reasons.  reasons. Note that this also affects \eb, because it is defined in terms of \ew
380    and \eW.
381  .P  .P
382  The sequences \eh, \eH, \ev, and \eV are Perl 5.10 features. In contrast to the  The sequences \eh, \eH, \ev, and \eV are Perl 5.10 features. In contrast to the
383  other sequences, these do match certain high-valued codepoints in UTF-8 mode.  other sequences, these do match certain high-valued codepoints in UTF-8 mode.
# Line 436  one of the following sequences: Line 468  one of the following sequences:
468    (*BSR_ANYCRLF)   CR, LF, or CRLF only    (*BSR_ANYCRLF)   CR, LF, or CRLF only
469    (*BSR_UNICODE)   any Unicode newline sequence    (*BSR_UNICODE)   any Unicode newline sequence
470  .sp  .sp
471  These override the default and the options given to \fBpcre_compile()\fP, but  These override the default and the options given to \fBpcre_compile()\fP or
472  they can be overridden by options given to \fBpcre_exec()\fP. Note that these  \fBpcre_compile2()\fP, but they can be overridden by options given to
473  special settings, which are not Perl-compatible, are recognized only at the  \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP. Note that these special settings,
474  very start of a pattern, and that they must be in upper case. If more than one  which are not Perl-compatible, are recognized only at the very start of a
475  of them is present, the last one is used. They can be combined with a change of  pattern, and that they must be in upper case. If more than one of them is
476  newline convention, for example, a pattern can start with:  present, the last one is used. They can be combined with a change of newline
477    convention, for example, a pattern can start with:
478  .sp  .sp
479    (*ANY)(*BSR_ANYCRLF)    (*ANY)(*BSR_ANYCRLF)
480  .sp  .sp
# Line 615  cannot be tested by PCRE, unless UTF-8 v Line 648  cannot be tested by PCRE, unless UTF-8 v
648  .\" HREF  .\" HREF
649  \fBpcreapi\fP  \fBpcreapi\fP
650  .\"  .\"
651  page).  page). Perl does not support the Cs property.
652  .P  .P
653  The long synonyms for these properties that Perl supports (such as \ep{Letter})  The long synonyms for property names that Perl supports (such as \ep{Letter})
654  are not supported by PCRE, nor is it permitted to prefix any of these  are not supported by PCRE, nor is it permitted to prefix any of these
655  properties with "Is".  properties with "Is".
656  .P  .P
# Line 708  different meaning, namely the backspace Line 741  different meaning, namely the backspace
741  A word boundary is a position in the subject string where the current character  A word boundary is a position in the subject string where the current character
742  and the previous character do not both match \ew or \eW (i.e. one matches  and the previous character do not both match \ew or \eW (i.e. one matches
743  \ew and the other matches \eW), or the start or end of the string if the  \ew and the other matches \eW), or the start or end of the string if the
744  first or last character matches \ew, respectively.  first or last character matches \ew, respectively. Neither PCRE nor Perl has a
745    separte "start of word" or "end of word" metasequence. However, whatever
746    follows \eb normally determines which it is. For example, the fragment
747    \eba matches "a" at the start of a word.
748  .P  .P
749  The \eA, \eZ, and \ez assertions differ from the traditional circumflex and  The \eA, \eZ, and \ez assertions differ from the traditional circumflex and
750  dollar (described in the next section) in that they only ever match at the very  dollar (described in the next section) in that they only ever match at the very
# Line 840  the lookbehind. Line 876  the lookbehind.
876  .rs  .rs
877  .sp  .sp
878  An opening square bracket introduces a character class, terminated by a closing  An opening square bracket introduces a character class, terminated by a closing
879  square bracket. A closing square bracket on its own is not special. If a  square bracket. A closing square bracket on its own is not special by default.
880  closing square bracket is required as a member of the class, it should be the  However, if the PCRE_JAVASCRIPT_COMPAT option is set, a lone closing square
881  first data character in the class (after an initial circumflex, if present) or  bracket causes a compile-time error. If a closing square bracket is required as
882  escaped with a backslash.  a member of the class, it should be the first data character in the class
883    (after an initial circumflex, if present) or escaped with a backslash.
884  .P  .P
885  A character class matches a single character in the subject. In UTF-8 mode, the  A character class matches a single character in the subject. In UTF-8 mode, the
886  character may occupy more than one byte. A matched character must be in the set  character may be more than one byte long. A matched character must be in the
887  of characters defined by the class, unless the first character in the class  set of characters defined by the class, unless the first character in the class
888  definition is a circumflex, in which case the subject character must not be in  definition is a circumflex, in which case the subject character must not be in
889  the set defined by the class. If a circumflex is actually required as a member  the set defined by the class. If a circumflex is actually required as a member
890  of the class, ensure it is not the first character, or escape it with a  of the class, ensure it is not the first character, or escape it with a
# Line 857  For example, the character class [aeiou] Line 894  For example, the character class [aeiou]
894  [^aeiou] matches any character that is not a lower case vowel. Note that a  [^aeiou] matches any character that is not a lower case vowel. Note that a
895  circumflex is just a convenient notation for specifying the characters that  circumflex is just a convenient notation for specifying the characters that
896  are in the class by enumerating those that are not. A class that starts with a  are in the class by enumerating those that are not. A class that starts with a
897  circumflex is not an assertion: it still consumes a character from the subject  circumflex is not an assertion; it still consumes a character from the subject
898  string, and therefore it fails if the current pointer is at the end of the  string, and therefore it fails if the current pointer is at the end of the
899  string.  string.
900  .P  .P
# Line 871  caseful version would. In UTF-8 mode, PC Line 908  caseful version would. In UTF-8 mode, PC
908  case for characters whose values are less than 128, so caseless matching is  case for characters whose values are less than 128, so caseless matching is
909  always possible. For characters with higher values, the concept of case is  always possible. For characters with higher values, the concept of case is
910  supported if PCRE is compiled with Unicode property support, but not otherwise.  supported if PCRE is compiled with Unicode property support, but not otherwise.
911  If you want to use caseless matching for characters 128 and above, you must  If you want to use caseless matching in UTF8-mode for characters 128 and above,
912  ensure that PCRE is compiled with Unicode property support as well as with  you must ensure that PCRE is compiled with Unicode property support as well as
913  UTF-8 support.  with UTF-8 support.
914  .P  .P
915  Characters that might indicate line breaks are never treated in any special way  Characters that might indicate line breaks are never treated in any special way
916  when matching character classes, whatever line-ending sequence is in use, and  when matching character classes, whatever line-ending sequence is in use, and
# Line 1012  The PCRE-specific options PCRE_DUPNAMES, Line 1049  The PCRE-specific options PCRE_DUPNAMES,
1049  changed in the same way as the Perl-compatible options by using the characters  changed in the same way as the Perl-compatible options by using the characters
1050  J, U and X respectively.  J, U and X respectively.
1051  .P  .P
1052  When an option change occurs at top level (that is, not inside subpattern  When one of these option changes occurs at top level (that is, not inside
1053  parentheses), the change applies to the remainder of the pattern that follows.  subpattern parentheses), the change applies to the remainder of the pattern
1054  If the change is placed right at the start of a pattern, PCRE extracts it into  that follows. If the change is placed right at the start of a pattern, PCRE
1055  the global options (and it will therefore show up in data extracted by the  extracts it into the global options (and it will therefore show up in data
1056  \fBpcre_fullinfo()\fP function).  extracted by the \fBpcre_fullinfo()\fP function).
1057  .P  .P
1058  An option change within a subpattern (see below for a description of  An option change within a subpattern (see below for a description of
1059  subpatterns) affects only that part of the current pattern that follows it, so  subpatterns) affects only that part of the current pattern that follows it, so
# Line 1034  matches "ab", "aB", "c", and "C", even t Line 1071  matches "ab", "aB", "c", and "C", even t
1071  branch is abandoned before the option setting. This is because the effects of  branch is abandoned before the option setting. This is because the effects of
1072  option settings happen at compile time. There would be some very weird  option settings happen at compile time. There would be some very weird
1073  behaviour otherwise.  behaviour otherwise.
1074    .P
1075    \fBNote:\fP There are other PCRE-specific options that can be set by the
1076    application when the compile or match functions are called. In some cases the
1077    pattern can contain special leading sequences such as (*CRLF) to override what
1078    the application has set or what has been defaulted. Details are given in the
1079    section entitled
1080    .\" HTML <a href="#newlineseq">
1081    .\" </a>
1082    "Newline sequences"
1083    .\"
1084    above. There is also the (*UTF8) leading sequence that can be used to set UTF-8
1085    mode; this is equivalent to setting the PCRE_UTF8 option.
1086  .  .
1087  .  .
1088  .\" HTML <a name="subpattern"></a>  .\" HTML <a name="subpattern"></a>
# Line 1088  is reached, an option setting in one bra Line 1137  is reached, an option setting in one bra
1137  the above patterns match "SUNDAY" as well as "Saturday".  the above patterns match "SUNDAY" as well as "Saturday".
1138  .  .
1139  .  .
1140    .\" HTML <a name="dupsubpatternnumber"></a>
1141  .SH "DUPLICATE SUBPATTERN NUMBERS"  .SH "DUPLICATE SUBPATTERN NUMBERS"
1142  .rs  .rs
1143  .sp  .sp
# Line 1113  stored. Line 1163  stored.
1163    / ( a )  (?| x ( y ) z | (p (q) r) | (t) u (v) ) ( z ) /x    / ( a )  (?| x ( y ) z | (p (q) r) | (t) u (v) ) ( z ) /x
1164    # 1            2         2  3        2     3     4    # 1            2         2  3        2     3     4
1165  .sp  .sp
1166  A backreference or a recursive call to a numbered subpattern always refers to  A backreference to a numbered subpattern uses the most recent value that is set
1167  the first one in the pattern with the given number.  for that number by any subpattern. The following pattern matches "abcabc" or
1168    "defdef":
1169    .sp
1170      /(?|(abc)|(def))\1/
1171    .sp
1172    In contrast, a recursive or "subroutine" call to a numbered subpattern always
1173    refers to the first one in the pattern with the given number. The following
1174    pattern matches "abcabc" or "defabc":
1175    .sp
1176      /(?|(abc)|(def))(?1)/
1177    .sp
1178    If a
1179    .\" HTML <a href="#conditions">
1180    .\" </a>
1181    condition test
1182    .\"
1183    for a subpattern's having matched refers to a non-unique number, the test is
1184    true if any of the subpatterns of that number have matched.
1185  .P  .P
1186  An alternative approach to using this "branch reset" feature is to use  An alternative approach to using this "branch reset" feature is to use
1187  duplicate named subpatterns, as described in the next section.  duplicate named subpatterns, as described in the next section.
# Line 1129  if an expression is modified, the number Line 1196  if an expression is modified, the number
1196  difficulty, PCRE supports the naming of subpatterns. This feature was not  difficulty, PCRE supports the naming of subpatterns. This feature was not
1197  added to Perl until release 5.10. Python had the feature earlier, and PCRE  added to Perl until release 5.10. Python had the feature earlier, and PCRE
1198  introduced it at release 4.0, using the Python syntax. PCRE now supports both  introduced it at release 4.0, using the Python syntax. PCRE now supports both
1199  the Perl and the Python syntax.  the Perl and the Python syntax. Perl allows identically numbered subpatterns to
1200    have different names, but PCRE does not.
1201  .P  .P
1202  In PCRE, a subpattern can be named in one of three ways: (?<name>...) or  In PCRE, a subpattern can be named in one of three ways: (?<name>...) or
1203  (?'name'...) as in Perl, or (?P<name>...) as in Python. References to capturing  (?'name'...) as in Perl, or (?P<name>...) as in Python. References to capturing
# Line 1156  extracting the name-to-number translatio Line 1224  extracting the name-to-number translatio
1224  is also a convenience function for extracting a captured substring by name.  is also a convenience function for extracting a captured substring by name.
1225  .P  .P
1226  By default, a name must be unique within a pattern, but it is possible to relax  By default, a name must be unique within a pattern, but it is possible to relax
1227  this constraint by setting the PCRE_DUPNAMES option at compile time. This can  this constraint by setting the PCRE_DUPNAMES option at compile time. (Duplicate
1228  be useful for patterns where only one instance of the named parentheses can  names are also always permitted for subpatterns with the same number, set up as
1229  match. Suppose you want to match the name of a weekday, either as a 3-letter  described in the previous section.) Duplicate names can be useful for patterns
1230  abbreviation or as the full name, and in both cases you want to extract the  where only one instance of the named parentheses can match. Suppose you want to
1231  abbreviation. This pattern (ignoring the line breaks) does the job:  match the name of a weekday, either as a 3-letter abbreviation or as the full
1232    name, and in both cases you want to extract the abbreviation. This pattern
1233    (ignoring the line breaks) does the job:
1234  .sp  .sp
1235    (?<DN>Mon|Fri|Sun)(?:day)?|    (?<DN>Mon|Fri|Sun)(?:day)?|
1236    (?<DN>Tue)(?:sday)?|    (?<DN>Tue)(?:sday)?|
# Line 1174  subpattern, as described in the previous Line 1244  subpattern, as described in the previous
1244  .P  .P
1245  The convenience function for extracting the data by name returns the substring  The convenience function for extracting the data by name returns the substring
1246  for the first (and in this example, the only) subpattern of that name that  for the first (and in this example, the only) subpattern of that name that
1247  matched. This saves searching to find which numbered subpattern it was. If you  matched. This saves searching to find which numbered subpattern it was.
1248  make a reference to a non-unique named subpattern from elsewhere in the  .P
1249  pattern, the one that corresponds to the lowest number is used. For further  If you make a backreference to a non-unique named subpattern from elsewhere in
1250  details of the interfaces for handling named subpatterns, see the  the pattern, the one that corresponds to the first occurrence of the name is
1251    used. In the absence of duplicate numbers (see the previous section) this is
1252    the one with the lowest number. If you use a named reference in a condition
1253    test (see the
1254    .\"
1255    .\" HTML <a href="#conditions">
1256    .\" </a>
1257    section about conditions
1258    .\"
1259    below), either to check whether a subpattern has matched, or to check for
1260    recursion, all subpatterns with the same name are tested. If the condition is
1261    true for any one of them, the overall condition is true. This is the same
1262    behaviour as testing by number. For further details of the interfaces for
1263    handling named subpatterns, see the
1264  .\" HREF  .\" HREF
1265  \fBpcreapi\fP  \fBpcreapi\fP
1266  .\"  .\"
1267  documentation.  documentation.
1268    .P
1269    \fBWarning:\fP You cannot use different names to distinguish between two
1270    subpatterns with the same number because PCRE uses only the numbers when
1271    matching. For this reason, an error is given at compile time if different names
1272    are given to subpatterns with the same number. However, you can give the same
1273    name to subpatterns with the same number, even when PCRE_DUPNAMES is not set.
1274  .  .
1275  .  .
1276  .SH REPETITION  .SH REPETITION
# Line 1199  items: Line 1288  items:
1288    a character class    a character class
1289    a back reference (see next section)    a back reference (see next section)
1290    a parenthesized subpattern (unless it is an assertion)    a parenthesized subpattern (unless it is an assertion)
1291      a recursive or "subroutine" call to a subpattern
1292  .sp  .sp
1293  The general repetition quantifier specifies a minimum and maximum number of  The general repetition quantifier specifies a minimum and maximum number of
1294  permitted matches, by giving the two numbers in curly brackets (braces),  permitted matches, by giving the two numbers in curly brackets (braces),
# Line 1230  support is available, \eX{3} matches thr Line 1320  support is available, \eX{3} matches thr
1320  which may be several bytes long (and they may be of different lengths).  which may be several bytes long (and they may be of different lengths).
1321  .P  .P
1322  The quantifier {0} is permitted, causing the expression to behave as if the  The quantifier {0} is permitted, causing the expression to behave as if the
1323  previous item and the quantifier were not present.  previous item and the quantifier were not present. This may be useful for
1324    subpatterns that are referenced as
1325    .\" HTML <a href="#subpatternsassubroutines">
1326    .\" </a>
1327    subroutines
1328    .\"
1329    from elsewhere in the pattern. Items other than subpatterns that have a {0}
1330    quantifier are omitted from the compiled pattern.
1331  .P  .P
1332  For convenience, the three most common quantifiers have single-character  For convenience, the three most common quantifiers have single-character
1333  abbreviations:  abbreviations:
# Line 1513  after the reference. Line 1610  after the reference.
1610  .P  .P
1611  There may be more than one back reference to the same subpattern. If a  There may be more than one back reference to the same subpattern. If a
1612  subpattern has not actually been used in a particular match, any back  subpattern has not actually been used in a particular match, any back
1613  references to it always fail. For example, the pattern  references to it always fail by default. For example, the pattern
1614  .sp  .sp
1615    (a|(bc))\e2    (a|(bc))\e2
1616  .sp  .sp
1617  always fails if it starts to match "a" rather than "bc". Because there may be  always fails if it starts to match "a" rather than "bc". However, if the
1618  many capturing parentheses in a pattern, all digits following the backslash are  PCRE_JAVASCRIPT_COMPAT option is set at compile time, a back reference to an
1619  taken as part of a potential back reference number. If the pattern continues  unset value matches an empty string.
1620  with a digit character, some delimiter must be used to terminate the back  .P
1621  reference. If the PCRE_EXTENDED option is set, this can be whitespace.  Because there may be many capturing parentheses in a pattern, all digits
1622  Otherwise an empty comment (see  following a backslash are taken as part of a potential back reference number.
1623    If the pattern continues with a digit character, some delimiter must be used to
1624    terminate the back reference. If the PCRE_EXTENDED option is set, this can be
1625    whitespace. Otherwise, the \eg{ syntax or an empty comment (see
1626  .\" HTML <a href="#comments">  .\" HTML <a href="#comments">
1627  .\" </a>  .\" </a>
1628  "Comments"  "Comments"
# Line 1595  lookbehind assertion is needed to achiev Line 1695  lookbehind assertion is needed to achiev
1695  If you want to force a matching failure at some point in a pattern, the most  If you want to force a matching failure at some point in a pattern, the most
1696  convenient way to do it is with (?!) because an empty string always matches, so  convenient way to do it is with (?!) because an empty string always matches, so
1697  an assertion that requires there not to be an empty string must always fail.  an assertion that requires there not to be an empty string must always fail.
1698    The Perl 5.10 backtracking control verb (*FAIL) or (*F) is essentially a
1699    synonym for (?!).
1700  .  .
1701  .  .
1702  .\" HTML <a name="lookbehind"></a>  .\" HTML <a name="lookbehind"></a>
# Line 1619  is permitted, but Line 1721  is permitted, but
1721  .sp  .sp
1722  causes an error at compile time. Branches that match different length strings  causes an error at compile time. Branches that match different length strings
1723  are permitted only at the top level of a lookbehind assertion. This is an  are permitted only at the top level of a lookbehind assertion. This is an
1724  extension compared with Perl (at least for 5.8), which requires all branches to  extension compared with Perl (5.8 and 5.10), which requires all branches to
1725  match the same length of string. An assertion such as  match the same length of string. An assertion such as
1726  .sp  .sp
1727    (?<=ab(c|de))    (?<=ab(c|de))
1728  .sp  .sp
1729  is not permitted, because its single top-level branch can match two different  is not permitted, because its single top-level branch can match two different
1730  lengths, but it is acceptable if rewritten to use two top-level branches:  lengths, but it is acceptable to PCRE if rewritten to use two top-level
1731    branches:
1732  .sp  .sp
1733    (?<=abc|abde)    (?<=abc|abde)
1734  .sp  .sp
# Line 1634  In some cases, the Perl 5.10 escape sequ Line 1737  In some cases, the Perl 5.10 escape sequ
1737  .\" </a>  .\" </a>
1738  (see above)  (see above)
1739  .\"  .\"
1740  can be used instead of a lookbehind assertion; this is not restricted to a  can be used instead of a lookbehind assertion to get round the fixed-length
1741  fixed-length.  restriction.
1742  .P  .P
1743  The implementation of lookbehind assertions is, for each alternative, to  The implementation of lookbehind assertions is, for each alternative, to
1744  temporarily move the current position back by the fixed length and then try to  temporarily move the current position back by the fixed length and then try to
# Line 1647  to appear in lookbehind assertions, beca Line 1750  to appear in lookbehind assertions, beca
1750  the length of the lookbehind. The \eX and \eR escapes, which can match  the length of the lookbehind. The \eX and \eR escapes, which can match
1751  different numbers of bytes, are also not permitted.  different numbers of bytes, are also not permitted.
1752  .P  .P
1753    .\" HTML <a href="#subpatternsassubroutines">
1754    .\" </a>
1755    "Subroutine"
1756    .\"
1757    calls (see below) such as (?2) or (?&X) are permitted in lookbehinds, as long
1758    as the subpattern matches a fixed-length string.
1759    .\" HTML <a href="#recursion">
1760    .\" </a>
1761    Recursion,
1762    .\"
1763    however, is not supported.
1764    .P
1765  Possessive quantifiers can be used in conjunction with lookbehind assertions to  Possessive quantifiers can be used in conjunction with lookbehind assertions to
1766  specify efficient matching at the end of the subject string. Consider a simple  specify efficient matching of fixed-length strings at the end of subject
1767  pattern such as  strings. Consider a simple pattern such as
1768  .sp  .sp
1769    abcd$    abcd$
1770  .sp  .sp
# Line 1713  characters that are not "999". Line 1828  characters that are not "999".
1828  .sp  .sp
1829  It is possible to cause the matching process to obey a subpattern  It is possible to cause the matching process to obey a subpattern
1830  conditionally or to choose between two alternative subpatterns, depending on  conditionally or to choose between two alternative subpatterns, depending on
1831  the result of an assertion, or whether a previous capturing subpattern matched  the result of an assertion, or whether a specific capturing subpattern has
1832  or not. The two possible forms of conditional subpattern are  already been matched. The two possible forms of conditional subpattern are:
1833  .sp  .sp
1834    (?(condition)yes-pattern)    (?(condition)yes-pattern)
1835    (?(condition)yes-pattern|no-pattern)    (?(condition)yes-pattern|no-pattern)
# Line 1730  recursion, a pseudo-condition called DEF Line 1845  recursion, a pseudo-condition called DEF
1845  .rs  .rs
1846  .sp  .sp
1847  If the text between the parentheses consists of a sequence of digits, the  If the text between the parentheses consists of a sequence of digits, the
1848  condition is true if the capturing subpattern of that number has previously  condition is true if a capturing subpattern of that number has previously
1849  matched. An alternative notation is to precede the digits with a plus or minus  matched. If there is more than one capturing subpattern with the same number
1850  sign. In this case, the subpattern number is relative rather than absolute.  (see the earlier
1851  The most recently opened parentheses can be referenced by (?(-1), the next most  .\"
1852  recent by (?(-2), and so on. In looping constructs it can also make sense to  .\" HTML <a href="#recursion">
1853  refer to subsequent groups with constructs such as (?(+2).  .\" </a>
1854    section about duplicate subpattern numbers),
1855    .\"
1856    the condition is true if any of them have been set. An alternative notation is
1857    to precede the digits with a plus or minus sign. In this case, the subpattern
1858    number is relative rather than absolute. The most recently opened parentheses
1859    can be referenced by (?(-1), the next most recent by (?(-2), and so on. In
1860    looping constructs it can also make sense to refer to subsequent groups with
1861    constructs such as (?(+2).
1862  .P  .P
1863  Consider the following pattern, which contains non-significant white space to  Consider the following pattern, which contains non-significant white space to
1864  make it more readable (assume the PCRE_EXTENDED option) and to divide it into  make it more readable (assume the PCRE_EXTENDED option) and to divide it into
# Line 1776  Rewriting the above example to use a nam Line 1899  Rewriting the above example to use a nam
1899  .sp  .sp
1900    (?<OPEN> \e( )?    [^()]+    (?(<OPEN>) \e) )    (?<OPEN> \e( )?    [^()]+    (?(<OPEN>) \e) )
1901  .sp  .sp
1902    If the name used in a condition of this kind is a duplicate, the test is
1903    applied to all subpatterns of the same name, and is true if any one of them has
1904    matched.
1905  .  .
1906  .SS "Checking for pattern recursion"  .SS "Checking for pattern recursion"
1907  .rs  .rs
# Line 1787  letter R, for example: Line 1913  letter R, for example:
1913  .sp  .sp
1914    (?(R3)...) or (?(R&name)...)    (?(R3)...) or (?(R&name)...)
1915  .sp  .sp
1916  the condition is true if the most recent recursion is into the subpattern whose  the condition is true if the most recent recursion is into a subpattern whose
1917  number or name is given. This condition does not check the entire recursion  number or name is given. This condition does not check the entire recursion
1918  stack.  stack. If the name used in a condition of this kind is a duplicate, the test is
1919    applied to all subpatterns of the same name, and is true if any one of them is
1920    the most recent recursion.
1921  .P  .P
1922  At "top level", all these recursion test conditions are false. Recursive  At "top level", all these recursion test conditions are false.
1923  patterns are described below.  .\" HTML <a href="#recursion">
1924    .\" </a>
1925    The syntax for recursive patterns
1926    .\"
1927    is described below.
1928  .  .
1929  .SS "Defining subpatterns for use by reference only"  .SS "Defining subpatterns for use by reference only"
1930  .rs  .rs
# Line 1801  If the condition is the string (DEFINE), Line 1933  If the condition is the string (DEFINE),
1933  name DEFINE, the condition is always false. In this case, there may be only one  name DEFINE, the condition is always false. In this case, there may be only one
1934  alternative in the subpattern. It is always skipped if control reaches this  alternative in the subpattern. It is always skipped if control reaches this
1935  point in the pattern; the idea of DEFINE is that it can be used to define  point in the pattern; the idea of DEFINE is that it can be used to define
1936  "subroutines" that can be referenced from elsewhere. (The use of "subroutines"  "subroutines" that can be referenced from elsewhere. (The use of
1937    .\" HTML <a href="#subpatternsassubroutines">
1938    .\" </a>
1939    "subroutines"
1940    .\"
1941  is described below.) For example, a pattern to match an IPv4 address could be  is described below.) For example, a pattern to match an IPv4 address could be
1942  written like this (ignore whitespace and line breaks):  written like this (ignore whitespace and line breaks):
1943  .sp  .sp
# Line 1811  written like this (ignore whitespace and Line 1947  written like this (ignore whitespace and
1947  The first part of the pattern is a DEFINE group inside which a another group  The first part of the pattern is a DEFINE group inside which a another group
1948  named "byte" is defined. This matches an individual component of an IPv4  named "byte" is defined. This matches an individual component of an IPv4
1949  address (a number less than 256). When matching takes place, this part of the  address (a number less than 256). When matching takes place, this part of the
1950  pattern is skipped because DEFINE acts like a false condition.  pattern is skipped because DEFINE acts like a false condition. The rest of the
1951  .P  pattern uses references to the named group to match the four dot-separated
1952  The rest of the pattern uses references to the named group to match the four  components of an IPv4 address, insisting on a word boundary at each end.
 dot-separated components of an IPv4 address, insisting on a word boundary at  
 each end.  
1953  .  .
1954  .SS "Assertion conditions"  .SS "Assertion conditions"
1955  .rs  .rs
# Line 1872  recursively to the pattern in which it a Line 2006  recursively to the pattern in which it a
2006  Obviously, PCRE cannot support the interpolation of Perl code. Instead, it  Obviously, PCRE cannot support the interpolation of Perl code. Instead, it
2007  supports special syntax for recursion of the entire pattern, and also for  supports special syntax for recursion of the entire pattern, and also for
2008  individual subpattern recursion. After its introduction in PCRE and Python,  individual subpattern recursion. After its introduction in PCRE and Python,
2009  this kind of recursion was introduced into Perl at release 5.10.  this kind of recursion was subsequently introduced into Perl at release 5.10.
2010  .P  .P
2011  A special item that consists of (? followed by a number greater than zero and a  A special item that consists of (? followed by a number greater than zero and a
2012  closing parenthesis is a recursive call of the subpattern of the given number,  closing parenthesis is a recursive call of the subpattern of the given number,
2013  provided that it occurs inside that subpattern. (If not, it is a "subroutine"  provided that it occurs inside that subpattern. (If not, it is a
2014    .\" HTML <a href="#subpatternsassubroutines">
2015    .\" </a>
2016    "subroutine"
2017    .\"
2018  call, which is described in the next section.) The special item (?R) or (?0) is  call, which is described in the next section.) The special item (?R) or (?0) is
2019  a recursive call of the entire regular expression.  a recursive call of the entire regular expression.
2020  .P  .P
 In PCRE (like Python, but unlike Perl), a recursive subpattern call is always  
 treated as an atomic group. That is, once it has matched some of the subject  
 string, it is never re-entered, even if it contains untried alternatives and  
 there is a subsequent matching failure.  
 .P  
2021  This PCRE pattern solves the nested parentheses problem (assume the  This PCRE pattern solves the nested parentheses problem (assume the
2022  PCRE_EXTENDED option is set so that white space is ignored):  PCRE_EXTENDED option is set so that white space is ignored):
2023  .sp  .sp
2024    \e( ( (?>[^()]+) | (?R) )* \e)    \e( ( [^()]++ | (?R) )* \e)
2025  .sp  .sp
2026  First it matches an opening parenthesis. Then it matches any number of  First it matches an opening parenthesis. Then it matches any number of
2027  substrings which can either be a sequence of non-parentheses, or a recursive  substrings which can either be a sequence of non-parentheses, or a recursive
2028  match of the pattern itself (that is, a correctly parenthesized substring).  match of the pattern itself (that is, a correctly parenthesized substring).
2029  Finally there is a closing parenthesis.  Finally there is a closing parenthesis. Note the use of a possessive quantifier
2030    to avoid backtracking into sequences of non-parentheses.
2031  .P  .P
2032  If this were part of a larger pattern, you would not want to recurse the entire  If this were part of a larger pattern, you would not want to recurse the entire
2033  pattern, so instead you could use this:  pattern, so instead you could use this:
2034  .sp  .sp
2035    ( \e( ( (?>[^()]+) | (?1) )* \e) )    ( \e( ( [^()]++ | (?1) )* \e) )
2036  .sp  .sp
2037  We have put the pattern into parentheses, and caused the recursion to refer to  We have put the pattern into parentheses, and caused the recursion to refer to
2038  them instead of the whole pattern.  them instead of the whole pattern.
2039  .P  .P
2040  In a larger pattern, keeping track of parenthesis numbers can be tricky. This  In a larger pattern, keeping track of parenthesis numbers can be tricky. This
2041  is made easier by the use of relative references. (A Perl 5.10 feature.)  is made easier by the use of relative references (a Perl 5.10 feature).
2042  Instead of (?1) in the pattern above you can write (?-2) to refer to the second  Instead of (?1) in the pattern above you can write (?-2) to refer to the second
2043  most recently opened parentheses preceding the recursion. In other words, a  most recently opened parentheses preceding the recursion. In other words, a
2044  negative number counts capturing parentheses leftwards from the point at which  negative number counts capturing parentheses leftwards from the point at which
# Line 1913  it is encountered. Line 2047  it is encountered.
2047  It is also possible to refer to subsequently opened parentheses, by writing  It is also possible to refer to subsequently opened parentheses, by writing
2048  references such as (?+2). However, these cannot be recursive because the  references such as (?+2). However, these cannot be recursive because the
2049  reference is not inside the parentheses that are referenced. They are always  reference is not inside the parentheses that are referenced. They are always
2050  "subroutine" calls, as described in the next section.  .\" HTML <a href="#subpatternsassubroutines">
2051    .\" </a>
2052    "subroutine"
2053    .\"
2054    calls, as described in the next section.
2055  .P  .P
2056  An alternative approach is to use named parentheses instead. The Perl syntax  An alternative approach is to use named parentheses instead. The Perl syntax
2057  for this is (?&name); PCRE's earlier syntax (?P>name) is also supported. We  for this is (?&name); PCRE's earlier syntax (?P>name) is also supported. We
2058  could rewrite the above example as follows:  could rewrite the above example as follows:
2059  .sp  .sp
2060    (?<pn> \e( ( (?>[^()]+) | (?&pn) )* \e) )    (?<pn> \e( ( [^()]++ | (?&pn) )* \e) )
2061  .sp  .sp
2062  If there is more than one subpattern with the same name, the earliest one is  If there is more than one subpattern with the same name, the earliest one is
2063  used.  used.
2064  .P  .P
2065  This particular example pattern that we have been looking at contains nested  This particular example pattern that we have been looking at contains nested
2066  unlimited repeats, and so the use of atomic grouping for matching strings of  unlimited repeats, and so the use of a possessive quantifier for matching
2067  non-parentheses is important when applying the pattern to strings that do not  strings of non-parentheses is important when applying the pattern to strings
2068  match. For example, when this pattern is applied to  that do not match. For example, when this pattern is applied to
2069  .sp  .sp
2070    (aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa()    (aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa()
2071  .sp  .sp
2072  it yields "no match" quickly. However, if atomic grouping is not used,  it yields "no match" quickly. However, if a possessive quantifier is not used,
2073  the match runs for a very long time indeed because there are so many different  the match runs for a very long time indeed because there are so many different
2074  ways the + and * repeats can carve up the subject, and all have to be tested  ways the + and * repeats can carve up the subject, and all have to be tested
2075  before failure can be reported.  before failure can be reported.
# Line 1950  documentation). If the pattern above is Line 2088  documentation). If the pattern above is
2088  the value for the capturing parentheses is "ef", which is the last value taken  the value for the capturing parentheses is "ef", which is the last value taken
2089  on at the top level. If additional parentheses are added, giving  on at the top level. If additional parentheses are added, giving
2090  .sp  .sp
2091    \e( ( ( (?>[^()]+) | (?R) )* ) \e)    \e( ( ( [^()]++ | (?R) )* ) \e)
2092       ^                        ^       ^                        ^
2093       ^                        ^       ^                        ^
2094  .sp  .sp
# Line 1972  different alternatives for the recursive Line 2110  different alternatives for the recursive
2110  is the actual recursive call.  is the actual recursive call.
2111  .  .
2112  .  .
2113    .\" HTML <a name="recursiondifference"></a>
2114    .SS "Recursion difference from Perl"
2115    .rs
2116    .sp
2117    In PCRE (like Python, but unlike Perl), a recursive subpattern call is always
2118    treated as an atomic group. That is, once it has matched some of the subject
2119    string, it is never re-entered, even if it contains untried alternatives and
2120    there is a subsequent matching failure. This can be illustrated by the
2121    following pattern, which purports to match a palindromic string that contains
2122    an odd number of characters (for example, "a", "aba", "abcba", "abcdcba"):
2123    .sp
2124      ^(.|(.)(?1)\e2)$
2125    .sp
2126    The idea is that it either matches a single character, or two identical
2127    characters surrounding a sub-palindrome. In Perl, this pattern works; in PCRE
2128    it does not if the pattern is longer than three characters. Consider the
2129    subject string "abcba":
2130    .P
2131    At the top level, the first character is matched, but as it is not at the end
2132    of the string, the first alternative fails; the second alternative is taken
2133    and the recursion kicks in. The recursive call to subpattern 1 successfully
2134    matches the next character ("b"). (Note that the beginning and end of line
2135    tests are not part of the recursion).
2136    .P
2137    Back at the top level, the next character ("c") is compared with what
2138    subpattern 2 matched, which was "a". This fails. Because the recursion is
2139    treated as an atomic group, there are now no backtracking points, and so the
2140    entire match fails. (Perl is able, at this point, to re-enter the recursion and
2141    try the second alternative.) However, if the pattern is written with the
2142    alternatives in the other order, things are different:
2143    .sp
2144      ^((.)(?1)\e2|.)$
2145    .sp
2146    This time, the recursing alternative is tried first, and continues to recurse
2147    until it runs out of characters, at which point the recursion fails. But this
2148    time we do have another alternative to try at the higher level. That is the big
2149    difference: in the previous case the remaining alternative is at a deeper
2150    recursion level, which PCRE cannot use.
2151    .P
2152    To change the pattern so that matches all palindromic strings, not just those
2153    with an odd number of characters, it is tempting to change the pattern to this:
2154    .sp
2155      ^((.)(?1)\e2|.?)$
2156    .sp
2157    Again, this works in Perl, but not in PCRE, and for the same reason. When a
2158    deeper recursion has matched a single character, it cannot be entered again in
2159    order to match an empty string. The solution is to separate the two cases, and
2160    write out the odd and even cases as alternatives at the higher level:
2161    .sp
2162      ^(?:((.)(?1)\e2|)|((.)(?3)\e4|.))
2163    .sp
2164    If you want to match typical palindromic phrases, the pattern has to ignore all
2165    non-word characters, which can be done like this:
2166    .sp
2167      ^\eW*+(?:((.)\eW*+(?1)\eW*+\e2|)|((.)\eW*+(?3)\eW*+\4|\eW*+.\eW*+))\eW*+$
2168    .sp
2169    If run with the PCRE_CASELESS option, this pattern matches phrases such as "A
2170    man, a plan, a canal: Panama!" and it works well in both PCRE and Perl. Note
2171    the use of the possessive quantifier *+ to avoid backtracking into sequences of
2172    non-word characters. Without this, PCRE takes a great deal longer (ten times or
2173    more) to match typical phrases, and Perl takes so long that you think it has
2174    gone into a loop.
2175    .P
2176    \fBWARNING\fP: The palindrome-matching patterns above work only if the subject
2177    string does not start with a palindrome that is shorter than the entire string.
2178    For example, although "abcba" is correctly matched, if the subject is "ababa",
2179    PCRE finds the palindrome "aba" at the start, then fails at top level because
2180    the end of the string does not follow. Once again, it cannot jump back into the
2181    recursion to try other alternatives, so the entire match fails.
2182    .
2183    .
2184  .\" HTML <a name="subpatternsassubroutines"></a>  .\" HTML <a name="subpatternsassubroutines"></a>
2185  .SH "SUBPATTERNS AS SUBROUTINES"  .SH "SUBPATTERNS AS SUBROUTINES"
2186  .rs  .rs
# Line 2013  It matches "abcabc". It does not match " Line 2222  It matches "abcabc". It does not match "
2222  processing option does not affect the called subpattern.  processing option does not affect the called subpattern.
2223  .  .
2224  .  .
2225    .\" HTML <a name="onigurumasubroutines"></a>
2226    .SH "ONIGURUMA SUBROUTINE SYNTAX"
2227    .rs
2228    .sp
2229    For compatibility with Oniguruma, the non-Perl syntax \eg followed by a name or
2230    a number enclosed either in angle brackets or single quotes, is an alternative
2231    syntax for referencing a subpattern as a subroutine, possibly recursively. Here
2232    are two of the examples used above, rewritten using this syntax:
2233    .sp
2234      (?<pn> \e( ( (?>[^()]+) | \eg<pn> )* \e) )
2235      (sens|respons)e and \eg'1'ibility
2236    .sp
2237    PCRE supports an extension to Oniguruma: if a number is preceded by a
2238    plus or a minus sign it is taken as a relative reference. For example:
2239    .sp
2240      (abc)(?i:\eg<-1>)
2241    .sp
2242    Note that \eg{...} (Perl syntax) and \eg<...> (Oniguruma syntax) are \fInot\fP
2243    synonymous. The former is a back reference; the latter is a subroutine call.
2244    .
2245    .
2246  .SH CALLOUTS  .SH CALLOUTS
2247  .rs  .rs
2248  .sp  .sp
# Line 2058  or removal in a future version of Perl". Line 2288  or removal in a future version of Perl".
2288  production code should be noted to avoid problems during upgrades." The same  production code should be noted to avoid problems during upgrades." The same
2289  remarks apply to the PCRE features described in this section.  remarks apply to the PCRE features described in this section.
2290  .P  .P
2291  Since these verbs are specifically related to backtracking, they can be used  Since these verbs are specifically related to backtracking, most of them can be
2292  only when the pattern is to be matched using \fBpcre_exec()\fP, which uses a  used only when the pattern is to be matched using \fBpcre_exec()\fP, which uses
2293  backtracking algorithm. They cause an error if encountered by  a backtracking algorithm. With the exception of (*FAIL), which behaves like a
2294    failing negative assertion, they cause an error if encountered by
2295  \fBpcre_dfa_exec()\fP.  \fBpcre_dfa_exec()\fP.
2296  .P  .P
2297    If any of these verbs are used in an assertion subpattern, their effect is
2298    confined to that subpattern; it does not extend to the surrounding pattern.
2299    Note that assertion subpatterns are processed as anchored at the point where
2300    they are tested.
2301    .P
2302  The new verbs make use of what was previously invalid syntax: an opening  The new verbs make use of what was previously invalid syntax: an opening
2303  parenthesis followed by an asterisk. In Perl, they are generally of the form  parenthesis followed by an asterisk. In Perl, they are generally of the form
2304  (*VERB:ARG) but PCRE does not support the use of arguments, so its general  (*VERB:ARG) but PCRE does not support the use of arguments, so its general
# Line 2078  The following verbs act as soon as they Line 2314  The following verbs act as soon as they
2314  .sp  .sp
2315  This verb causes the match to end successfully, skipping the remainder of the  This verb causes the match to end successfully, skipping the remainder of the
2316  pattern. When inside a recursion, only the innermost pattern is ended  pattern. When inside a recursion, only the innermost pattern is ended
2317  immediately. PCRE differs from Perl in what happens if the (*ACCEPT) is inside  immediately. If (*ACCEPT) is inside capturing parentheses, the data so far is
2318  capturing parentheses. In Perl, the data so far is captured: in PCRE no data is  captured. (This feature was added to PCRE at release 8.00.) For example:
 captured. For example:  
2319  .sp  .sp
2320    A(A|B(*ACCEPT)|C)D    A((?:A|B(*ACCEPT)|C)D)
2321  .sp  .sp
2322  This matches "AB", "AAD", or "ACD", but when it matches "AB", no data is  This matches "AB", "AAD", or "ACD"; when it matches "AB", "B" is captured by
2323  captured.  the outer parentheses.
2324  .sp  .sp
2325    (*FAIL) or (*F)    (*FAIL) or (*F)
2326  .sp  .sp
# Line 2111  The verbs differ in exactly what kind of Line 2346  The verbs differ in exactly what kind of
2346  .sp  .sp
2347  This verb causes the whole match to fail outright if the rest of the pattern  This verb causes the whole match to fail outright if the rest of the pattern
2348  does not match. Even if the pattern is unanchored, no further attempts to find  does not match. Even if the pattern is unanchored, no further attempts to find
2349  a match by advancing the start point take place. Once (*COMMIT) has been  a match by advancing the starting point take place. Once (*COMMIT) has been
2350  passed, \fBpcre_exec()\fP is committed to finding a match at the current  passed, \fBpcre_exec()\fP is committed to finding a match at the current
2351  starting point, or not at all. For example:  starting point, or not at all. For example:
2352  .sp  .sp
# Line 2143  was matched leading up to it cannot be p Line 2378  was matched leading up to it cannot be p
2378  If the subject is "aaaac...", after the first match attempt fails (starting at  If the subject is "aaaac...", after the first match attempt fails (starting at
2379  the first character in the string), the starting point skips on to start the  the first character in the string), the starting point skips on to start the
2380  next attempt at "c". Note that a possessive quantifer does not have the same  next attempt at "c". Note that a possessive quantifer does not have the same
2381  effect in this example; although it would suppress backtracking during the  effect as this example; although it would suppress backtracking during the
2382  first match attempt, the second attempt would start at the second character  first match attempt, the second attempt would start at the second character
2383  instead of skipping on to "c".  instead of skipping on to "c".
2384  .sp  .sp
# Line 2165  is used outside of any alternation, it a Line 2400  is used outside of any alternation, it a
2400  .SH "SEE ALSO"  .SH "SEE ALSO"
2401  .rs  .rs
2402  .sp  .sp
2403  \fBpcreapi\fP(3), \fBpcrecallout\fP(3), \fBpcrematching\fP(3), \fBpcre\fP(3).  \fBpcreapi\fP(3), \fBpcrecallout\fP(3), \fBpcrematching\fP(3),
2404    \fBpcresyntax\fP(3), \fBpcre\fP(3).
2405  .  .
2406  .  .
2407  .SH AUTHOR  .SH AUTHOR
# Line 2182  Cambridge CB2 3QH, England. Line 2418  Cambridge CB2 3QH, England.
2418  .rs  .rs
2419  .sp  .sp
2420  .nf  .nf
2421  Last updated: 14 September 2007  Last updated: 04 October 2009
2422  Copyright (c) 1997-2007 University of Cambridge.  Copyright (c) 1997-2009 University of Cambridge.
2423  .fi  .fi

Legend:
Removed from v.247  
changed lines
  Added in v.459

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12