/[pcre]/code/trunk/doc/pcre.txt
ViewVC logotype

Diff of /code/trunk/doc/pcre.txt

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

revision 83 by nigel, Sat Feb 24 21:41:06 2007 UTC revision 286 by ph10, Mon Dec 17 14:46:11 2007 UTC
# Line 18  INTRODUCTION Line 18  INTRODUCTION
18    
19         The  PCRE  library is a set of functions that implement regular expres-         The  PCRE  library is a set of functions that implement regular expres-
20         sion pattern matching using the same syntax and semantics as Perl, with         sion pattern matching using the same syntax and semantics as Perl, with
21         just  a  few  differences.  The current implementation of PCRE (release         just  a  few differences. (Certain features that appeared in Python and
22         6.x) corresponds approximately with Perl  5.8,  including  support  for         PCRE before they appeared in Perl are also available using  the  Python
23         UTF-8 encoded strings and Unicode general category properties. However,         syntax.)
24         this support has to be explicitly enabled; it is not the default.  
25           The  current  implementation of PCRE (release 7.x) corresponds approxi-
26         In addition to the Perl-compatible matching function,  PCRE  also  con-         mately with Perl 5.10, including support for UTF-8 encoded strings  and
27         tains  an  alternative matching function that matches the same compiled         Unicode general category properties. However, UTF-8 and Unicode support
28         patterns in a different way. In certain circumstances, the  alternative         has to be explicitly enabled; it is not the default. The Unicode tables
29         function  has  some  advantages.  For  a discussion of the two matching         correspond to Unicode release 5.0.0.
30         algorithms, see the pcrematching page.  
31           In  addition to the Perl-compatible matching function, PCRE contains an
32         PCRE is written in C and released as a C library. A  number  of  people         alternative matching function that matches the same  compiled  patterns
33         have  written  wrappers and interfaces of various kinds. In particular,         in  a different way. In certain circumstances, the alternative function
34         Google Inc.  have provided a comprehensive C++  wrapper.  This  is  now         has some advantages. For a discussion of the two  matching  algorithms,
35           see the pcrematching page.
36    
37           PCRE  is  written  in C and released as a C library. A number of people
38           have written wrappers and interfaces of various kinds.  In  particular,
39           Google  Inc.   have  provided  a comprehensive C++ wrapper. This is now
40         included as part of the PCRE distribution. The pcrecpp page has details         included as part of the PCRE distribution. The pcrecpp page has details
41         of this interface. Other people's contributions can  be  found  in  the         of  this  interface.  Other  people's contributions can be found in the
42         Contrib directory at the primary FTP site, which is:         Contrib directory at the primary FTP site, which is:
43    
44         ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre         ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre
45    
46         Details  of  exactly which Perl regular expression features are and are         Details of exactly which Perl regular expression features are  and  are
47         not supported by PCRE are given in separate documents. See the pcrepat-         not supported by PCRE are given in separate documents. See the pcrepat-
48         tern and pcrecompat pages.         tern and pcrecompat pages. There is a syntax summary in the  pcresyntax
49           page.
50    
51         Some  features  of  PCRE can be included, excluded, or changed when the         Some  features  of  PCRE can be included, excluded, or changed when the
52         library is built. The pcre_config() function makes it  possible  for  a         library is built. The pcre_config() function makes it  possible  for  a
# Line 67  USER DOCUMENTATION Line 73  USER DOCUMENTATION
73         of searching. The sections are as follows:         of searching. The sections are as follows:
74    
75           pcre              this document           pcre              this document
76             pcre-config       show PCRE installation configuration information
77           pcreapi           details of PCRE's native C API           pcreapi           details of PCRE's native C API
78           pcrebuild         options for building PCRE           pcrebuild         options for building PCRE
79           pcrecallout       details of the callout feature           pcrecallout       details of the callout feature
# Line 77  USER DOCUMENTATION Line 84  USER DOCUMENTATION
84           pcrepartial       details of the partial matching facility           pcrepartial       details of the partial matching facility
85           pcrepattern       syntax and semantics of supported           pcrepattern       syntax and semantics of supported
86                               regular expressions                               regular expressions
87             pcresyntax        quick syntax reference
88           pcreperform       discussion of performance issues           pcreperform       discussion of performance issues
89           pcreposix         the POSIX-compatible C API           pcreposix         the POSIX-compatible C API
90           pcreprecompile    details of saving and re-using precompiled patterns           pcreprecompile    details of saving and re-using precompiled patterns
91           pcresample        discussion of the sample program           pcresample        discussion of the sample program
92             pcrestack         discussion of stack usage
93           pcretest          description of the pcretest testing command           pcretest          description of the pcretest testing command
94    
95         In  addition,  in the "man" and HTML formats, there is a short page for         In  addition,  in the "man" and HTML formats, there is a short page for
# Line 98  LIMITATIONS Line 107  LIMITATIONS
107         PCRE with an internal linkage size of 3 or 4 (see the  README  file  in         PCRE with an internal linkage size of 3 or 4 (see the  README  file  in
108         the  source  distribution and the pcrebuild documentation for details).         the  source  distribution and the pcrebuild documentation for details).
109         In these cases the limit is substantially larger.  However,  the  speed         In these cases the limit is substantially larger.  However,  the  speed
110         of execution will be slower.         of execution is slower.
111    
112           All values in repeating quantifiers must be less than 65536.
113    
114         All values in repeating quantifiers must be less than 65536.  The maxi-         There is no limit to the number of parenthesized subpatterns, but there
115         mum number of capturing subpatterns is 65535.         can be no more than 65535 capturing subpatterns.
116    
117         There is no limit to the number of non-capturing subpatterns,  but  the         The maximum length of name for a named subpattern is 32 characters, and
118         maximum  depth  of  nesting  of  all kinds of parenthesized subpattern,         the maximum number of named subpatterns is 10000.
        including capturing subpatterns, assertions, and other types of subpat-  
        tern, is 200.  
119    
120         The  maximum  length of a subject string is the largest positive number         The  maximum  length of a subject string is the largest positive number
121         that an integer variable can hold. However, when using the  traditional         that an integer variable can hold. However, when using the  traditional
122         matching function, PCRE uses recursion to handle subpatterns and indef-         matching function, PCRE uses recursion to handle subpatterns and indef-
123         inite repetition.  This means that the available stack space may  limit         inite repetition.  This means that the available stack space may  limit
124         the size of a subject string that can be processed by certain patterns.         the size of a subject string that can be processed by certain patterns.
125           For a discussion of stack issues, see the pcrestack documentation.
126    
127    
128  UTF-8 AND UNICODE PROPERTY SUPPORT  UTF-8 AND UNICODE PROPERTY SUPPORT
# Line 130  UTF-8 AND UNICODE PROPERTY SUPPORT Line 140  UTF-8 AND UNICODE PROPERTY SUPPORT
140    
141         If  you compile PCRE with UTF-8 support, but do not use it at run time,         If  you compile PCRE with UTF-8 support, but do not use it at run time,
142         the library will be a bit bigger, but the additional run time  overhead         the library will be a bit bigger, but the additional run time  overhead
143         is  limited  to testing the PCRE_UTF8 flag in several places, so should         is limited to testing the PCRE_UTF8 flag occasionally, so should not be
144         not be very large.         very big.
145    
146         If PCRE is built with Unicode character property support (which implies         If PCRE is built with Unicode character property support (which implies
147         UTF-8  support),  the  escape sequences \p{..}, \P{..}, and \X are sup-         UTF-8  support),  the  escape sequences \p{..}, \P{..}, and \X are sup-
148         ported.  The available properties that can be tested are limited to the         ported.  The available properties that can be tested are limited to the
149         general  category  properties such as Lu for an upper case letter or Nd         general  category  properties such as Lu for an upper case letter or Nd
150         for a decimal number. A full list is given in the pcrepattern  documen-         for a decimal number, the Unicode script names such as Arabic  or  Han,
151         tation. The PCRE library is increased in size by about 90K when Unicode         and  the  derived  properties  Any  and L&. A full list is given in the
152         property support is included.         pcrepattern documentation. Only the short names for properties are sup-
153           ported.  For example, \p{L} matches a letter. Its Perl synonym, \p{Let-
154         The following comments apply when PCRE is running in UTF-8 mode:         ter}, is not supported.  Furthermore,  in  Perl,  many  properties  may
155           optionally  be  prefixed by "Is", for compatibility with Perl 5.6. PCRE
156         1. When you set the PCRE_UTF8 flag, the strings passed as patterns  and         does not support this.
157         subjects  are  checked for validity on entry to the relevant functions.  
158         If an invalid UTF-8 string is passed, an error return is given. In some     Validity of UTF-8 strings
159         situations,  you  may  already  know  that  your strings are valid, and  
160         therefore want to skip these checks in order to improve performance. If         When you set the PCRE_UTF8 flag, the strings  passed  as  patterns  and
161         you  set  the  PCRE_NO_UTF8_CHECK  flag at compile time or at run time,         subjects are (by default) checked for validity on entry to the relevant
162         PCRE assumes that the pattern or subject  it  is  given  (respectively)         functions. From release 7.3 of PCRE, the check is according  the  rules
163         contains  only valid UTF-8 codes. In this case, it does not diagnose an         of  RFC  3629, which are themselves derived from the Unicode specifica-
164         invalid UTF-8 string. If you pass an invalid UTF-8 string to PCRE  when         tion. Earlier releases of PCRE followed the rules of  RFC  2279,  which
165         PCRE_NO_UTF8_CHECK  is set, the results are undefined. Your program may         allows  the  full range of 31-bit values (0 to 0x7FFFFFFF). The current
166         crash.         check allows only values in the range U+0 to U+10FFFF, excluding U+D800
167           to U+DFFF.
168         2. In a pattern, the escape sequence \x{...}, where the contents of the  
169         braces  is  a  string  of hexadecimal digits, is interpreted as a UTF-8         The  excluded  code  points are the "Low Surrogate Area" of Unicode, of
170         character whose code number is the given hexadecimal number, for  exam-         which the Unicode Standard says this: "The Low Surrogate Area does  not
171         ple:  \x{1234}.  If a non-hexadecimal digit appears between the braces,         contain  any  character  assignments,  consequently  no  character code
172         the item is not recognized.  This escape sequence can be used either as         charts or namelists are provided for this area. Surrogates are reserved
173         a literal, or within a character class.         for  use  with  UTF-16 and then must be used in pairs." The code points
174           that are encoded by UTF-16 pairs  are  available  as  independent  code
175           points  in  the  UTF-8  encoding.  (In other words, the whole surrogate
176           thing is a fudge for UTF-16 which unfortunately messes up UTF-8.)
177    
178           If an  invalid  UTF-8  string  is  passed  to  PCRE,  an  error  return
179           (PCRE_ERROR_BADUTF8) is given. In some situations, you may already know
180           that your strings are valid, and therefore want to skip these checks in
181           order to improve performance. If you set the PCRE_NO_UTF8_CHECK flag at
182           compile time or at run time, PCRE assumes that the pattern  or  subject
183           it  is  given  (respectively)  contains only valid UTF-8 codes. In this
184           case, it does not diagnose an invalid UTF-8 string.
185    
186           If you pass an invalid UTF-8 string  when  PCRE_NO_UTF8_CHECK  is  set,
187           what  happens  depends on why the string is invalid. If the string con-
188           forms to the "old" definition of UTF-8 (RFC 2279), it is processed as a
189           string  of  characters  in  the  range 0 to 0x7FFFFFFF. In other words,
190           apart from the initial validity test, PCRE (when in UTF-8 mode) handles
191           strings  according  to  the more liberal rules of RFC 2279. However, if
192           the string does not even conform to RFC 2279, the result is  undefined.
193           Your program may crash.
194    
195           If  you  want  to  process  strings  of  values  in the full range 0 to
196           0x7FFFFFFF, encoded in a UTF-8-like manner as per the old RFC, you  can
197           set PCRE_NO_UTF8_CHECK to bypass the more restrictive test. However, in
198           this situation, you will have to apply your own validity check.
199    
200       General comments about UTF-8 mode
201    
202         3.  The  original hexadecimal escape sequence, \xhh, matches a two-byte         1. An unbraced hexadecimal escape sequence (such  as  \xb3)  matches  a
203         UTF-8 character if the value is greater than 127.         two-byte UTF-8 character if the value is greater than 127.
204    
205         4. Repeat quantifiers apply to complete UTF-8 characters, not to  indi-         2.  Octal  numbers  up to \777 are recognized, and match two-byte UTF-8
206           characters for values greater than \177.
207    
208           3. Repeat quantifiers apply to complete UTF-8 characters, not to  indi-
209         vidual bytes, for example: \x{100}{3}.         vidual bytes, for example: \x{100}{3}.
210    
211         5.  The dot metacharacter matches one UTF-8 character instead of a sin-         4.  The dot metacharacter matches one UTF-8 character instead of a sin-
212         gle byte.         gle byte.
213    
214         6. The escape sequence \C can be used to match a single byte  in  UTF-8         5. The escape sequence \C can be used to match a single byte  in  UTF-8
215         mode,  but  its  use can lead to some strange effects. This facility is         mode,  but  its  use can lead to some strange effects. This facility is
216         not available in the alternative matching function, pcre_dfa_exec().         not available in the alternative matching function, pcre_dfa_exec().
217    
218         7. The character escapes \b, \B, \d, \D, \s, \S, \w, and  \W  correctly         6. The character escapes \b, \B, \d, \D, \s, \S, \w, and  \W  correctly
219         test  characters of any code value, but the characters that PCRE recog-         test  characters of any code value, but the characters that PCRE recog-
220         nizes as digits, spaces, or word characters  remain  the  same  set  as         nizes as digits, spaces, or word characters  remain  the  same  set  as
221         before, all with values less than 256. This remains true even when PCRE         before, all with values less than 256. This remains true even when PCRE
# Line 184  UTF-8 AND UNICODE PROPERTY SUPPORT Line 224  UTF-8 AND UNICODE PROPERTY SUPPORT
224         sense of, say, "digit", you must use Unicode  property  tests  such  as         sense of, say, "digit", you must use Unicode  property  tests  such  as
225         \p{Nd}.         \p{Nd}.
226    
227         8.  Similarly,  characters that match the POSIX named character classes         7.  Similarly,  characters that match the POSIX named character classes
228         are all low-valued characters.         are all low-valued characters.
229    
230           8. However, the Perl 5.10 horizontal and vertical  whitespace  matching
231           escapes (\h, \H, \v, and \V) do match all the appropriate Unicode char-
232           acters.
233    
234         9. Case-insensitive matching applies only to  characters  whose  values         9. Case-insensitive matching applies only to  characters  whose  values
235         are  less than 128, unless PCRE is built with Unicode property support.         are  less than 128, unless PCRE is built with Unicode property support.
236         Even when Unicode property support is available, PCRE  still  uses  its         Even when Unicode property support is available, PCRE  still  uses  its
237         own  character  tables when checking the case of low-valued characters,         own  character  tables when checking the case of low-valued characters,
238         so as not to degrade performance.  The Unicode property information  is         so as not to degrade performance.  The Unicode property information  is
239         used only for characters with higher values.         used only for characters with higher values. Even when Unicode property
240           support is available, PCRE supports case-insensitive matching only when
241           there  is  a  one-to-one  mapping between a letter's cases. There are a
242           small number of many-to-one mappings in Unicode;  these  are  not  sup-
243           ported by PCRE.
244    
245    
246  AUTHOR  AUTHOR
247    
248         Philip Hazel         Philip Hazel
249         University Computing Service,         University Computing Service
250         Cambridge CB2 3QG, England.         Cambridge CB2 3QH, England.
251    
252         Putting  an actual email address here seems to have been a spam magnet,         Putting  an actual email address here seems to have been a spam magnet,
253         so I've taken it away. If you want to email me, use my initial and sur-         so I've taken it away. If you want to email me, use  my  two  initials,
254         name, separated by a dot, at the domain ucs.cam.ac.uk.         followed by the two digits 10, at the domain cam.ac.uk.
255    
256    
257    REVISION
258    
259  Last updated: 07 March 2005         Last updated: 09 August 2007
260  Copyright (c) 1997-2005 University of Cambridge.         Copyright (c) 1997-2007 University of Cambridge.
261  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
262    
263    
# Line 220  NAME Line 271  NAME
271  PCRE BUILD-TIME OPTIONS  PCRE BUILD-TIME OPTIONS
272    
273         This  document  describes  the  optional  features  of PCRE that can be         This  document  describes  the  optional  features  of PCRE that can be
274         selected when the library is compiled. They are all selected, or  dese-         selected when the library is compiled. It assumes use of the  configure
275         lected, by providing options to the configure script that is run before         script,  where the optional features are selected or deselected by pro-
276         the make command. The complete list of  options  for  configure  (which         viding options to configure before running the make  command.  However,
277         includes  the  standard  ones such as the selection of the installation         the  same  options  can be selected in both Unix-like and non-Unix-like
278         directory) can be obtained by running         environments using the GUI facility of  CMakeSetup  if  you  are  using
279           CMake instead of configure to build PCRE.
280    
281           The complete list of options for configure (which includes the standard
282           ones such as the  selection  of  the  installation  directory)  can  be
283           obtained by running
284    
285           ./configure --help           ./configure --help
286    
287         The following sections describe certain options whose names begin  with         The  following  sections  include  descriptions  of options whose names
288         --enable  or  --disable. These settings specify changes to the defaults         begin with --enable or --disable. These settings specify changes to the
289         for the configure command. Because of the  way  that  configure  works,         defaults  for  the configure command. Because of the way that configure
290         --enable  and  --disable  always  come  in  pairs, so the complementary         works, --enable and --disable always come in pairs, so  the  complemen-
291         option always exists as well, but as it specifies the  default,  it  is         tary  option always exists as well, but as it specifies the default, it
292         not described.         is not described.
293    
294    
295  C++ SUPPORT  C++ SUPPORT
# Line 253  UTF-8 SUPPORT Line 309  UTF-8 SUPPORT
309    
310           --enable-utf8           --enable-utf8
311    
312         to  the  configure  command.  Of  itself, this does not make PCRE treat         to the configure command. Of itself, this  does  not  make  PCRE  treat
313         strings as UTF-8. As well as compiling PCRE with this option, you  also         strings  as UTF-8. As well as compiling PCRE with this option, you also
314         have  have to set the PCRE_UTF8 option when you call the pcre_compile()         have have to set the PCRE_UTF8 option when you call the  pcre_compile()
315         function.         function.
316    
317    
318  UNICODE CHARACTER PROPERTY SUPPORT  UNICODE CHARACTER PROPERTY SUPPORT
319    
320         UTF-8 support allows PCRE to process character values greater than  255         UTF-8  support allows PCRE to process character values greater than 255
321         in  the  strings that it handles. On its own, however, it does not pro-         in the strings that it handles. On its own, however, it does  not  pro-
322         vide any facilities for accessing the properties of such characters. If         vide any facilities for accessing the properties of such characters. If
323         you  want  to  be able to use the pattern escapes \P, \p, and \X, which         you want to be able to use the pattern escapes \P, \p,  and  \X,  which
324         refer to Unicode character properties, you must add         refer to Unicode character properties, you must add
325    
326           --enable-unicode-properties           --enable-unicode-properties
327    
328         to the configure command. This implies UTF-8 support, even if you  have         to  the configure command. This implies UTF-8 support, even if you have
329         not explicitly requested it.         not explicitly requested it.
330    
331         Including  Unicode  property  support  adds around 90K of tables to the         Including Unicode property support adds around 30K  of  tables  to  the
332         PCRE library, approximately doubling its size. Only the  general  cate-         PCRE  library.  Only  the general category properties such as Lu and Nd
333         gory  properties  such as Lu and Nd are supported. Details are given in         are supported. Details are given in the pcrepattern documentation.
        the pcrepattern documentation.  
334    
335    
336  CODE VALUE OF NEWLINE  CODE VALUE OF NEWLINE
337    
338         By default, PCRE treats character 10 (linefeed) as the newline  charac-         By default, PCRE interprets character 10 (linefeed, LF)  as  indicating
339         ter. This is the normal newline character on Unix-like systems. You can         the  end  of  a line. This is the normal newline character on Unix-like
340         compile PCRE to use character 13 (carriage return) instead by adding         systems. You can compile PCRE to use character 13 (carriage return, CR)
341           instead, by adding
342    
343           --enable-newline-is-cr           --enable-newline-is-cr
344    
345         to the configure command. For completeness there is  also  a  --enable-         to  the  configure  command.  There  is  also  a --enable-newline-is-lf
346         newline-is-lf  option,  which explicitly specifies linefeed as the new-         option, which explicitly specifies linefeed as the newline character.
347         line character.  
348           Alternatively, you can specify that line endings are to be indicated by
349           the two character sequence CRLF. If you want this, add
350    
351             --enable-newline-is-crlf
352    
353           to the configure command. There is a fourth option, specified by
354    
355             --enable-newline-is-anycrlf
356    
357           which  causes  PCRE  to recognize any of the three sequences CR, LF, or
358           CRLF as indicating a line ending. Finally, a fifth option, specified by
359    
360             --enable-newline-is-any
361    
362           causes PCRE to recognize any Unicode newline sequence.
363    
364           Whatever  line  ending convention is selected when PCRE is built can be
365           overridden when the library functions are called. At build time  it  is
366           conventional to use the standard for your operating system.
367    
368    
369    WHAT \R MATCHES
370    
371           By  default,  the  sequence \R in a pattern matches any Unicode newline
372           sequence, whatever has been selected as the line  ending  sequence.  If
373           you specify
374    
375             --enable-bsr-anycrlf
376    
377           the  default  is changed so that \R matches only CR, LF, or CRLF. What-
378           ever is selected when PCRE is built can be overridden when the  library
379           functions are called.
380    
381    
382  BUILDING SHARED AND STATIC LIBRARIES  BUILDING SHARED AND STATIC LIBRARIES
383    
384         The PCRE building process uses libtool to build both shared and  static         The  PCRE building process uses libtool to build both shared and static
385         Unix  libraries by default. You can suppress one of these by adding one         Unix libraries by default. You can suppress one of these by adding  one
386         of         of
387    
388           --disable-shared           --disable-shared
# Line 306  BUILDING SHARED AND STATIC LIBRARIES Line 394  BUILDING SHARED AND STATIC LIBRARIES
394  POSIX MALLOC USAGE  POSIX MALLOC USAGE
395    
396         When PCRE is called through the POSIX interface (see the pcreposix doc-         When PCRE is called through the POSIX interface (see the pcreposix doc-
397         umentation),  additional  working  storage  is required for holding the         umentation), additional working storage is  required  for  holding  the
398         pointers to capturing substrings, because PCRE requires three  integers         pointers  to capturing substrings, because PCRE requires three integers
399         per  substring,  whereas  the POSIX interface provides only two. If the         per substring, whereas the POSIX interface provides only  two.  If  the
400         number of expected substrings is small, the wrapper function uses space         number of expected substrings is small, the wrapper function uses space
401         on the stack, because this is faster than using malloc() for each call.         on the stack, because this is faster than using malloc() for each call.
402         The default threshold above which the stack is no longer used is 10; it         The default threshold above which the stack is no longer used is 10; it
# Line 319  POSIX MALLOC USAGE Line 407  POSIX MALLOC USAGE
407         to the configure command.         to the configure command.
408    
409    
 LIMITING PCRE RESOURCE USAGE  
   
        Internally,  PCRE has a function called match(), which it calls repeat-  
        edly  (possibly  recursively)  when  matching  a   pattern   with   the  
        pcre_exec()  function.  By controlling the maximum number of times this  
        function may be called during a single matching operation, a limit  can  
        be  placed  on  the resources used by a single call to pcre_exec(). The  
        limit can be changed at run time, as described in the pcreapi  documen-  
        tation.  The default is 10 million, but this can be changed by adding a  
        setting such as  
   
          --with-match-limit=500000  
   
        to  the  configure  command.  This  setting  has  no  effect   on   the  
        pcre_dfa_exec() matching function.  
   
   
410  HANDLING VERY LARGE PATTERNS  HANDLING VERY LARGE PATTERNS
411    
412         Within  a  compiled  pattern,  offset values are used to point from one         Within a compiled pattern, offset values are used  to  point  from  one
413         part to another (for example, from an opening parenthesis to an  alter-         part  to another (for example, from an opening parenthesis to an alter-
414         nation  metacharacter).  By default, two-byte values are used for these         nation metacharacter). By default, two-byte values are used  for  these
415         offsets, leading to a maximum size for a  compiled  pattern  of  around         offsets,  leading  to  a  maximum size for a compiled pattern of around
416         64K.  This  is sufficient to handle all but the most gigantic patterns.         64K. This is sufficient to handle all but the most  gigantic  patterns.
417         Nevertheless, some people do want to process enormous patterns,  so  it         Nevertheless,  some  people do want to process enormous patterns, so it
418         is  possible  to compile PCRE to use three-byte or four-byte offsets by         is possible to compile PCRE to use three-byte or four-byte  offsets  by
419         adding a setting such as         adding a setting such as
420    
421           --with-link-size=3           --with-link-size=3
422    
423         to the configure command. The value given must be 2,  3,  or  4.  Using         to  the  configure  command.  The value given must be 2, 3, or 4. Using
424         longer  offsets slows down the operation of PCRE because it has to load         longer offsets slows down the operation of PCRE because it has to  load
425         additional bytes when handling them.         additional bytes when handling them.
426    
        If you build PCRE with an increased link size, test 2 (and  test  5  if  
        you  are using UTF-8) will fail. Part of the output of these tests is a  
        representation of the compiled pattern, and this changes with the  link  
        size.  
   
