/[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 171 by ph10, Mon Jun 4 14:28:58 2007 UTC revision 210 by ph10, Wed Aug 8 14:24:50 2007 UTC
# Line 4  PCRE - Perl-compatible regular expressio Line 4  PCRE - Perl-compatible regular expressio
4  .SH "PCRE REGULAR EXPRESSION DETAILS"  .SH "PCRE REGULAR EXPRESSION DETAILS"
5  .rs  .rs
6  .sp  .sp
7  The syntax and semantics of the regular expressions supported by PCRE are  The syntax and semantics of the regular expressions that are supported by PCRE
8  described below. Regular expressions are also described in the Perl  are described in detail below. There is a quick-reference syntax summary in the
9  documentation and in a number of books, some of which have copious examples.  .\" HREF
10  Jeffrey Friedl's "Mastering Regular Expressions", published by O'Reilly, covers  \fBpcresyntax\fP
11  regular expressions in great detail. This description of PCRE's regular  .\"
12  expressions is intended as reference material.  page. Perl's regular expressions are described in its own documentation, and
13    regular expressions in general are covered in a number of books, some of which
14    have copious examples. Jeffrey Friedl's "Mastering Regular Expressions",
15    published by O'Reilly, covers regular expressions in great detail. This
16    description of PCRE's regular expressions is intended as reference material.
17  .P  .P
18  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,
19  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, you must
# Line 30  The remainder of this document discusses Line 34  The remainder of this document discusses
34  PCRE when its main matching function, \fBpcre_exec()\fP, is used.  PCRE when its main matching function, \fBpcre_exec()\fP, is used.
35  From release 6.0, PCRE offers a second matching function,  From release 6.0, PCRE offers a second matching function,
36  \fBpcre_dfa_exec()\fP, which matches using a different algorithm that is not  \fBpcre_dfa_exec()\fP, which matches using a different algorithm that is not
37  Perl-compatible. Some of the features discussed below are not available when  Perl-compatible. Some of the features discussed below are not available when
38  \fBpcre_dfa_exec()\fP is used. The advantages and disadvantages of the  \fBpcre_dfa_exec()\fP is used. The advantages and disadvantages of the
39  alternative function, and how it differs from the normal function, are  alternative function, and how it differs from the normal function, are
40  discussed in the  discussed in the
# Line 240  meanings Line 244  meanings
244  .SS "Absolute and relative back references"  .SS "Absolute and relative back references"
245  .rs  .rs
246  .sp  .sp
247  The sequence \eg followed by a positive or negative number, optionally enclosed  The sequence \eg followed by an unsigned or a negative number, optionally
248  in braces, is an absolute or relative back reference. A named back reference  enclosed in braces, is an absolute or relative back reference. A named back
249  can be coded as \eg{name}. Back references are discussed  reference can be coded as \eg{name}. Back references are discussed
250  .\" HTML <a href="#backreferences">  .\" HTML <a href="#backreferences">
251  .\" </a>  .\" </a>
252  later,  later,
# Line 262  following are always recognized: Line 266  following are always recognized:
266  .sp  .sp
267    \ed     any decimal digit    \ed     any decimal digit
268    \eD     any character that is not a decimal digit    \eD     any character that is not a decimal digit
269      \eh     any horizontal whitespace character
270      \eH     any character that is not a horizontal whitespace character
271    \es     any whitespace character    \es     any whitespace character
272    \eS     any character that is not a whitespace character    \eS     any character that is not a whitespace character
273      \ev     any vertical whitespace character
274      \eV     any character that is not a vertical whitespace character
275    \ew     any "word" character    \ew     any "word" character
276    \eW     any "non-word" character    \eW     any "non-word" character
277  .sp  .sp
# Line 277  there is no character to match. Line 285  there is no character to match.
285  .P  .P
286  For compatibility with Perl, \es does not match the VT character (code 11).  For compatibility with Perl, \es does not match the VT character (code 11).
287  This makes it different from the the POSIX "space" class. The \es characters  This makes it different from the the POSIX "space" class. The \es characters
288  are HT (9), LF (10), FF (12), CR (13), and space (32). (If "use locale;" is  are HT (9), LF (10), FF (12), CR (13), and space (32). If "use locale;" is
289  included in a Perl script, \es may match the VT character. In PCRE, it never  included in a Perl script, \es may match the VT character. In PCRE, it never
290  does.)  does.
291    .P
292    In UTF-8 mode, characters with values greater than 128 never match \ed, \es, or
293    \ew, and always match \eD, \eS, and \eW. This is true even when Unicode
294    character property support is available. These sequences retain their original
295    meanings from before UTF-8 support was available, mainly for efficiency
296    reasons.
297    .P
298    The sequences \eh, \eH, \ev, and \eV are Perl 5.10 features. In contrast to the
299    other sequences, these do match certain high-valued codepoints in UTF-8 mode.
300    The horizontal space characters are:
301    .sp
302      U+0009     Horizontal tab
303      U+0020     Space
304      U+00A0     Non-break space
305      U+1680     Ogham space mark
306      U+180E     Mongolian vowel separator
307      U+2000     En quad
308      U+2001     Em quad
309      U+2002     En space
310      U+2003     Em space
311      U+2004     Three-per-em space
312      U+2005     Four-per-em space
313      U+2006     Six-per-em space
314      U+2007     Figure space
315      U+2008     Punctuation space
316      U+2009     Thin space
317      U+200A     Hair space
318      U+202F     Narrow no-break space
319      U+205F     Medium mathematical space
320      U+3000     Ideographic space
321    .sp
322    The vertical space characters are:
323    .sp
324      U+000A     Linefeed
325      U+000B     Vertical tab
326      U+000C     Formfeed
327      U+000D     Carriage return
328      U+0085     Next line
329      U+2028     Line separator
330      U+2029     Paragraph separator
331  .P  .P
332  A "word" character is an underscore or any character less than 256 that is a  A "word" character is an underscore or any character less than 256 that is a
333  letter or digit. The definition of letters and digits is controlled by PCRE's  letter or digit. The definition of letters and digits is controlled by PCRE's
# Line 295  in the Line 343  in the
343  .\"  .\"
344  page). For example, in a French locale such as "fr_FR" in Unix-like systems,  page). For example, in a French locale such as "fr_FR" in Unix-like systems,
345  or "french" in Windows, some character codes greater than 128 are used for  or "french" in Windows, some character codes greater than 128 are used for
346  accented letters, and these are matched by \ew.  accented letters, and these are matched by \ew. The use of locales with Unicode
347  .P  is discouraged.
 In UTF-8 mode, characters with values greater than 128 never match \ed, \es, or  
 \ew, and always match \eD, \eS, and \eW. This is true even when Unicode  
 character property support is available. The use of locales with Unicode is  
 discouraged.  
348  .  .
349  .  .
350  .SS "Newline sequences"  .SS "Newline sequences"
351  .rs  .rs
352  .sp  .sp
353  Outside a character class, the escape sequence \eR matches any Unicode newline  Outside a character class, the escape sequence \eR matches any Unicode newline
354  sequence. This is an extension to Perl. In non-UTF-8 mode \eR is equivalent to  sequence. This is a Perl 5.10 feature. In non-UTF-8 mode \eR is equivalent to
355  the following:  the following:
356  .sp  .sp
357    (?>\er\en|\en|\ex0b|\ef|\er|\ex85)    (?>\er\en|\en|\ex0b|\ef|\er|\ex85)
# Line 336  Inside a character class, \eR matches th Line 380  Inside a character class, \eR matches th
380  .rs  .rs
381  .sp  .sp
382  When PCRE is built with Unicode character property support, three additional  When PCRE is built with Unicode character property support, three additional
383  escape sequences to match character properties are available when UTF-8 mode  escape sequences that match characters with specific properties are available.
384  is selected. They are:  When not in UTF-8 mode, these sequences are of course limited to testing
385    characters whose codepoints are less than 256, but they do work in this mode.
386    The extra escape sequences are:
387  .sp  .sp
388    \ep{\fIxx\fP}   a character with the \fIxx\fP property    \ep{\fIxx\fP}   a character with the \fIxx\fP property
389    \eP{\fIxx\fP}   a character without the \fIxx\fP property    \eP{\fIxx\fP}   a character without the \fIxx\fP property
# Line 513  atomic group Line 559  atomic group
559  (see below).  (see below).
560  .\"  .\"
561  Characters with the "mark" property are typically accents that affect the  Characters with the "mark" property are typically accents that affect the
562  preceding character.  preceding character. None of them have codepoints less than 256, so in
563    non-UTF-8 mode \eX matches any one character.
564  .P  .P
565  Matching characters by Unicode property is not fast, because PCRE has to search  Matching characters by Unicode property is not fast, because PCRE has to search
566  a structure that contains data for over fifteen thousand characters. That is  a structure that contains data for over fifteen thousand characters. That is
# Line 525  properties in PCRE. Line 572  properties in PCRE.
572  .SS "Resetting the match start"  .SS "Resetting the match start"
573  .rs  .rs
574  .sp  .sp
575  The escape sequence \eK, which is a Perl 5.10 feature, causes any previously  The escape sequence \eK, which is a Perl 5.10 feature, causes any previously
576  matched characters not to be included in the final matched sequence. For  matched characters not to be included in the final matched sequence. For
577  example, the pattern:  example, the pattern:
578  .sp  .sp
579    foo\eKbar    foo\eKbar
580  .sp  .sp
581  matches "foobar", but reports that it has matched "bar". This feature is  matches "foobar", but reports that it has matched "bar". This feature is
582  similar to a lookbehind assertion  similar to a lookbehind assertion
583  .\" HTML <a href="#lookbehind">  .\" HTML <a href="#lookbehind">
584  .\" </a>  .\" </a>
585  (described below).  (described below).
586  .\"  .\"
587  However, in this case, the part of the subject before the real match does not  However, in this case, the part of the subject before the real match does not
588  have to be of fixed length, as lookbehind assertions do. The use of \eK does  have to be of fixed length, as lookbehind assertions do. The use of \eK does
589  not interfere with the setting of  not interfere with the setting of
590  .\" HTML <a href="#subpattern">  .\" HTML <a href="#subpattern">
591  .\" </a>  .\" </a>
592  captured substrings.  captured substrings.
593  .\"  .\"
594  For example, when the pattern  For example, when the pattern
595  .sp  .sp
596    (foo)\eKbar    (foo)\eKbar
597  .sp  .sp
598  matches "foobar", the first substring is still set to "foo".  matches "foobar", the first substring is still set to "foo".
599  .  .
600  .  .
601  .\" HTML <a name="smallassertions"></a>  .\" HTML <a name="smallassertions"></a>
# Line 958  is reached, an option setting in one bra Line 1005  is reached, an option setting in one bra
1005  the above patterns match "SUNDAY" as well as "Saturday".  the above patterns match "SUNDAY" as well as "Saturday".
1006  .  .
1007  .  .
1008    .SH "DUPLICATE SUBPATTERN NUMBERS"
1009    .rs
1010    .sp
1011    Perl 5.10 introduced a feature whereby each alternative in a subpattern uses
1012    the same numbers for its capturing parentheses. Such a subpattern starts with
1013    (?| and is itself a non-capturing subpattern. For example, consider this
1014    pattern:
1015    .sp
1016      (?|(Sat)ur|(Sun))day
1017    .sp
1018    Because the two alternatives are inside a (?| group, both sets of capturing
1019    parentheses are numbered one. Thus, when the pattern matches, you can look
1020    at captured substring number one, whichever alternative matched. This construct
1021    is useful when you want to capture part, but not all, of one of a number of
1022    alternatives. Inside a (?| group, parentheses are numbered as usual, but the
1023    number is reset at the start of each branch. The numbers of any capturing
1024    buffers that follow the subpattern start after the highest number used in any
1025    branch. The following example is taken from the Perl documentation.
1026    The numbers underneath show in which buffer the captured content will be
1027    stored.
1028    .sp
1029      # before  ---------------branch-reset----------- after
1030      / ( a )  (?| x ( y ) z | (p (q) r) | (t) u (v) ) ( z ) /x
1031      # 1            2         2  3        2     3     4
1032    .sp
1033    A backreference or a recursive call to a numbered subpattern always refers to
1034    the first one in the pattern with the given number.
1035    .P
1036    An alternative approach to using this "branch reset" feature is to use
1037    duplicate named subpatterns, as described in the next section.
1038    .
1039    .
1040  .SH "NAMED SUBPATTERNS"  .SH "NAMED SUBPATTERNS"
1041  .rs  .rs
1042  .sp  .sp
# Line 1007  abbreviation. This pattern (ignoring the Line 1086  abbreviation. This pattern (ignoring the
1086    (?<DN>Sat)(?:urday)?    (?<DN>Sat)(?:urday)?
1087  .sp  .sp
1088  There are five capturing substrings, but only one is ever set after a match.  There are five capturing substrings, but only one is ever set after a match.
1089    (An alternative way of solving this problem is to use a "branch reset"
1090    subpattern, as described in the previous section.)
1091    .P
1092  The convenience function for extracting the data by name returns the substring  The convenience function for extracting the data by name returns the substring
1093  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
1094  matched. This saves searching to find which numbered subpattern it was. If you  matched. This saves searching to find which numbered subpattern it was. If you
# Line 1212  previous example can be rewritten as Line 1294  previous example can be rewritten as
1294  .sp  .sp
1295    \ed++foo    \ed++foo
1296  .sp  .sp
1297    Note that a possessive quantifier can be used with an entire group, for
1298    example:
1299    .sp
1300      (abc|xyz){2,3}+
1301    .sp
1302  Possessive quantifiers are always greedy; the setting of the PCRE_UNGREEDY  Possessive quantifiers are always greedy; the setting of the PCRE_UNGREEDY
1303  option is ignored. They are a convenient notation for the simpler forms of  option is ignored. They are a convenient notation for the simpler forms of
1304  atomic group. However, there is no difference in the meaning of a possessive  atomic group. However, there is no difference in the meaning of a possessive
# Line 1286  subpattern is possible using named paren Line 1373  subpattern is possible using named paren
1373  .P  .P
1374  Another way of avoiding the ambiguity inherent in the use of digits following a  Another way of avoiding the ambiguity inherent in the use of digits following a
1375  backslash is to use the \eg escape sequence, which is a feature introduced in  backslash is to use the \eg escape sequence, which is a feature introduced in
1376  Perl 5.10. This escape must be followed by a positive or a negative number,  Perl 5.10. This escape must be followed by an unsigned number or a negative
1377  optionally enclosed in braces. These examples are all identical:  number, optionally enclosed in braces. These examples are all identical:
1378  .sp  .sp
1379    (ring), \e1    (ring), \e1
1380    (ring), \eg1    (ring), \eg1
1381    (ring), \eg{1}    (ring), \eg{1}
1382  .sp  .sp
1383  A positive number specifies an absolute reference without the ambiguity that is  An unsigned number specifies an absolute reference without the ambiguity that
1384  present in the older syntax. It is also useful when literal digits follow the  is present in the older syntax. It is also useful when literal digits follow
1385  reference. A negative number is a relative reference. Consider this example:  the reference. A negative number is a relative reference. Consider this
1386    example:
1387  .sp  .sp
1388    (abc(def)ghi)\eg{-1}    (abc(def)ghi)\eg{-1}
1389  .sp  .sp
# Line 1458  lengths, but it is acceptable if rewritt Line 1546  lengths, but it is acceptable if rewritt
1546  .sp  .sp
1547    (?<=abc|abde)    (?<=abc|abde)
1548  .sp  .sp
1549  In some cases, the Perl 5.10 escape sequence \eK  In some cases, the Perl 5.10 escape sequence \eK
1550  .\" HTML <a href="#resetmatchstart">  .\" HTML <a href="#resetmatchstart">
1551  .\" </a>  .\" </a>
1552  (see above)  (see above)
# Line 1560  recursion, a pseudo-condition called DEF Line 1648  recursion, a pseudo-condition called DEF
1648  .sp  .sp
1649  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
1650  condition is true if the capturing subpattern of that number has previously  condition is true if the capturing subpattern of that number has previously
1651  matched. An alternative notation is to precede the digits with a plus or minus  matched. An alternative notation is to precede the digits with a plus or minus
1652  sign. In this case, the subpattern number is relative rather than absolute.  sign. In this case, the subpattern number is relative rather than absolute.
1653  The most recently opened parentheses can be referenced by (?(-1), the next most  The most recently opened parentheses can be referenced by (?(-1), the next most
1654  recent by (?(-2), and so on. In looping constructs it can also make sense to  recent by (?(-2), and so on. In looping constructs it can also make sense to
1655  refer to subsequent groups with constructs such as (?(+2).  refer to subsequent groups with constructs such as (?(+2).
1656  .P  .P
# Line 1582  parenthesis is required. Otherwise, sinc Line 1670  parenthesis is required. Otherwise, sinc
1670  subpattern matches nothing. In other words, this pattern matches a sequence of  subpattern matches nothing. In other words, this pattern matches a sequence of
1671  non-parentheses, optionally enclosed in parentheses.  non-parentheses, optionally enclosed in parentheses.
1672  .P  .P
1673  If you were embedding this pattern in a larger one, you could use a relative  If you were embedding this pattern in a larger one, you could use a relative
1674  reference:  reference:
1675  .sp  .sp
1676    ...other stuff... ( \e( )?    [^()]+    (?(-1) \e) ) ...    ...other stuff... ( \e( )?    [^()]+    (?(-1) \e) ) ...
# Line 1730  pattern, so instead you could use this: Line 1818  pattern, so instead you could use this:
1818    ( \e( ( (?>[^()]+) | (?1) )* \e) )    ( \e( ( (?>[^()]+) | (?1) )* \e) )
1819  .sp  .sp
1820  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
1821  them instead of the whole pattern.  them instead of the whole pattern.
1822  .P  .P
1823  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
1824  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.)
# Line 1751  could rewrite the above example as follo Line 1839  could rewrite the above example as follo
1839    (?<pn> \e( ( (?>[^()]+) | (?&pn) )* \e) )    (?<pn> \e( ( (?>[^()]+) | (?&pn) )* \e) )
1840  .sp  .sp
1841  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
1842  used.  used.
1843  .P  .P
1844  This particular example pattern that we have been looking at contains nested  This particular example pattern that we have been looking at contains nested
1845  unlimited repeats, and so the use of atomic grouping for matching strings of  unlimited repeats, and so the use of atomic grouping for matching strings of
# Line 1813  relative, as in these examples: Line 1901  relative, as in these examples:
1901  .sp  .sp
1902    (...(absolute)...)...(?2)...    (...(absolute)...)...(?2)...
1903    (...(relative)...)...(?-1)...    (...(relative)...)...(?-1)...
1904    (...(?+1)...(relative)...    (...(?+1)...(relative)...
1905  .sp  .sp
1906  An earlier example pointed out that the pattern  An earlier example pointed out that the pattern
1907  .sp  .sp
# Line 1878  description of the interface to the call Line 1966  description of the interface to the call
1966  documentation.  documentation.
1967  .  .
1968  .  .
1969    .SH "BACTRACKING CONTROL"
1970    .rs
1971    .sp
1972    Perl 5.10 introduced a number of "Special Backtracking Control Verbs", which
1973    are described in the Perl documentation as "experimental and subject to change
1974    or removal in a future version of Perl". It goes on to say: "Their usage in
1975    production code should be noted to avoid problems during upgrades." The same
1976    remarks apply to the PCRE features described in this section.
1977    .P
1978    Since these verbs are specifically related to backtracking, they can be used
1979    only when the pattern is to be matched using \fBpcre_exec()\fP, which uses a
1980    backtracking algorithm. They cause an error if encountered by
1981    \fBpcre_dfa_exec()\fP.
1982    .P
1983    The new verbs make use of what was previously invalid syntax: an opening
1984    parenthesis followed by an asterisk. In Perl, they are generally of the form
1985    (*VERB:ARG) but PCRE does not support the use of arguments, so its general
1986    form is just (*VERB). Any number of these verbs may occur in a pattern. There
1987    are two kinds:
1988    .
1989    .SS "Verbs that act immediately"
1990    .rs
1991    .sp
1992    The following verbs act as soon as they are encountered:
1993    .sp
1994       (*ACCEPT)
1995    .sp
1996    This verb causes the match to end successfully, skipping the remainder of the
1997    pattern. When inside a recursion, only the innermost pattern is ended
1998    immediately. PCRE differs from Perl in what happens if the (*ACCEPT) is inside
1999    capturing parentheses. In Perl, the data so far is captured: in PCRE no data is
2000    captured. For example:
2001    .sp
2002      A(A|B(*ACCEPT)|C)D
2003    .sp
2004    This matches "AB", "AAD", or "ACD", but when it matches "AB", no data is
2005    captured.
2006    .sp
2007      (*FAIL) or (*F)
2008    .sp
2009    This verb causes the match to fail, forcing backtracking to occur. It is
2010    equivalent to (?!) but easier to read. The Perl documentation notes that it is
2011    probably useful only when combined with (?{}) or (??{}). Those are, of course,
2012    Perl features that are not present in PCRE. The nearest equivalent is the
2013    callout feature, as for example in this pattern:
2014    .sp
2015      a+(?C)(*FAIL)
2016    .sp
2017    A match with the string "aaaa" always fails, but the callout is taken before
2018    each backtrack happens (in this example, 10 times).
2019    .
2020    .SS "Verbs that act after backtracking"
2021    .rs
2022    .sp
2023    The following verbs do nothing when they are encountered. Matching continues
2024    with what follows, but if there is no subsequent match, a failure is forced.
2025    The verbs differ in exactly what kind of failure occurs.
2026    .sp
2027      (*COMMIT)
2028    .sp
2029    This verb causes the whole match to fail outright if the rest of the pattern
2030    does not match. Even if the pattern is unanchored, no further attempts to find
2031    a match by advancing the start point take place. Once (*COMMIT) has been
2032    passed, \fBpcre_exec()\fP is committed to finding a match at the current
2033    starting point, or not at all. For example:
2034    .sp
2035      a+(*COMMIT)b
2036    .sp
2037    This matches "xxaab" but not "aacaab". It can be thought of as a kind of
2038    dynamic anchor, or "I've started, so I must finish."
2039    .sp
2040      (*PRUNE)
2041    .sp
2042    This verb causes the match to fail at the current position if the rest of the
2043    pattern does not match. If the pattern is unanchored, the normal "bumpalong"
2044    advance to the next starting character then happens. Backtracking can occur as
2045    usual to the left of (*PRUNE), or when matching to the right of (*PRUNE), but
2046    if there is no match to the right, backtracking cannot cross (*PRUNE).
2047    In simple cases, the use of (*PRUNE) is just an alternative to an atomic
2048    group or possessive quantifier, but there are some uses of (*PRUNE) that cannot
2049    be expressed in any other way.
2050    .sp
2051      (*SKIP)
2052    .sp
2053    This verb is like (*PRUNE), except that if the pattern is unanchored, the
2054    "bumpalong" advance is not to the next character, but to the position in the
2055    subject where (*SKIP) was encountered. (*SKIP) signifies that whatever text
2056    was matched leading up to it cannot be part of a successful match. Consider:
2057    .sp
2058      a+(*SKIP)b
2059    .sp
2060    If the subject is "aaaac...", after the first match attempt fails (starting at
2061    the first character in the string), the starting point skips on to start the
2062    next attempt at "c". Note that a possessive quantifer does not have the same
2063    effect in this example; although it would suppress backtracking during the
2064    first match attempt, the second attempt would start at the second character
2065    instead of skipping on to "c".
2066    .sp
2067      (*THEN)
2068    .sp
2069    This verb causes a skip to the next alternation if the rest of the pattern does
2070    not match. That is, it cancels pending backtracking, but only within the
2071    current alternation. Its name comes from the observation that it can be used
2072    for a pattern-based if-then-else block:
2073    .sp
2074      ( COND1 (*THEN) FOO | COND2 (*THEN) BAR | COND3 (*THEN) BAZ ) ...
2075    .sp
2076    If the COND1 pattern matches, FOO is tried (and possibly further items after
2077    the end of the group if FOO succeeds); on failure the matcher skips to the
2078    second alternative and tries COND2, without backtracking into COND1. If (*THEN)
2079    is used outside of any alternation, it acts exactly like (*PRUNE).
2080    .
2081    .
2082  .SH "SEE ALSO"  .SH "SEE ALSO"
2083  .rs  .rs
2084  .sp  .sp
# Line 1898  Cambridge CB2 3QH, England. Line 2099  Cambridge CB2 3QH, England.
2099  .rs  .rs
2100  .sp  .sp
2101  .nf  .nf
2102  Last updated: 29 May 2007  Last updated: 08 August 2007
2103  Copyright (c) 1997-2007 University of Cambridge.  Copyright (c) 1997-2007 University of Cambridge.
2104  .fi  .fi

Legend:
Removed from v.171  
changed lines
  Added in v.210

  ViewVC Help
Powered by ViewVC 1.1.5