427    
428  AVOIDING EXCESSIVE STACK USAGE  AVOIDING EXCESSIVE STACK USAGE
429    
# Line 365  AVOIDING EXCESSIVE STACK USAGE Line 431  AVOIDING EXCESSIVE STACK USAGE
431         ing by making recursive calls to an internal function  called  match().         ing by making recursive calls to an internal function  called  match().
432         In  environments  where  the size of the stack is limited, this can se-         In  environments  where  the size of the stack is limited, this can se-
433         verely limit PCRE's operation. (The Unix environment does  not  usually         verely limit PCRE's operation. (The Unix environment does  not  usually
434         suffer  from  this  problem.)  An alternative approach that uses memory         suffer from this problem, but it may sometimes be necessary to increase
435         from the heap to remember data, instead  of  using  recursive  function         the maximum stack size.  There is a discussion in the  pcrestack  docu-
436         calls,  has been implemented to work round this problem. If you want to         mentation.)  An alternative approach to recursion that uses memory from
437         build a version of PCRE that works this way, add         the heap to remember data, instead of using recursive  function  calls,
438           has  been  implemented to work round the problem of limited stack size.
439           If you want to build a version of PCRE that works this way, add
440    
441           --disable-stack-for-recursion           --disable-stack-for-recursion
442    
443         to the configure command. With this configuration, PCRE  will  use  the         to the configure command. With this configuration, PCRE  will  use  the
444         pcre_stack_malloc  and pcre_stack_free variables to call memory manage-         pcre_stack_malloc  and pcre_stack_free variables to call memory manage-
445         ment functions. Separate functions are provided because  the  usage  is         ment functions. By default these point to malloc() and free(), but  you
446         very  predictable:  the  block sizes requested are always the same, and         can replace the pointers so that your own functions are used.
447         the blocks are always freed in reverse order. A calling  program  might  
448         be  able  to implement optimized functions that perform better than the         Separate  functions  are  provided  rather  than  using pcre_malloc and
449         standard malloc() and  free()  functions.  PCRE  runs  noticeably  more         pcre_free because the  usage  is  very  predictable:  the  block  sizes
450         slowly when built in this way. This option affects only the pcre_exec()         requested  are  always  the  same,  and  the blocks are always freed in
451         function; it is not relevant for the the pcre_dfa_exec() function.         reverse order. A calling program might be able to  implement  optimized
452           functions  that  perform  better  than  malloc()  and free(). PCRE runs
453           noticeably more slowly when built in this way. This option affects only
454           the   pcre_exec()   function;   it   is   not   relevant  for  the  the
455           pcre_dfa_exec() function.
456    
457    
458    LIMITING PCRE RESOURCE USAGE
459    
460           Internally, PCRE has a function called match(), which it calls  repeat-
461           edly   (sometimes   recursively)  when  matching  a  pattern  with  the
462           pcre_exec() function. By controlling the maximum number of  times  this
463           function  may be called during a single matching operation, a limit can
464           be placed on the resources used by a single call  to  pcre_exec().  The
465           limit  can be changed at run time, as described in the pcreapi documen-
466           tation. The default is 10 million, but this can be changed by adding  a
467           setting such as
468    
469             --with-match-limit=500000
470    
471           to   the   configure  command.  This  setting  has  no  effect  on  the
472           pcre_dfa_exec() matching function.
473    
474           In some environments it is desirable to limit the  depth  of  recursive
475           calls of match() more strictly than the total number of calls, in order
476           to restrict the maximum amount of stack (or heap,  if  --disable-stack-
477           for-recursion is specified) that is used. A second limit controls this;
478           it defaults to the value that  is  set  for  --with-match-limit,  which
479           imposes  no  additional constraints. However, you can set a lower limit
480           by adding, for example,
481    
482             --with-match-limit-recursion=10000
483    
484           to the configure command. This value can  also  be  overridden  at  run
485           time.
486    
487    
488    CREATING CHARACTER TABLES AT BUILD TIME
489    
490           PCRE  uses fixed tables for processing characters whose code values are
491           less than 256. By default, PCRE is built with a set of tables that  are
492           distributed  in  the  file pcre_chartables.c.dist. These tables are for
493           ASCII codes only. If you add
494    
495             --enable-rebuild-chartables
496    
497           to the configure command, the distributed tables are  no  longer  used.
498           Instead,  a  program  called dftables is compiled and run. This outputs
499           the source for new set of tables, created in the default locale of your
500           C runtime system. (This method of replacing the tables does not work if
501           you are cross compiling, because dftables is run on the local host.  If
502           you  need  to  create alternative tables when cross compiling, you will
503           have to do so "by hand".)
504    
505    
506  USING EBCDIC CODE  USING EBCDIC CODE
507    
508         PCRE assumes by default that it will run in an  environment  where  the         PCRE assumes by default that it will run in an  environment  where  the
509         character  code  is  ASCII  (or Unicode, which is a superset of ASCII).         character  code  is  ASCII  (or Unicode, which is a superset of ASCII).
510         PCRE can, however, be compiled to  run  in  an  EBCDIC  environment  by         This is the case for most computer operating systems.  PCRE  can,  how-
511         adding         ever, be compiled to run in an EBCDIC environment by adding
512    
513           --enable-ebcdic           --enable-ebcdic
514    
515         to the configure command.         to the configure command. This setting implies --enable-rebuild-charta-
516           bles. You should only use it if you know that  you  are  in  an  EBCDIC
517           environment (for example, an IBM mainframe operating system).
518    
519    
520    PCREGREP OPTIONS FOR COMPRESSED FILE SUPPORT
521    
522           By default, pcregrep reads all files as plain text. You can build it so
523           that it recognizes files whose names end in .gz or .bz2, and reads them
524           with libz or libbz2, respectively, by adding one or both of
525    
526             --enable-pcregrep-libz
527             --enable-pcregrep-libbz2
528    
529           to the configure command. These options naturally require that the rel-
530           evant libraries are installed on your system. Configuration  will  fail
531           if they are not.
532    
533    
534  Last updated: 15 August 2005  SEE ALSO
535  Copyright (c) 1997-2005 University of Cambridge.  
536           pcreapi(3), pcre_config(3).
537    
538    
539    AUTHOR
540    
541           Philip Hazel
542           University Computing Service
543           Cambridge CB2 3QH, England.
544    
545    
546    REVISION
547    
548           Last updated: 17 December 2007
549           Copyright (c) 1997-2007 University of Cambridge.
550  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
551    
552    
# Line 431  PCRE MATCHING ALGORITHMS Line 582  PCRE MATCHING ALGORITHMS
582           <something> <something else> <something further>           <something> <something else> <something further>
583    
584         there are three possible answers. The standard algorithm finds only one         there are three possible answers. The standard algorithm finds only one
585         of them, whereas the DFA algorithm finds all three.         of them, whereas the alternative algorithm finds all three.
586    
587    
588  REGULAR EXPRESSIONS AS TREES  REGULAR EXPRESSIONS AS TREES
# Line 440  REGULAR EXPRESSIONS AS TREES Line 591  REGULAR EXPRESSIONS AS TREES
591         resented  as  a  tree structure. An unlimited repetition in the pattern         resented  as  a  tree structure. An unlimited repetition in the pattern
592         makes the tree of infinite size, but it is still a tree.  Matching  the         makes the tree of infinite size, but it is still a tree.  Matching  the
593         pattern  to a given subject string (from a given starting point) can be         pattern  to a given subject string (from a given starting point) can be
594         thought of as a search of the tree.  There are  two  standard  ways  to         thought of as a search of the tree.  There are two  ways  to  search  a
595         search  a  tree: depth-first and breadth-first, and these correspond to         tree:  depth-first  and  breadth-first, and these correspond to the two
596         the two matching algorithms provided by PCRE.         matching algorithms provided by PCRE.
597    
598    
599  THE STANDARD MATCHING ALGORITHM  THE STANDARD MATCHING ALGORITHM
600    
601         In the terminology of Jeffrey Friedl's book Mastering  Regular  Expres-         In the terminology of Jeffrey Friedl's book "Mastering Regular  Expres-
602         sions,  the  standard  algorithm  is  an "NFA algorithm". It conducts a         sions",  the  standard  algorithm  is an "NFA algorithm". It conducts a
603         depth-first search of the pattern tree. That is, it  proceeds  along  a         depth-first search of the pattern tree. That is, it  proceeds  along  a
604         single path through the tree, checking that the subject matches what is         single path through the tree, checking that the subject matches what is
605         required. When there is a mismatch, the algorithm  tries  any  alterna-         required. When there is a mismatch, the algorithm  tries  any  alterna-
# Line 472  THE STANDARD MATCHING ALGORITHM Line 623  THE STANDARD MATCHING ALGORITHM
623         This provides support for capturing parentheses and back references.         This provides support for capturing parentheses and back references.
624    
625    
626  THE DFA MATCHING ALGORITHM  THE ALTERNATIVE MATCHING ALGORITHM
627    
628         DFA stands for "deterministic finite automaton", but you do not need to         This algorithm conducts a breadth-first search of  the  tree.  Starting
629         understand the origins of that name. This algorithm conducts a breadth-         from  the  first  matching  point  in the subject, it scans the subject
630         first search of the tree. Starting from the first matching point in the         string from left to right, once, character by character, and as it does
631         subject,  it scans the subject string from left to right, once, charac-         this,  it remembers all the paths through the tree that represent valid
632         ter by character, and as it does  this,  it  remembers  all  the  paths         matches. In Friedl's terminology, this is a kind  of  "DFA  algorithm",
633         through the tree that represent valid matches.         though  it is not implemented as a traditional finite state machine (it
634           keeps multiple states active simultaneously).
635         The  scan  continues until either the end of the subject is reached, or  
636         there are no more unterminated paths. At this point,  terminated  paths         The scan continues until either the end of the subject is  reached,  or
637         represent  the different matching possibilities (if there are none, the         there  are  no more unterminated paths. At this point, terminated paths
638         match has failed).  Thus, if there is more  than  one  possible  match,         represent the different matching possibilities (if there are none,  the
639           match  has  failed).   Thus,  if there is more than one possible match,
640         this algorithm finds all of them, and in particular, it finds the long-         this algorithm finds all of them, and in particular, it finds the long-
641         est. In PCRE, there is an option to stop the algorithm after the  first         est.  In PCRE, there is an option to stop the algorithm after the first
642         match (which is necessarily the shortest) has been found.         match (which is necessarily the shortest) has been found.
643    
644         Note that all the matches that are found start at the same point in the         Note that all the matches that are found start at the same point in the
# Line 494  THE DFA MATCHING ALGORITHM Line 646  THE DFA MATCHING ALGORITHM
646    
647           cat(er(pillar)?)           cat(er(pillar)?)
648    
649         is matched against the string "the caterpillar catchment",  the  result         is  matched  against the string "the caterpillar catchment", the result
650         will  be the three strings "cat", "cater", and "caterpillar" that start         will be the three strings "cat", "cater", and "caterpillar" that  start
651         at the fourth character of the subject. The algorithm does not automat-         at the fourth character of the subject. The algorithm does not automat-
652         ically move on to find matches that start at later positions.         ically move on to find matches that start at later positions.
653    
654         There are a number of features of PCRE regular expressions that are not         There are a number of features of PCRE regular expressions that are not
655         supported by the DFA matching algorithm. They are as follows:         supported by the alternative matching algorithm. They are as follows:
656    
657         1. Because the algorithm finds all  possible  matches,  the  greedy  or         1.  Because  the  algorithm  finds  all possible matches, the greedy or
658         ungreedy  nature  of repetition quantifiers is not relevant. Greedy and         ungreedy nature of repetition quantifiers is not relevant.  Greedy  and
659         ungreedy quantifiers are treated in exactly the same way.         ungreedy quantifiers are treated in exactly the same way. However, pos-
660           sessive quantifiers can make a difference when what follows could  also
661           match what is quantified, for example in a pattern like this:
662    
663             ^a++\w!
664    
665           This  pattern matches "aaab!" but not "aaa!", which would be matched by
666           a non-possessive quantifier. Similarly, if an atomic group is  present,
667           it  is matched as if it were a standalone pattern at the current point,
668           and the longest match is then "locked in" for the rest of  the  overall
669           pattern.
670    
671         2. When dealing with multiple paths through the tree simultaneously, it         2. When dealing with multiple paths through the tree simultaneously, it
672         is  not  straightforward  to  keep track of captured substrings for the         is not straightforward to keep track of  captured  substrings  for  the
673         different matching possibilities, and  PCRE's  implementation  of  this         different  matching  possibilities,  and  PCRE's implementation of this
674         algorithm does not attempt to do this. This means that no captured sub-         algorithm does not attempt to do this. This means that no captured sub-
675         strings are available.         strings are available.
676    
677         3. Because no substrings are captured, back references within the  pat-         3.  Because no substrings are captured, back references within the pat-
678         tern are not supported, and cause errors if encountered.         tern are not supported, and cause errors if encountered.
679    
680         4.  For  the same reason, conditional expressions that use a backrefer-         4. For the same reason, conditional expressions that use  a  backrefer-
681         ence as the condition are not supported.         ence  as  the  condition or test for a specific group recursion are not
682           supported.
683    
684           5. Because many paths through the tree may be  active,  the  \K  escape
685           sequence, which resets the start of the match when encountered (but may
686           be on some paths and not on others), is not  supported.  It  causes  an
687           error if encountered.
688    
689         5. Callouts are supported, but the value of the  capture_top  field  is         6.  Callouts  are  supported, but the value of the capture_top field is
690         always 1, and the value of the capture_last field is always -1.         always 1, and the value of the capture_last field is always -1.
691    
692         6.  The \C escape sequence, which (in the standard algorithm) matches a         7. The \C escape sequence, which (in the standard algorithm) matches  a
693         single byte, even in UTF-8 mode, is not supported because the DFA algo-         single  byte, even in UTF-8 mode, is not supported because the alterna-
694         rithm moves through the subject string one character at a time, for all         tive algorithm moves through the subject  string  one  character  at  a
695         active paths through the tree.         time, for all active paths through the tree.
696    
697           8.  None  of  the  backtracking control verbs such as (*PRUNE) are sup-
698           ported.
699    
700    
701  ADVANTAGES OF THE DFA ALGORITHM  ADVANTAGES OF THE ALTERNATIVE ALGORITHM
702    
703         Using the DFA matching algorithm provides the following advantages:         Using the alternative matching algorithm provides the following  advan-
704           tages:
705    
706         1. All possible matches (at a single point in the subject) are automat-         1. All possible matches (at a single point in the subject) are automat-
707         ically  found,  and  in particular, the longest match is found. To find         ically found, and in particular, the longest match is  found.  To  find
708         more than one match using the standard algorithm, you have to do kludgy         more than one match using the standard algorithm, you have to do kludgy
709         things with callouts.         things with callouts.
710    
711         2.  There is much better support for partial matching. The restrictions         2. There is much better support for partial matching. The  restrictions
712         on the content of the pattern that apply when using the standard  algo-         on  the content of the pattern that apply when using the standard algo-
713         rithm  for partial matching do not apply to the DFA algorithm. For non-         rithm for partial matching do not apply to the  alternative  algorithm.
714         anchored patterns, the starting position of a partial match  is  avail-         For  non-anchored patterns, the starting position of a partial match is
715         able.         available.
716    
717         3.  Because  the  DFA algorithm scans the subject string just once, and         3. Because the alternative algorithm  scans  the  subject  string  just
718         never needs to backtrack, it is possible  to  pass  very  long  subject         once,  and  never  needs to backtrack, it is possible to pass very long
719         strings  to  the matching function in several pieces, checking for par-         subject strings to the matching function in  several  pieces,  checking
720         tial matching each time.         for partial matching each time.
721    
722    
723  DISADVANTAGES OF THE DFA ALGORITHM  DISADVANTAGES OF THE ALTERNATIVE ALGORITHM
724    
725         The DFA algorithm suffers from a number of disadvantages:         The alternative algorithm suffers from a number of disadvantages:
726    
727         1. It is substantially slower than  the  standard  algorithm.  This  is         1.  It  is  substantially  slower  than the standard algorithm. This is
728         partly  because  it has to search for all possible matches, but is also         partly because it has to search for all possible matches, but  is  also
729         because it is less susceptible to optimization.         because it is less susceptible to optimization.
730    
731         2. Capturing parentheses and back references are not supported.         2. Capturing parentheses and back references are not supported.
732    
733         3. The "atomic group" feature of PCRE regular expressions is supported,         3. Although atomic groups are supported, their use does not provide the
734         but  does not provide the advantage that it does for the standard algo-         performance advantage that it does for the standard algorithm.
735         rithm.  
736    
737    AUTHOR
738    
739           Philip Hazel
740           University Computing Service
741           Cambridge CB2 3QH, England.
742    
743    
744  Last updated: 28 February 2005  REVISION
745  Copyright (c) 1997-2005 University of Cambridge.  
746           Last updated: 08 August 2007
747           Copyright (c) 1997-2007 University of Cambridge.
748  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
749    
750    
# Line 616  PCRE NATIVE API Line 797  PCRE NATIVE API
797         int pcre_get_stringnumber(const pcre *code,         int pcre_get_stringnumber(const pcre *code,
798              const char *name);              const char *name);
799    
800           int pcre_get_stringtable_entries(const pcre *code,
801                const char *name, char **first, char **last);
802    
803         int pcre_get_substring(const char *subject, int *ovector,         int pcre_get_substring(const char *subject, int *ovector,
804              int stringcount, int stringnumber,              int stringcount, int stringnumber,
805              const char **stringptr);              const char **stringptr);
# Line 654  PCRE NATIVE API Line 838  PCRE NATIVE API
838  PCRE API OVERVIEW  PCRE API OVERVIEW
839    
840         PCRE has its own native API, which is described in this document. There         PCRE has its own native API, which is described in this document. There
841         is also a set of wrapper functions that correspond to the POSIX regular         are also some wrapper functions that correspond to  the  POSIX  regular
842         expression  API.  These  are  described in the pcreposix documentation.         expression  API.  These  are  described in the pcreposix documentation.
843         Both of these APIs define a set of C function calls. A C++  wrapper  is         Both of these APIs define a set of C function calls. A C++  wrapper  is
844         distributed with PCRE. It is documented in the pcrecpp page.         distributed with PCRE. It is documented in the pcrecpp page.
# Line 676  PCRE API OVERVIEW Line 860  PCRE API OVERVIEW
860    
861         A second matching function, pcre_dfa_exec(), which is not Perl-compati-         A second matching function, pcre_dfa_exec(), which is not Perl-compati-
862         ble,  is  also provided. This uses a different algorithm for the match-         ble,  is  also provided. This uses a different algorithm for the match-
863         ing. This allows it to find all possible matches (at a given  point  in         ing. The alternative algorithm finds all possible matches (at  a  given
864         the  subject),  not  just  one. However, this algorithm does not return         point  in  the subject), and scans the subject just once. However, this
865         captured substrings. A description of the two matching  algorithms  and         algorithm does not return captured substrings. A description of the two
866         their  advantages  and disadvantages is given in the pcrematching docu-         matching  algorithms and their advantages and disadvantages is given in
867         mentation.         the pcrematching documentation.
868    
869         In addition to the main compiling and  matching  functions,  there  are         In addition to the main compiling and  matching  functions,  there  are
870         convenience functions for extracting captured substrings from a subject         convenience functions for extracting captured substrings from a subject
# Line 692  PCRE API OVERVIEW Line 876  PCRE API OVERVIEW
876           pcre_get_named_substring()           pcre_get_named_substring()
877           pcre_get_substring_list()           pcre_get_substring_list()
878           pcre_get_stringnumber()           pcre_get_stringnumber()
879             pcre_get_stringtable_entries()
880    
881         pcre_free_substring() and pcre_free_substring_list() are also provided,         pcre_free_substring() and pcre_free_substring_list() are also provided,
882         to free the memory used for extracted strings.         to free the memory used for extracted strings.
# Line 723  PCRE API OVERVIEW Line 908  PCRE API OVERVIEW
908         indirections  to  memory  management functions. These special functions         indirections  to  memory  management functions. These special functions
909         are used only when PCRE is compiled to use  the  heap  for  remembering         are used only when PCRE is compiled to use  the  heap  for  remembering
910         data, instead of recursive function calls, when running the pcre_exec()         data, instead of recursive function calls, when running the pcre_exec()
911         function. This is a non-standard way of building PCRE, for use in envi-         function. See the pcrebuild documentation for  details  of  how  to  do
912         ronments that have limited stacks. Because of the greater use of memory         this.  It  is  a non-standard way of building PCRE, for use in environ-
913         management, it runs more slowly.  Separate functions  are  provided  so         ments that have limited stacks. Because of the greater  use  of  memory
914         that  special-purpose  external  code  can  be used for this case. When         management,  it  runs  more  slowly. Separate functions are provided so
915         used, these functions are always called in a  stack-like  manner  (last         that special-purpose external code can be  used  for  this  case.  When
916         obtained,  first freed), and always for memory blocks of the same size.         used,  these  functions  are always called in a stack-like manner (last
917           obtained, first freed), and always for memory blocks of the same  size.
918           There  is  a discussion about PCRE's stack usage in the pcrestack docu-
919           mentation.
920    
921         The global variable pcre_callout initially contains NULL. It can be set         The global variable pcre_callout initially contains NULL. It can be set
922         by  the  caller  to  a "callout" function, which PCRE will then call at         by  the  caller  to  a "callout" function, which PCRE will then call at
# Line 736  PCRE API OVERVIEW Line 924  PCRE API OVERVIEW
924         pcrecallout documentation.         pcrecallout documentation.
925    
926    
927    NEWLINES
928    
929           PCRE  supports five different conventions for indicating line breaks in
930           strings: a single CR (carriage return) character, a  single  LF  (line-
931           feed) character, the two-character sequence CRLF, any of the three pre-
932           ceding, or any Unicode newline sequence. The Unicode newline  sequences
933           are  the  three just mentioned, plus the single characters VT (vertical
934           tab, U+000B), FF (formfeed, U+000C), NEL (next line, U+0085), LS  (line
935           separator, U+2028), and PS (paragraph separator, U+2029).
936    
937           Each  of  the first three conventions is used by at least one operating
938           system as its standard newline sequence. When PCRE is built, a  default
939           can  be  specified.  The default default is LF, which is the Unix stan-
940           dard. When PCRE is run, the default can be overridden,  either  when  a
941           pattern is compiled, or when it is matched.
942    
943           At compile time, the newline convention can be specified by the options
944           argument of pcre_compile(), or it can be specified by special  text  at
945           the start of the pattern itself; this overrides any other settings. See
946           the pcrepattern page for details of the special character sequences.
947    
948           In the PCRE documentation the word "newline" is used to mean "the char-
949           acter  or pair of characters that indicate a line break". The choice of
950           newline convention affects the handling of  the  dot,  circumflex,  and
951           dollar metacharacters, the handling of #-comments in /x mode, and, when
952           CRLF is a recognized line ending sequence, the match position  advance-
953           ment for a non-anchored pattern. There is more detail about this in the
954           section on pcre_exec() options below.
955    
956           The choice of newline convention does not affect the interpretation  of
957           the  \n  or  \r  escape  sequences, nor does it affect what \R matches,
958           which is controlled in a similar way, but by separate options.
959    
960    
961  MULTITHREADING  MULTITHREADING
962    
963         The  PCRE  functions  can be used in multi-threading applications, with         The PCRE functions can be used in  multi-threading  applications,  with
964         the  proviso  that  the  memory  management  functions  pointed  to  by         the  proviso  that  the  memory  management  functions  pointed  to  by
965         pcre_malloc, pcre_free, pcre_stack_malloc, and pcre_stack_free, and the         pcre_malloc, pcre_free, pcre_stack_malloc, and pcre_stack_free, and the
966         callout function pointed to by pcre_callout, are shared by all threads.         callout function pointed to by pcre_callout, are shared by all threads.
967    
968         The  compiled form of a regular expression is not altered during match-         The compiled form of a regular expression is not altered during  match-
969         ing, so the same compiled pattern can safely be used by several threads         ing, so the same compiled pattern can safely be used by several threads
970         at once.         at once.
971    
# Line 751  MULTITHREADING Line 973  MULTITHREADING
973  SAVING PRECOMPILED PATTERNS FOR LATER USE  SAVING PRECOMPILED PATTERNS FOR LATER USE
974    
975         The compiled form of a regular expression can be saved and re-used at a         The compiled form of a regular expression can be saved and re-used at a
976         later time, possibly by a different program, and even on a  host  other         later  time,  possibly by a different program, and even on a host other
977         than  the  one  on  which  it  was  compiled.  Details are given in the         than the one on which  it  was  compiled.  Details  are  given  in  the
978         pcreprecompile documentation.         pcreprecompile  documentation.  However, compiling a regular expression
979           with one version of PCRE for use with a different version is not  guar-
980           anteed to work and may cause crashes.
981    
982    
983  CHECKING BUILD-TIME OPTIONS  CHECKING BUILD-TIME OPTIONS
984    
985         int pcre_config(int what, void *where);         int pcre_config(int what, void *where);
986    
987         The function pcre_config() makes it possible for a PCRE client to  dis-         The  function pcre_config() makes it possible for a PCRE client to dis-
988         cover which optional features have been compiled into the PCRE library.         cover which optional features have been compiled into the PCRE library.
989         The pcrebuild documentation has more details about these optional  fea-         The  pcrebuild documentation has more details about these optional fea-
990         tures.         tures.
991    
992         The  first  argument  for pcre_config() is an integer, specifying which         The first argument for pcre_config() is an  integer,  specifying  which
993         information is required; the second argument is a pointer to a variable         information is required; the second argument is a pointer to a variable
994         into  which  the  information  is  placed. The following information is         into which the information is  placed.  The  following  information  is
995         available:         available:
996    
997           PCRE_CONFIG_UTF8           PCRE_CONFIG_UTF8
998    
999         The output is an integer that is set to one if UTF-8 support is  avail-         The  output is an integer that is set to one if UTF-8 support is avail-
1000         able; otherwise it is set to zero.         able; otherwise it is set to zero.
1001    
1002           PCRE_CONFIG_UNICODE_PROPERTIES           PCRE_CONFIG_UNICODE_PROPERTIES
1003    
1004         The  output  is  an  integer  that is set to one if support for Unicode         The output is an integer that is set to  one  if  support  for  Unicode
1005         character properties is available; otherwise it is set to zero.         character properties is available; otherwise it is set to zero.
1006    
1007           PCRE_CONFIG_NEWLINE           PCRE_CONFIG_NEWLINE
1008    
1009         The output is an integer that is set to the value of the code  that  is         The  output  is  an integer whose value specifies the default character
1010         used  for the newline character. It is either linefeed (10) or carriage         sequence that is recognized as meaning "newline". The four values  that
1011         return (13), and should normally be the  standard  character  for  your         are supported are: 10 for LF, 13 for CR, 3338 for CRLF, -2 for ANYCRLF,
1012         operating system.         and -1 for ANY. The default should normally be  the  standard  sequence
1013           for your operating system.
1014    
1015             PCRE_CONFIG_BSR
1016    
1017           The output is an integer whose value indicates what character sequences
1018           the \R escape sequence matches by default. A value of 0 means  that  \R
1019           matches  any  Unicode  line ending sequence; a value of 1 means that \R
1020           matches only CR, LF, or CRLF. The default can be overridden when a pat-
1021           tern is compiled or matched.
1022    
1023           PCRE_CONFIG_LINK_SIZE           PCRE_CONFIG_LINK_SIZE
1024    
# Line 808  CHECKING BUILD-TIME OPTIONS Line 1041  CHECKING BUILD-TIME OPTIONS
1041         internal  matching  function  calls in a pcre_exec() execution. Further         internal  matching  function  calls in a pcre_exec() execution. Further
1042         details are given with pcre_exec() below.         details are given with pcre_exec() below.
1043    
1044             PCRE_CONFIG_MATCH_LIMIT_RECURSION
1045    
1046           The output is an integer that gives the default limit for the depth  of
1047           recursion  when calling the internal matching function in a pcre_exec()
1048           execution. Further details are given with pcre_exec() below.
1049    
1050           PCRE_CONFIG_STACKRECURSE           PCRE_CONFIG_STACKRECURSE
1051    
1052         The output is an integer that is set to one if internal recursion  when         The output is an integer that is set to one if internal recursion  when
# Line 840  COMPILING A PATTERN Line 1079  COMPILING A PATTERN
1079         obtained  via  pcre_malloc is returned. This contains the compiled code         obtained  via  pcre_malloc is returned. This contains the compiled code
1080         and related data. The pcre type is defined for the returned block; this         and related data. The pcre type is defined for the returned block; this
1081         is a typedef for a structure whose contents are not externally defined.         is a typedef for a structure whose contents are not externally defined.
1082         It is up to the caller  to  free  the  memory  when  it  is  no  longer         It is up to the caller to free the memory (via pcre_free) when it is no
1083         required.         longer required.
1084    
1085         Although  the compiled code of a PCRE regex is relocatable, that is, it         Although  the compiled code of a PCRE regex is relocatable, that is, it
1086         does not depend on memory location, the complete pcre data block is not         does not depend on memory location, the complete pcre data block is not
1087         fully  relocatable, because it may contain a copy of the tableptr argu-         fully  relocatable, because it may contain a copy of the tableptr argu-
1088         ment, which is an address (see below).         ment, which is an address (see below).
1089    
1090         The options argument contains independent bits that affect the compila-         The options argument contains various bit settings that affect the com-
1091         tion.  It  should  be  zero  if  no options are required. The available         pilation.  It  should be zero if no options are required. The available
1092         options are described below. Some of them, in  particular,  those  that         options are described below. Some of them, in  particular,  those  that
1093         are  compatible  with  Perl,  can also be set and unset from within the         are  compatible  with  Perl,  can also be set and unset from within the
1094         pattern (see the detailed description  in  the  pcrepattern  documenta-         pattern (see the detailed description  in  the  pcrepattern  documenta-
1095         tion).  For  these options, the contents of the options argument speci-         tion).  For  these options, the contents of the options argument speci-
1096         fies their initial settings at the start of compilation and  execution.         fies their initial settings at the start of compilation and  execution.
1097         The  PCRE_ANCHORED option can be set at the time of matching as well as         The  PCRE_ANCHORED  and PCRE_NEWLINE_xxx options can be set at the time
1098         at compile time.         of matching as well as at compile time.
1099    
1100         If errptr is NULL, pcre_compile() returns NULL immediately.  Otherwise,         If errptr is NULL, pcre_compile() returns NULL immediately.  Otherwise,
1101         if  compilation  of  a  pattern fails, pcre_compile() returns NULL, and         if  compilation  of  a  pattern fails, pcre_compile() returns NULL, and
1102         sets the variable pointed to by errptr to point to a textual error mes-         sets the variable pointed to by errptr to point to a textual error mes-
1103         sage.  The  offset from the start of the pattern to the character where         sage. This is a static string that is part of the library. You must not
1104         the error was discovered is  placed  in  the  variable  pointed  to  by         try to free it. The offset from the start of the pattern to the charac-
1105         erroffset,  which  must  not  be  NULL. If it is, an immediate error is         ter where the error was discovered is placed in the variable pointed to
1106           by erroffset, which must not be NULL. If it is, an immediate  error  is
1107         given.         given.
1108    
1109         If pcre_compile2() is used instead of pcre_compile(),  and  the  error-         If  pcre_compile2()  is  used instead of pcre_compile(), and the error-
1110         codeptr  argument is not NULL, a non-zero error code number is returned         codeptr argument is not NULL, a non-zero error code number is  returned
1111         via this argument in the event of an error. This is in addition to  the         via  this argument in the event of an error. This is in addition to the
1112         textual error message. Error codes and messages are listed below.         textual error message. Error codes and messages are listed below.
1113    
1114         If  the  final  argument, tableptr, is NULL, PCRE uses a default set of         If the final argument, tableptr, is NULL, PCRE uses a  default  set  of
1115         character tables that are  built  when  PCRE  is  compiled,  using  the         character  tables  that  are  built  when  PCRE  is compiled, using the
1116         default  C  locale.  Otherwise, tableptr must be an address that is the         default C locale. Otherwise, tableptr must be an address  that  is  the
1117         result of a call to pcre_maketables(). This value is  stored  with  the         result  of  a  call to pcre_maketables(). This value is stored with the
1118         compiled  pattern,  and used again by pcre_exec(), unless another table         compiled pattern, and used again by pcre_exec(), unless  another  table
1119         pointer is passed to it. For more discussion, see the section on locale         pointer is passed to it. For more discussion, see the section on locale
1120         support below.         support below.
1121    
1122         This  code  fragment  shows a typical straightforward call to pcre_com-         This code fragment shows a typical straightforward  call  to  pcre_com-
1123         pile():         pile():
1124    
1125           pcre *re;           pcre *re;
# Line 892  COMPILING A PATTERN Line 1132  COMPILING A PATTERN
1132             &erroffset,       /* for error offset */             &erroffset,       /* for error offset */
1133             NULL);            /* use default character tables */             NULL);            /* use default character tables */
1134    
1135         The following names for option bits are defined in  the  pcre.h  header         The  following  names  for option bits are defined in the pcre.h header
1136         file:         file:
1137    
1138           PCRE_ANCHORED           PCRE_ANCHORED
1139    
1140         If this bit is set, the pattern is forced to be "anchored", that is, it         If this bit is set, the pattern is forced to be "anchored", that is, it
1141         is constrained to match only at the first matching point in the  string         is  constrained to match only at the first matching point in the string
1142         that  is being searched (the "subject string"). This effect can also be         that is being searched (the "subject string"). This effect can also  be
1143         achieved by appropriate constructs in the pattern itself, which is  the         achieved  by appropriate constructs in the pattern itself, which is the
1144         only way to do it in Perl.         only way to do it in Perl.
1145    
1146           PCRE_AUTO_CALLOUT           PCRE_AUTO_CALLOUT
1147    
1148         If this bit is set, pcre_compile() automatically inserts callout items,         If this bit is set, pcre_compile() automatically inserts callout items,
1149         all with number 255, before each pattern item. For  discussion  of  the         all  with  number  255, before each pattern item. For discussion of the
1150         callout facility, see the pcrecallout documentation.         callout facility, see the pcrecallout documentation.
1151    
1152             PCRE_BSR_ANYCRLF
1153             PCRE_BSR_UNICODE
1154    
1155           These options (which are mutually exclusive) control what the \R escape
1156           sequence  matches.  The choice is either to match only CR, LF, or CRLF,
1157           or to match any Unicode newline sequence. The default is specified when
1158           PCRE is built. It can be overridden from within the pattern, or by set-
1159           ting an option when a compiled pattern is matched.
1160    
1161           PCRE_CASELESS           PCRE_CASELESS
1162    
1163         If  this  bit is set, letters in the pattern match both upper and lower         If this bit is set, letters in the pattern match both upper  and  lower
1164         case letters. It is equivalent to Perl's  /i  option,  and  it  can  be         case  letters.  It  is  equivalent  to  Perl's /i option, and it can be
1165         changed  within a pattern by a (?i) option setting. In UTF-8 mode, PCRE         changed within a pattern by a (?i) option setting. In UTF-8 mode,  PCRE
1166         always understands the concept of case for characters whose values  are         always  understands the concept of case for characters whose values are
1167         less  than 128, so caseless matching is always possible. For characters         less than 128, so caseless matching is always possible. For  characters
1168         with higher values, the concept of case is supported if  PCRE  is  com-         with  higher  values,  the concept of case is supported if PCRE is com-
1169         piled  with Unicode property support, but not otherwise. If you want to         piled with Unicode property support, but not otherwise. If you want  to
1170         use caseless matching for characters 128 and  above,  you  must  ensure         use  caseless  matching  for  characters 128 and above, you must ensure
1171         that  PCRE  is  compiled  with Unicode property support as well as with         that PCRE is compiled with Unicode property support  as  well  as  with
1172         UTF-8 support.         UTF-8 support.
1173    
1174           PCRE_DOLLAR_ENDONLY           PCRE_DOLLAR_ENDONLY
1175    
1176         If this bit is set, a dollar metacharacter in the pattern matches  only         If  this bit is set, a dollar metacharacter in the pattern matches only
1177         at  the  end  of the subject string. Without this option, a dollar also         at the end of the subject string. Without this option,  a  dollar  also
1178         matches immediately before the final character if it is a newline  (but         matches  immediately before a newline at the end of the string (but not
1179         not  before  any  other  newlines).  The  PCRE_DOLLAR_ENDONLY option is         before any other newlines). The PCRE_DOLLAR_ENDONLY option  is  ignored
1180         ignored if PCRE_MULTILINE is set. There is no equivalent to this option         if  PCRE_MULTILINE  is  set.   There is no equivalent to this option in
1181         in Perl, and no way to set it within a pattern.         Perl, and no way to set it within a pattern.
1182    
1183           PCRE_DOTALL           PCRE_DOTALL
1184    
1185         If this bit is set, a dot metacharater in the pattern matches all char-         If this bit is set, a dot metacharater in the pattern matches all char-
1186         acters, including newlines. Without it,  newlines  are  excluded.  This         acters,  including  those that indicate newline. Without it, a dot does
1187         option  is equivalent to Perl's /s option, and it can be changed within         not match when the current position is at a  newline.  This  option  is
1188         a pattern by a (?s) option setting.  A  negative  class  such  as  [^a]         equivalent  to Perl's /s option, and it can be changed within a pattern
1189         always  matches a newline character, independent of the setting of this         by a (?s) option setting. A negative class such as [^a] always  matches
1190         option.         newline characters, independent of the setting of this option.
1191    
1192             PCRE_DUPNAMES
1193    
1194           If  this  bit is set, names used to identify capturing subpatterns need
1195           not be unique. This can be helpful for certain types of pattern when it
1196           is  known  that  only  one instance of the named subpattern can ever be
1197           matched. There are more details of named subpatterns  below;  see  also
1198           the pcrepattern documentation.
1199    
1200           PCRE_EXTENDED           PCRE_EXTENDED
1201    
1202         If this bit is set, whitespace  data  characters  in  the  pattern  are         If  this  bit  is  set,  whitespace  data characters in the pattern are
1203         totally ignored except when escaped or inside a character class. White-         totally ignored except when escaped or inside a character class. White-
1204         space does not include the VT character (code 11). In addition, charac-         space does not include the VT character (code 11). In addition, charac-
1205         ters between an unescaped # outside a character class and the next new-         ters between an unescaped # outside a character class and the next new-
1206         line character, inclusive, are also  ignored.  This  is  equivalent  to         line,  inclusive,  are  also  ignored.  This is equivalent to Perl's /x
1207         Perl's  /x  option,  and  it  can be changed within a pattern by a (?x)         option, and it can be changed within a pattern by a  (?x)  option  set-
1208         option setting.         ting.
1209    
1210         This option makes it possible to include  comments  inside  complicated         This  option  makes  it possible to include comments inside complicated
1211         patterns.   Note,  however,  that this applies only to data characters.         patterns.  Note, however, that this applies only  to  data  characters.
1212         Whitespace  characters  may  never  appear  within  special   character         Whitespace   characters  may  never  appear  within  special  character
1213         sequences  in  a  pattern,  for  example  within the sequence (?( which         sequences in a pattern, for  example  within  the  sequence  (?(  which
1214         introduces a conditional subpattern.         introduces a conditional subpattern.
1215    
1216           PCRE_EXTRA           PCRE_EXTRA
1217    
1218         This option was invented in order to turn on  additional  functionality         This  option  was invented in order to turn on additional functionality
1219         of  PCRE  that  is  incompatible with Perl, but it is currently of very         of PCRE that is incompatible with Perl, but it  is  currently  of  very
1220         little use. When set, any backslash in a pattern that is followed by  a         little  use. When set, any backslash in a pattern that is followed by a
1221         letter  that  has  no  special  meaning causes an error, thus reserving         letter that has no special meaning  causes  an  error,  thus  reserving
1222         these combinations for future expansion. By  default,  as  in  Perl,  a         these  combinations  for  future  expansion.  By default, as in Perl, a
1223         backslash  followed by a letter with no special meaning is treated as a         backslash followed by a letter with no special meaning is treated as  a
1224         literal. There are at present no  other  features  controlled  by  this         literal.  (Perl can, however, be persuaded to give a warning for this.)
1225         option. It can also be set by a (?X) option setting within a pattern.         There are at present no other features controlled by  this  option.  It
1226           can also be set by a (?X) option setting within a pattern.
1227    
1228           PCRE_FIRSTLINE           PCRE_FIRSTLINE
1229    
1230         If  this  option  is  set,  an  unanchored pattern is required to match         If  this  option  is  set,  an  unanchored pattern is required to match
1231         before or at the first newline character in the subject string,  though         before or at the first  newline  in  the  subject  string,  though  the
1232         the matched text may continue over the newline.         matched text may continue over the newline.
1233    
1234           PCRE_MULTILINE           PCRE_MULTILINE
1235    
# Line 983  COMPILING A PATTERN Line 1241  COMPILING A PATTERN
1241         is set). This is the same as Perl.         is set). This is the same as Perl.
1242    
1243         When PCRE_MULTILINE it is set, the "start of line" and  "end  of  line"         When PCRE_MULTILINE it is set, the "start of line" and  "end  of  line"
1244         constructs  match  immediately following or immediately before any new-         constructs  match  immediately following or immediately before internal
1245         line in the subject string, respectively, as well as at the very  start         newlines in the subject string, respectively, as well as  at  the  very
1246         and  end. This is equivalent to Perl's /m option, and it can be changed         start  and  end.  This is equivalent to Perl's /m option, and it can be
1247         within a pattern by a (?m) option setting. If there are no "\n" charac-         changed within a pattern by a (?m) option setting. If there are no new-
1248         ters  in  a  subject  string, or no occurrences of ^ or $ in a pattern,         lines  in  a  subject string, or no occurrences of ^ or $ in a pattern,
1249         setting PCRE_MULTILINE has no effect.         setting PCRE_MULTILINE has no effect.
1250    
1251             PCRE_NEWLINE_CR
1252             PCRE_NEWLINE_LF
1253             PCRE_NEWLINE_CRLF
1254             PCRE_NEWLINE_ANYCRLF
1255             PCRE_NEWLINE_ANY
1256    
1257           These options override the default newline definition that  was  chosen
1258           when  PCRE  was built. Setting the first or the second specifies that a
1259           newline is indicated by a single character (CR  or  LF,  respectively).
1260           Setting  PCRE_NEWLINE_CRLF specifies that a newline is indicated by the
1261           two-character CRLF  sequence.  Setting  PCRE_NEWLINE_ANYCRLF  specifies
1262           that any of the three preceding sequences should be recognized. Setting
1263           PCRE_NEWLINE_ANY specifies that any Unicode newline sequence should  be
1264           recognized. The Unicode newline sequences are the three just mentioned,
1265           plus the single characters VT (vertical  tab,  U+000B),  FF  (formfeed,
1266           U+000C),  NEL  (next line, U+0085), LS (line separator, U+2028), and PS
1267           (paragraph separator, U+2029). The last  two  are  recognized  only  in
1268           UTF-8 mode.
1269    
1270           The  newline  setting  in  the  options  word  uses three bits that are
1271           treated as a number, giving eight possibilities. Currently only six are
1272           used  (default  plus the five values above). This means that if you set
1273           more than one newline option, the combination may or may not be  sensi-
1274           ble. For example, PCRE_NEWLINE_CR with PCRE_NEWLINE_LF is equivalent to
1275           PCRE_NEWLINE_CRLF, but other combinations may yield unused numbers  and
1276           cause an error.
1277    
1278           The  only time that a line break is specially recognized when compiling
1279           a pattern is if PCRE_EXTENDED is set, and  an  unescaped  #  outside  a
1280           character  class  is  encountered.  This indicates a comment that lasts
1281           until after the next line break sequence. In other circumstances,  line
1282           break   sequences   are   treated  as  literal  data,  except  that  in
1283           PCRE_EXTENDED mode, both CR and LF are treated as whitespace characters
1284           and are therefore ignored.
1285    
1286           The newline option that is set at compile time becomes the default that
1287           is used for pcre_exec() and pcre_dfa_exec(), but it can be  overridden.
1288    
1289           PCRE_NO_AUTO_CAPTURE           PCRE_NO_AUTO_CAPTURE
1290    
1291         If this option is set, it disables the use of numbered capturing paren-         If this option is set, it disables the use of numbered capturing paren-
1292         theses  in the pattern. Any opening parenthesis that is not followed by         theses in the pattern. Any opening parenthesis that is not followed  by
1293         ? behaves as if it were followed by ?: but named parentheses can  still         ?  behaves as if it were followed by ?: but named parentheses can still
1294         be  used  for  capturing  (and  they acquire numbers in the usual way).         be used for capturing (and they acquire  numbers  in  the  usual  way).
1295         There is no equivalent of this option in Perl.         There is no equivalent of this option in Perl.
1296    
1297           PCRE_UNGREEDY           PCRE_UNGREEDY
1298    
1299         This option inverts the "greediness" of the quantifiers  so  that  they         This  option  inverts  the "greediness" of the quantifiers so that they
1300         are  not greedy by default, but become greedy if followed by "?". It is         are not greedy by default, but become greedy if followed by "?". It  is
1301         not compatible with Perl. It can also be set by a (?U)  option  setting         not  compatible  with Perl. It can also be set by a (?U) option setting
1302         within the pattern.         within the pattern.
1303    
1304           PCRE_UTF8           PCRE_UTF8
1305    
1306         This  option  causes PCRE to regard both the pattern and the subject as         This option causes PCRE to regard both the pattern and the  subject  as
1307         strings of UTF-8 characters instead of single-byte  character  strings.         strings  of  UTF-8 characters instead of single-byte character strings.
1308         However,  it is available only when PCRE is built to include UTF-8 sup-         However, it is available only when PCRE is built to include UTF-8  sup-
1309         port. If not, the use of this option provokes an error. Details of  how         port.  If not, the use of this option provokes an error. Details of how
1310         this  option  changes the behaviour of PCRE are given in the section on         this option changes the behaviour of PCRE are given in the  section  on
1311         UTF-8 support in the main pcre page.         UTF-8 support in the main pcre page.
1312    
1313           PCRE_NO_UTF8_CHECK           PCRE_NO_UTF8_CHECK
1314    
1315         When PCRE_UTF8 is set, the validity of the pattern as a UTF-8 string is         When PCRE_UTF8 is set, the validity of the pattern as a UTF-8 string is
1316         automatically  checked. If an invalid UTF-8 sequence of bytes is found,         automatically checked. There is a  discussion  about  the  validity  of
1317         pcre_compile() returns an error. If you already know that your  pattern         UTF-8  strings  in  the main pcre page. If an invalid UTF-8 sequence of
1318         is  valid, and you want to skip this check for performance reasons, you         bytes is found, pcre_compile() returns an error. If  you  already  know
1319         can set the PCRE_NO_UTF8_CHECK option. When it is set,  the  effect  of         that your pattern is valid, and you want to skip this check for perfor-
1320         passing an invalid UTF-8 string as a pattern is undefined. It may cause         mance reasons, you can set the PCRE_NO_UTF8_CHECK option.  When  it  is
1321         your program to crash.  Note that this option can  also  be  passed  to         set,  the  effect  of  passing  an invalid UTF-8 string as a pattern is
1322         pcre_exec()  and pcre_dfa_exec(), to suppress the UTF-8 validity check-         undefined. It may cause your program to crash. Note  that  this  option
1323         ing of subject strings.         can  also be passed to pcre_exec() and pcre_dfa_exec(), to suppress the
1324           UTF-8 validity checking of subject strings.
1325    
1326    
1327  COMPILATION ERROR CODES  COMPILATION ERROR CODES
1328    
1329         The following table lists the error  codes  than  may  be  returned  by         The following table lists the error  codes  than  may  be  returned  by
1330         pcre_compile2(),  along with the error messages that may be returned by         pcre_compile2(),  along with the error messages that may be returned by
1331         both compiling functions.         both compiling functions. As PCRE has developed, some error codes  have
1332           fallen out of use. To avoid confusion, they have not been re-used.
1333    
1334            0  no error            0  no error
1335            1  \ at end of pattern            1  \ at end of pattern
# Line 1043  COMPILATION ERROR CODES Line 1341  COMPILATION ERROR CODES
1341            7  invalid escape sequence in character class            7  invalid escape sequence in character class
1342            8  range out of order in character class            8  range out of order in character class
1343            9  nothing to repeat            9  nothing to repeat
1344           10  operand of unlimited repeat could match the empty string           10  [this code is not in use]
1345           11  internal error: unexpected repeat           11  internal error: unexpected repeat
1346           12  unrecognized character after (?           12  unrecognized character after (?
1347           13  POSIX named classes are supported only within a class           13  POSIX named classes are supported only within a class
# Line 1052  COMPILATION ERROR CODES Line 1350  COMPILATION ERROR CODES
1350           16  erroffset passed as NULL           16  erroffset passed as NULL
1351           17  unknown option bit(s) set           17  unknown option bit(s) set
1352           18  missing ) after comment           18  missing ) after comment
1353           19  parentheses nested too deeply           19  [this code is not in use]
1354           20  regular expression too large           20  regular expression too large
1355           21  failed to get memory           21  failed to get memory
1356           22  unmatched parentheses           22  unmatched parentheses
1357           23  internal error: code overflow           23  internal error: code overflow
1358           24  unrecognized character after (?<           24  unrecognized character after (?<
1359           25  lookbehind assertion is not fixed length           25  lookbehind assertion is not fixed length
1360           26  malformed number after (?(           26  malformed number or name after (?(
1361           27  conditional group contains more than two branches           27  conditional group contains more than two branches
1362           28  assertion expected after (?(           28  assertion expected after (?(
1363           29  (?R or (?digits must be followed by )           29  (?R or (?[+-]digits must be followed by )
1364           30  unknown POSIX class name           30  unknown POSIX class name
1365           31  POSIX collating elements are not supported           31  POSIX collating elements are not supported
1366           32  this version of PCRE is not compiled with PCRE_UTF8 support           32  this version of PCRE is not compiled with PCRE_UTF8 support
1367           33  spare error           33  [this code is not in use]
1368           34  character value in \x{...} sequence is too large           34  character value in \x{...} sequence is too large
1369           35  invalid condition (?(0)           35  invalid condition (?(0)
1370           36  \C not allowed in lookbehind assertion           36  \C not allowed in lookbehind assertion
# Line 1075  COMPILATION ERROR CODES Line 1373  COMPILATION ERROR CODES
1373           39  closing ) for (?C expected           39  closing ) for (?C expected
1374           40  recursive call could loop indefinitely           40  recursive call could loop indefinitely
1375           41  unrecognized character after (?P           41  unrecognized character after (?P
1376           42  syntax error after (?P           42  syntax error in subpattern name (missing terminator)
1377           43  two named groups have the same name           43  two named subpatterns have the same name
1378           44  invalid UTF-8 string           44  invalid UTF-8 string
1379           45  support for \P, \p, and \X has not been compiled           45  support for \P, \p, and \X has not been compiled
1380           46  malformed \P or \p sequence           46  malformed \P or \p sequence
1381           47  unknown property name after \P or \p           47  unknown property name after \P or \p
1382             48  subpattern name is too long (maximum 32 characters)
1383             49  too many named subpatterns (maximum 10,000)
1384             50  [this code is not in use]
1385             51  octal value is greater than \377 (not in UTF-8 mode)
1386             52  internal error: overran compiling workspace
1387             53   internal  error:  previously-checked  referenced  subpattern not
1388           found
1389             54  DEFINE group contains more than one branch
1390             55  repeating a DEFINE group is not allowed
1391             56  inconsistent NEWLINE options
1392             57  \g is not followed by a braced name or an optionally braced
1393                   non-zero number
1394             58  (?+ or (?- or (?(+ or (?(- must be followed by a non-zero number
1395    
1396    
1397  STUDYING A PATTERN  STUDYING A PATTERN
# Line 1111  STUDYING A PATTERN Line 1422  STUDYING A PATTERN
1422    
1423         The  third argument for pcre_study() is a pointer for an error message.         The  third argument for pcre_study() is a pointer for an error message.
1424         If studying succeeds (even if no data is  returned),  the  variable  it         If studying succeeds (even if no data is  returned),  the  variable  it
1425         points  to  is set to NULL. Otherwise it points to a textual error mes-         points  to  is  set  to NULL. Otherwise it is set to point to a textual
1426         sage. You should therefore test the error pointer for NULL after  call-         error message. This is a static string that is part of the library. You
1427         ing pcre_study(), to be sure that it has run successfully.         must  not  try  to  free it. You should test the error pointer for NULL
1428           after calling pcre_study(), to be sure that it has run successfully.
1429    
1430         This is a typical call to pcre_study():         This is a typical call to pcre_study():
1431    
# Line 1124  STUDYING A PATTERN Line 1436  STUDYING A PATTERN
1436             &error);        /* set to NULL or points to a message */             &error);        /* set to NULL or points to a message */
1437    
1438         At present, studying a pattern is useful only for non-anchored patterns         At present, studying a pattern is useful only for non-anchored patterns
1439         that do not have a single fixed starting character. A bitmap of  possi-         that  do not have a single fixed starting character. A bitmap of possi-
1440         ble starting bytes is created.         ble starting bytes is created.
1441    
1442    
1443  LOCALE SUPPORT  LOCALE SUPPORT
1444    
1445         PCRE  handles  caseless matching, and determines whether characters are         PCRE handles caseless matching, and determines whether  characters  are
1446         letters digits, or whatever, by reference to a set of  tables,  indexed         letters,  digits, or whatever, by reference to a set of tables, indexed
1447         by  character  value.  When running in UTF-8 mode, this applies only to         by character value. When running in UTF-8 mode, this  applies  only  to
1448         characters with codes less than 128. Higher-valued  codes  never  match         characters  with  codes  less than 128. Higher-valued codes never match
1449         escapes  such  as  \w or \d, but can be tested with \p if PCRE is built         escapes such as \w or \d, but can be tested with \p if  PCRE  is  built
1450         with Unicode character property support.         with  Unicode  character property support. The use of locales with Uni-
1451           code is discouraged. If you are handling characters with codes  greater
1452         An internal set of tables is created in the default C locale when  PCRE         than  128, you should either use UTF-8 and Unicode, or use locales, but
1453         is  built.  This  is  used when the final argument of pcre_compile() is         not try to mix the two.
1454         NULL, and is sufficient for many applications. An  alternative  set  of  
1455         tables  can,  however, be supplied. These may be created in a different         PCRE contains an internal set of tables that are used  when  the  final
1456         locale from the default. As more and more applications change to  using         argument  of  pcre_compile()  is  NULL.  These  are sufficient for many
1457         Unicode, the need for this locale support is expected to die away.         applications.  Normally, the internal tables recognize only ASCII char-
1458           acters. However, when PCRE is built, it is possible to cause the inter-
1459         External  tables  are  built by calling the pcre_maketables() function,         nal tables to be rebuilt in the default "C" locale of the local system,
1460         which has no arguments, in the relevant locale. The result can then  be         which may cause them to be different.
1461         passed  to  pcre_compile()  or  pcre_exec()  as often as necessary. For  
1462         example, to build and use tables that are appropriate  for  the  French         The  internal tables can always be overridden by tables supplied by the
1463         locale  (where  accented  characters  with  values greater than 128 are         application that calls PCRE. These may be created in a different locale
1464           from  the  default.  As more and more applications change to using Uni-
1465           code, the need for this locale support is expected to die away.
1466    
1467           External tables are built by calling  the  pcre_maketables()  function,
1468           which  has no arguments, in the relevant locale. The result can then be
1469           passed to pcre_compile() or pcre_exec()  as  often  as  necessary.  For
1470           example,  to  build  and use tables that are appropriate for the French
1471           locale (where accented characters with  values  greater  than  128  are
1472         treated as letters), the following code could be used:         treated as letters), the following code could be used:
1473    
1474           setlocale(LC_CTYPE, "fr_FR");           setlocale(LC_CTYPE, "fr_FR");
1475           tables = pcre_maketables();           tables = pcre_maketables();
1476           re = pcre_compile(..., tables);           re = pcre_compile(..., tables);
1477    
1478           The  locale  name "fr_FR" is used on Linux and other Unix-like systems;
1479           if you are using Windows, the name for the French locale is "french".
1480    
1481         When pcre_maketables() runs, the tables are built  in  memory  that  is         When pcre_maketables() runs, the tables are built  in  memory  that  is
1482         obtained  via  pcre_malloc. It is the caller's responsibility to ensure         obtained  via  pcre_malloc. It is the caller's responsibility to ensure
1483         that the memory containing the tables remains available for as long  as         that the memory containing the tables remains available for as long  as
# Line 1200  INFORMATION ABOUT A PATTERN Line 1523  INFORMATION ABOUT A PATTERN
1523         pattern:         pattern:
1524    
1525           int rc;           int rc;
1526           unsigned long int length;           size_t length;
1527           rc = pcre_fullinfo(           rc = pcre_fullinfo(
1528             re,               /* result of pcre_compile() */             re,               /* result of pcre_compile() */
1529             pe,               /* result of pcre_study(), or NULL */             pe,               /* result of pcre_study(), or NULL */
# Line 1232  INFORMATION ABOUT A PATTERN Line 1555  INFORMATION ABOUT A PATTERN
1555           PCRE_INFO_FIRSTBYTE           PCRE_INFO_FIRSTBYTE
1556    
1557         Return  information  about  the first byte of any matched string, for a         Return  information  about  the first byte of any matched string, for a
1558         non-anchored   pattern.   (This    option    used    to    be    called         non-anchored pattern. The fourth argument should point to an int  vari-
1559         PCRE_INFO_FIRSTCHAR;  the  old  name  is still recognized for backwards         able.  (This option used to be called PCRE_INFO_FIRSTCHAR; the old name
1560         compatibility.)         is still recognized for backwards compatibility.)
1561    
1562         If there is a fixed first byte, for example, from  a  pattern  such  as         If there is a fixed first byte, for example, from  a  pattern  such  as
1563         (cat|cow|coyote),  it  is  returned in the integer pointed to by where.         (cat|cow|coyote), its value is returned. Otherwise, if either
        Otherwise, if either  
1564    
1565         (a) the pattern was compiled with the PCRE_MULTILINE option, and  every         (a)  the pattern was compiled with the PCRE_MULTILINE option, and every
1566         branch starts with "^", or         branch starts with "^", or
1567    
1568         (b) every branch of the pattern starts with ".*" and PCRE_DOTALL is not         (b) every branch of the pattern starts with ".*" and PCRE_DOTALL is not
1569         set (if it were set, the pattern would be anchored),         set (if it were set, the pattern would be anchored),
1570    
1571         -1 is returned, indicating that the pattern matches only at  the  start         -1  is  returned, indicating that the pattern matches only at the start
1572         of  a  subject string or after any newline within the string. Otherwise         of a subject string or after any newline within the  string.  Otherwise
1573         -2 is returned. For anchored patterns, -2 is returned.         -2 is returned. For anchored patterns, -2 is returned.
1574    
1575           PCRE_INFO_FIRSTTABLE           PCRE_INFO_FIRSTTABLE
1576    
1577         If the pattern was studied, and this resulted in the construction of  a         If  the pattern was studied, and this resulted in the construction of a
1578         256-bit table indicating a fixed set of bytes for the first byte in any         256-bit table indicating a fixed set of bytes for the first byte in any
1579         matching string, a pointer to the table is returned. Otherwise NULL  is         matching  string, a pointer to the table is returned. Otherwise NULL is
1580         returned.  The fourth argument should point to an unsigned char * vari-         returned. The fourth argument should point to an unsigned char *  vari-
1581         able.         able.
1582    
1583             PCRE_INFO_HASCRORLF
1584    
1585           Return  1  if  the  pattern  contains any explicit matches for CR or LF
1586           characters, otherwise 0. The fourth argument should  point  to  an  int
1587           variable.  An explicit match is either a literal CR or LF character, or
1588           \r or \n.
1589    
1590             PCRE_INFO_JCHANGED
1591    
1592           Return 1 if the (?J) or (?-J) option setting is used  in  the  pattern,
1593           otherwise  0. The fourth argument should point to an int variable. (?J)
1594           and (?-J) set and unset the local PCRE_DUPNAMES option, respectively.
1595    
1596           PCRE_INFO_LASTLITERAL           PCRE_INFO_LASTLITERAL
1597    
1598         Return the value of the rightmost literal byte that must exist  in  any         Return the value of the rightmost literal byte that must exist  in  any
# Line 1274  INFORMATION ABOUT A PATTERN Line 1609  INFORMATION ABOUT A PATTERN
1609    
1610         PCRE supports the use of named as well as numbered capturing  parenthe-         PCRE supports the use of named as well as numbered capturing  parenthe-
1611         ses.  The names are just an additional way of identifying the parenthe-         ses.  The names are just an additional way of identifying the parenthe-
1612         ses,  which  still  acquire  numbers.  A  convenience  function  called         ses, which still acquire numbers. Several convenience functions such as
1613         pcre_get_named_substring()  is  provided  for  extracting an individual         pcre_get_named_substring()  are  provided  for extracting captured sub-
1614         captured substring by name. It is also possible  to  extract  the  data         strings by name. It is also possible to extract the data  directly,  by
1615         directly,  by  first converting the name to a number in order to access         first  converting  the  name to a number in order to access the correct
1616         the correct pointers in the output vector (described  with  pcre_exec()         pointers in the output vector (described with pcre_exec() below). To do
1617         below).  To  do the conversion, you need to use the name-to-number map,         the  conversion,  you  need  to  use  the  name-to-number map, which is
1618         which is described by these three values.         described by these three values.
1619    
1620         The map consists of a number of fixed-size entries. PCRE_INFO_NAMECOUNT         The map consists of a number of fixed-size entries. PCRE_INFO_NAMECOUNT
1621         gives the number of entries, and PCRE_INFO_NAMEENTRYSIZE gives the size         gives the number of entries, and PCRE_INFO_NAMEENTRYSIZE gives the size
# Line 1290  INFORMATION ABOUT A PATTERN Line 1625  INFORMATION ABOUT A PATTERN
1625         first two bytes of each entry are the number of the capturing parenthe-         first two bytes of each entry are the number of the capturing parenthe-
1626         sis, most significant byte first. The rest of the entry is  the  corre-         sis, most significant byte first. The rest of the entry is  the  corre-
1627         sponding  name,  zero  terminated. The names are in alphabetical order.         sponding  name,  zero  terminated. The names are in alphabetical order.
1628         For example, consider the following pattern  (assume  PCRE_EXTENDED  is         When PCRE_DUPNAMES is set, duplicate names are in order of their paren-
1629         set, so white space - including newlines - is ignored):         theses  numbers.  For  example,  consider the following pattern (assume
1630           PCRE_EXTENDED is  set,  so  white  space  -  including  newlines  -  is
1631           ignored):
1632    
1633           (?P<date> (?P<year>(\d\d)?\d\d) -           (?<date> (?<year>(\d\d)?\d\d) -
1634           (?P<month>\d\d) - (?P<day>\d\d) )           (?<month>\d\d) - (?<day>\d\d) )
1635    
1636         There  are  four  named subpatterns, so the table has four entries, and         There  are  four  named subpatterns, so the table has four entries, and
1637         each entry in the table is eight bytes long. The table is  as  follows,         each entry in the table is eight bytes long. The table is  as  follows,
# Line 1307  INFORMATION ABOUT A PATTERN Line 1644  INFORMATION ABOUT A PATTERN
1644           00 02 y  e  a  r  00 ??           00 02 y  e  a  r  00 ??
1645    
1646         When writing code to extract data  from  named  subpatterns  using  the         When writing code to extract data  from  named  subpatterns  using  the
1647         name-to-number map, remember that the length of each entry is likely to         name-to-number  map,  remember that the length of the entries is likely
1648         be different for each compiled pattern.         to be different for each compiled pattern.
1649    
1650             PCRE_INFO_OKPARTIAL
1651    
1652           Return 1 if the pattern can be used for partial matching, otherwise  0.
1653           The  fourth  argument  should point to an int variable. The pcrepartial
1654           documentation lists the restrictions that apply to patterns  when  par-
1655           tial matching is used.
1656    
1657           PCRE_INFO_OPTIONS           PCRE_INFO_OPTIONS
1658    
1659         Return a copy of the options with which the pattern was  compiled.  The         Return  a  copy of the options with which the pattern was compiled. The
1660         fourth  argument  should  point to an unsigned long int variable. These         fourth argument should point to an unsigned long  int  variable.  These
1661         option bits are those specified in the call to pcre_compile(), modified         option bits are those specified in the call to pcre_compile(), modified
1662         by any top-level option settings within the pattern itself.         by any top-level option settings at the start of the pattern itself. In
1663           other  words,  they are the options that will be in force when matching
1664           starts. For example, if the pattern /(?im)abc(?-i)d/ is  compiled  with
1665           the  PCRE_EXTENDED option, the result is PCRE_CASELESS, PCRE_MULTILINE,
1666           and PCRE_EXTENDED.
1667    
1668         A  pattern  is  automatically  anchored by PCRE if all of its top-level         A pattern is automatically anchored by PCRE if  all  of  its  top-level
1669         alternatives begin with one of the following:         alternatives begin with one of the following:
1670    
1671           ^     unless PCRE_MULTILINE is set           ^     unless PCRE_MULTILINE is set
# Line 1331  INFORMATION ABOUT A PATTERN Line 1679  INFORMATION ABOUT A PATTERN
1679    
1680           PCRE_INFO_SIZE           PCRE_INFO_SIZE
1681    
1682         Return  the  size  of the compiled pattern, that is, the value that was         Return the size of the compiled pattern, that is, the  value  that  was
1683         passed as the argument to pcre_malloc() when PCRE was getting memory in         passed as the argument to pcre_malloc() when PCRE was getting memory in
1684         which to place the compiled data. The fourth argument should point to a         which to place the compiled data. The fourth argument should point to a
1685         size_t variable.         size_t variable.
# Line 1339  INFORMATION ABOUT A PATTERN Line 1687  INFORMATION ABOUT A PATTERN
1687           PCRE_INFO_STUDYSIZE           PCRE_INFO_STUDYSIZE
1688    
1689         Return the size of the data block pointed to by the study_data field in         Return the size of the data block pointed to by the study_data field in
1690         a  pcre_extra  block.  That  is,  it  is  the  value that was passed to         a pcre_extra block. That is,  it  is  the  value  that  was  passed  to
1691         pcre_malloc() when PCRE was getting memory into which to place the data         pcre_malloc() when PCRE was getting memory into which to place the data
1692         created  by  pcre_study(). The fourth argument should point to a size_t         created by pcre_study(). The fourth argument should point to  a  size_t
1693         variable.         variable.
1694    
1695    
# Line 1349  OBSOLETE INFO FUNCTION Line 1697  OBSOLETE INFO FUNCTION
1697    
1698         int pcre_info(const pcre *code, int *optptr, int *firstcharptr);         int pcre_info(const pcre *code, int *optptr, int *firstcharptr);
1699    
1700         The pcre_info() function is now obsolete because its interface  is  too         The  pcre_info()  function is now obsolete because its interface is too
1701         restrictive  to return all the available data about a compiled pattern.         restrictive to return all the available data about a compiled  pattern.
1702         New  programs  should  use  pcre_fullinfo()  instead.  The   yield   of         New   programs   should  use  pcre_fullinfo()  instead.  The  yield  of
1703         pcre_info()  is the number of capturing subpatterns, or one of the fol-         pcre_info() is the number of capturing subpatterns, or one of the  fol-
1704         lowing negative numbers:         lowing negative numbers:
1705    
1706           PCRE_ERROR_NULL       the argument code was NULL           PCRE_ERROR_NULL       the argument code was NULL
1707           PCRE_ERROR_BADMAGIC   the "magic number" was not found           PCRE_ERROR_BADMAGIC   the "magic number" was not found
1708    
1709         If the optptr argument is not NULL, a copy of the  options  with  which         If  the  optptr  argument is not NULL, a copy of the options with which
1710         the  pattern  was  compiled  is placed in the integer it points to (see         the pattern was compiled is placed in the integer  it  points  to  (see
1711         PCRE_INFO_OPTIONS above).         PCRE_INFO_OPTIONS above).
1712    
1713         If the pattern is not anchored and the  firstcharptr  argument  is  not         If  the  pattern  is  not anchored and the firstcharptr argument is not
1714         NULL,  it is used to pass back information about the first character of         NULL, it is used to pass back information about the first character  of
1715         any matched string (see PCRE_INFO_FIRSTBYTE above).         any matched string (see PCRE_INFO_FIRSTBYTE above).
1716    
1717    
# Line 1371  REFERENCE COUNTS Line 1719  REFERENCE COUNTS
1719    
1720         int pcre_refcount(pcre *code, int adjust);         int pcre_refcount(pcre *code, int adjust);
1721    
1722         The pcre_refcount() function is used to maintain a reference  count  in         The  pcre_refcount()  function is used to maintain a reference count in
1723         the data block that contains a compiled pattern. It is provided for the         the data block that contains a compiled pattern. It is provided for the
1724         benefit of applications that  operate  in  an  object-oriented  manner,         benefit  of  applications  that  operate  in an object-oriented manner,
1725         where different parts of the application may be using the same compiled         where different parts of the application may be using the same compiled
1726         pattern, but you want to free the block when they are all done.         pattern, but you want to free the block when they are all done.
1727    
1728         When a pattern is compiled, the reference count field is initialized to         When a pattern is compiled, the reference count field is initialized to
1729         zero.   It is changed only by calling this function, whose action is to         zero.  It is changed only by calling this function, whose action is  to
1730         add the adjust value (which may be positive or  negative)  to  it.  The         add  the  adjust  value  (which may be positive or negative) to it. The
1731         yield of the function is the new value. However, the value of the count         yield of the function is the new value. However, the value of the count
1732         is constrained to lie between 0 and 65535, inclusive. If the new  value         is  constrained to lie between 0 and 65535, inclusive. If the new value
1733         is outside these limits, it is forced to the appropriate limit value.         is outside these limits, it is forced to the appropriate limit value.
1734    
1735         Except  when it is zero, the reference count is not correctly preserved         Except when it is zero, the reference count is not correctly  preserved
1736         if a pattern is compiled on one host and then  transferred  to  a  host         if  a  pattern  is  compiled on one host and then transferred to a host
1737         whose byte-order is different. (This seems a highly unlikely scenario.)         whose byte-order is different. (This seems a highly unlikely scenario.)
1738    
1739    
# Line 1395  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1743  MATCHING A PATTERN: THE TRADITIONAL FUNC
1743              const char *subject, int length, int startoffset,              const char *subject, int length, int startoffset,
1744              int options, int *ovector, int ovecsize);              int options, int *ovector, int ovecsize);
1745    
1746         The function pcre_exec() is called to match a subject string against  a         The  function pcre_exec() is called to match a subject string against a
1747         compiled  pattern, which is passed in the code argument. If the pattern         compiled pattern, which is passed in the code argument. If the  pattern
1748         has been studied, the result of the study should be passed in the extra         has been studied, the result of the study should be passed in the extra
1749         argument.  This  function is the main matching facility of the library,         argument. This function is the main matching facility of  the  library,
1750         and it operates in a Perl-like manner. For specialist use there is also         and it operates in a Perl-like manner. For specialist use there is also
1751         an  alternative matching function, which is described below in the sec-         an alternative matching function, which is described below in the  sec-
1752         tion about the pcre_dfa_exec() function.         tion about the pcre_dfa_exec() function.
1753    
1754         In most applications, the pattern will have been compiled (and  option-         In  most applications, the pattern will have been compiled (and option-
1755         ally  studied)  in the same process that calls pcre_exec(). However, it         ally studied) in the same process that calls pcre_exec().  However,  it
1756         is possible to save compiled patterns and study data, and then use them         is possible to save compiled patterns and study data, and then use them
1757         later  in  different processes, possibly even on different hosts. For a         later in different processes, possibly even on different hosts.  For  a
1758         discussion about this, see the pcreprecompile documentation.         discussion about this, see the pcreprecompile documentation.
1759    
1760         Here is an example of a simple call to pcre_exec():         Here is an example of a simple call to pcre_exec():
# Line 1425  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1773  MATCHING A PATTERN: THE TRADITIONAL FUNC
1773    
1774     Extra data for pcre_exec()     Extra data for pcre_exec()
1775    
1776         If the extra argument is not NULL, it must point to a  pcre_extra  data         If  the  extra argument is not NULL, it must point to a pcre_extra data
1777         block.  The pcre_study() function returns such a block (when it doesn't         block. The pcre_study() function returns such a block (when it  doesn't
1778         return NULL), but you can also create one for yourself, and pass  addi-         return  NULL), but you can also create one for yourself, and pass addi-
1779         tional  information in it. The fields in a pcre_extra block are as fol-         tional information in it. The pcre_extra block contains  the  following
1780         lows:         fields (not necessarily in this order):
1781    
1782           unsigned long int flags;           unsigned long int flags;
1783           void *study_data;           void *study_data;
1784           unsigned long int match_limit;           unsigned long int match_limit;
1785             unsigned long int match_limit_recursion;
1786           void *callout_data;           void *callout_data;
1787           const unsigned char *tables;           const unsigned char *tables;
1788    
1789         The flags field is a bitmap that specifies which of  the  other  fields         The  flags  field  is a bitmap that specifies which of the other fields
1790         are set. The flag bits are:         are set. The flag bits are:
1791    
1792           PCRE_EXTRA_STUDY_DATA           PCRE_EXTRA_STUDY_DATA
1793           PCRE_EXTRA_MATCH_LIMIT           PCRE_EXTRA_MATCH_LIMIT
1794             PCRE_EXTRA_MATCH_LIMIT_RECURSION
1795           PCRE_EXTRA_CALLOUT_DATA           PCRE_EXTRA_CALLOUT_DATA
1796           PCRE_EXTRA_TABLES           PCRE_EXTRA_TABLES
1797    
1798         Other  flag  bits should be set to zero. The study_data field is set in         Other flag bits should be set to zero. The study_data field is  set  in
1799         the pcre_extra block that is returned by  pcre_study(),  together  with         the  pcre_extra  block  that is returned by pcre_study(), together with
1800         the appropriate flag bit. You should not set this yourself, but you may         the appropriate flag bit. You should not set this yourself, but you may
1801         add to the block by setting the other fields  and  their  corresponding         add  to  the  block by setting the other fields and their corresponding
1802         flag bits.         flag bits.
1803    
1804         The match_limit field provides a means of preventing PCRE from using up         The match_limit field provides a means of preventing PCRE from using up
1805         a vast amount of resources when running patterns that are not going  to         a  vast amount of resources when running patterns that are not going to
1806         match,  but  which  have  a very large number of possibilities in their         match, but which have a very large number  of  possibilities  in  their
1807         search trees. The classic  example  is  the  use  of  nested  unlimited         search  trees.  The  classic  example  is  the  use of nested unlimited
1808         repeats.         repeats.
1809    
1810         Internally,  PCRE uses a function called match() which it calls repeat-         Internally, PCRE uses a function called match() which it calls  repeat-
1811         edly (sometimes recursively). The limit is imposed  on  the  number  of         edly  (sometimes  recursively). The limit set by match_limit is imposed
1812         times  this  function is called during a match, which has the effect of         on the number of times this function is called during  a  match,  which
1813         limiting the amount of recursion and backtracking that can take  place.         has  the  effect  of  limiting the amount of backtracking that can take
1814         For patterns that are not anchored, the count starts from zero for each         place. For patterns that are not anchored, the count restarts from zero
1815         position in the subject string.         for each position in the subject string.
1816    
1817         The default limit for the library can be set when PCRE  is  built;  the         The  default  value  for  the  limit can be set when PCRE is built; the
1818         default  default  is 10 million, which handles all but the most extreme         default default is 10 million, which handles all but the  most  extreme
1819         cases. You can reduce  the  default  by  suppling  pcre_exec()  with  a         cases.  You  can  override  the  default by suppling pcre_exec() with a
1820         pcre_extra  block  in  which match_limit is set to a smaller value, and         pcre_extra    block    in    which    match_limit    is    set,     and
1821         PCRE_EXTRA_MATCH_LIMIT is set in the  flags  field.  If  the  limit  is         PCRE_EXTRA_MATCH_LIMIT  is  set  in  the  flags  field. If the limit is
1822         exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.         exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
1823    
1824         The  pcre_callout  field is used in conjunction with the "callout" fea-         The match_limit_recursion field is similar to match_limit, but  instead
1825           of limiting the total number of times that match() is called, it limits
1826           the depth of recursion. The recursion depth is a  smaller  number  than
1827           the  total number of calls, because not all calls to match() are recur-
1828           sive.  This limit is of use only if it is set smaller than match_limit.
1829    
1830           Limiting  the  recursion  depth  limits the amount of stack that can be
1831           used, or, when PCRE has been compiled to use memory on the heap instead
1832           of the stack, the amount of heap memory that can be used.
1833    
1834           The  default  value  for  match_limit_recursion can be set when PCRE is
1835           built; the default default  is  the  same  value  as  the  default  for
1836           match_limit.  You can override the default by suppling pcre_exec() with
1837           a  pcre_extra  block  in  which  match_limit_recursion  is   set,   and
1838           PCRE_EXTRA_MATCH_LIMIT_RECURSION  is  set  in  the  flags field. If the
1839           limit is exceeded, pcre_exec() returns PCRE_ERROR_RECURSIONLIMIT.
1840    
1841           The pcre_callout field is used in conjunction with the  "callout"  fea-
1842         ture, which is described in the pcrecallout documentation.         ture, which is described in the pcrecallout documentation.
1843    
1844         The tables field  is  used  to  pass  a  character  tables  pointer  to         The  tables  field  is  used  to  pass  a  character  tables pointer to
1845         pcre_exec();  this overrides the value that is stored with the compiled         pcre_exec(); this overrides the value that is stored with the  compiled
1846         pattern. A non-NULL value is stored with the compiled pattern  only  if         pattern.  A  non-NULL value is stored with the compiled pattern only if
1847         custom  tables  were  supplied to pcre_compile() via its tableptr argu-         custom tables were supplied to pcre_compile() via  its  tableptr  argu-
1848         ment.  If NULL is passed to pcre_exec() using this mechanism, it forces         ment.  If NULL is passed to pcre_exec() using this mechanism, it forces
1849         PCRE's  internal  tables  to be used. This facility is helpful when re-         PCRE's internal tables to be used. This facility is  helpful  when  re-
1850         using patterns that have been saved after compiling  with  an  external         using  patterns  that  have been saved after compiling with an external
1851         set  of  tables,  because  the  external tables might be at a different         set of tables, because the external tables  might  be  at  a  different
1852         address when pcre_exec() is called. See the  pcreprecompile  documenta-         address  when  pcre_exec() is called. See the pcreprecompile documenta-
1853         tion for a discussion of saving compiled patterns for later use.         tion for a discussion of saving compiled patterns for later use.
1854    
1855     Option bits for pcre_exec()     Option bits for pcre_exec()
1856    
1857         The  unused  bits of the options argument for pcre_exec() must be zero.         The unused bits of the options argument for pcre_exec() must  be  zero.
1858         The  only  bits  that  may  be  set  are  PCRE_ANCHORED,   PCRE_NOTBOL,         The  only  bits  that  may  be set are PCRE_ANCHORED, PCRE_NEWLINE_xxx,
1859         PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NO_UTF8_CHECK and PCRE_PARTIAL.         PCRE_NOTBOL,   PCRE_NOTEOL,   PCRE_NOTEMPTY,   PCRE_NO_UTF8_CHECK   and
1860           PCRE_PARTIAL.
1861    
1862           PCRE_ANCHORED           PCRE_ANCHORED
1863    
# Line 1498  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1866  MATCHING A PATTERN: THE TRADITIONAL FUNC
1866         turned  out to be anchored by virtue of its contents, it cannot be made         turned  out to be anchored by virtue of its contents, it cannot be made
1867         unachored at matching time.         unachored at matching time.
1868    
1869             PCRE_BSR_ANYCRLF
1870             PCRE_BSR_UNICODE
1871    
1872           These options (which are mutually exclusive) control what the \R escape
1873           sequence  matches.  The choice is either to match only CR, LF, or CRLF,
1874           or to match any Unicode newline sequence. These  options  override  the
1875           choice that was made or defaulted when the pattern was compiled.
1876    
1877             PCRE_NEWLINE_CR
1878             PCRE_NEWLINE_LF
1879             PCRE_NEWLINE_CRLF
1880             PCRE_NEWLINE_ANYCRLF
1881             PCRE_NEWLINE_ANY
1882    
1883           These  options  override  the  newline  definition  that  was chosen or
1884           defaulted when the pattern was compiled. For details, see the  descrip-
1885           tion  of  pcre_compile()  above.  During  matching,  the newline choice
1886           affects the behaviour of the dot, circumflex,  and  dollar  metacharac-
1887           ters.  It may also alter the way the match position is advanced after a
1888           match failure for an unanchored pattern.
1889    
1890           When PCRE_NEWLINE_CRLF, PCRE_NEWLINE_ANYCRLF,  or  PCRE_NEWLINE_ANY  is
1891           set,  and a match attempt for an unanchored pattern fails when the cur-
1892           rent position is at a  CRLF  sequence,  and  the  pattern  contains  no
1893           explicit  matches  for  CR  or  LF  characters,  the  match position is
1894           advanced by two characters instead of one, in other words, to after the
1895           CRLF.
1896    
1897           The above rule is a compromise that makes the most common cases work as
1898           expected. For example, if the  pattern  is  .+A  (and  the  PCRE_DOTALL
1899           option is not set), it does not match the string "\r\nA" because, after
1900           failing at the start, it skips both the CR and the LF before  retrying.
1901           However,  the  pattern  [\r\n]A does match that string, because it con-
1902           tains an explicit CR or LF reference, and so advances only by one char-
1903           acter after the first failure.
1904    
1905           An explicit match for CR of LF is either a literal appearance of one of
1906           those characters, or one of the \r or  \n  escape  sequences.  Implicit
1907           matches  such  as [^X] do not count, nor does \s (which includes CR and
1908           LF in the characters that it matches).
1909    
1910           Notwithstanding the above, anomalous effects may still occur when  CRLF
1911           is a valid newline sequence and explicit \r or \n escapes appear in the
1912           pattern.
1913    
1914           PCRE_NOTBOL           PCRE_NOTBOL
1915    
1916         This option specifies that first character of the subject string is not         This option specifies that first character of the subject string is not
# Line 1543  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1956  MATCHING A PATTERN: THE TRADITIONAL FUNC
1956         When PCRE_UTF8 is set at compile time, the validity of the subject as a         When PCRE_UTF8 is set at compile time, the validity of the subject as a
1957         UTF-8  string is automatically checked when pcre_exec() is subsequently         UTF-8  string is automatically checked when pcre_exec() is subsequently
1958         called.  The value of startoffset is also checked  to  ensure  that  it         called.  The value of startoffset is also checked  to  ensure  that  it
1959         points  to the start of a UTF-8 character. If an invalid UTF-8 sequence         points  to  the start of a UTF-8 character. There is a discussion about
1960         of bytes is found, pcre_exec() returns the error PCRE_ERROR_BADUTF8. If         the validity of UTF-8 strings in the section on UTF-8  support  in  the
1961         startoffset  contains  an  invalid  value, PCRE_ERROR_BADUTF8_OFFSET is         main  pcre  page.  If  an  invalid  UTF-8  sequence  of bytes is found,
1962         returned.         pcre_exec() returns the error PCRE_ERROR_BADUTF8. If  startoffset  con-
1963           tains an invalid value, PCRE_ERROR_BADUTF8_OFFSET is returned.
1964         If you already know that your subject is valid, and you  want  to  skip  
1965         these    checks    for   performance   reasons,   you   can   set   the         If  you  already  know that your subject is valid, and you want to skip
1966         PCRE_NO_UTF8_CHECK option when calling pcre_exec(). You might  want  to         these   checks   for   performance   reasons,   you   can    set    the
1967         do  this  for the second and subsequent calls to pcre_exec() if you are         PCRE_NO_UTF8_CHECK  option  when calling pcre_exec(). You might want to
1968         making repeated calls to find all  the  matches  in  a  single  subject         do this for the second and subsequent calls to pcre_exec() if  you  are
1969         string.  However,  you  should  be  sure  that the value of startoffset         making  repeated  calls  to  find  all  the matches in a single subject
1970         points to the start of a UTF-8 character.  When  PCRE_NO_UTF8_CHECK  is         string. However, you should be  sure  that  the  value  of  startoffset
1971         set,  the  effect of passing an invalid UTF-8 string as a subject, or a         points  to  the  start of a UTF-8 character. When PCRE_NO_UTF8_CHECK is
1972         value of startoffset that does not point to the start of a UTF-8  char-         set, the effect of passing an invalid UTF-8 string as a subject,  or  a
1973           value  of startoffset that does not point to the start of a UTF-8 char-
1974         acter, is undefined. Your program may crash.         acter, is undefined. Your program may crash.
1975    
1976           PCRE_PARTIAL           PCRE_PARTIAL
1977    
1978         This  option  turns  on  the  partial  matching feature. If the subject         This option turns on the  partial  matching  feature.  If  the  subject
1979         string fails to match the pattern, but at some point during the  match-         string  fails to match the pattern, but at some point during the match-
1980         ing  process  the  end of the subject was reached (that is, the subject         ing process the end of the subject was reached (that  is,  the  subject
1981         partially matches the pattern and the failure to  match  occurred  only         partially  matches  the  pattern and the failure to match occurred only
1982         because  there were not enough subject characters), pcre_exec() returns         because there were not enough subject characters), pcre_exec()  returns
1983         PCRE_ERROR_PARTIAL instead of PCRE_ERROR_NOMATCH. When PCRE_PARTIAL  is         PCRE_ERROR_PARTIAL  instead of PCRE_ERROR_NOMATCH. When PCRE_PARTIAL is
1984         used,  there  are restrictions on what may appear in the pattern. These         used, there are restrictions on what may appear in the  pattern.  These
1985         are discussed in the pcrepartial documentation.         are discussed in the pcrepartial documentation.
1986    
1987     The string to be matched by pcre_exec()     The string to be matched by pcre_exec()
1988    
1989         The subject string is passed to pcre_exec() as a pointer in subject,  a         The  subject string is passed to pcre_exec() as a pointer in subject, a
1990         length  in  length, and a starting byte offset in startoffset. In UTF-8         length in length, and a starting byte offset in startoffset.  In  UTF-8
1991         mode, the byte offset must point to the start  of  a  UTF-8  character.         mode,  the  byte  offset  must point to the start of a UTF-8 character.
1992         Unlike  the  pattern string, the subject may contain binary zero bytes.         Unlike the pattern string, the subject may contain binary  zero  bytes.
1993         When the starting offset is zero, the search for a match starts at  the         When  the starting offset is zero, the search for a match starts at the
1994         beginning of the subject, and this is by far the most common case.         beginning of the subject, and this is by far the most common case.
1995    
1996         A  non-zero  starting offset is useful when searching for another match         A non-zero starting offset is useful when searching for  another  match
1997         in the same subject by calling pcre_exec() again after a previous  suc-         in  the same subject by calling pcre_exec() again after a previous suc-
1998         cess.   Setting  startoffset differs from just passing over a shortened         cess.  Setting startoffset differs from just passing over  a  shortened
1999         string and setting PCRE_NOTBOL in the case of  a  pattern  that  begins         string  and  setting  PCRE_NOTBOL  in the case of a pattern that begins
2000         with any kind of lookbehind. For example, consider the pattern         with any kind of lookbehind. For example, consider the pattern
2001    
2002           \Biss\B           \Biss\B
2003    
2004         which  finds  occurrences  of "iss" in the middle of words. (\B matches         which finds occurrences of "iss" in the middle of  words.  (\B  matches
2005         only if the current position in the subject is not  a  word  boundary.)         only  if  the  current position in the subject is not a word boundary.)
2006         When  applied  to the string "Mississipi" the first call to pcre_exec()         When applied to the string "Mississipi" the first call  to  pcre_exec()
2007         finds the first occurrence. If pcre_exec() is called  again  with  just         finds  the  first  occurrence. If pcre_exec() is called again with just
2008         the  remainder  of  the  subject,  namely  "issipi", it does not match,         the remainder of the subject,  namely  "issipi",  it  does  not  match,
2009         because \B is always false at the start of the subject, which is deemed         because \B is always false at the start of the subject, which is deemed
2010         to  be  a  word  boundary. However, if pcre_exec() is passed the entire         to be a word boundary. However, if pcre_exec()  is  passed  the  entire
2011         string again, but with startoffset set to 4, it finds the second occur-         string again, but with startoffset set to 4, it finds the second occur-
2012         rence  of "iss" because it is able to look behind the starting point to         rence of "iss" because it is able to look behind the starting point  to
2013         discover that it is preceded by a letter.         discover that it is preceded by a letter.
2014    
2015         If a non-zero starting offset is passed when the pattern  is  anchored,         If  a  non-zero starting offset is passed when the pattern is anchored,
2016         one attempt to match at the given offset is made. This can only succeed         one attempt to match at the given offset is made. This can only succeed
2017         if the pattern does not require the match to be at  the  start  of  the         if  the  pattern  does  not require the match to be at the start of the
2018         subject.         subject.
2019    
2020     How pcre_exec() returns captured substrings     How pcre_exec() returns captured substrings
2021    
2022         In  general, a pattern matches a certain portion of the subject, and in         In general, a pattern matches a certain portion of the subject, and  in
2023         addition, further substrings from the subject  may  be  picked  out  by         addition,  further  substrings  from  the  subject may be picked out by
2024         parts  of  the  pattern.  Following the usage in Jeffrey Friedl's book,         parts of the pattern. Following the usage  in  Jeffrey  Friedl's  book,
2025         this is called "capturing" in what follows, and the  phrase  "capturing         this  is  called "capturing" in what follows, and the phrase "capturing
2026         subpattern"  is  used for a fragment of a pattern that picks out a sub-         subpattern" is used for a fragment of a pattern that picks out  a  sub-
2027         string. PCRE supports several other kinds of  parenthesized  subpattern         string.  PCRE  supports several other kinds of parenthesized subpattern
2028         that do not cause substrings to be captured.         that do not cause substrings to be captured.
2029    
2030         Captured  substrings are returned to the caller via a vector of integer         Captured substrings are returned to the caller via a vector of  integer
2031         offsets whose address is passed in ovector. The number of  elements  in         offsets  whose  address is passed in ovector. The number of elements in
2032         the  vector is passed in ovecsize, which must be a non-negative number.         the vector is passed in ovecsize, which must be a non-negative  number.
2033         Note: this argument is NOT the size of ovector in bytes.         Note: this argument is NOT the size of ovector in bytes.
2034    
2035         The first two-thirds of the vector is used to pass back  captured  sub-         The  first  two-thirds of the vector is used to pass back captured sub-
2036         strings,  each  substring using a pair of integers. The remaining third         strings, each substring using a pair of integers. The  remaining  third
2037         of the vector is used as workspace by pcre_exec() while  matching  cap-         of  the  vector is used as workspace by pcre_exec() while matching cap-
2038         turing  subpatterns, and is not available for passing back information.         turing subpatterns, and is not available for passing back  information.
2039         The length passed in ovecsize should always be a multiple of three.  If         The  length passed in ovecsize should always be a multiple of three. If
2040         it is not, it is rounded down.         it is not, it is rounded down.
2041    
2042         When  a  match  is successful, information about captured substrings is         When a match is successful, information about  captured  substrings  is
2043         returned in pairs of integers, starting at the  beginning  of  ovector,         returned  in  pairs  of integers, starting at the beginning of ovector,
2044         and  continuing  up  to two-thirds of its length at the most. The first         and continuing up to two-thirds of its length at the  most.  The  first
2045         element of a pair is set to the offset of the first character in a sub-         element of a pair is set to the offset of the first character in a sub-
2046         string,  and  the  second  is  set to the offset of the first character         string, and the second is set to the  offset  of  the  first  character
2047         after the end of a substring. The  first  pair,  ovector[0]  and  ovec-         after  the  end  of  a  substring. The first pair, ovector[0] and ovec-
2048         tor[1],  identify  the  portion  of  the  subject string matched by the         tor[1], identify the portion of  the  subject  string  matched  by  the
2049         entire pattern. The next pair is used for the first  capturing  subpat-         entire  pattern.  The next pair is used for the first capturing subpat-
2050         tern,  and  so  on.  The value returned by pcre_exec() is the number of         tern, and so on. The value returned by pcre_exec() is one more than the
2051         pairs that have been set. If there are no  capturing  subpatterns,  the         highest numbered pair that has been set. For example, if two substrings
2052         return  value  from  a  successful match is 1, indicating that just the         have been captured, the returned value is 3. If there are no  capturing
2053         first pair of offsets has been set.         subpatterns,  the return value from a successful match is 1, indicating
2054           that just the first pair of offsets has been set.
        Some convenience functions are provided  for  extracting  the  captured  
        substrings  as  separate  strings. These are described in the following  
        section.  
   
        It is possible for an capturing subpattern number  n+1  to  match  some  
        part  of  the  subject  when subpattern n has not been used at all. For  
        example, if the string "abc" is matched against the pattern (a|(z))(bc)  
        subpatterns  1 and 3 are matched, but 2 is not. When this happens, both  
        offset values corresponding to the unused subpattern are set to -1.  
2055    
2056         If a capturing subpattern is matched repeatedly, it is the last portion         If a capturing subpattern is matched repeatedly, it is the last portion
2057         of the string that it matched that is returned.         of the string that it matched that is returned.
# Line 1660  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2065  MATCHING A PATTERN: THE TRADITIONAL FUNC
2065         substrings,  PCRE has to get additional memory for use during matching.         substrings,  PCRE has to get additional memory for use during matching.
2066         Thus it is usually advisable to supply an ovector.         Thus it is usually advisable to supply an ovector.
2067    
2068         Note that pcre_info() can be used to find out how many  capturing  sub-         The pcre_info() function can be used to find  out  how  many  capturing
2069         patterns there are in a compiled pattern. The smallest size for ovector         subpatterns  there  are  in  a  compiled pattern. The smallest size for
2070         that will allow for n captured substrings, in addition to  the  offsets         ovector that will allow for n captured substrings, in addition  to  the
2071         of the substring matched by the whole pattern, is (n+1)*3.         offsets of the substring matched by the whole pattern, is (n+1)*3.
2072    
2073           It  is  possible for capturing subpattern number n+1 to match some part
2074           of the subject when subpattern n has not been used at all. For example,
2075           if  the  string  "abc"  is  matched against the pattern (a|(z))(bc) the
2076           return from the function is 4, and subpatterns 1 and 3 are matched, but
2077           2  is  not.  When  this happens, both values in the offset pairs corre-
2078           sponding to unused subpatterns are set to -1.
2079    
2080           Offset values that correspond to unused subpatterns at the end  of  the
2081           expression  are  also  set  to  -1. For example, if the string "abc" is
2082           matched against the pattern (abc)(x(yz)?)? subpatterns 2 and 3 are  not
2083           matched.  The  return  from the function is 2, because the highest used
2084           capturing subpattern number is 1. However, you can refer to the offsets
2085           for  the  second  and third capturing subpatterns if you wish (assuming
2086           the vector is large enough, of course).
2087    
2088           Some convenience functions are provided  for  extracting  the  captured
2089           substrings as separate strings. These are described below.
2090    
2091     Return values from pcre_exec()     Error return values from pcre_exec()
2092    
2093         If  pcre_exec()  fails, it returns a negative number. The following are         If  pcre_exec()  fails, it returns a negative number. The following are
2094         defined in the header file:         defined in the header file:
# Line 1691  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2114  MATCHING A PATTERN: THE TRADITIONAL FUNC
2114         an environment with the other endianness. This is the error  that  PCRE         an environment with the other endianness. This is the error  that  PCRE
2115         gives when the magic number is not present.         gives when the magic number is not present.
2116    
2117           PCRE_ERROR_UNKNOWN_NODE   (-5)           PCRE_ERROR_UNKNOWN_OPCODE (-5)
2118    
2119         While running the pattern match, an unknown item was encountered in the         While running the pattern match, an unknown item was encountered in the
2120         compiled pattern. This error could be caused by a bug  in  PCRE  or  by         compiled pattern. This error could be caused by a bug  in  PCRE  or  by
# Line 1713  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2136  MATCHING A PATTERN: THE TRADITIONAL FUNC
2136    
2137           PCRE_ERROR_MATCHLIMIT     (-8)           PCRE_ERROR_MATCHLIMIT     (-8)
2138    
2139         The  recursion  and backtracking limit, as specified by the match_limit         The  backtracking  limit,  as  specified  by the match_limit field in a
2140         field in a pcre_extra structure (or defaulted)  was  reached.  See  the         pcre_extra structure (or defaulted) was reached.  See  the  description
2141         description above.         above.
2142    
2143           PCRE_ERROR_CALLOUT        (-9)           PCRE_ERROR_CALLOUT        (-9)
2144    
# Line 1754  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2177  MATCHING A PATTERN: THE TRADITIONAL FUNC
2177    
2178         This error is given if the value of the ovecsize argument is  negative.         This error is given if the value of the ovecsize argument is  negative.
2179    
2180             PCRE_ERROR_RECURSIONLIMIT (-21)
2181    
2182           The internal recursion limit, as specified by the match_limit_recursion
2183           field in a pcre_extra structure (or defaulted)  was  reached.  See  the
2184           description above.
2185    
2186             PCRE_ERROR_BADNEWLINE     (-23)
2187    
2188           An invalid combination of PCRE_NEWLINE_xxx options was given.
2189    
2190           Error numbers -16 to -20 and -22 are not used by pcre_exec().
2191    
2192    
2193  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
2194    
# Line 1774  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER Line 2209  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
2209         string_list() are provided for extracting captured substrings  as  new,         string_list() are provided for extracting captured substrings  as  new,
2210         separate,  zero-terminated strings. These functions identify substrings         separate,  zero-terminated strings. These functions identify substrings
2211         by number. The next section describes functions  for  extracting  named         by number. The next section describes functions  for  extracting  named
2212         substrings.  A  substring  that  contains  a  binary  zero is correctly         substrings.
2213         extracted and has a further zero added on the end, but  the  result  is  
2214         not, of course, a C string.         A  substring that contains a binary zero is correctly extracted and has
2215           a further zero added on the end, but the result is not, of course, a  C
2216           string.   However,  you  can  process such a string by referring to the
2217           length that is  returned  by  pcre_copy_substring()  and  pcre_get_sub-
2218           string().  Unfortunately, the interface to pcre_get_substring_list() is
2219           not adequate for handling strings containing binary zeros, because  the
2220           end of the final string is not independently indicated.
2221    
2222         The  first  three  arguments  are the same for all three of these func-         The  first  three  arguments  are the same for all three of these func-
2223         tions: subject is the subject string that has  just  been  successfully         tions: subject is the subject string that has  just  been  successfully
# Line 1796  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER Line 2237  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
2237         buffersize, while for pcre_get_substring() a new  block  of  memory  is         buffersize, while for pcre_get_substring() a new  block  of  memory  is
2238         obtained  via  pcre_malloc,  and its address is returned via stringptr.         obtained  via  pcre_malloc,  and its address is returned via stringptr.
2239         The yield of the function is the length of the  string,  not  including         The yield of the function is the length of the  string,  not  including
2240         the terminating zero, or one of         the terminating zero, or one of these error codes:
2241    
2242           PCRE_ERROR_NOMEMORY       (-6)           PCRE_ERROR_NOMEMORY       (-6)
2243    
# Line 1812  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER Line 2253  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
2253         single block of memory that is obtained via pcre_malloc. The address of         single block of memory that is obtained via pcre_malloc. The address of
2254         the  memory  block  is returned via listptr, which is also the start of         the  memory  block  is returned via listptr, which is also the start of
2255         the list of string pointers. The end of the list is marked  by  a  NULL         the list of string pointers. The end of the list is marked  by  a  NULL
2256         pointer. The yield of the function is zero if all went well, or         pointer.  The  yield  of  the function is zero if all went well, or the
2257           error code
2258    
2259           PCRE_ERROR_NOMEMORY       (-6)           PCRE_ERROR_NOMEMORY       (-6)
2260    
2261         if the attempt to get the memory block failed.         if the attempt to get the memory block failed.
2262    
2263         When  any of these functions encounter a substring that is unset, which         When any of these functions encounter a substring that is unset,  which
2264         can happen when capturing subpattern number n+1 matches  some  part  of         can  happen  when  capturing subpattern number n+1 matches some part of
2265         the  subject, but subpattern n has not been used at all, they return an         the subject, but subpattern n has not been used at all, they return  an
2266         empty string. This can be distinguished from a genuine zero-length sub-         empty string. This can be distinguished from a genuine zero-length sub-
2267         string  by inspecting the appropriate offset in ovector, which is nega-         string by inspecting the appropriate offset in ovector, which is  nega-
2268         tive for unset substrings.         tive for unset substrings.
2269    
2270         The two convenience functions pcre_free_substring() and  pcre_free_sub-         The  two convenience functions pcre_free_substring() and pcre_free_sub-
2271         string_list()  can  be  used  to free the memory returned by a previous         string_list() can be used to free the memory  returned  by  a  previous
2272         call  of  pcre_get_substring()  or  pcre_get_substring_list(),  respec-         call  of  pcre_get_substring()  or  pcre_get_substring_list(),  respec-
2273         tively.  They  do  nothing  more  than  call the function pointed to by         tively. They do nothing more than  call  the  function  pointed  to  by
2274         pcre_free, which of course could be called directly from a  C  program.         pcre_free,  which  of course could be called directly from a C program.
2275         However,  PCRE is used in some situations where it is linked via a spe-         However, PCRE is used in some situations where it is linked via a  spe-
2276         cial  interface  to  another  programming  language  which  cannot  use         cial   interface  to  another  programming  language  that  cannot  use
2277         pcre_free  directly;  it is for these cases that the functions are pro-         pcre_free directly; it is for these cases that the functions  are  pro-
2278         vided.         vided.
2279    
2280    
# Line 1851  EXTRACTING CAPTURED SUBSTRINGS BY NAME Line 2293  EXTRACTING CAPTURED SUBSTRINGS BY NAME
2293              int stringcount, const char *stringname,              int stringcount, const char *stringname,
2294              const char **stringptr);              const char **stringptr);
2295    
2296         To extract a substring by name, you first have to find associated  num-         To  extract a substring by name, you first have to find associated num-
2297         ber.  For example, for this pattern         ber.  For example, for this pattern
2298    
2299           (a+)b(?P<xxx>\d+)...           (a+)b(?<xxx>\d+)...
2300    
2301         the number of the subpattern called "xxx" is 2. You can find the number         the number of the subpattern called "xxx" is 2. If the name is known to
2302         from the name by calling pcre_get_stringnumber(). The first argument is         be unique (PCRE_DUPNAMES was not set), you can find the number from the
2303         the  compiled  pattern,  and  the  second is the name. The yield of the         name by calling pcre_get_stringnumber(). The first argument is the com-
2304         function is the subpattern number, or  PCRE_ERROR_NOSUBSTRING  (-7)  if         piled pattern, and the second is the name. The yield of the function is
2305         there is no subpattern of that name.         the subpattern number, or PCRE_ERROR_NOSUBSTRING (-7) if  there  is  no
2306           subpattern of that name.
2307    
2308         Given the number, you can extract the substring directly, or use one of         Given the number, you can extract the substring directly, or use one of
2309         the functions described in the previous section. For convenience, there         the functions described in the previous section. For convenience, there
# Line 1879  EXTRACTING CAPTURED SUBSTRINGS BY NAME Line 2322  EXTRACTING CAPTURED SUBSTRINGS BY NAME
2322    
2323         These functions call pcre_get_stringnumber(), and if it succeeds,  they         These functions call pcre_get_stringnumber(), and if it succeeds,  they
2324         then  call  pcre_copy_substring() or pcre_get_substring(), as appropri-         then  call  pcre_copy_substring() or pcre_get_substring(), as appropri-
2325         ate.         ate. NOTE: If PCRE_DUPNAMES is set and there are duplicate  names,  the
2326           behaviour may not be what you want (see the next section).
2327    
2328    
2329    DUPLICATE SUBPATTERN NAMES
2330    
2331           int pcre_get_stringtable_entries(const pcre *code,
2332                const char *name, char **first, char **last);
2333    
2334           When  a  pattern  is  compiled with the PCRE_DUPNAMES option, names for
2335           subpatterns are not required to  be  unique.  Normally,  patterns  with
2336           duplicate  names  are such that in any one match, only one of the named
2337           subpatterns participates. An example is shown in the pcrepattern  docu-
2338           mentation.
2339    
2340           When    duplicates   are   present,   pcre_copy_named_substring()   and
2341           pcre_get_named_substring() return the first substring corresponding  to
2342           the  given  name  that  is set. If none are set, PCRE_ERROR_NOSUBSTRING
2343           (-7) is returned; no  data  is  returned.  The  pcre_get_stringnumber()
2344           function  returns one of the numbers that are associated with the name,
2345           but it is not defined which it is.
2346    
2347           If you want to get full details of all captured substrings for a  given
2348           name,  you  must  use  the pcre_get_stringtable_entries() function. The
2349           first argument is the compiled pattern, and the second is the name. The
2350           third  and  fourth  are  pointers to variables which are updated by the
2351           function. After it has run, they point to the first and last entries in
2352           the  name-to-number  table  for  the  given  name.  The function itself
2353           returns the length of each entry,  or  PCRE_ERROR_NOSUBSTRING  (-7)  if
2354           there  are none. The format of the table is described above in the sec-
2355           tion entitled Information about a  pattern.   Given  all  the  relevant
2356           entries  for the name, you can extract each of their numbers, and hence
2357           the captured data, if any.
2358    
2359    
2360  FINDING ALL POSSIBLE MATCHES  FINDING ALL POSSIBLE MATCHES
# Line 1908  MATCHING A PATTERN: THE ALTERNATIVE FUNC Line 2383  MATCHING A PATTERN: THE ALTERNATIVE FUNC
2383              int *workspace, int wscount);              int *workspace, int wscount);
2384    
2385         The  function  pcre_dfa_exec()  is  called  to  match  a subject string         The  function  pcre_dfa_exec()  is  called  to  match  a subject string
2386         against a compiled pattern, using a "DFA" matching algorithm. This  has         against a compiled pattern, using a matching algorithm that  scans  the
2387         different  characteristics to the normal algorithm, and is not compati-         subject  string  just  once, and does not backtrack. This has different
2388         ble with Perl. Some of the features of PCRE patterns are not supported.         characteristics to the normal algorithm, and  is  not  compatible  with
2389         Nevertheless, there are times when this kind of matching can be useful.         Perl.  Some  of the features of PCRE patterns are not supported. Never-
2390         For a discussion of the two matching algorithms, see  the  pcrematching         theless, there are times when this kind of matching can be useful.  For
2391         documentation.         a discussion of the two matching algorithms, see the pcrematching docu-
2392           mentation.
2393    
2394         The  arguments  for  the  pcre_dfa_exec()  function are the same as for         The arguments for the pcre_dfa_exec() function  are  the  same  as  for
2395         pcre_exec(), plus two extras. The ovector argument is used in a differ-         pcre_exec(), plus two extras. The ovector argument is used in a differ-
2396         ent  way,  and  this is described below. The other common arguments are         ent way, and this is described below. The other  common  arguments  are
2397         used in the same way as for pcre_exec(), so their  description  is  not         used  in  the  same way as for pcre_exec(), so their description is not
2398         repeated here.         repeated here.
2399    
2400         The  two  additional  arguments provide workspace for the function. The         The two additional arguments provide workspace for  the  function.  The
2401         workspace vector should contain at least 20 elements. It  is  used  for         workspace  vector  should  contain at least 20 elements. It is used for
2402         keeping  track  of  multiple  paths  through  the  pattern  tree.  More         keeping  track  of  multiple  paths  through  the  pattern  tree.  More
2403         workspace will be needed for patterns and subjects where  there  are  a         workspace  will  be  needed for patterns and subjects where there are a
2404         lot of possible matches.         lot of potential matches.
2405    
2406         Here is an example of a simple call to pcre_exec():         Here is an example of a simple call to pcre_dfa_exec():
2407    
2408           int rc;           int rc;
2409           int ovector[10];           int ovector[10];
2410           int wspace[20];           int wspace[20];
2411           rc = pcre_exec(           rc = pcre_dfa_exec(
2412             re,             /* result of pcre_compile() */             re,             /* result of pcre_compile() */
2413             NULL,           /* we didn't study the pattern */             NULL,           /* we didn't study the pattern */
2414             "some string",  /* the subject string */             "some string",  /* the subject string */
# Line 1946  MATCHING A PATTERN: THE ALTERNATIVE FUNC Line 2422  MATCHING A PATTERN: THE ALTERNATIVE FUNC
2422    
2423     Option bits for pcre_dfa_exec()     Option bits for pcre_dfa_exec()
2424    
2425         The  unused  bits  of  the options argument for pcre_dfa_exec() must be         The unused bits of the options argument  for  pcre_dfa_exec()  must  be
2426         zero. The only bits that may be  set  are  PCRE_ANCHORED,  PCRE_NOTBOL,         zero.  The  only  bits  that  may  be  set are PCRE_ANCHORED, PCRE_NEW-
2427         PCRE_NOTEOL,     PCRE_NOTEMPTY,    PCRE_NO_UTF8_CHECK,    PCRE_PARTIAL,         LINE_xxx, PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY,  PCRE_NO_UTF8_CHECK,
2428         PCRE_DFA_SHORTEST, and PCRE_DFA_RESTART. All  but  the  last  three  of         PCRE_PARTIAL, PCRE_DFA_SHORTEST, and PCRE_DFA_RESTART. All but the last
2429         these  are  the  same  as  for pcre_exec(), so their description is not         three of these are the same as for pcre_exec(), so their description is
2430         repeated here.         not repeated here.
2431    
2432           PCRE_PARTIAL           PCRE_PARTIAL
2433    
2434         This has the same general effect as it does for  pcre_exec(),  but  the         This  has  the  same general effect as it does for pcre_exec(), but the
2435         details   are   slightly   different.  When  PCRE_PARTIAL  is  set  for         details  are  slightly  different.  When  PCRE_PARTIAL   is   set   for
2436         pcre_dfa_exec(), the return code PCRE_ERROR_NOMATCH is  converted  into         pcre_dfa_exec(),  the  return code PCRE_ERROR_NOMATCH is converted into
2437         PCRE_ERROR_PARTIAL  if  the  end  of the subject is reached, there have         PCRE_ERROR_PARTIAL if the end of the subject  is  reached,  there  have
2438         been no complete matches, but there is still at least one matching pos-         been no complete matches, but there is still at least one matching pos-
2439         sibility.  The portion of the string that provided the partial match is         sibility. The portion of the string that provided the partial match  is
2440         set as the first matching string.         set as the first matching string.
2441    
2442           PCRE_DFA_SHORTEST           PCRE_DFA_SHORTEST
2443    
2444         Setting the PCRE_DFA_SHORTEST option causes the matching  algorithm  to         Setting  the  PCRE_DFA_SHORTEST option causes the matching algorithm to
2445         stop  as  soon  as  it  has found one match. Because of the way the DFA         stop as soon as it has found one match. Because of the way the alterna-
2446         algorithm works, this is necessarily the shortest possible match at the         tive  algorithm  works, this is necessarily the shortest possible match
2447         first possible matching point in the subject string.         at the first possible matching point in the subject string.
2448    
2449           PCRE_DFA_RESTART           PCRE_DFA_RESTART
2450    
2451         When  pcre_dfa_exec()  is  called  with  the  PCRE_PARTIAL  option, and         When pcre_dfa_exec()  is  called  with  the  PCRE_PARTIAL  option,  and
2452         returns a partial match, it is possible to call it  again,  with  addi-         returns  a  partial  match, it is possible to call it again, with addi-
2453         tional  subject  characters,  and have it continue with the same match.         tional subject characters, and have it continue with  the  same  match.
2454         The PCRE_DFA_RESTART option requests this action; when it is  set,  the         The  PCRE_DFA_RESTART  option requests this action; when it is set, the
2455         workspace  and wscount options must reference the same vector as before         workspace and wscount options must reference the same vector as  before
2456         because data about the match so far is left in  them  after  a  partial         because  data  about  the  match so far is left in them after a partial
2457         match.  There  is  more  discussion of this facility in the pcrepartial         match. There is more discussion of this  facility  in  the  pcrepartial
2458         documentation.         documentation.
2459    
2460     Successful returns from pcre_dfa_exec()     Successful returns from pcre_dfa_exec()
2461    
2462         When pcre_dfa_exec() succeeds, it may have matched more than  one  sub-         When  pcre_dfa_exec()  succeeds, it may have matched more than one sub-
2463         string in the subject. Note, however, that all the matches from one run         string in the subject. Note, however, that all the matches from one run
2464         of the function start at the same point in  the  subject.  The  shorter         of  the  function  start  at the same point in the subject. The shorter
2465         matches  are all initial substrings of the longer matches. For example,         matches are all initial substrings of the longer matches. For  example,
2466         if the pattern         if the pattern
2467    
2468           <.*>           <.*>
# Line 2001  MATCHING A PATTERN: THE ALTERNATIVE FUNC Line 2477  MATCHING A PATTERN: THE ALTERNATIVE FUNC
2477           <something> <something else>           <something> <something else>
2478           <something> <something else> <something further>           <something> <something else> <something further>
2479    
2480         On success, the yield of the function is a number  greater  than  zero,         On  success,  the  yield of the function is a number greater than zero,
2481         which  is  the  number of matched substrings. The substrings themselves         which is the number of matched substrings.  The  substrings  themselves
2482         are returned in ovector. Each string uses two elements;  the  first  is         are  returned  in  ovector. Each string uses two elements; the first is
2483         the  offset  to the start, and the second is the offset to the end. All         the offset to the start, and the second is the offset to  the  end.  In
2484         the strings have the same start offset. (Space could have been saved by         fact,  all  the  strings  have the same start offset. (Space could have
2485         giving  this only once, but it was decided to retain some compatibility         been saved by giving this only once, but it was decided to retain  some
2486         with the way pcre_exec() returns data, even though the meaning  of  the         compatibility  with  the  way pcre_exec() returns data, even though the
2487         strings is different.)         meaning of the strings is different.)
2488    
2489         The strings are returned in reverse order of length; that is, the long-         The strings are returned in reverse order of length; that is, the long-
2490         est matching string is given first. If there were too many  matches  to         est  matching  string is given first. If there were too many matches to
2491         fit  into ovector, the yield of the function is zero, and the vector is         fit into ovector, the yield of the function is zero, and the vector  is
2492         filled with the longest matches.         filled with the longest matches.
2493    
2494     Error returns from pcre_dfa_exec()     Error returns from pcre_dfa_exec()
2495    
2496         The pcre_dfa_exec() function returns a negative number when  it  fails.         The  pcre_dfa_exec()  function returns a negative number when it fails.
2497         Many  of  the  errors  are  the  same as for pcre_exec(), and these are         Many of the errors are the same  as  for  pcre_exec(),  and  these  are
2498         described above.  There are in addition the following errors  that  are         described  above.   There are in addition the following errors that are
2499         specific to pcre_dfa_exec():         specific to pcre_dfa_exec():
2500    
2501           PCRE_ERROR_DFA_UITEM      (-16)           PCRE_ERROR_DFA_UITEM      (-16)
2502    
2503         This  return is given if pcre_dfa_exec() encounters an item in the pat-         This return is given if pcre_dfa_exec() encounters an item in the  pat-
2504         tern that it does not support, for instance, the use of \C  or  a  back         tern  that  it  does not support, for instance, the use of \C or a back
2505         reference.         reference.
2506    
2507           PCRE_ERROR_DFA_UCOND      (-17)           PCRE_ERROR_DFA_UCOND      (-17)
2508    
2509         This  return is given if pcre_dfa_exec() encounters a condition item in         This return is given if pcre_dfa_exec()  encounters  a  condition  item
2510         a pattern that uses a back reference for the  condition.  This  is  not         that  uses  a back reference for the condition, or a test for recursion
2511         supported.         in a specific group. These are not supported.
2512    
2513           PCRE_ERROR_DFA_UMLIMIT    (-18)           PCRE_ERROR_DFA_UMLIMIT    (-18)
2514    
2515         This  return  is given if pcre_dfa_exec() is called with an extra block         This return is given if pcre_dfa_exec() is called with an  extra  block
2516         that contains a setting of the match_limit field. This is not supported         that contains a setting of the match_limit field. This is not supported
2517         (it is meaningless).         (it is meaningless).
2518    
2519           PCRE_ERROR_DFA_WSSIZE     (-19)           PCRE_ERROR_DFA_WSSIZE     (-19)
2520    
2521         This  return  is  given  if  pcre_dfa_exec()  runs  out of space in the         This return is given if  pcre_dfa_exec()  runs  out  of  space  in  the
2522         workspace vector.         workspace vector.
2523    
2524           PCRE_ERROR_DFA_RECURSE    (-20)           PCRE_ERROR_DFA_RECURSE    (-20)
2525    
2526         When a recursive subpattern is processed, the matching  function  calls         When  a  recursive subpattern is processed, the matching function calls
2527         itself  recursively,  using  private vectors for ovector and workspace.         itself recursively, using private vectors for  ovector  and  workspace.
2528         This error is given if the output vector  is  not  large  enough.  This         This  error  is  given  if  the output vector is not large enough. This
2529         should be extremely rare, as a vector of size 1000 is used.         should be extremely rare, as a vector of size 1000 is used.
2530    
2531  Last updated: 16 May 2005  
2532  Copyright (c) 1997-2005 University of Cambridge.  SEE ALSO
2533    
2534           pcrebuild(3), pcrecallout(3), pcrecpp(3)(3), pcrematching(3),  pcrepar-
2535           tial(3),  pcreposix(3), pcreprecompile(3), pcresample(3), pcrestack(3).
2536    
2537    
2538    AUTHOR
2539    
2540           Philip Hazel
2541           University Computing Service
2542           Cambridge CB2 3QH, England.
2543    
2544    
2545    REVISION
2546    
2547           Last updated: 27 November 2007
2548           Copyright (c) 1997-2007 University of Cambridge.
2549  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
2550    
2551    
# Line 2080  PCRE CALLOUTS Line 2572  PCRE CALLOUTS
2572         default value is zero.  For  example,  this  pattern  has  two  callout         default value is zero.  For  example,  this  pattern  has  two  callout
2573         points:         points:
2574    
2575           (?C1)eabc(?C2)def           (?C1)abc(?C2)def
2576    
2577         If  the  PCRE_AUTO_CALLOUT  option  bit  is  set when pcre_compile() is         If  the  PCRE_AUTO_CALLOUT  option  bit  is  set when pcre_compile() is
2578         called, PCRE automatically  inserts  callouts,  all  with  number  255,         called, PCRE automatically  inserts  callouts,  all  with  number  255,
# Line 2155  THE CALLOUT INTERFACE Line 2647  THE CALLOUT INTERFACE
2647         The subject and subject_length fields contain copies of the values that         The subject and subject_length fields contain copies of the values that
2648         were passed to pcre_exec().         were passed to pcre_exec().
2649    
2650         The start_match field contains the offset within the subject  at  which         The start_match field normally contains the offset within  the  subject
2651         the  current match attempt started. If the pattern is not anchored, the         at  which  the  current  match  attempt started. However, if the escape
2652         callout function may be called several times from the same point in the         sequence \K has been encountered, this value is changed to reflect  the
2653         pattern for different starting points in the subject.         modified  starting  point.  If the pattern is not anchored, the callout
2654           function may be called several times from the same point in the pattern
2655           for different starting points in the subject.
2656    
2657         The  current_position  field  contains the offset within the subject of         The  current_position  field  contains the offset within the subject of
2658         the current match pointer.         the current match pointer.
# Line 2211  RETURN VALUES Line 2705  RETURN VALUES
2705         reserved for use by callout functions; it will never be  used  by  PCRE         reserved for use by callout functions; it will never be  used  by  PCRE
2706         itself.         itself.
2707    
2708  Last updated: 28 February 2005  
2709  Copyright (c) 1997-2005 University of Cambridge.  AUTHOR
2710    
2711           Philip Hazel
2712           University Computing Service
2713           Cambridge CB2 3QH, England.
2714    
2715    
2716    REVISION
2717    
2718           Last updated: 29 May 2007
2719           Copyright (c) 1997-2007 University of Cambridge.
2720  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
2721    
2722    
# Line 2226  NAME Line 2730  NAME
2730  DIFFERENCES BETWEEN PCRE AND PERL  DIFFERENCES BETWEEN PCRE AND PERL
2731    
2732         This  document describes the differences in the ways that PCRE and Perl         This  document describes the differences in the ways that PCRE and Perl
2733         handle regular expressions. The differences  described  here  are  with         handle regular expressions. The differences described here  are  mainly
2734         respect to Perl 5.8.         with  respect  to  Perl 5.8, though PCRE versions 7.0 and later contain
2735           some features that are expected to be in the forthcoming Perl 5.10.
2736         1.  PCRE does not have full UTF-8 support. Details of what it does have  
2737         are given in the section on UTF-8 support in the main pcre page.         1. PCRE has only a subset of Perl's UTF-8 and Unicode support.  Details
2738           of  what  it does have are given in the section on UTF-8 support in the
2739           main pcre page.
2740    
2741         2. PCRE does not allow repeat quantifiers on lookahead assertions. Perl         2. PCRE does not allow repeat quantifiers on lookahead assertions. Perl
2742         permits  them,  but they do not mean what you might think. For example,         permits  them,  but they do not mean what you might think. For example,
# Line 2257  DIFFERENCES BETWEEN PCRE AND PERL Line 2763  DIFFERENCES BETWEEN PCRE AND PERL
2763         6. The Perl escape sequences \p, \P, and \X are supported only if  PCRE         6. The Perl escape sequences \p, \P, and \X are supported only if  PCRE
2764         is  built  with Unicode character property support. The properties that         is  built  with Unicode character property support. The properties that
2765         can be tested with \p and \P are limited to the general category  prop-         can be tested with \p and \P are limited to the general category  prop-
2766         erties such as Lu and Nd.         erties  such  as  Lu and Nd, script names such as Greek or Han, and the
2767           derived properties Any and L&.
2768    
2769         7. PCRE does support the \Q...\E escape for quoting substrings. Charac-         7. PCRE does support the \Q...\E escape for quoting substrings. Charac-
2770         ters in between are treated as literals.  This  is  slightly  different         ters  in  between  are  treated as literals. This is slightly different
2771         from  Perl  in  that  $  and  @ are also handled as literals inside the         from Perl in that $ and @ are  also  handled  as  literals  inside  the
2772         quotes. In Perl, they cause variable interpolation (but of course  PCRE         quotes.  In Perl, they cause variable interpolation (but of course PCRE
2773         does not have variables). Note the following examples:         does not have variables). Note the following examples:
2774    
2775             Pattern            PCRE matches      Perl matches             Pattern            PCRE matches      Perl matches
# Line 2272  DIFFERENCES BETWEEN PCRE AND PERL Line 2779  DIFFERENCES BETWEEN PCRE AND PERL
2779             \Qabc\$xyz\E       abc\$xyz          abc\$xyz             \Qabc\$xyz\E       abc\$xyz          abc\$xyz
2780             \Qabc\E\$\Qxyz\E   abc$xyz           abc$xyz             \Qabc\E\$\Qxyz\E   abc$xyz           abc$xyz
2781    
2782         The  \Q...\E  sequence  is recognized both inside and outside character         The \Q...\E sequence is recognized both inside  and  outside  character
2783         classes.         classes.
2784    
2785         8. Fairly obviously, PCRE does not support the (?{code}) and (?p{code})         8. Fairly obviously, PCRE does not support the (?{code}) and (??{code})
2786         constructions.  However,  there is support for recursive patterns using         constructions. However, there is support for recursive  patterns.  This
2787         the non-Perl items (?R),  (?number),  and  (?P>name).  Also,  the  PCRE         is  not available in Perl 5.8, but will be in Perl 5.10. Also, the PCRE
2788         "callout"  feature allows an external function to be called during pat-         "callout" feature allows an external function to be called during  pat-
2789         tern matching. See the pcrecallout documentation for details.         tern matching. See the pcrecallout documentation for details.
2790    
2791         9. There are some differences that are concerned with the  settings  of         9.  Subpatterns  that  are  called  recursively or as "subroutines" are
2792         captured  strings  when  part  of  a  pattern is repeated. For example,         always treated as atomic groups in  PCRE.  This  is  like  Python,  but
2793         matching "aba" against the  pattern  /^(a(b)?)+$/  in  Perl  leaves  $2         unlike Perl.
2794    
2795           10.  There are some differences that are concerned with the settings of
2796           captured strings when part of  a  pattern  is  repeated.  For  example,
2797           matching  "aba"  against  the  pattern  /^(a(b)?)+$/  in Perl leaves $2
2798         unset, but in PCRE it is set to "b".         unset, but in PCRE it is set to "b".
2799    
2800         10. PCRE provides some extensions to the Perl regular expression facil-         11.  PCRE  does  support  Perl  5.10's  backtracking  verbs  (*ACCEPT),
2801         ities:         (*FAIL),  (*F),  (*COMMIT), (*PRUNE), (*SKIP), and (*THEN), but only in
2802           the forms without an  argument.  PCRE  does  not  support  (*MARK).  If
2803           (*ACCEPT)  is within capturing parentheses, PCRE does not set that cap-
2804           ture group; this is different to Perl.
2805    
2806           12. PCRE provides some extensions to the Perl regular expression facil-
2807           ities.   Perl  5.10  will  include new features that are not in earlier
2808           versions, some of which (such as named parentheses) have been  in  PCRE
2809           for some time. This list is with respect to Perl 5.10:
2810    
2811         (a) Although lookbehind assertions must  match  fixed  length  strings,         (a)  Although  lookbehind  assertions  must match fixed length strings,
2812         each alternative branch of a lookbehind assertion can match a different         each alternative branch of a lookbehind assertion can match a different
2813         length of string. Perl requires them all to have the same length.         length of string. Perl requires them all to have the same length.
2814    
2815         (b) If PCRE_DOLLAR_ENDONLY is set and PCRE_MULTILINE is not set, the  $         (b)  If PCRE_DOLLAR_ENDONLY is set and PCRE_MULTILINE is not set, the $
2816         meta-character matches only at the very end of the string.         meta-character matches only at the very end of the string.
2817    
2818         (c) If PCRE_EXTRA is set, a backslash followed by a letter with no spe-         (c) If PCRE_EXTRA is set, a backslash followed by a letter with no spe-
2819         cial meaning is faulted.         cial meaning is faulted. Otherwise, like Perl, the backslash is quietly
2820           ignored.  (Perl can be made to issue a warning.)
2821    
2822         (d) If PCRE_UNGREEDY is set, the greediness of the  repetition  quanti-         (d) If PCRE_UNGREEDY is set, the greediness of the  repetition  quanti-
2823         fiers is inverted, that is, by default they are not greedy, but if fol-         fiers is inverted, that is, by default they are not greedy, but if fol-
# Line 2309  DIFFERENCES BETWEEN PCRE AND PERL Line 2829  DIFFERENCES BETWEEN PCRE AND PERL
2829         (f)  The PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, and PCRE_NO_AUTO_CAP-         (f)  The PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, and PCRE_NO_AUTO_CAP-
2830         TURE options for pcre_exec() have no Perl equivalents.         TURE options for pcre_exec() have no Perl equivalents.
2831    
2832         (g) The (?R), (?number), and (?P>name) constructs allows for  recursive         (g) The \R escape sequence can be restricted to match only CR,  LF,  or
2833         pattern  matching  (Perl  can  do  this using the (?p{code}) construct,         CRLF by the PCRE_BSR_ANYCRLF option.
2834         which PCRE cannot support.)  
2835           (h) The callout facility is PCRE-specific.
2836    
2837           (i) The partial matching facility is PCRE-specific.
2838    
2839           (j) Patterns compiled by PCRE can be saved and re-used at a later time,
2840           even on different hosts that have the other endianness.
2841    
2842         (h) PCRE supports named capturing substrings, using the Python  syntax.         (k) The alternative matching function (pcre_dfa_exec())  matches  in  a
2843           different way and is not Perl-compatible.
2844    
2845         (i)  PCRE  supports  the  possessive quantifier "++" syntax, taken from         (l)  PCRE  recognizes some special sequences such as (*CR) at the start
2846         Sun's Java package.         of a pattern that set overall options that cannot be changed within the
2847           pattern.
2848    
        (j) The (R) condition, for testing recursion, is a PCRE extension.  
2849    
2850         (k) The callout facility is PCRE-specific.  AUTHOR
2851    
2852         (l) The partial matching facility is PCRE-specific.         Philip Hazel
2853           University Computing Service
2854           Cambridge CB2 3QH, England.
2855    
        (m) Patterns compiled by PCRE can be saved and re-used at a later time,  
        even on different hosts that have the other endianness.  
2856    
2857         (n)  The  alternative  matching function (pcre_dfa_exec()) matches in a  REVISION
        different way and is not Perl-compatible.  
2858    
2859  Last updated: 28 February 2005         Last updated: 11 September 2007
2860  Copyright (c) 1997-2005 University of Cambridge.         Copyright (c) 1997-2007 University of Cambridge.
2861  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
2862    
2863    
# Line 2344  NAME Line 2870  NAME
2870    
2871  PCRE REGULAR EXPRESSION DETAILS  PCRE REGULAR EXPRESSION DETAILS
2872    
2873         The  syntax  and semantics of the regular expressions supported by PCRE         The  syntax and semantics of the regular expressions that are supported
2874         are described below. Regular expressions are also described in the Perl         by PCRE are described in detail below. There is a quick-reference  syn-
2875         documentation  and  in  a  number  of books, some of which have copious         tax  summary  in  the  pcresyntax  page. Perl's regular expressions are
2876         examples.  Jeffrey Friedl's "Mastering Regular Expressions",  published         described in its own documentation, and regular expressions in  general
2877         by  O'Reilly, covers regular expressions in great detail. This descrip-         are  covered in a number of books, some of which have copious examples.
2878         tion of PCRE's regular expressions is intended as reference material.         Jeffrey  Friedl's  "Mastering  Regular   Expressions",   published   by
2879           O'Reilly,  covers regular expressions in great detail. This description
2880           of PCRE's regular expressions is intended as reference material.
2881    
2882         The original operation of PCRE was on strings of  one-byte  characters.         The original operation of PCRE was on strings of  one-byte  characters.
2883         However,  there is now also support for UTF-8 character strings. To use         However,  there is now also support for UTF-8 character strings. To use
# Line 2363  PCRE REGULAR EXPRESSION DETAILS Line 2891  PCRE REGULAR EXPRESSION DETAILS
2891         ported  by  PCRE when its main matching function, pcre_exec(), is used.         ported  by  PCRE when its main matching function, pcre_exec(), is used.
2892         From  release  6.0,   PCRE   offers   a   second   matching   function,         From  release  6.0,   PCRE   offers   a   second   matching   function,
2893         pcre_dfa_exec(),  which matches using a different algorithm that is not         pcre_dfa_exec(),  which matches using a different algorithm that is not
2894         Perl-compatible. The advantages and disadvantages  of  the  alternative         Perl-compatible. Some of the features discussed below are not available
2895         function, and how it differs from the normal function, are discussed in         when  pcre_dfa_exec()  is used. The advantages and disadvantages of the
2896         the pcrematching page.         alternative function, and how it differs from the normal function,  are
2897           discussed in the pcrematching page.
2898         A regular expression is a pattern that is  matched  against  a  subject  
2899         string  from  left  to right. Most characters stand for themselves in a  
2900         pattern, and match the corresponding characters in the  subject.  As  a  NEWLINE CONVENTIONS
2901    
2902           PCRE  supports five different conventions for indicating line breaks in
2903           strings: a single CR (carriage return) character, a  single  LF  (line-
2904           feed) character, the two-character sequence CRLF, any of the three pre-
2905           ceding, or any Unicode newline sequence. The pcreapi page  has  further
2906           discussion  about newlines, and shows how to set the newline convention
2907           in the options arguments for the compiling and matching functions.
2908    
2909           It is also possible to specify a newline convention by starting a  pat-
2910           tern string with one of the following five sequences:
2911    
2912             (*CR)        carriage return
2913             (*LF)        linefeed
2914             (*CRLF)      carriage return, followed by linefeed
2915             (*ANYCRLF)   any of the three above
2916             (*ANY)       all Unicode newline sequences
2917    
2918           These override the default and the options given to pcre_compile(). For
2919           example, on a Unix system where LF is the default newline sequence, the
2920           pattern
2921    
2922             (*CR)a.b
2923    
2924           changes the convention to CR. That pattern matches "a\nb" because LF is
2925           no longer a newline. Note that these special settings,  which  are  not
2926           Perl-compatible,  are  recognized  only at the very start of a pattern,
2927           and that they must be in upper case.  If  more  than  one  of  them  is
2928           present, the last one is used.
2929    
2930           The  newline  convention  does  not  affect what the \R escape sequence
2931           matches. By default, this is any Unicode  newline  sequence,  for  Perl
2932           compatibility.  However, this can be changed; see the description of \R
2933           in the section entitled "Newline sequences" below. A change of \R  set-
2934           ting can be combined with a change of newline convention.
2935    
2936    
2937    CHARACTERS AND METACHARACTERS
2938    
2939           A  regular  expression  is  a pattern that is matched against a subject
2940           string from left to right. Most characters stand for  themselves  in  a
2941           pattern,  and  match  the corresponding characters in the subject. As a
2942         trivial example, the pattern         trivial example, the pattern
2943    
2944           The quick brown fox           The quick brown fox
2945    
2946         matches a portion of a subject string that is identical to itself. When         matches a portion of a subject string that is identical to itself. When
2947         caseless matching is specified (the PCRE_CASELESS option), letters  are         caseless  matching is specified (the PCRE_CASELESS option), letters are
2948         matched  independently  of case. In UTF-8 mode, PCRE always understands         matched independently of case. In UTF-8 mode, PCRE  always  understands
2949         the concept of case for characters whose values are less than  128,  so         the  concept  of case for characters whose values are less than 128, so
2950         caseless  matching  is always possible. For characters with higher val-         caseless matching is always possible. For characters with  higher  val-
2951         ues, the concept of case is supported if PCRE is compiled with  Unicode         ues,  the concept of case is supported if PCRE is compiled with Unicode
2952         property  support,  but  not  otherwise.   If  you want to use caseless         property support, but not otherwise.   If  you  want  to  use  caseless
2953         matching for characters 128 and above, you must  ensure  that  PCRE  is         matching  for  characters  128  and above, you must ensure that PCRE is
2954         compiled with Unicode property support as well as with UTF-8 support.         compiled with Unicode property support as well as with UTF-8 support.
2955    
2956         The  power  of  regular  expressions  comes from the ability to include         The power of regular expressions comes  from  the  ability  to  include
2957         alternatives and repetitions in the pattern. These are encoded  in  the         alternatives  and  repetitions in the pattern. These are encoded in the
2958         pattern by the use of metacharacters, which do not stand for themselves         pattern by the use of metacharacters, which do not stand for themselves
2959         but instead are interpreted in some special way.         but instead are interpreted in some special way.
2960    
2961         There are two different sets of metacharacters: those that  are  recog-         There  are  two different sets of metacharacters: those that are recog-
2962         nized  anywhere in the pattern except within square brackets, and those         nized anywhere in the pattern except within square brackets, and  those
2963         that are recognized in square brackets. Outside  square  brackets,  the         that  are  recognized  within square brackets. Outside square brackets,
2964         metacharacters are as follows:         the metacharacters are as follows:
2965    
2966           \      general escape character with several uses           \      general escape character with several uses
2967           ^      assert start of string (or line, in multiline mode)           ^      assert start of string (or line, in multiline mode)
# Line 2410  PCRE REGULAR EXPRESSION DETAILS Line 2979  PCRE REGULAR EXPRESSION DETAILS
2979                  also "possessive quantifier"                  also "possessive quantifier"
2980           {      start min/max quantifier           {      start min/max quantifier
2981    
2982         Part  of  a  pattern  that is in square brackets is called a "character         Part of a pattern that is in square brackets  is  called  a  "character
2983         class". In a character class the only metacharacters are:         class". In a character class the only metacharacters are:
2984    
2985           \      general escape character           \      general escape character
# Line 2420  PCRE REGULAR EXPRESSION DETAILS Line 2989  PCRE REGULAR EXPRESSION DETAILS
2989                    syntax)                    syntax)
2990           ]      terminates the character class           ]      terminates the character class
2991    
2992         The following sections describe the use of each of the  metacharacters.         The  following sections describe the use of each of the metacharacters.
2993    
2994    
2995  BACKSLASH  BACKSLASH
2996    
2997         The backslash character has several uses. Firstly, if it is followed by         The backslash character has several uses. Firstly, if it is followed by
2998         a non-alphanumeric character, it takes away any  special  meaning  that         a  non-alphanumeric  character,  it takes away any special meaning that
2999         character  may  have.  This  use  of  backslash  as an escape character         character may have. This  use  of  backslash  as  an  escape  character
3000         applies both inside and outside character classes.         applies both inside and outside character classes.
3001    
3002         For example, if you want to match a * character, you write  \*  in  the         For  example,  if  you want to match a * character, you write \* in the
3003         pattern.   This  escaping  action  applies whether or not the following         pattern.  This escaping action applies whether  or  not  the  following
3004         character would otherwise be interpreted as a metacharacter, so  it  is         character  would  otherwise be interpreted as a metacharacter, so it is
3005         always  safe  to  precede  a non-alphanumeric with backslash to specify         always safe to precede a non-alphanumeric  with  backslash  to  specify
3006         that it stands for itself. In particular, if you want to match a  back-         that  it stands for itself. In particular, if you want to match a back-
3007         slash, you write \\.         slash, you write \\.
3008    
3009         If  a  pattern is compiled with the PCRE_EXTENDED option, whitespace in         If a pattern is compiled with the PCRE_EXTENDED option,  whitespace  in
3010         the pattern (other than in a character class) and characters between  a         the  pattern (other than in a character class) and characters between a
3011         # outside a character class and the next newline character are ignored.         # outside a character class and the next newline are ignored. An escap-
3012         An escaping backslash can be used to include a whitespace or #  charac-         ing  backslash  can  be  used to include a whitespace or # character as
3013         ter as part of the pattern.         part of the pattern.
3014    
3015         If  you  want  to remove the special meaning from a sequence of charac-         If you want to remove the special meaning from a  sequence  of  charac-
3016         ters, you can do so by putting them between \Q and \E. This is  differ-         ters,  you can do so by putting them between \Q and \E. This is differ-
3017         ent  from  Perl  in  that  $  and  @ are handled as literals in \Q...\E         ent from Perl in that $ and  @  are  handled  as  literals  in  \Q...\E
3018         sequences in PCRE, whereas in Perl, $ and @ cause  variable  interpola-         sequences  in  PCRE, whereas in Perl, $ and @ cause variable interpola-
3019         tion. Note the following examples:         tion. Note the following examples:
3020    
3021           Pattern            PCRE matches   Perl matches           Pattern            PCRE matches   Perl matches
# Line 2456  BACKSLASH Line 3025  BACKSLASH
3025           \Qabc\$xyz\E       abc\$xyz       abc\$xyz           \Qabc\$xyz\E       abc\$xyz       abc\$xyz
3026           \Qabc\E\$\Qxyz\E   abc$xyz        abc$xyz           \Qabc\E\$\Qxyz\E   abc$xyz        abc$xyz
3027    
3028         The  \Q...\E  sequence  is recognized both inside and outside character         The \Q...\E sequence is recognized both inside  and  outside  character
3029         classes.         classes.
3030    
3031     Non-printing characters     Non-printing characters
3032    
3033         A second use of backslash provides a way of encoding non-printing char-         A second use of backslash provides a way of encoding non-printing char-
3034         acters  in patterns in a visible manner. There is no restriction on the         acters in patterns in a visible manner. There is no restriction on  the
3035         appearance of non-printing characters, apart from the binary zero  that         appearance  of non-printing characters, apart from the binary zero that
3036         terminates  a  pattern,  but  when  a pattern is being prepared by text         terminates a pattern, but when a pattern  is  being  prepared  by  text
3037         editing, it is usually easier  to  use  one  of  the  following  escape         editing,  it  is  usually  easier  to  use  one of the following escape
3038         sequences than the binary character it represents:         sequences than the binary character it represents:
3039    
3040           \a        alarm, that is, the BEL character (hex 07)           \a        alarm, that is, the BEL character (hex 07)
3041           \cx       "control-x", where x is any character           \cx       "control-x", where x is any character
3042           \e        escape (hex 1B)           \e        escape (hex 1B)
3043           \f        formfeed (hex 0C)           \f        formfeed (hex 0C)
3044           \n        newline (hex 0A)           \n        linefeed (hex 0A)
3045           \r        carriage return (hex 0D)           \r        carriage return (hex 0D)
3046           \t        tab (hex 09)           \t        tab (hex 09)
3047           \ddd      character with octal code ddd, or backreference           \ddd      character with octal code ddd, or backreference
3048           \xhh      character with hex code hh           \xhh      character with hex code hh
3049           \x{hhh..} character with hex code hhh... (UTF-8 mode only)           \x{hhh..} character with hex code hhh..
3050    
3051         The  precise  effect of \cx is as follows: if x is a lower case letter,         The precise effect of \cx is as follows: if x is a lower  case  letter,
3052         it is converted to upper case. Then bit 6 of the character (hex 40)  is         it  is converted to upper case. Then bit 6 of the character (hex 40) is
3053         inverted.   Thus  \cz becomes hex 1A, but \c{ becomes hex 3B, while \c;         inverted.  Thus \cz becomes hex 1A, but \c{ becomes hex 3B,  while  \c;
3054         becomes hex 7B.         becomes hex 7B.
3055    
3056         After \x, from zero to two hexadecimal digits are read (letters can  be         After  \x, from zero to two hexadecimal digits are read (letters can be
3057         in  upper or lower case). In UTF-8 mode, any number of hexadecimal dig-         in upper or lower case). Any number of hexadecimal  digits  may  appear
3058         its may appear between \x{ and }, but the value of the  character  code         between  \x{  and  },  but the value of the character code must be less
3059         must  be  less  than  2**31  (that is, the maximum hexadecimal value is         than 256 in non-UTF-8 mode, and less than 2**31 in UTF-8 mode. That is,
3060         7FFFFFFF). If characters other than hexadecimal digits  appear  between         the  maximum value in hexadecimal is 7FFFFFFF. Note that this is bigger
3061         \x{  and }, or if there is no terminating }, this form of escape is not         than the largest Unicode code point, which is 10FFFF.
3062         recognized. Instead, the initial \x will  be  interpreted  as  a  basic  
3063         hexadecimal  escape, with no following digits, giving a character whose         If characters other than hexadecimal digits appear between \x{  and  },
3064         value is zero.         or if there is no terminating }, this form of escape is not recognized.
3065           Instead, the initial \x will be  interpreted  as  a  basic  hexadecimal
3066           escape,  with  no  following  digits, giving a character whose value is
3067           zero.
3068    
3069         Characters whose value is less than 256 can be defined by either of the         Characters whose value is less than 256 can be defined by either of the
3070         two  syntaxes for \x when PCRE is in UTF-8 mode. There is no difference         two  syntaxes  for  \x. There is no difference in the way they are han-
3071         in the way they are handled. For example, \xdc is exactly the  same  as         dled. For example, \xdc is exactly the same as \x{dc}.
3072         \x{dc}.  
3073           After \0 up to two further octal digits are read. If  there  are  fewer
3074         After  \0  up  to  two further octal digits are read. In both cases, if         than  two  digits,  just  those  that  are  present  are used. Thus the
3075         there are fewer than two digits, just those that are present are  used.         sequence \0\x\07 specifies two binary zeros followed by a BEL character
3076         Thus  the sequence \0\x\07 specifies two binary zeros followed by a BEL         (code  value 7). Make sure you supply two digits after the initial zero
3077         character (code value 7). Make sure you supply  two  digits  after  the         if the pattern character that follows is itself an octal digit.
        initial  zero  if the pattern character that follows is itself an octal  
        digit.  
3078    
3079         The handling of a backslash followed by a digit other than 0 is compli-         The handling of a backslash followed by a digit other than 0 is compli-
3080         cated.  Outside a character class, PCRE reads it and any following dig-         cated.  Outside a character class, PCRE reads it and any following dig-
# Line 2516  BACKSLASH Line 3086  BACKSLASH
3086    
3087         Inside a character class, or if the decimal number is  greater  than  9         Inside a character class, or if the decimal number is  greater  than  9
3088         and  there have not been that many capturing subpatterns, PCRE re-reads         and  there have not been that many capturing subpatterns, PCRE re-reads
3089         up to three octal digits following the backslash, and generates a  sin-         up to three octal digits following the backslash, and uses them to gen-
3090         gle byte from the least significant 8 bits of the value. Any subsequent         erate  a data character. Any subsequent digits stand for themselves. In
3091         digits stand for themselves.  For example:         non-UTF-8 mode, the value of a character specified  in  octal  must  be
3092           less  than  \400.  In  UTF-8 mode, values up to \777 are permitted. For
3093           example:
3094    
3095           \040   is another way of writing a space           \040   is another way of writing a space
3096           \40    is the same, provided there are fewer than 40           \40    is the same, provided there are fewer than 40
# Line 2538  BACKSLASH Line 3110  BACKSLASH
3110         Note that octal values of 100 or greater must not be  introduced  by  a         Note that octal values of 100 or greater must not be  introduced  by  a
3111         leading zero, because no more than three octal digits are ever read.         leading zero, because no more than three octal digits are ever read.
3112    
3113         All  the  sequences  that  define a single byte value or a single UTF-8         All the sequences that define a single character value can be used both
3114         character (in UTF-8 mode) can be used both inside and outside character         inside and outside character classes. In addition, inside  a  character
3115         classes.  In  addition,  inside  a  character class, the sequence \b is         class,  the  sequence \b is interpreted as the backspace character (hex
3116         interpreted as the backspace character (hex 08), and the sequence \X is         08), and the sequences \R and \X are interpreted as the characters  "R"
3117         interpreted  as  the  character  "X".  Outside a character class, these         and  "X", respectively. Outside a character class, these sequences have
3118         sequences have different meanings (see below).         different meanings (see below).
3119    
3120       Absolute and relative back references
3121    
3122           The sequence \g followed by an unsigned or a negative  number,  option-
3123           ally  enclosed  in braces, is an absolute or relative back reference. A
3124           named back reference can be coded as \g{name}. Back references are dis-
3125           cussed later, following the discussion of parenthesized subpatterns.
3126    
3127     Generic character types     Generic character types
3128    
3129         The third use of backslash is for specifying generic  character  types.         Another use of backslash is for specifying generic character types. The
3130         The following are always recognized:         following are always recognized:
3131    
3132           \d     any decimal digit           \d     any decimal digit
3133           \D     any character that is not a decimal digit           \D     any character that is not a decimal digit
3134             \h     any horizontal whitespace character
3135             \H     any character that is not a horizontal whitespace character
3136           \s     any whitespace character           \s     any whitespace character
3137           \S     any character that is not a whitespace character           \S     any character that is not a whitespace character
3138             \v     any vertical whitespace character
3139             \V     any character that is not a vertical whitespace character
3140           \w     any "word" character           \w     any "word" character
3141           \W     any "non-word" character           \W     any "non-word" character
3142    
3143         Each pair of escape sequences partitions the complete set of characters         Each pair of escape sequences partitions the complete set of characters
3144         into two disjoint sets. Any given character matches one, and only  one,         into  two disjoint sets. Any given character matches one, and only one,
3145         of each pair.         of each pair.
3146    
3147         These character type sequences can appear both inside and outside char-         These character type sequences can appear both inside and outside char-
3148         acter classes. They each match one character of the  appropriate  type.         acter  classes.  They each match one character of the appropriate type.
3149         If  the current matching point is at the end of the subject string, all         If the current matching point is at the end of the subject string,  all
3150         of them fail, since there is no character to match.         of them fail, since there is no character to match.
3151    
3152         For compatibility with Perl, \s does not match the VT  character  (code         For  compatibility  with Perl, \s does not match the VT character (code
3153         11).   This makes it different from the the POSIX "space" class. The \s         11).  This makes it different from the the POSIX "space" class. The  \s
3154         characters are HT (9), LF (10), FF (12), CR (13), and space (32).         characters  are  HT  (9), LF (10), FF (12), CR (13), and space (32). If
3155           "use locale;" is included in a Perl script, \s may match the VT charac-
3156           ter. In PCRE, it never does.
3157    
3158           In  UTF-8 mode, characters with values greater than 128 never match \d,
3159           \s, or \w, and always match \D, \S, and \W. This is true even when Uni-
3160           code  character  property  support is available. These sequences retain
3161           their original meanings from before UTF-8 support was available, mainly
3162           for efficiency reasons.
3163    
3164           The sequences \h, \H, \v, and \V are Perl 5.10 features. In contrast to
3165           the other sequences, these do match certain high-valued  codepoints  in
3166           UTF-8 mode.  The horizontal space characters are:
3167    
3168             U+0009     Horizontal tab
3169             U+0020     Space
3170             U+00A0     Non-break space
3171             U+1680     Ogham space mark
3172             U+180E     Mongolian vowel separator
3173             U+2000     En quad
3174             U+2001     Em quad
3175             U+2002     En space
3176             U+2003     Em space
3177             U+2004     Three-per-em space
3178             U+2005     Four-per-em space
3179             U+2006     Six-per-em space
3180             U+2007     Figure space
3181             U+2008     Punctuation space
3182             U+2009     Thin space
3183             U+200A     Hair space
3184             U+202F     Narrow no-break space
3185             U+205F     Medium mathematical space
3186             U+3000     Ideographic space
3187    
3188           The vertical space characters are:
3189    
3190             U+000A     Linefeed
3191             U+000B     Vertical tab
3192             U+000C     Formfeed
3193             U+000D     Carriage return
3194             U+0085     Next line
3195             U+2028     Line separator
3196             U+2029     Paragraph separator
3197    
3198         A "word" character is an underscore or any character less than 256 that         A "word" character is an underscore or any character less than 256 that
3199         is  a  letter  or  digit.  The definition of letters and digits is con-         is a letter or digit. The definition of  letters  and  digits  is  con-
3200         trolled by PCRE's low-valued character tables, and may vary if  locale-         trolled  by PCRE's low-valued character tables, and may vary if locale-
3201         specific  matching is taking place (see "Locale support" in the pcreapi         specific matching is taking place (see "Locale support" in the  pcreapi
3202         page). For example, in the  "fr_FR"  (French)  locale,  some  character         page).  For  example,  in  a French locale such as "fr_FR" in Unix-like
3203         codes  greater  than  128  are used for accented letters, and these are         systems, or "french" in Windows, some character codes greater than  128
3204         matched by \w.         are  used for accented letters, and these are matched by \w. The use of
3205           locales with Unicode is discouraged.
3206    
3207       Newline sequences
3208    
3209           Outside a character class, by default, the escape sequence  \R  matches
3210           any Unicode newline sequence. This is a Perl 5.10 feature. In non-UTF-8
3211           mode \R is equivalent to the following:
3212    
3213             (?>\r\n|\n|\x0b|\f|\r|\x85)
3214    
3215           This is an example of an "atomic group", details  of  which  are  given
3216           below.  This particular group matches either the two-character sequence
3217           CR followed by LF, or  one  of  the  single  characters  LF  (linefeed,
3218           U+000A), VT (vertical tab, U+000B), FF (formfeed, U+000C), CR (carriage
3219           return, U+000D), or NEL (next line, U+0085). The two-character sequence
3220           is treated as a single unit that cannot be split.
3221    
3222           In  UTF-8  mode, two additional characters whose codepoints are greater
3223           than 255 are added: LS (line separator, U+2028) and PS (paragraph sepa-
3224           rator,  U+2029).   Unicode character property support is not needed for
3225           these characters to be recognized.
3226    
3227           It is possible to restrict \R to match only CR, LF, or CRLF (instead of
3228           the  complete  set  of  Unicode  line  endings)  by  setting the option
3229           PCRE_BSR_ANYCRLF either at compile time or when the pattern is matched.
3230           (BSR is an abbrevation for "backslash R".) This can be made the default
3231           when PCRE is built; if this is the case, the  other  behaviour  can  be
3232           requested  via  the  PCRE_BSR_UNICODE  option.   It is also possible to
3233           specify these settings by starting a pattern string  with  one  of  the
3234           following sequences:
3235    
3236             (*BSR_ANYCRLF)   CR, LF, or CRLF only
3237             (*BSR_UNICODE)   any Unicode newline sequence
3238    
3239           These override the default and the options given to pcre_compile(), but
3240           they can be overridden by options given to pcre_exec(). Note that these
3241           special settings, which are not Perl-compatible, are recognized only at
3242           the very start of a pattern, and that they must be in  upper  case.  If
3243           more  than  one  of  them is present, the last one is used. They can be
3244           combined with a change of newline convention, for  example,  a  pattern
3245           can start with:
3246    
3247         In UTF-8 mode, characters with values greater than 128 never match  \d,           (*ANY)(*BSR_ANYCRLF)
3248         \s, or \w, and always match \D, \S, and \W. This is true even when Uni-  
3249         code character property support is available.         Inside a character class, \R matches the letter "R".
3250    
3251     Unicode character properties     Unicode character properties
3252    
3253         When PCRE is built with Unicode character property support, three addi-         When PCRE is built with Unicode character property support, three addi-
3254         tional  escape sequences to match generic character types are available         tional escape sequences that match characters with specific  properties
3255         when UTF-8 mode is selected. They are:         are  available.   When not in UTF-8 mode, these sequences are of course
3256           limited to testing characters whose codepoints are less than  256,  but
3257          \p{xx}   a character with the xx property         they do work in this mode.  The extra escape sequences are:
3258          \P{xx}   a character without the xx property  
3259          \X       an extended Unicode sequence           \p{xx}   a character with the xx property
3260             \P{xx}   a character without the xx property
3261         The property names represented by xx above are limited to  the  Unicode           \X       an extended Unicode sequence
3262         general  category properties. Each character has exactly one such prop-  
3263         erty, specified by a two-letter abbreviation.  For  compatibility  with         The  property  names represented by xx above are limited to the Unicode
3264         Perl,  negation  can be specified by including a circumflex between the         script names, the general category properties, and "Any", which matches
3265         opening brace and the property name. For example, \p{^Lu} is  the  same         any character (including newline). Other properties such as "InMusical-
3266         as \P{Lu}.         Symbols" are not currently supported by PCRE. Note  that  \P{Any}  does
3267           not match any characters, so always causes a match failure.
3268         If  only  one  letter  is  specified with \p or \P, it includes all the  
3269         properties that start with that letter. In this case, in the absence of         Sets of Unicode characters are defined as belonging to certain scripts.
3270         negation, the curly brackets in the escape sequence are optional; these         A character from one of these sets can be matched using a script  name.
3271         two examples have the same effect:         For example:
3272    
3273             \p{Greek}
3274             \P{Han}
3275    
3276           Those  that are not part of an identified script are lumped together as
3277           "Common". The current list of scripts is:
3278    
3279           Arabic,  Armenian,  Balinese,  Bengali,  Bopomofo,  Braille,  Buginese,
3280           Buhid,   Canadian_Aboriginal,   Cherokee,  Common,  Coptic,  Cuneiform,
3281           Cypriot, Cyrillic, Deseret, Devanagari, Ethiopic, Georgian, Glagolitic,
3282           Gothic,  Greek, Gujarati, Gurmukhi, Han, Hangul, Hanunoo, Hebrew, Hira-
3283           gana, Inherited, Kannada,  Katakana,  Kharoshthi,  Khmer,  Lao,  Latin,
3284           Limbu,  Linear_B,  Malayalam,  Mongolian,  Myanmar,  New_Tai_Lue,  Nko,
3285           Ogham, Old_Italic, Old_Persian, Oriya, Osmanya,  Phags_Pa,  Phoenician,
3286           Runic,  Shavian,  Sinhala,  Syloti_Nagri,  Syriac,  Tagalog,  Tagbanwa,
3287           Tai_Le, Tamil, Telugu, Thaana, Thai, Tibetan, Tifinagh, Ugaritic, Yi.
3288    
3289           Each character has exactly one general category property, specified  by
3290           a two-letter abbreviation. For compatibility with Perl, negation can be
3291           specified by including a circumflex between the opening brace  and  the
3292           property name. For example, \p{^Lu} is the same as \P{Lu}.
3293    
3294           If only one letter is specified with \p or \P, it includes all the gen-
3295           eral category properties that start with that letter. In this case,  in
3296           the  absence of negation, the curly brackets in the escape sequence are
3297           optional; these two examples have the same effect:
3298    
3299           \p{L}           \p{L}
3300           \pL           \pL
3301    
3302         The following property codes are supported:         The following general category property codes are supported:
3303    
3304           C     Other           C     Other
3305           Cc    Control           Cc    Control
# Line 2653  BACKSLASH Line 3345  BACKSLASH
3345           Zp    Paragraph separator           Zp    Paragraph separator
3346           Zs    Space separator           Zs    Space separator
3347    
3348         Extended properties such as "Greek" or "InMusicalSymbols" are not  sup-         The special property L& is also supported: it matches a character  that
3349         ported by PCRE.         has  the  Lu,  Ll, or Lt property, in other words, a letter that is not
3350           classified as a modifier or "other".
3351    
3352           The Cs (Surrogate) property applies only to  characters  in  the  range
3353           U+D800  to  U+DFFF. Such characters are not valid in UTF-8 strings (see
3354           RFC 3629) and so cannot be tested by PCRE, unless UTF-8 validity check-
3355           ing  has  been  turned off (see the discussion of PCRE_NO_UTF8_CHECK in
3356           the pcreapi page).
3357    
3358           The long synonyms for these properties  that  Perl  supports  (such  as
3359           \p{Letter})  are  not  supported by PCRE, nor is it permitted to prefix
3360           any of these properties with "Is".
3361    
3362           No character that is in the Unicode table has the Cn (unassigned) prop-
3363           erty.  Instead, this property is assumed for any code point that is not
3364           in the Unicode table.
3365    
3366         Specifying  caseless  matching  does not affect these escape sequences.         Specifying caseless matching does not affect  these  escape  sequences.
3367         For example, \p{Lu} always matches only upper case letters.         For example, \p{Lu} always matches only upper case letters.
3368    
3369         The \X escape matches any number of Unicode  characters  that  form  an         The  \X  escape  matches  any number of Unicode characters that form an
3370         extended Unicode sequence. \X is equivalent to         extended Unicode sequence. \X is equivalent to
3371    
3372           (?>\PM\pM*)           (?>\PM\pM*)
3373    
3374         That  is,  it matches a character without the "mark" property, followed         That is, it matches a character without the "mark"  property,  followed
3375         by zero or more characters with the "mark"  property,  and  treats  the         by  zero  or  more  characters with the "mark" property, and treats the
3376         sequence  as  an  atomic group (see below).  Characters with the "mark"         sequence as an atomic group (see below).  Characters  with  the  "mark"
3377         property are typically accents that affect the preceding character.         property  are  typically  accents  that affect the preceding character.
3378           None of them have codepoints less than 256, so  in  non-UTF-8  mode  \X
3379           matches any one character.
3380    
3381         Matching characters by Unicode property is not fast, because  PCRE  has         Matching  characters  by Unicode property is not fast, because PCRE has
3382         to  search  a  structure  that  contains data for over fifteen thousand         to search a structure that contains  data  for  over  fifteen  thousand
3383         characters. That is why the traditional escape sequences such as \d and         characters. That is why the traditional escape sequences such as \d and
3384         \w do not use Unicode properties in PCRE.         \w do not use Unicode properties in PCRE.
3385    
3386       Resetting the match start
3387    
3388           The escape sequence \K, which is a Perl 5.10 feature, causes any previ-
3389           ously  matched  characters  not  to  be  included  in the final matched
3390           sequence. For example, the pattern:
3391    
3392             foo\Kbar
3393    
3394           matches "foobar", but reports that it has matched "bar".  This  feature
3395           is  similar  to  a lookbehind assertion (described below).  However, in
3396           this case, the part of the subject before the real match does not  have
3397           to  be of fixed length, as lookbehind assertions do. The use of \K does
3398           not interfere with the setting of captured  substrings.   For  example,
3399           when the pattern
3400    
3401             (foo)\Kbar
3402    
3403           matches "foobar", the first substring is still set to "foo".
3404    
3405     Simple assertions     Simple assertions
3406    
3407         The fourth use of backslash is for certain simple assertions. An asser-         The  final use of backslash is for certain simple assertions. An asser-
3408         tion specifies a condition that has to be met at a particular point  in         tion specifies a condition that has to be met at a particular point  in
3409         a  match, without consuming any characters from the subject string. The         a  match, without consuming any characters from the subject string. The
3410         use of subpatterns for more complicated assertions is described  below.         use of subpatterns for more complicated assertions is described  below.
# Line 2684  BACKSLASH Line 3412  BACKSLASH
3412    
3413           \b     matches at a word boundary           \b     matches at a word boundary
3414           \B     matches when not at a word boundary           \B     matches when not at a word boundary
3415           \A     matches at start of subject           \A     matches at the start of the subject
3416           \Z     matches at end of subject or before newline at end           \Z     matches at the end of the subject
3417           \z     matches at end of subject                   also matches before a newline at the end of the subject
3418           \G     matches at first matching position in subject           \z     matches only at the end of the subject
3419             \G     matches at the first matching position in the subject
3420    
3421         These  assertions may not appear in character classes (but note that \b         These  assertions may not appear in character classes (but note that \b
3422         has a different meaning, namely the backspace character, inside a char-         has a different meaning, namely the backspace character, inside a char-
# Line 2707  BACKSLASH Line 3436  BACKSLASH
3436         However, if the startoffset argument of pcre_exec() is non-zero,  indi-         However, if the startoffset argument of pcre_exec() is non-zero,  indi-
3437         cating that matching is to start at a point other than the beginning of         cating that matching is to start at a point other than the beginning of
3438         the subject, \A can never match. The difference between \Z  and  \z  is         the subject, \A can never match. The difference between \Z  and  \z  is
3439         that  \Z  matches  before  a  newline that is the last character of the         that \Z matches before a newline at the end of the string as well as at
3440         string as well as at the end of the string, whereas \z matches only  at         the very end, whereas \z matches only at the end.
3441         the end.  
3442           The \G assertion is true only when the current matching position is  at
3443         The  \G assertion is true only when the current matching position is at         the  start point of the match, as specified by the startoffset argument
3444         the start point of the match, as specified by the startoffset  argument         of pcre_exec(). It differs from \A when the  value  of  startoffset  is
3445         of  pcre_exec().  It  differs  from \A when the value of startoffset is         non-zero.  By calling pcre_exec() multiple times with appropriate argu-
        non-zero. By calling pcre_exec() multiple times with appropriate  argu-  
3446         ments, you can mimic Perl's /g option, and it is in this kind of imple-         ments, you can mimic Perl's /g option, and it is in this kind of imple-
3447         mentation where \G can be useful.         mentation where \G can be useful.
3448    
3449         Note, however, that PCRE's interpretation of \G, as the  start  of  the         Note,  however,  that  PCRE's interpretation of \G, as the start of the
3450         current match, is subtly different from Perl's, which defines it as the         current match, is subtly different from Perl's, which defines it as the
3451         end of the previous match. In Perl, these can  be  different  when  the         end  of  the  previous  match. In Perl, these can be different when the
3452         previously  matched  string was empty. Because PCRE does just one match         previously matched string was empty. Because PCRE does just  one  match
3453         at a time, it cannot reproduce this behaviour.         at a time, it cannot reproduce this behaviour.
3454    
3455         If all the alternatives of a pattern begin with \G, the  expression  is         If  all  the alternatives of a pattern begin with \G, the expression is
3456         anchored to the starting match position, and the "anchored" flag is set         anchored to the starting match position, and the "anchored" flag is set
3457         in the compiled regular expression.         in the compiled regular expression.
3458    
# Line 2732  BACKSLASH Line 3460  BACKSLASH
3460  CIRCUMFLEX AND DOLLAR  CIRCUMFLEX AND DOLLAR
3461    
3462         Outside a character class, in the default matching mode, the circumflex         Outside a character class, in the default matching mode, the circumflex
3463         character  is  an  assertion  that is true only if the current matching         character is an assertion that is true only  if  the  current  matching
3464         point is at the start of the subject string. If the  startoffset  argu-         point  is  at the start of the subject string. If the startoffset argu-
3465         ment  of  pcre_exec()  is  non-zero,  circumflex can never match if the         ment of pcre_exec() is non-zero, circumflex  can  never  match  if  the
3466         PCRE_MULTILINE option is unset. Inside a  character  class,  circumflex         PCRE_MULTILINE  option  is  unset. Inside a character class, circumflex
3467         has an entirely different meaning (see below).         has an entirely different meaning (see below).
3468    
3469         Circumflex  need  not be the first character of the pattern if a number         Circumflex need not be the first character of the pattern if  a  number
3470         of alternatives are involved, but it should be the first thing in  each         of  alternatives are involved, but it should be the first thing in each
3471         alternative  in  which  it appears if the pattern is ever to match that         alternative in which it appears if the pattern is ever  to  match  that
3472         branch. If all possible alternatives start with a circumflex, that  is,         branch.  If all possible alternatives start with a circumflex, that is,
3473         if  the  pattern  is constrained to match only at the start of the sub-         if the pattern is constrained to match only at the start  of  the  sub-
3474         ject, it is said to be an "anchored" pattern.  (There  are  also  other         ject,  it  is  said  to be an "anchored" pattern. (There are also other
3475         constructs that can cause a pattern to be anchored.)         constructs that can cause a pattern to be anchored.)
3476    
3477         A  dollar  character  is  an assertion that is true only if the current         A dollar character is an assertion that is true  only  if  the  current
3478         matching point is at the end of  the  subject  string,  or  immediately         matching  point  is  at  the  end of the subject string, or immediately
3479         before a newline character that is the last character in the string (by         before a newline at the end of the string (by default). Dollar need not
3480         default). Dollar need not be the last character of  the  pattern  if  a         be  the  last  character of the pattern if a number of alternatives are
3481         number  of alternatives are involved, but it should be the last item in         involved, but it should be the last item in  any  branch  in  which  it
3482         any branch in which it appears.  Dollar has no  special  meaning  in  a         appears. Dollar has no special meaning in a character class.
        character class.  
3483    
3484         The  meaning  of  dollar  can be changed so that it matches only at the         The  meaning  of  dollar  can be changed so that it matches only at the
3485         very end of the string, by setting the  PCRE_DOLLAR_ENDONLY  option  at         very end of the string, by setting the  PCRE_DOLLAR_ENDONLY  option  at
3486         compile time. This does not affect the \Z assertion.         compile time. This does not affect the \Z assertion.
3487    
3488         The meanings of the circumflex and dollar characters are changed if the         The meanings of the circumflex and dollar characters are changed if the
3489         PCRE_MULTILINE option is set. When this is the case, they match immedi-         PCRE_MULTILINE option is set. When  this  is  the  case,  a  circumflex
3490         ately  after  and  immediately  before  an  internal newline character,         matches  immediately after internal newlines as well as at the start of
3491         respectively, in addition to matching at the start and end of the  sub-         the subject string. It does not match after a  newline  that  ends  the
3492         ject  string.  For  example,  the  pattern  /^abc$/ matches the subject         string.  A dollar matches before any newlines in the string, as well as
3493         string "def\nabc" (where \n represents a newline character)  in  multi-         at the very end, when PCRE_MULTILINE is set. When newline is  specified
3494         line mode, but not otherwise.  Consequently, patterns that are anchored         as  the  two-character  sequence CRLF, isolated CR and LF characters do
3495         in single line mode because all branches start with ^ are not  anchored         not indicate newlines.
3496         in  multiline  mode,  and  a  match for circumflex is possible when the  
3497         startoffset  argument  of  pcre_exec()  is  non-zero.   The   PCRE_DOL-         For example, the pattern /^abc$/ matches the subject string  "def\nabc"
3498         LAR_ENDONLY option is ignored if PCRE_MULTILINE is set.         (where  \n  represents a newline) in multiline mode, but not otherwise.
3499           Consequently, patterns that are anchored in single  line  mode  because
3500         Note  that  the sequences \A, \Z, and \z can be used to match the start         all  branches  start  with  ^ are not anchored in multiline mode, and a
3501         and end of the subject in both modes, and if all branches of a  pattern         match for circumflex is  possible  when  the  startoffset  argument  of
3502         start  with  \A it is always anchored, whether PCRE_MULTILINE is set or         pcre_exec()  is  non-zero. The PCRE_DOLLAR_ENDONLY option is ignored if
3503         not.         PCRE_MULTILINE is set.
3504    
3505           Note that the sequences \A, \Z, and \z can be used to match  the  start
3506           and  end of the subject in both modes, and if all branches of a pattern
3507           start with \A it is always anchored, whether or not  PCRE_MULTILINE  is
3508           set.
3509    
3510    
3511  FULL STOP (PERIOD, DOT)  FULL STOP (PERIOD, DOT)
3512    
3513         Outside a character class, a dot in the pattern matches any one charac-         Outside a character class, a dot in the pattern matches any one charac-
3514         ter  in  the  subject,  including a non-printing character, but not (by         ter in the subject string except (by default) a character  that  signi-
3515         default) newline.  In UTF-8 mode, a dot matches  any  UTF-8  character,         fies  the  end  of  a line. In UTF-8 mode, the matched character may be
3516         which might be more than one byte long, except (by default) newline. If         more than one byte long.
3517         the PCRE_DOTALL option is set, dots match newlines as  well.  The  han-  
3518         dling  of dot is entirely independent of the handling of circumflex and         When a line ending is defined as a single character, dot never  matches
3519         dollar, the only relationship being  that  they  both  involve  newline         that  character; when the two-character sequence CRLF is used, dot does
3520         characters. Dot has no special meaning in a character class.         not match CR if it is immediately followed  by  LF,  but  otherwise  it
3521           matches  all characters (including isolated CRs and LFs). When any Uni-
3522           code line endings are being recognized, dot does not match CR or LF  or
3523           any of the other line ending characters.
3524    
3525           The  behaviour  of  dot  with regard to newlines can be changed. If the
3526           PCRE_DOTALL option is set, a dot matches  any  one  character,  without
3527           exception. If the two-character sequence CRLF is present in the subject
3528           string, it takes two dots to match it.
3529    
3530           The handling of dot is entirely independent of the handling of  circum-
3531           flex  and  dollar,  the  only relationship being that they both involve
3532           newlines. Dot has no special meaning in a character class.
3533    
3534    
3535  MATCHING A SINGLE BYTE  MATCHING A SINGLE BYTE
3536    
3537         Outside a character class, the escape sequence \C matches any one byte,         Outside a character class, the escape sequence \C matches any one byte,
3538         both in and out of UTF-8 mode. Unlike a dot, it can  match  a  newline.         both  in  and  out  of  UTF-8 mode. Unlike a dot, it always matches any
3539         The  feature  is provided in Perl in order to match individual bytes in         line-ending characters. The feature is provided in  Perl  in  order  to
3540         UTF-8 mode. Because it  breaks  up  UTF-8  characters  into  individual         match  individual bytes in UTF-8 mode. Because it breaks up UTF-8 char-
3541         bytes,  what remains in the string may be a malformed UTF-8 string. For         acters into individual bytes, what remains in the string may be a  mal-
3542         this reason, the \C escape sequence is best avoided.         formed  UTF-8  string.  For this reason, the \C escape sequence is best
3543           avoided.
3544    
3545         PCRE does not allow \C to appear in  lookbehind  assertions  (described         PCRE does not allow \C to appear in  lookbehind  assertions  (described
3546         below),  because  in UTF-8 mode this would make it impossible to calcu-         below),  because  in UTF-8 mode this would make it impossible to calcu-
# Line 2842  SQUARE BRACKETS AND CHARACTER CLASSES Line 3587  SQUARE BRACKETS AND CHARACTER CLASSES
3587         PCRE  is  compiled  with Unicode property support as well as with UTF-8         PCRE  is  compiled  with Unicode property support as well as with UTF-8
3588         support.         support.
3589    
3590         The newline character is never treated in any special way in  character         Characters that might indicate line breaks are  never  treated  in  any
3591         classes,  whatever  the  setting  of  the PCRE_DOTALL or PCRE_MULTILINE         special  way  when  matching  character  classes,  whatever line-ending
3592         options is. A class such as [^a] will always match a newline.         sequence is in  use,  and  whatever  setting  of  the  PCRE_DOTALL  and
3593           PCRE_MULTILINE options is used. A class such as [^a] always matches one
3594           of these characters.
3595    
3596         The minus (hyphen) character can be used to specify a range of  charac-         The minus (hyphen) character can be used to specify a range of  charac-
3597         ters  in  a  character  class.  For  example,  [d-m] matches any letter         ters  in  a  character  class.  For  example,  [d-m] matches any letter
# Line 2870  SQUARE BRACKETS AND CHARACTER CLASSES Line 3617  SQUARE BRACKETS AND CHARACTER CLASSES
3617         If a range that includes letters is used when caseless matching is set,         If a range that includes letters is used when caseless matching is set,
3618         it matches the letters in either case. For example, [W-c] is equivalent         it matches the letters in either case. For example, [W-c] is equivalent
3619         to  [][\\^_`wxyzabc],  matched  caselessly,  and  in non-UTF-8 mode, if         to  [][\\^_`wxyzabc],  matched  caselessly,  and  in non-UTF-8 mode, if
3620         character tables for the "fr_FR" locale are in use, [\xc8-\xcb] matches         character tables for a French locale are in  use,  [\xc8-\xcb]  matches
3621         accented  E  characters in both cases. In UTF-8 mode, PCRE supports the         accented  E  characters in both cases. In UTF-8 mode, PCRE supports the
3622         concept of case for characters with values greater than 128  only  when         concept of case for characters with values greater than 128  only  when
3623         it is compiled with Unicode property support.         it is compiled with Unicode property support.
# Line 2945  VERTICAL BAR Line 3692  VERTICAL BAR
3692    
3693         matches  either "gilbert" or "sullivan". Any number of alternatives may         matches  either "gilbert" or "sullivan". Any number of alternatives may
3694         appear, and an empty  alternative  is  permitted  (matching  the  empty         appear, and an empty  alternative  is  permitted  (matching  the  empty
3695         string).   The  matching  process  tries each alternative in turn, from         string). The matching process tries each alternative in turn, from left
3696         left to right, and the first one that succeeds is used. If the alterna-         to right, and the first one that succeeds is used. If the  alternatives
3697         tives  are within a subpattern (defined below), "succeeds" means match-         are  within a subpattern (defined below), "succeeds" means matching the
3698         ing the rest of the main pattern as well as the alternative in the sub-         rest of the main pattern as well as the alternative in the  subpattern.
        pattern.  
3699    
3700    
3701  INTERNAL OPTION SETTING  INTERNAL OPTION SETTING
3702    
3703         The  settings  of  the  PCRE_CASELESS, PCRE_MULTILINE, PCRE_DOTALL, and         The  settings  of  the  PCRE_CASELESS, PCRE_MULTILINE, PCRE_DOTALL, and
3704         PCRE_EXTENDED options can be changed  from  within  the  pattern  by  a         PCRE_EXTENDED options (which are Perl-compatible) can be  changed  from
3705         sequence  of  Perl  option  letters  enclosed between "(?" and ")". The         within  the  pattern  by  a  sequence  of  Perl option letters enclosed
3706         option letters are         between "(?" and ")".  The option letters are
3707    
3708           i  for PCRE_CASELESS           i  for PCRE_CASELESS
3709           m  for PCRE_MULTILINE           m  for PCRE_MULTILINE
# Line 2971  INTERNAL OPTION SETTING Line 3717  INTERNAL OPTION SETTING
3717         is also permitted. If a  letter  appears  both  before  and  after  the         is also permitted. If a  letter  appears  both  before  and  after  the
3718         hyphen, the option is unset.         hyphen, the option is unset.
3719    
3720           The  PCRE-specific options PCRE_DUPNAMES, PCRE_UNGREEDY, and PCRE_EXTRA
3721           can be changed in the same way as the Perl-compatible options by  using
3722           the characters J, U and X respectively.
3723    
3724         When  an option change occurs at top level (that is, not inside subpat-         When  an option change occurs at top level (that is, not inside subpat-
3725         tern parentheses), the change applies to the remainder of  the  pattern         tern parentheses), the change applies to the remainder of  the  pattern
3726         that follows.  If the change is placed right at the start of a pattern,         that follows.  If the change is placed right at the start of a pattern,
3727         PCRE extracts it into the global options (and it will therefore show up         PCRE extracts it into the global options (and it will therefore show up
3728         in data extracted by the pcre_fullinfo() function).         in data extracted by the pcre_fullinfo() function).
3729    
3730         An option change within a subpattern affects only that part of the cur-         An  option  change  within a subpattern (see below for a description of
3731         rent pattern that follows it, so         subpatterns) affects only that part of the current pattern that follows
3732           it, so
3733    
3734           (a(?i)b)c           (a(?i)b)c
3735    
3736         matches abc and aBc and no other strings (assuming PCRE_CASELESS is not         matches abc and aBc and no other strings (assuming PCRE_CASELESS is not
3737         used).   By  this means, options can be made to have different settings         used).  By this means, options can be made to have  different  settings
3738         in different parts of the pattern. Any changes made in one  alternative         in  different parts of the pattern. Any changes made in one alternative
3739         do  carry  on  into subsequent branches within the same subpattern. For         do carry on into subsequent branches within the  same  subpattern.  For
3740         example,         example,
3741    
3742           (a(?i)b|c)           (a(?i)b|c)
3743    
3744         matches "ab", "aB", "c", and "C", even though  when  matching  "C"  the         matches  "ab",  "aB",  "c",  and "C", even though when matching "C" the
3745         first  branch  is  abandoned before the option setting. This is because         first branch is abandoned before the option setting.  This  is  because
3746         the effects of option settings happen at compile time. There  would  be         the  effects  of option settings happen at compile time. There would be
3747         some very weird behaviour otherwise.         some very weird behaviour otherwise.
3748    
3749         The  PCRE-specific  options PCRE_UNGREEDY and PCRE_EXTRA can be changed         Note: There are other PCRE-specific options that  can  be  set  by  the
3750         in the same way as the Perl-compatible options by using the  characters         application  when  the  compile  or match functions are called. In some
3751         U  and X respectively. The (?X) flag setting is special in that it must         cases the pattern can contain special  leading  sequences  to  override
3752         always occur earlier in the pattern than any of the additional features         what  the  application  has set or what has been defaulted. Details are
3753         it  turns on, even when it is at top level. It is best to put it at the         given in the section entitled "Newline sequences" above.
        start.  
3754    
3755    
3756  SUBPATTERNS  SUBPATTERNS
# Line 3013  SUBPATTERNS Line 3763  SUBPATTERNS
3763           cat(aract|erpillar|)           cat(aract|erpillar|)
3764    
3765         matches  one  of the words "cat", "cataract", or "caterpillar". Without         matches  one  of the words "cat", "cataract", or "caterpillar". Without
3766         the parentheses, it would match "cataract",  "erpillar"  or  the  empty         the parentheses, it would match  "cataract",  "erpillar"  or  an  empty
3767         string.         string.
3768    
3769         2.  It  sets  up  the  subpattern as a capturing subpattern. This means         2.  It  sets  up  the  subpattern as a capturing subpattern. This means
# Line 3042  SUBPATTERNS Line 3792  SUBPATTERNS
3792           the ((?:red|white) (king|queen))           the ((?:red|white) (king|queen))
3793    
3794         the captured substrings are "white queen" and "queen", and are numbered         the captured substrings are "white queen" and "queen", and are numbered
3795         1  and 2. The maximum number of capturing subpatterns is 65535, and the         1 and 2. The maximum number of capturing subpatterns is 65535.
        maximum depth of nesting of all subpatterns, both  capturing  and  non-  
        capturing, is 200.  
3796    
3797         As  a  convenient shorthand, if any option settings are required at the         As  a  convenient shorthand, if any option settings are required at the
3798         start of a non-capturing subpattern,  the  option  letters  may  appear         start of a non-capturing subpattern,  the  option  letters  may  appear
# Line 3060  SUBPATTERNS Line 3808  SUBPATTERNS
3808         "Saturday".         "Saturday".
3809    
3810    
3811    DUPLICATE SUBPATTERN NUMBERS
3812    
3813           Perl 5.10 introduced a feature whereby each alternative in a subpattern
3814           uses the same numbers for its capturing parentheses. Such a  subpattern
3815           starts  with (?| and is itself a non-capturing subpattern. For example,
3816           consider this pattern:
3817    
3818             (?|(Sat)ur|(Sun))day
3819    
3820           Because the two alternatives are inside a (?| group, both sets of  cap-
3821           turing  parentheses  are  numbered one. Thus, when the pattern matches,
3822           you can look at captured substring number  one,  whichever  alternative
3823           matched.  This  construct  is useful when you want to capture part, but
3824           not all, of one of a number of alternatives. Inside a (?| group, paren-
3825           theses  are  numbered as usual, but the number is reset at the start of
3826           each branch. The numbers of any capturing buffers that follow the  sub-
3827           pattern  start after the highest number used in any branch. The follow-
3828           ing example is taken from the Perl documentation.  The  numbers  under-
3829           neath show in which buffer the captured content will be stored.
3830    
3831             # before  ---------------branch-reset----------- after
3832             / ( a )  (?| x ( y ) z | (p (q) r) | (t) u (v) ) ( z ) /x
3833             # 1            2         2  3        2     3     4
3834    
3835           A  backreference  or  a  recursive call to a numbered subpattern always
3836           refers to the first one in the pattern with the given number.
3837    
3838           An alternative approach to using this "branch reset" feature is to  use
3839           duplicate named subpatterns, as described in the next section.
3840    
3841    
3842  NAMED SUBPATTERNS  NAMED SUBPATTERNS
3843    
3844         Identifying  capturing  parentheses  by number is simple, but it can be         Identifying  capturing  parentheses  by number is simple, but it can be
3845         very hard to keep track of the numbers in complicated  regular  expres-         very hard to keep track of the numbers in complicated  regular  expres-
3846         sions.  Furthermore,  if  an