/[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 77 by nigel, Sat Feb 24 21:40:45 2007 UTC revision 289 by ph10, Sun Dec 23 12:17:20 2007 UTC
# Line 7  separate text files for the pcregrep and Line 7  separate text files for the pcregrep and
7  -----------------------------------------------------------------------------  -----------------------------------------------------------------------------
8    
9    
10    PCRE(3)                                                                PCRE(3)
11    
12    
13  NAME  NAME
14         PCRE - Perl-compatible regular expressions         PCRE - Perl-compatible regular expressions
# Line 16  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 51  INTRODUCTION Line 59  INTRODUCTION
59         data  tables  that  are  used by more than one of the exported external         data  tables  that  are  used by more than one of the exported external
60         functions, but which are not intended  for  use  by  external  callers.         functions, but which are not intended  for  use  by  external  callers.
61         Their  names  all begin with "_pcre_", which hopefully will not provoke         Their  names  all begin with "_pcre_", which hopefully will not provoke
62         any name clashes.         any name clashes. In some environments, it is possible to control which
63           external  symbols  are  exported when a shared library is built, and in
64           these cases the undocumented symbols are not exported.
65    
66    
67  USER DOCUMENTATION  USER DOCUMENTATION
# Line 63  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 73  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 94  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.  The maxi-         All values in repeating quantifiers must be less than 65536.
        mum number of capturing subpatterns is 65535.  
113    
114         There is no limit to the number of non-capturing subpatterns,  but  the         There is no limit to the number of parenthesized subpatterns, but there
115         maximum  depth  of  nesting  of  all kinds of parenthesized subpattern,         can be no more than 65535 capturing subpatterns.
116         including capturing subpatterns, assertions, and other types of subpat-  
117         tern, is 200.         The maximum length of name for a named subpattern is 32 characters, and
118           the maximum number of named subpatterns is 10000.
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 126  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           1. An unbraced hexadecimal escape sequence (such  as  \xb3)  matches  a
203           two-byte UTF-8 character if the value is greater than 127.
204    
205         3.  The  original hexadecimal escape sequence, \xhh, matches a two-byte         2.  Octal  numbers  up to \777 are recognized, and match two-byte UTF-8
206         UTF-8 character if the value is greater than 127.         characters for values greater than \177.
207    
208         4. Repeat quantifiers apply to complete UTF-8 characters, not to  indi-         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 180  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    
 Last updated: 07 March 2005  
 Copyright (c) 1997-2005 University of Cambridge.  
 -----------------------------------------------------------------------------  
256    
257    REVISION
258    
259           Last updated: 09 August 2007
260           Copyright (c) 1997-2007 University of Cambridge.
261    ------------------------------------------------------------------------------
262    
263    
264    PCREBUILD(3)                                                      PCREBUILD(3)
265    
266    
267  NAME  NAME
# Line 214  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
296    
297           By default, the configure script will search for a C++ compiler and C++
298           header files. If it finds them, it automatically builds the C++ wrapper
299           library for PCRE. You can disable this by adding
300    
301             --disable-cpp
302    
303           to the configure command.
304    
305    
306  UTF-8 SUPPORT  UTF-8 SUPPORT
# Line 236  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 289  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 302  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 348  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    
 Last updated: 28 February 2005  
 Copyright (c) 1997-2005 University of Cambridge.  
 -----------------------------------------------------------------------------  
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    PCRETEST OPTION FOR LIBREADLINE SUPPORT
535    
536           If you add
537    
538             --enable-pcretest-libreadline
539    
540           to  the  configure  command,  pcretest  is  linked with the libreadline
541           library, and when its input is from a terminal, it reads it  using  the
542           readline() function. This provides line-editing and history facilities.
543           Note that libreadline is GPL-licenced, so if you distribute a binary of
544           pcretest linked in this way, there may be licensing issues.
545    
546    
547    SEE ALSO
548    
549           pcreapi(3), pcre_config(3).
550    
551    
552    AUTHOR
553    
554           Philip Hazel
555           University Computing Service
556           Cambridge CB2 3QH, England.
557    
558    
559    REVISION
560    
561           Last updated: 18 December 2007
562           Copyright (c) 1997-2007 University of Cambridge.
563    ------------------------------------------------------------------------------
564    
565    
566    PCREMATCHING(3)                                                PCREMATCHING(3)
567    
568    
569  NAME  NAME
# Line 412  PCRE MATCHING ALGORITHMS Line 595  PCRE MATCHING ALGORITHMS
595           <something> <something else> <something further>           <something> <something else> <something further>
596    
597         there are three possible answers. The standard algorithm finds only one         there are three possible answers. The standard algorithm finds only one
598         of them, whereas the DFA algorithm finds all three.         of them, whereas the alternative algorithm finds all three.
599    
600    
601  REGULAR EXPRESSIONS AS TREES  REGULAR EXPRESSIONS AS TREES
# Line 421  REGULAR EXPRESSIONS AS TREES Line 604  REGULAR EXPRESSIONS AS TREES
604         resented  as  a  tree structure. An unlimited repetition in the pattern         resented  as  a  tree structure. An unlimited repetition in the pattern
605         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
606         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
607         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
608         search  a  tree: depth-first and breadth-first, and these correspond to         tree:  depth-first  and  breadth-first, and these correspond to the two
609         the two matching algorithms provided by PCRE.         matching algorithms provided by PCRE.
610    
611    
612  THE STANDARD MATCHING ALGORITHM  THE STANDARD MATCHING ALGORITHM
613    
614         In the terminology of Jeffrey Friedl's book Mastering  Regular  Expres-         In the terminology of Jeffrey Friedl's book "Mastering Regular  Expres-
615         sions,  the  standard  algorithm  is  an "NFA algorithm". It conducts a         sions",  the  standard  algorithm  is an "NFA algorithm". It conducts a
616         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
617         single path through the tree, checking that the subject matches what is         single path through the tree, checking that the subject matches what is
618         required. When there is a mismatch, the algorithm  tries  any  alterna-         required. When there is a mismatch, the algorithm  tries  any  alterna-
# Line 453  THE STANDARD MATCHING ALGORITHM Line 636  THE STANDARD MATCHING ALGORITHM
636         This provides support for capturing parentheses and back references.         This provides support for capturing parentheses and back references.
637    
638    
639  THE DFA MATCHING ALGORITHM  THE ALTERNATIVE MATCHING ALGORITHM
640    
641         DFA stands for "deterministic finite automaton", but you do not need to         This algorithm conducts a breadth-first search of  the  tree.  Starting
642         understand the origins of that name. This algorithm conducts a breadth-         from  the  first  matching  point  in the subject, it scans the subject
643         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
644         subject,  it scans the subject string from left to right, once, charac-         this,  it remembers all the paths through the tree that represent valid
645         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",
646         through the tree that represent valid matches.         though  it is not implemented as a traditional finite state machine (it
647           keeps multiple states active simultaneously).
648         The  scan  continues until either the end of the subject is reached, or  
649         there are no more unterminated paths. At this point,  terminated  paths         The scan continues until either the end of the subject is  reached,  or
650         represent  the different matching possibilities (if there are none, the         there  are  no more unterminated paths. At this point, terminated paths
651         match has failed).  Thus, if there is more  than  one  possible  match,         represent the different matching possibilities (if there are none,  the
652           match  has  failed).   Thus,  if there is more than one possible match,
653         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-
654         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
655         match (which is necessarily the shortest) has been found.         match (which is necessarily the shortest) has been found.
656    
657         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 475  THE DFA MATCHING ALGORITHM Line 659  THE DFA MATCHING ALGORITHM
659    
660           cat(er(pillar)?)           cat(er(pillar)?)
661    
662         is matched against the string "the caterpillar catchment",  the  result         is  matched  against the string "the caterpillar catchment", the result
663         will  be the three strings "cat", "cater", and "caterpillar" that start         will be the three strings "cat", "cater", and "caterpillar" that  start
664         at the fourth character of the subject. The algorithm does not automat-         at the fourth character of the subject. The algorithm does not automat-
665         ically move on to find matches that start at later positions.         ically move on to find matches that start at later positions.
666    
667         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
668         supported by the DFA matching algorithm. They are as follows:         supported by the alternative matching algorithm. They are as follows:
669    
670         1. Because the algorithm finds all  possible  matches,  the  greedy  or         1.  Because  the  algorithm  finds  all possible matches, the greedy or
671         ungreedy  nature  of repetition quantifiers is not relevant. Greedy and         ungreedy nature of repetition quantifiers is not relevant.  Greedy  and
672         ungreedy quantifiers are treated in exactly the same way.         ungreedy quantifiers are treated in exactly the same way. However, pos-
673           sessive quantifiers can make a difference when what follows could  also
674           match what is quantified, for example in a pattern like this:
675    
676             ^a++\w!
677    
678           This  pattern matches "aaab!" but not "aaa!", which would be matched by
679           a non-possessive quantifier. Similarly, if an atomic group is  present,
680           it  is matched as if it were a standalone pattern at the current point,
681           and the longest match is then "locked in" for the rest of  the  overall
682           pattern.
683    
684         2. When dealing with multiple paths through the tree simultaneously, it         2. When dealing with multiple paths through the tree simultaneously, it
685         is  not  straightforward  to  keep track of captured substrings for the         is not straightforward to keep track of  captured  substrings  for  the
686         different matching possibilities, and  PCRE's  implementation  of  this         different  matching  possibilities,  and  PCRE's implementation of this
687         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-
688         strings are available.         strings are available.
689    
690         3. Because no substrings are captured, back references within the  pat-         3.  Because no substrings are captured, back references within the pat-
691         tern are not supported, and cause errors if encountered.         tern are not supported, and cause errors if encountered.
692    
693         4.  For  the same reason, conditional expressions that use a backrefer-         4. For the same reason, conditional expressions that use  a  backrefer-
694         ence as the condition are not supported.         ence  as  the  condition or test for a specific group recursion are not
695           supported.
696    
697           5. Because many paths through the tree may be  active,  the  \K  escape
698           sequence, which resets the start of the match when encountered (but may
699           be on some paths and not on others), is not  supported.  It  causes  an
700           error if encountered.
701    
702         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
703         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.
704    
705         6.  The \C escape sequence, which (in the standard algorithm) matches a         7. The \C escape sequence, which (in the standard algorithm) matches  a
706         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-
707         rithm moves through the subject string one character at a time, for all         tive algorithm moves through the subject  string  one  character  at  a
708         active paths through the tree.         time, for all active paths through the tree.
709    
710           8.  None  of  the  backtracking control verbs such as (*PRUNE) are sup-
711           ported.
712    
 ADVANTAGES OF THE DFA ALGORITHM  
713    
714         Using the DFA matching algorithm provides the following advantages:  ADVANTAGES OF THE ALTERNATIVE ALGORITHM
715    
716           Using the alternative matching algorithm provides the following  advan-
717           tages:
718    
719         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-
720         ically  found,  and  in particular, the longest match is found. To find         ically found, and in particular, the longest match is  found.  To  find
721         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
722         things with callouts.         things with callouts.
723    
724         2.  There is much better support for partial matching. The restrictions         2. There is much better support for partial matching. The  restrictions
725         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-
726         rithm  for partial matching do not apply to the DFA algorithm. For non-         rithm for partial matching do not apply to the  alternative  algorithm.
727         anchored patterns, the starting position of a partial match  is  avail-         For  non-anchored patterns, the starting position of a partial match is
728         able.         available.
729    
730         3.  Because  the  DFA algorithm scans the subject string just once, and         3. Because the alternative algorithm  scans  the  subject  string  just
731         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
732         strings  to  the matching function in several pieces, checking for par-         subject strings to the matching function in  several  pieces,  checking
733         tial matching each time.         for partial matching each time.
734    
735    
736  DISADVANTAGES OF THE DFA ALGORITHM  DISADVANTAGES OF THE ALTERNATIVE ALGORITHM
737    
738         The DFA algorithm suffers from a number of disadvantages:         The alternative algorithm suffers from a number of disadvantages:
739    
740         1. It is substantially slower than  the  standard  algorithm.  This  is         1.  It  is  substantially  slower  than the standard algorithm. This is
741         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
742         because it is less susceptible to optimization.         because it is less susceptible to optimization.
743    
744         2. Capturing parentheses and back references are not supported.         2. Capturing parentheses and back references are not supported.
745    
746         3. The "atomic group" feature of PCRE regular expressions is supported,         3. Although atomic groups are supported, their use does not provide the
747         but  does not provide the advantage that it does for the standard algo-         performance advantage that it does for the standard algorithm.
        rithm.  
748    
 Last updated: 28 February 2005  
 Copyright (c) 1997-2005 University of Cambridge.  
 -----------------------------------------------------------------------------  
749    
750    AUTHOR
751    
752           Philip Hazel
753           University Computing Service
754           Cambridge CB2 3QH, England.
755    
756    
757    REVISION
758    
759           Last updated: 08 August 2007
760           Copyright (c) 1997-2007 University of Cambridge.
761    ------------------------------------------------------------------------------
762    
763    
764    PCREAPI(3)                                                          PCREAPI(3)
765    
766    
767  NAME  NAME
# Line 595  PCRE NATIVE API Line 810  PCRE NATIVE API
810         int pcre_get_stringnumber(const pcre *code,         int pcre_get_stringnumber(const pcre *code,
811              const char *name);              const char *name);
812    
813           int pcre_get_stringtable_entries(const pcre *code,
814                const char *name, char **first, char **last);
815    
816         int pcre_get_substring(const char *subject, int *ovector,         int pcre_get_substring(const char *subject, int *ovector,
817              int stringcount, int stringnumber,              int stringcount, int stringnumber,
818              const char **stringptr);              const char **stringptr);
# Line 633  PCRE NATIVE API Line 851  PCRE NATIVE API
851  PCRE API OVERVIEW  PCRE API OVERVIEW
852    
853         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
854         is also a set of wrapper functions that correspond to the POSIX regular         are also some wrapper functions that correspond to  the  POSIX  regular
855         expression  API.  These  are  described in the pcreposix documentation.         expression  API.  These  are  described in the pcreposix documentation.
856         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
857         distributed with PCRE. It is documented in the pcrecpp page.         distributed with PCRE. It is documented in the pcrecpp page.
# Line 655  PCRE API OVERVIEW Line 873  PCRE API OVERVIEW
873    
874         A second matching function, pcre_dfa_exec(), which is not Perl-compati-         A second matching function, pcre_dfa_exec(), which is not Perl-compati-
875         ble,  is  also provided. This uses a different algorithm for the match-         ble,  is  also provided. This uses a different algorithm for the match-
876         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
877         the  subject),  not  just  one. However, this algorithm does not return         point  in  the subject), and scans the subject just once. However, this
878         captured substrings. A description of the two matching  algorithms  and         algorithm does not return captured substrings. A description of the two
879         their  advantages  and disadvantages is given in the pcrematching docu-         matching  algorithms and their advantages and disadvantages is given in
880         mentation.         the pcrematching documentation.
881    
882         In addition to the main compiling and  matching  functions,  there  are         In addition to the main compiling and  matching  functions,  there  are
883         convenience functions for extracting captured substrings from a subject         convenience functions for extracting captured substrings from a subject
# Line 671  PCRE API OVERVIEW Line 889  PCRE API OVERVIEW
889           pcre_get_named_substring()           pcre_get_named_substring()
890           pcre_get_substring_list()           pcre_get_substring_list()
891           pcre_get_stringnumber()           pcre_get_stringnumber()
892             pcre_get_stringtable_entries()
893    
894         pcre_free_substring() and pcre_free_substring_list() are also provided,         pcre_free_substring() and pcre_free_substring_list() are also provided,
895         to free the memory used for extracted strings.         to free the memory used for extracted strings.
# Line 702  PCRE API OVERVIEW Line 921  PCRE API OVERVIEW
921         indirections  to  memory  management functions. These special functions         indirections  to  memory  management functions. These special functions
922         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
923         data, instead of recursive function calls, when running the pcre_exec()         data, instead of recursive function calls, when running the pcre_exec()
924         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
925         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-
926         management, it runs more slowly.  Separate functions  are  provided  so         ments that have limited stacks. Because of the greater  use  of  memory
927         that  special-purpose  external  code  can  be used for this case. When         management,  it  runs  more  slowly. Separate functions are provided so
928         used, these functions are always called in a  stack-like  manner  (last         that special-purpose external code can be  used  for  this  case.  When
929         obtained,  first freed), and always for memory blocks of the same size.         used,  these  functions  are always called in a stack-like manner (last
930           obtained, first freed), and always for memory blocks of the same  size.
931           There  is  a discussion about PCRE's stack usage in the pcrestack docu-
932           mentation.
933    
934         The global variable pcre_callout initially contains NULL. It can be set         The global variable pcre_callout initially contains NULL. It can be set
935         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 715  PCRE API OVERVIEW Line 937  PCRE API OVERVIEW
937         pcrecallout documentation.         pcrecallout documentation.
938    
939    
940    NEWLINES
941    
942           PCRE  supports five different conventions for indicating line breaks in
943           strings: a single CR (carriage return) character, a  single  LF  (line-
944           feed) character, the two-character sequence CRLF, any of the three pre-
945           ceding, or any Unicode newline sequence. The Unicode newline  sequences
946           are  the  three just mentioned, plus the single characters VT (vertical
947           tab, U+000B), FF (formfeed, U+000C), NEL (next line, U+0085), LS  (line
948           separator, U+2028), and PS (paragraph separator, U+2029).
949    
950           Each  of  the first three conventions is used by at least one operating
951           system as its standard newline sequence. When PCRE is built, a  default
952           can  be  specified.  The default default is LF, which is the Unix stan-
953           dard. When PCRE is run, the default can be overridden,  either  when  a
954           pattern is compiled, or when it is matched.
955    
956           At compile time, the newline convention can be specified by the options
957           argument of pcre_compile(), or it can be specified by special  text  at
958           the start of the pattern itself; this overrides any other settings. See
959           the pcrepattern page for details of the special character sequences.
960    
961           In the PCRE documentation the word "newline" is used to mean "the char-
962           acter  or pair of characters that indicate a line break". The choice of
963           newline convention affects the handling of  the  dot,  circumflex,  and
964           dollar metacharacters, the handling of #-comments in /x mode, and, when
965           CRLF is a recognized line ending sequence, the match position  advance-
966           ment for a non-anchored pattern. There is more detail about this in the
967           section on pcre_exec() options below.
968    
969           The choice of newline convention does not affect the interpretation  of
970           the  \n  or  \r  escape  sequences, nor does it affect what \R matches,
971           which is controlled in a similar way, but by separate options.
972    
973    
974  MULTITHREADING  MULTITHREADING
975    
976         The  PCRE  functions  can be used in multi-threading applications, with         The PCRE functions can be used in  multi-threading  applications,  with
977         the  proviso  that  the  memory  management  functions  pointed  to  by         the  proviso  that  the  memory  management  functions  pointed  to  by
978         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
979         callout function pointed to by pcre_callout, are shared by all threads.         callout function pointed to by pcre_callout, are shared by all threads.
980    
981         The  compiled form of a regular expression is not altered during match-         The compiled form of a regular expression is not altered during  match-
982         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
983         at once.         at once.
984    
# Line 730  MULTITHREADING Line 986  MULTITHREADING
986  SAVING PRECOMPILED PATTERNS FOR LATER USE  SAVING PRECOMPILED PATTERNS FOR LATER USE
987    
988         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
989         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
990         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
991         pcreprecompile documentation.         pcreprecompile  documentation.  However, compiling a regular expression
992           with one version of PCRE for use with a different version is not  guar-
993           anteed to work and may cause crashes.
994    
995    
996  CHECKING BUILD-TIME OPTIONS  CHECKING BUILD-TIME OPTIONS
997    
998         int pcre_config(int what, void *where);         int pcre_config(int what, void *where);
999    
1000         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-
1001         cover which optional features have been compiled into the PCRE library.         cover which optional features have been compiled into the PCRE library.
1002         The pcrebuild documentation has more details about these optional  fea-         The  pcrebuild documentation has more details about these optional fea-
1003         tures.         tures.
1004    
1005         The  first  argument  for pcre_config() is an integer, specifying which         The first argument for pcre_config() is an  integer,  specifying  which
1006         information is required; the second argument is a pointer to a variable         information is required; the second argument is a pointer to a variable
1007         into  which  the  information  is  placed. The following information is         into which the information is  placed.  The  following  information  is
1008         available:         available:
1009    
1010           PCRE_CONFIG_UTF8           PCRE_CONFIG_UTF8
1011    
1012         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-
1013         able; otherwise it is set to zero.         able; otherwise it is set to zero.
1014    
1015           PCRE_CONFIG_UNICODE_PROPERTIES           PCRE_CONFIG_UNICODE_PROPERTIES
1016    
1017         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
1018         character properties is available; otherwise it is set to zero.         character properties is available; otherwise it is set to zero.
1019    
1020           PCRE_CONFIG_NEWLINE           PCRE_CONFIG_NEWLINE
1021    
1022         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
1023         used  for the newline character. It is either linefeed (10) or carriage         sequence that is recognized as meaning "newline". The four values  that
1024         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,
1025         operating system.         and -1 for ANY. The default should normally be  the  standard  sequence
1026           for your operating system.
1027    
1028             PCRE_CONFIG_BSR
1029    
1030           The output is an integer whose value indicates what character sequences
1031           the \R escape sequence matches by default. A value of 0 means  that  \R
1032           matches  any  Unicode  line ending sequence; a value of 1 means that \R
1033           matches only CR, LF, or CRLF. The default can be overridden when a pat-
1034           tern is compiled or matched.
1035    
1036           PCRE_CONFIG_LINK_SIZE           PCRE_CONFIG_LINK_SIZE
1037    
# Line 787  CHECKING BUILD-TIME OPTIONS Line 1054  CHECKING BUILD-TIME OPTIONS
1054         internal  matching  function  calls in a pcre_exec() execution. Further         internal  matching  function  calls in a pcre_exec() execution. Further
1055         details are given with pcre_exec() below.         details are given with pcre_exec() below.
1056    
1057             PCRE_CONFIG_MATCH_LIMIT_RECURSION
1058    
1059           The output is an integer that gives the default limit for the depth  of
1060           recursion  when calling the internal matching function in a pcre_exec()
1061           execution. Further details are given with pcre_exec() below.
1062    
1063           PCRE_CONFIG_STACKRECURSE           PCRE_CONFIG_STACKRECURSE
1064    
1065         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 819  COMPILING A PATTERN Line 1092  COMPILING A PATTERN
1092         obtained  via  pcre_malloc is returned. This contains the compiled code         obtained  via  pcre_malloc is returned. This contains the compiled code
1093         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
1094         is a typedef for a structure whose contents are not externally defined.         is a typedef for a structure whose contents are not externally defined.
1095         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
1096         required.         longer required.
1097    
1098         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
1099         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
1100         fully  relocatable, because it may contain a copy of the tableptr argu-         fully  relocatable, because it may contain a copy of the tableptr argu-
1101         ment, which is an address (see below).         ment, which is an address (see below).
1102    
1103         The options argument contains independent bits that affect the compila-         The options argument contains various bit settings that affect the com-
1104         tion.  It  should  be  zero  if  no options are required. The available         pilation.  It  should be zero if no options are required. The available
1105         options are described below. Some of them, in  particular,  those  that         options are described below. Some of them, in  particular,  those  that
1106         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
1107         pattern (see the detailed description  in  the  pcrepattern  documenta-         pattern (see the detailed description  in  the  pcrepattern  documenta-
1108         tion).  For  these options, the contents of the options argument speci-         tion).  For  these options, the contents of the options argument speci-
1109         fies their initial settings at the start of compilation and  execution.         fies their initial settings at the start of compilation and  execution.
1110         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
1111         at compile time.         of matching as well as at compile time.
1112    
1113         If errptr is NULL, pcre_compile() returns NULL immediately.  Otherwise,         If errptr is NULL, pcre_compile() returns NULL immediately.  Otherwise,
1114         if  compilation  of  a  pattern fails, pcre_compile() returns NULL, and         if  compilation  of  a  pattern fails, pcre_compile() returns NULL, and
1115         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-
1116         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
1117         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-
1118         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
1119           by erroffset, which must not be NULL. If it is, an immediate  error  is
1120         given.         given.
1121    
1122         If pcre_compile2() is used instead of pcre_compile(),  and  the  error-         If  pcre_compile2()  is  used instead of pcre_compile(), and the error-
1123         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
1124         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
1125         textual error message. Error codes and messages are listed below.         textual error message. Error codes and messages are listed below.
1126    
1127         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
1128         character tables that are  built  when  PCRE  is  compiled,  using  the         character  tables  that  are  built  when  PCRE  is compiled, using the
1129         default  C  locale.  Otherwise, tableptr must be an address that is the         default C locale. Otherwise, tableptr must be an address  that  is  the
1130         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
1131         compiled  pattern,  and used again by pcre_exec(), unless another table         compiled pattern, and used again by pcre_exec(), unless  another  table
1132         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
1133         support below.         support below.
1134    
1135         This  code  fragment  shows a typical straightforward call to pcre_com-         This code fragment shows a typical straightforward  call  to  pcre_com-
1136         pile():         pile():
1137    
1138           pcre *re;           pcre *re;
# Line 871  COMPILING A PATTERN Line 1145  COMPILING A PATTERN
1145             &erroffset,       /* for error offset */             &erroffset,       /* for error offset */
1146             NULL);            /* use default character tables */             NULL);            /* use default character tables */
1147    
1148         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
1149         file:         file:
1150    
1151           PCRE_ANCHORED           PCRE_ANCHORED
1152    
1153         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
1154         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
1155         that  is being searched (the "subject string"). This effect can also be         that is being searched (the "subject string"). This effect can also  be
1156         achieved by appropriate constructs in the pattern itself, which is  the         achieved  by appropriate constructs in the pattern itself, which is the
1157         only way to do it in Perl.         only way to do it in Perl.
1158    
1159           PCRE_AUTO_CALLOUT           PCRE_AUTO_CALLOUT
1160    
1161         If this bit is set, pcre_compile() automatically inserts callout items,         If this bit is set, pcre_compile() automatically inserts callout items,
1162         all with number 255, before each pattern item. For  discussion  of  the         all  with  number  255, before each pattern item. For discussion of the
1163         callout facility, see the pcrecallout documentation.         callout facility, see the pcrecallout documentation.
1164    
1165             PCRE_BSR_ANYCRLF
1166             PCRE_BSR_UNICODE
1167    
1168           These options (which are mutually exclusive) control what the \R escape
1169           sequence  matches.  The choice is either to match only CR, LF, or CRLF,
1170           or to match any Unicode newline sequence. The default is specified when
1171           PCRE is built. It can be overridden from within the pattern, or by set-
1172           ting an option when a compiled pattern is matched.
1173    
1174           PCRE_CASELESS           PCRE_CASELESS
1175    
1176         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
1177         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
1178         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
1179         always understands the concept of case for characters whose values  are         always  understands the concept of case for characters whose values are
1180         less  than 128, so caseless matching is always possible. For characters         less than 128, so caseless matching is always possible. For  characters
1181         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-
1182         piled  with Unicode property support, but not otherwise. If you want to         piled with Unicode property support, but not otherwise. If you want  to
1183         use caseless matching for characters 128 and  above,  you  must  ensure         use  caseless  matching  for  characters 128 and above, you must ensure
1184         that  PCRE  is  compiled  with Unicode property support as well as with         that PCRE is compiled with Unicode property support  as  well  as  with
1185         UTF-8 support.         UTF-8 support.
1186    
1187           PCRE_DOLLAR_ENDONLY           PCRE_DOLLAR_ENDONLY
1188    
1189         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
1190         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
1191         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
1192         not  before  any  other  newlines).  The  PCRE_DOLLAR_ENDONLY option is         before any other newlines). The PCRE_DOLLAR_ENDONLY option  is  ignored
1193         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
1194         in Perl, and no way to set it within a pattern.         Perl, and no way to set it within a pattern.
1195    
1196           PCRE_DOTALL           PCRE_DOTALL
1197    
1198         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-
1199         acters, including newlines. Without it,  newlines  are  excluded.  This         acters,  including  those that indicate newline. Without it, a dot does
1200         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
1201         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
1202         always  matches a newline character, independent of the setting of this         by a (?s) option setting. A negative class such as [^a] always  matches
1203         option.         newline characters, independent of the setting of this option.
1204    
1205             PCRE_DUPNAMES
1206    
1207           If  this  bit is set, names used to identify capturing subpatterns need
1208           not be unique. This can be helpful for certain types of pattern when it
1209           is  known  that  only  one instance of the named subpattern can ever be
1210           matched. There are more details of named subpatterns  below;  see  also
1211           the pcrepattern documentation.
1212    
1213           PCRE_EXTENDED           PCRE_EXTENDED
1214    
1215         If this bit is set, whitespace  data  characters  in  the  pattern  are         If  this  bit  is  set,  whitespace  data characters in the pattern are
1216         totally ignored except when escaped or inside a character class. White-         totally ignored except when escaped or inside a character class. White-
1217         space does not include the VT character (code 11). In addition, charac-         space does not include the VT character (code 11). In addition, charac-
1218         ters between an unescaped # outside a character class and the next new-         ters between an unescaped # outside a character class and the next new-
1219         line character, inclusive, are also  ignored.  This  is  equivalent  to         line,  inclusive,  are  also  ignored.  This is equivalent to Perl's /x
1220         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-
1221         option setting.         ting.
1222    
1223         This option makes it possible to include  comments  inside  complicated         This  option  makes  it possible to include comments inside complicated
1224         patterns.   Note,  however,  that this applies only to data characters.         patterns.  Note, however, that this applies only  to  data  characters.
1225         Whitespace  characters  may  never  appear  within  special   character         Whitespace   characters  may  never  appear  within  special  character
1226         sequences  in  a  pattern,  for  example  within the sequence (?( which         sequences in a pattern, for  example  within  the  sequence  (?(  which
1227         introduces a conditional subpattern.         introduces a conditional subpattern.
1228    
1229           PCRE_EXTRA           PCRE_EXTRA
1230    
1231         This option was invented in order to turn on  additional  functionality         This  option  was invented in order to turn on additional functionality
1232         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
1233         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
1234         letter  that  has  no  special  meaning causes an error, thus reserving         letter that has no special meaning  causes  an  error,  thus  reserving
1235         these combinations for future expansion. By  default,  as  in  Perl,  a         these  combinations  for  future  expansion.  By default, as in Perl, a
1236         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
1237         literal. There are at present no  other  features  controlled  by  this         literal.  (Perl can, however, be persuaded to give a warning for this.)
1238         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
1239           can also be set by a (?X) option setting within a pattern.
1240    
1241           PCRE_FIRSTLINE           PCRE_FIRSTLINE
1242    
1243         If  this  option  is  set,  an  unanchored pattern is required to match         If  this  option  is  set,  an  unanchored pattern is required to match
1244         before or at the first newline character in the subject string,  though         before or at the first  newline  in  the  subject  string,  though  the
1245         the matched text may continue over the newline.         matched text may continue over the newline.
1246    
1247           PCRE_MULTILINE           PCRE_MULTILINE
1248    
# Line 962  COMPILING A PATTERN Line 1254  COMPILING A PATTERN
1254         is set). This is the same as Perl.         is set). This is the same as Perl.
1255    
1256         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"
1257         constructs  match  immediately following or immediately before any new-         constructs  match  immediately following or immediately before internal
1258         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
1259         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
1260         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-
1261         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,
1262         setting PCRE_MULTILINE has no effect.         setting PCRE_MULTILINE has no effect.
1263    
1264             PCRE_NEWLINE_CR
1265             PCRE_NEWLINE_LF
1266             PCRE_NEWLINE_CRLF
1267             PCRE_NEWLINE_ANYCRLF
1268             PCRE_NEWLINE_ANY
1269    
1270           These options override the default newline definition that  was  chosen
1271           when  PCRE  was built. Setting the first or the second specifies that a
1272           newline is indicated by a single character (CR  or  LF,  respectively).
1273           Setting  PCRE_NEWLINE_CRLF specifies that a newline is indicated by the
1274           two-character CRLF  sequence.  Setting  PCRE_NEWLINE_ANYCRLF  specifies
1275           that any of the three preceding sequences should be recognized. Setting
1276           PCRE_NEWLINE_ANY specifies that any Unicode newline sequence should  be
1277           recognized. The Unicode newline sequences are the three just mentioned,
1278           plus the single characters VT (vertical  tab,  U+000B),  FF  (formfeed,
1279           U+000C),  NEL  (next line, U+0085), LS (line separator, U+2028), and PS
1280           (paragraph separator, U+2029). The last  two  are  recognized  only  in
1281           UTF-8 mode.
1282    
1283           The  newline  setting  in  the  options  word  uses three bits that are
1284           treated as a number, giving eight possibilities. Currently only six are
1285           used  (default  plus the five values above). This means that if you set
1286           more than one newline option, the combination may or may not be  sensi-
1287           ble. For example, PCRE_NEWLINE_CR with PCRE_NEWLINE_LF is equivalent to
1288           PCRE_NEWLINE_CRLF, but other combinations may yield unused numbers  and
1289           cause an error.
1290    
1291           The  only time that a line break is specially recognized when compiling
1292           a pattern is if PCRE_EXTENDED is set, and  an  unescaped  #  outside  a
1293           character  class  is  encountered.  This indicates a comment that lasts
1294           until after the next line break sequence. In other circumstances,  line
1295           break   sequences   are   treated  as  literal  data,  except  that  in
1296           PCRE_EXTENDED mode, both CR and LF are treated as whitespace characters
1297           and are therefore ignored.
1298    
1299           The newline option that is set at compile time becomes the default that
1300           is used for pcre_exec() and pcre_dfa_exec(), but it can be  overridden.
1301    
1302           PCRE_NO_AUTO_CAPTURE           PCRE_NO_AUTO_CAPTURE
1303    
1304         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-
1305         theses  in the pattern. Any opening parenthesis that is not followed by         theses in the pattern. Any opening parenthesis that is not followed  by
1306         ? behaves as if it were followed by ?: but named parentheses can  still         ?  behaves as if it were followed by ?: but named parentheses can still
1307         be  used  for  capturing  (and  they acquire numbers in the usual way).         be used for capturing (and they acquire  numbers  in  the  usual  way).
1308         There is no equivalent of this option in Perl.         There is no equivalent of this option in Perl.
1309    
1310           PCRE_UNGREEDY           PCRE_UNGREEDY
1311    
1312         This option inverts the "greediness" of the quantifiers  so  that  they         This  option  inverts  the "greediness" of the quantifiers so that they
1313         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
1314         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
1315         within the pattern.         within the pattern.
1316    
1317           PCRE_UTF8           PCRE_UTF8
1318    
1319         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
1320         strings of UTF-8 characters instead of single-byte  character  strings.         strings  of  UTF-8 characters instead of single-byte character strings.
1321         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-
1322         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
1323         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
1324         UTF-8 support in the main pcre page.         UTF-8 support in the main pcre page.
1325    
1326           PCRE_NO_UTF8_CHECK           PCRE_NO_UTF8_CHECK
1327    
1328         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
1329         automatically  checked. If an invalid UTF-8 sequence of bytes is found,         automatically checked. There is a  discussion  about  the  validity  of
1330         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
1331         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
1332         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-
1333         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
1334         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
1335         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
1336         ing of subject strings.         can  also be passed to pcre_exec() and pcre_dfa_exec(), to suppress the
1337           UTF-8 validity checking of subject strings.
1338    
1339    
1340  COMPILATION ERROR CODES  COMPILATION ERROR CODES
1341    
1342         The following table lists the error  codes  than  may  be  returned  by         The following table lists the error  codes  than  may  be  returned  by
1343         pcre_compile2(),  along with the error messages that may be returned by         pcre_compile2(),  along with the error messages that may be returned by
1344         both compiling functions.         both compiling functions. As PCRE has developed, some error codes  have
1345           fallen out of use. To avoid confusion, they have not been re-used.
1346    
1347            0  no error            0  no error
1348            1  \ at end of pattern            1  \ at end of pattern
# Line 1022  COMPILATION ERROR CODES Line 1354  COMPILATION ERROR CODES
1354            7  invalid escape sequence in character class            7  invalid escape sequence in character class
1355            8  range out of order in character class            8  range out of order in character class
1356            9  nothing to repeat            9  nothing to repeat
1357           10  operand of unlimited repeat could match the empty string           10  [this code is not in use]
1358           11  internal error: unexpected repeat           11  internal error: unexpected repeat
1359           12  unrecognized character after (?           12  unrecognized character after (?
1360           13  POSIX named classes are supported only within a class           13  POSIX named classes are supported only within a class
# Line 1031  COMPILATION ERROR CODES Line 1363  COMPILATION ERROR CODES
1363           16  erroffset passed as NULL           16  erroffset passed as NULL
1364           17  unknown option bit(s) set           17  unknown option bit(s) set
1365           18  missing ) after comment           18  missing ) after comment
1366           19  parentheses nested too deeply           19  [this code is not in use]
1367           20  regular expression too large           20  regular expression too large
1368           21  failed to get memory           21  failed to get memory
1369           22  unmatched parentheses           22  unmatched parentheses
1370           23  internal error: code overflow           23  internal error: code overflow
1371           24  unrecognized character after (?<           24  unrecognized character after (?<
1372           25  lookbehind assertion is not fixed length           25  lookbehind assertion is not fixed length
1373           26  malformed number after (?(           26  malformed number or name after (?(
1374           27  conditional group contains more than two branches           27  conditional group contains more than two branches
1375           28  assertion expected after (?(           28  assertion expected after (?(
1376           29  (?R or (?digits must be followed by )           29  (?R or (?[+-]digits must be followed by )
1377           30  unknown POSIX class name           30  unknown POSIX class name
1378           31  POSIX collating elements are not supported           31  POSIX collating elements are not supported
1379           32  this version of PCRE is not compiled with PCRE_UTF8 support           32  this version of PCRE is not compiled with PCRE_UTF8 support
1380           33  spare error           33  [this code is not in use]
1381           34  character value in \x{...} sequence is too large           34  character value in \x{...} sequence is too large
1382           35  invalid condition (?(0)           35  invalid condition (?(0)
1383           36  \C not allowed in lookbehind assertion           36  \C not allowed in lookbehind assertion
# Line 1054  COMPILATION ERROR CODES Line 1386  COMPILATION ERROR CODES
1386           39  closing ) for (?C expected           39  closing ) for (?C expected
1387           40  recursive call could loop indefinitely           40  recursive call could loop indefinitely
1388           41  unrecognized character after (?P           41  unrecognized character after (?P
1389           42  syntax error after (?P           42  syntax error in subpattern name (missing terminator)
1390           43  two named groups have the same name           43  two named subpatterns have the same name
1391           44  invalid UTF-8 string           44  invalid UTF-8 string
1392           45  support for \P, \p, and \X has not been compiled           45  support for \P, \p, and \X has not been compiled
1393           46  malformed \P or \p sequence           46  malformed \P or \p sequence
1394           47  unknown property name after \P or \p           47  unknown property name after \P or \p
1395             48  subpattern name is too long (maximum 32 characters)
1396             49  too many named subpatterns (maximum 10,000)
1397             50  [this code is not in use]
1398             51  octal value is greater than \377 (not in UTF-8 mode)
1399             52  internal error: overran compiling workspace
1400             53   internal  error:  previously-checked  referenced  subpattern not
1401           found
1402             54  DEFINE group contains more than one branch
1403             55  repeating a DEFINE group is not allowed
1404             56  inconsistent NEWLINE options
1405             57  \g is not followed by a braced name or an optionally braced
1406                   non-zero number
1407             58  (?+ or (?- or (?(+ or (?(- must be followed by a non-zero number
1408    
1409    
1410  STUDYING A PATTERN  STUDYING A PATTERN
# Line 1090  STUDYING A PATTERN Line 1435  STUDYING A PATTERN
1435    
1436         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.
1437         If studying succeeds (even if no data is  returned),  the  variable  it         If studying succeeds (even if no data is  returned),  the  variable  it
1438         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
1439         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
1440         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
1441           after calling pcre_study(), to be sure that it has run successfully.
1442    
1443         This is a typical call to pcre_study():         This is a typical call to pcre_study():
1444    
# Line 1103  STUDYING A PATTERN Line 1449  STUDYING A PATTERN
1449             &error);        /* set to NULL or points to a message */             &error);        /* set to NULL or points to a message */
1450    
1451         At present, studying a pattern is useful only for non-anchored patterns         At present, studying a pattern is useful only for non-anchored patterns
1452         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-
1453         ble starting bytes is created.         ble starting bytes is created.
1454    
1455    
1456  LOCALE SUPPORT  LOCALE SUPPORT
1457    
1458         PCRE  handles  caseless matching, and determines whether characters are         PCRE handles caseless matching, and determines whether  characters  are
1459         letters digits, or whatever, by reference to a set of  tables,  indexed         letters,  digits, or whatever, by reference to a set of tables, indexed
1460         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
1461         characters with codes less than 128. Higher-valued  codes  never  match         characters  with  codes  less than 128. Higher-valued codes never match
1462         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
1463         with Unicode character property support.         with  Unicode  character property support. The use of locales with Uni-
1464           code is discouraged. If you are handling characters with codes  greater
1465         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
1466         is  built.  This  is  used when the final argument of pcre_compile() is         not try to mix the two.
1467         NULL, and is sufficient for many applications. An  alternative  set  of  
1468         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
1469         locale from the default. As more and more applications change to  using         argument  of  pcre_compile()  is  NULL.  These  are sufficient for many
1470         Unicode, the need for this locale support is expected to die away.         applications.  Normally, the internal tables recognize only ASCII char-
1471           acters. However, when PCRE is built, it is possible to cause the inter-
1472         External  tables  are  built by calling the pcre_maketables() function,         nal tables to be rebuilt in the default "C" locale of the local system,
1473         which has no arguments, in the relevant locale. The result can then  be         which may cause them to be different.
1474         passed  to  pcre_compile()  or  pcre_exec()  as often as necessary. For  
1475         example, to build and use tables that are appropriate  for  the  French         The  internal tables can always be overridden by tables supplied by the
1476         locale  (where  accented  characters  with  values greater than 128 are         application that calls PCRE. These may be created in a different locale
1477           from  the  default.  As more and more applications change to using Uni-
1478           code, the need for this locale support is expected to die away.
1479    
1480           External tables are built by calling  the  pcre_maketables()  function,
1481           which  has no arguments, in the relevant locale. The result can then be
1482           passed to pcre_compile() or pcre_exec()  as  often  as  necessary.  For
1483           example,  to  build  and use tables that are appropriate for the French
1484           locale (where accented characters with  values  greater  than  128  are
1485         treated as letters), the following code could be used:         treated as letters), the following code could be used:
1486    
1487           setlocale(LC_CTYPE, "fr_FR");           setlocale(LC_CTYPE, "fr_FR");
1488           tables = pcre_maketables();           tables = pcre_maketables();
1489           re = pcre_compile(..., tables);           re = pcre_compile(..., tables);
1490    
1491           The  locale  name "fr_FR" is used on Linux and other Unix-like systems;
1492           if you are using Windows, the name for the French locale is "french".
1493    
1494         When pcre_maketables() runs, the tables are built  in  memory  that  is         When pcre_maketables() runs, the tables are built  in  memory  that  is
1495         obtained  via  pcre_malloc. It is the caller's responsibility to ensure         obtained  via  pcre_malloc. It is the caller's responsibility to ensure
1496         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 1179  INFORMATION ABOUT A PATTERN Line 1536  INFORMATION ABOUT A PATTERN
1536         pattern:         pattern:
1537    
1538           int rc;           int rc;
1539           unsigned long int length;           size_t length;
1540           rc = pcre_fullinfo(           rc = pcre_fullinfo(
1541             re,               /* result of pcre_compile() */             re,               /* result of pcre_compile() */
1542             pe,               /* result of pcre_study(), or NULL */             pe,               /* result of pcre_study(), or NULL */
# Line 1211  INFORMATION ABOUT A PATTERN Line 1568  INFORMATION ABOUT A PATTERN
1568           PCRE_INFO_FIRSTBYTE           PCRE_INFO_FIRSTBYTE
1569    
1570         Return  information  about  the first byte of any matched string, for a         Return  information  about  the first byte of any matched string, for a
1571         non-anchored   pattern.   (This    option    used    to    be    called         non-anchored pattern. The fourth argument should point to an int  vari-
1572         PCRE_INFO_FIRSTCHAR;  the  old  name  is still recognized for backwards         able.  (This option used to be called PCRE_INFO_FIRSTCHAR; the old name
1573         compatibility.)         is still recognized for backwards compatibility.)
1574    
1575         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
1576         (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  
1577    
1578         (a) the pattern was compiled with the PCRE_MULTILINE option, and  every         (a)  the pattern was compiled with the PCRE_MULTILINE option, and every
1579         branch starts with "^", or         branch starts with "^", or
1580    
1581         (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
1582         set (if it were set, the pattern would be anchored),         set (if it were set, the pattern would be anchored),
1583    
1584         -1 is returned, indicating that the pattern matches only at  the  start         -1  is  returned, indicating that the pattern matches only at the start
1585         of  a  subject string or after any newline within the string. Otherwise         of a subject string or after any newline within the  string.  Otherwise
1586         -2 is returned. For anchored patterns, -2 is returned.         -2 is returned. For anchored patterns, -2 is returned.
1587    
1588           PCRE_INFO_FIRSTTABLE           PCRE_INFO_FIRSTTABLE
1589    
1590         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
1591         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
1592         matching string, a pointer to the table is returned. Otherwise NULL  is         matching  string, a pointer to the table is returned. Otherwise NULL is
1593         returned.  The fourth argument should point to an unsigned char * vari-         returned. The fourth argument should point to an unsigned char *  vari-
1594         able.         able.
1595    
1596             PCRE_INFO_HASCRORLF
1597    
1598           Return  1  if  the  pattern  contains any explicit matches for CR or LF
1599           characters, otherwise 0. The fourth argument should  point  to  an  int
1600           variable.  An explicit match is either a literal CR or LF character, or
1601           \r or \n.
1602    
1603             PCRE_INFO_JCHANGED
1604    
1605           Return 1 if the (?J) or (?-J) option setting is used  in  the  pattern,
1606           otherwise  0. The fourth argument should point to an int variable. (?J)
1607           and (?-J) set and unset the local PCRE_DUPNAMES option, respectively.
1608    
1609           PCRE_INFO_LASTLITERAL           PCRE_INFO_LASTLITERAL
1610    
1611         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 1253  INFORMATION ABOUT A PATTERN Line 1622  INFORMATION ABOUT A PATTERN
1622    
1623         PCRE supports the use of named as well as numbered capturing  parenthe-         PCRE supports the use of named as well as numbered capturing  parenthe-
1624         ses.  The names are just an additional way of identifying the parenthe-         ses.  The names are just an additional way of identifying the parenthe-
1625         ses,  which  still  acquire  numbers.  A  convenience  function  called         ses, which still acquire numbers. Several convenience functions such as
1626         pcre_get_named_substring()  is  provided  for  extracting an individual         pcre_get_named_substring()  are  provided  for extracting captured sub-
1627         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
1628         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
1629         the correct pointers in the output vector (described  with  pcre_exec()         pointers in the output vector (described with pcre_exec() below). To do
1630         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
1631         which is described by these three values.         described by these three values.
1632    
1633         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
1634         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 1269  INFORMATION ABOUT A PATTERN Line 1638  INFORMATION ABOUT A PATTERN
1638         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-
1639         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-
1640         sponding  name,  zero  terminated. The names are in alphabetical order.         sponding  name,  zero  terminated. The names are in alphabetical order.
1641         For example, consider the following pattern  (assume  PCRE_EXTENDED  is         When PCRE_DUPNAMES is set, duplicate names are in order of their paren-
1642         set, so white space - including newlines - is ignored):         theses  numbers.  For  example,  consider the following pattern (assume
1643           PCRE_EXTENDED is  set,  so  white  space  -  including  newlines  -  is
1644           ignored):
1645    
1646           (?P<date> (?P<year>(\d\d)?\d\d) -           (?<date> (?<year>(\d\d)?\d\d) -
1647           (?P<month>\d\d) - (?P<day>\d\d) )           (?<month>\d\d) - (?<day>\d\d) )
1648    
1649         There  are  four  named subpatterns, so the table has four entries, and         There  are  four  named subpatterns, so the table has four entries, and
1650         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 1286  INFORMATION ABOUT A PATTERN Line 1657  INFORMATION ABOUT A PATTERN
1657           00 02 y  e  a  r  00 ??           00 02 y  e  a  r  00 ??
1658    
1659         When writing code to extract data  from  named  subpatterns  using  the         When writing code to extract data  from  named  subpatterns  using  the
1660         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
1661         be different for each compiled pattern.         to be different for each compiled pattern.
1662    
1663             PCRE_INFO_OKPARTIAL
1664    
1665           Return 1 if the pattern can be used for partial matching, otherwise  0.
1666           The  fourth  argument  should point to an int variable. The pcrepartial
1667           documentation lists the restrictions that apply to patterns  when  par-
1668           tial matching is used.
1669    
1670           PCRE_INFO_OPTIONS           PCRE_INFO_OPTIONS
1671    
1672         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
1673         fourth  argument  should  point to an unsigned long int variable. These         fourth argument should point to an unsigned long  int  variable.  These
1674         option bits are those specified in the call to pcre_compile(), modified         option bits are those specified in the call to pcre_compile(), modified
1675         by any top-level option settings within the pattern itself.         by any top-level option settings at the start of the pattern itself. In
1676           other  words,  they are the options that will be in force when matching
1677           starts. For example, if the pattern /(?im)abc(?-i)d/ is  compiled  with
1678           the  PCRE_EXTENDED option, the result is PCRE_CASELESS, PCRE_MULTILINE,
1679           and PCRE_EXTENDED.
1680    
1681         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
1682         alternatives begin with one of the following:         alternatives begin with one of the following:
1683    
1684           ^     unless PCRE_MULTILINE is set           ^     unless PCRE_MULTILINE is set
# Line 1310  INFORMATION ABOUT A PATTERN Line 1692  INFORMATION ABOUT A PATTERN
1692    
1693           PCRE_INFO_SIZE           PCRE_INFO_SIZE
1694    
1695         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
1696         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
1697         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
1698         size_t variable.         size_t variable.
# Line 1318  INFORMATION ABOUT A PATTERN Line 1700  INFORMATION ABOUT A PATTERN
1700           PCRE_INFO_STUDYSIZE           PCRE_INFO_STUDYSIZE
1701    
1702         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
1703         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
1704         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
1705         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
1706         variable.         variable.
1707    
1708    
# Line 1328  OBSOLETE INFO FUNCTION Line 1710  OBSOLETE INFO FUNCTION
1710    
1711         int pcre_info(const pcre *code, int *optptr, int *firstcharptr);         int pcre_info(const pcre *code, int *optptr, int *firstcharptr);
1712    
1713         The pcre_info() function is now obsolete because its interface  is  too         The  pcre_info()  function is now obsolete because its interface is too
1714         restrictive  to return all the available data about a compiled pattern.         restrictive to return all the available data about a compiled  pattern.
1715         New  programs  should  use  pcre_fullinfo()  instead.  The   yield   of         New   programs   should  use  pcre_fullinfo()  instead.  The  yield  of
1716         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-
1717         lowing negative numbers:         lowing negative numbers:
1718    
1719           PCRE_ERROR_NULL       the argument code was NULL           PCRE_ERROR_NULL       the argument code was NULL
1720           PCRE_ERROR_BADMAGIC   the "magic number" was not found           PCRE_ERROR_BADMAGIC   the "magic number" was not found
1721    
1722         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
1723         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
1724         PCRE_INFO_OPTIONS above).         PCRE_INFO_OPTIONS above).
1725    
1726         If the pattern is not anchored and the  firstcharptr  argument  is  not         If  the  pattern  is  not anchored and the firstcharptr argument is not
1727         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
1728         any matched string (see PCRE_INFO_FIRSTBYTE above).         any matched string (see PCRE_INFO_FIRSTBYTE above).
1729    
1730    
# Line 1350  REFERENCE COUNTS Line 1732  REFERENCE COUNTS
1732    
1733         int pcre_refcount(pcre *code, int adjust);         int pcre_refcount(pcre *code, int adjust);
1734    
1735         The pcre_refcount() function is used to maintain a reference  count  in         The  pcre_refcount()  function is used to maintain a reference count in
1736         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
1737         benefit of applications that  operate  in  an  object-oriented  manner,         benefit  of  applications  that  operate  in an object-oriented manner,
1738         where different parts of the application may be using the same compiled         where different parts of the application may be using the same compiled
1739         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.
1740    
1741         When a pattern is compiled, the reference count field is initialized to         When a pattern is compiled, the reference count field is initialized to
1742         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
1743         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
1744         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
1745         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
1746         is outside these limits, it is forced to the appropriate limit value.         is outside these limits, it is forced to the appropriate limit value.
1747    
1748         Except  when it is zero, the reference count is not correctly preserved         Except when it is zero, the reference count is not correctly  preserved
1749         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
1750         whose byte-order is different. (This seems a highly unlikely scenario.)         whose byte-order is different. (This seems a highly unlikely scenario.)
1751    
1752    
# Line 1374  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1756  MATCHING A PATTERN: THE TRADITIONAL FUNC
1756              const char *subject, int length, int startoffset,              const char *subject, int length, int startoffset,
1757              int options, int *ovector, int ovecsize);              int options, int *ovector, int ovecsize);
1758    
1759         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
1760         compiled  pattern, which is passed in the code argument. If the pattern         compiled pattern, which is passed in the code argument. If the  pattern
1761         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
1762         argument.  This  function is the main matching facility of the library,         argument. This function is the main matching facility of  the  library,
1763         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
1764         an  alternative matching function, which is described below in the sec-         an alternative matching function, which is described below in the  sec-
1765         tion about the pcre_dfa_exec() function.         tion about the pcre_dfa_exec() function.
1766    
1767         In most applications, the pattern will have been compiled (and  option-         In  most applications, the pattern will have been compiled (and option-
1768         ally  studied)  in the same process that calls pcre_exec(). However, it         ally studied) in the same process that calls pcre_exec().  However,  it
1769         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
1770         later  in  different processes, possibly even on different hosts. For a         later in different processes, possibly even on different hosts.  For  a
1771         discussion about this, see the pcreprecompile documentation.         discussion about this, see the pcreprecompile documentation.
1772    
1773         Here is an example of a simple call to pcre_exec():         Here is an example of a simple call to pcre_exec():
# Line 1404  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1786  MATCHING A PATTERN: THE TRADITIONAL FUNC
1786    
1787     Extra data for pcre_exec()     Extra data for pcre_exec()
1788    
1789         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
1790         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
1791         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-
1792         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
1793         lows:         fields (not necessarily in this order):
1794    
1795           unsigned long int flags;           unsigned long int flags;
1796           void *study_data;           void *study_data;
1797           unsigned long int match_limit;           unsigned long int match_limit;
1798             unsigned long int match_limit_recursion;
1799           void *callout_data;           void *callout_data;
1800           const unsigned char *tables;           const unsigned char *tables;
1801    
1802         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
1803         are set. The flag bits are:         are set. The flag bits are:
1804    
1805           PCRE_EXTRA_STUDY_DATA           PCRE_EXTRA_STUDY_DATA
1806           PCRE_EXTRA_MATCH_LIMIT           PCRE_EXTRA_MATCH_LIMIT
1807             PCRE_EXTRA_MATCH_LIMIT_RECURSION
1808           PCRE_EXTRA_CALLOUT_DATA           PCRE_EXTRA_CALLOUT_DATA
1809           PCRE_EXTRA_TABLES           PCRE_EXTRA_TABLES
1810    
1811         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
1812         the pcre_extra block that is returned by  pcre_study(),  together  with         the  pcre_extra  block  that is returned by pcre_study(), together with
1813         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
1814         add to the block by setting the other fields  and  their  corresponding         add  to  the  block by setting the other fields and their corresponding
1815         flag bits.         flag bits.
1816    
1817         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
1818         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
1819         match,  but  which  have  a very large number of possibilities in their         match, but which have a very large number  of  possibilities  in  their
1820         search trees. The classic  example  is  the  use  of  nested  unlimited         search  trees.  The  classic  example  is  the  use of nested unlimited
1821         repeats.         repeats.
1822    
1823         Internally,  PCRE uses a function called match() which it calls repeat-         Internally, PCRE uses a function called match() which it calls  repeat-
1824         edly (sometimes recursively). The limit is imposed  on  the  number  of         edly  (sometimes  recursively). The limit set by match_limit is imposed
1825         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
1826         limiting the amount of recursion and backtracking that can take  place.         has  the  effect  of  limiting the amount of backtracking that can take
1827         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
1828         position in the subject string.         for each position in the subject string.
1829    
1830         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
1831         default  default  is 10 million, which handles all but the most extreme         default default is 10 million, which handles all but the  most  extreme
1832         cases. You can reduce  the  default  by  suppling  pcre_exec()  with  a         cases.  You  can  override  the  default by suppling pcre_exec() with a
1833         pcre_extra  block  in  which match_limit is set to a smaller value, and         pcre_extra    block    in    which    match_limit    is    set,     and
1834         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
1835         exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.         exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
1836    
1837         The  pcre_callout  field is used in conjunction with the "callout" fea-         The match_limit_recursion field is similar to match_limit, but  instead
1838           of limiting the total number of times that match() is called, it limits
1839           the depth of recursion. The recursion depth is a  smaller  number  than
1840           the  total number of calls, because not all calls to match() are recur-
1841           sive.  This limit is of use only if it is set smaller than match_limit.
1842    
1843           Limiting  the  recursion  depth  limits the amount of stack that can be
1844           used, or, when PCRE has been compiled to use memory on the heap instead
1845           of the stack, the amount of heap memory that can be used.
1846    
1847           The  default  value  for  match_limit_recursion can be set when PCRE is
1848           built; the default default  is  the  same  value  as  the  default  for
1849           match_limit.  You can override the default by suppling pcre_exec() with
1850           a  pcre_extra  block  in  which  match_limit_recursion  is   set,   and
1851           PCRE_EXTRA_MATCH_LIMIT_RECURSION  is  set  in  the  flags field. If the
1852           limit is exceeded, pcre_exec() returns PCRE_ERROR_RECURSIONLIMIT.
1853    
1854           The pcre_callout field is used in conjunction with the  "callout"  fea-
1855         ture, which is described in the pcrecallout documentation.         ture, which is described in the pcrecallout documentation.
1856    
1857         The tables field  is  used  to  pass  a  character  tables  pointer  to         The  tables  field  is  used  to  pass  a  character  tables pointer to
1858         pcre_exec();  this overrides the value that is stored with the compiled         pcre_exec(); this overrides the value that is stored with the  compiled
1859         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
1860         custom  tables  were  supplied to pcre_compile() via its tableptr argu-         custom tables were supplied to pcre_compile() via  its  tableptr  argu-
1861         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
1862         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-
1863         using patterns that have been saved after compiling  with  an  external         using  patterns  that  have been saved after compiling with an external
1864         set  of  tables,  because  the  external tables might be at a different         set of tables, because the external tables  might  be  at  a  different
1865         address when pcre_exec() is called. See the  pcreprecompile  documenta-         address  when  pcre_exec() is called. See the pcreprecompile documenta-
1866         tion for a discussion of saving compiled patterns for later use.         tion for a discussion of saving compiled patterns for later use.
1867    
1868     Option bits for pcre_exec()     Option bits for pcre_exec()
1869    
1870         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.
1871         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,
1872         PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NO_UTF8_CHECK and PCRE_PARTIAL.         PCRE_NOTBOL,   PCRE_NOTEOL,   PCRE_NOTEMPTY,   PCRE_NO_UTF8_CHECK   and
1873           PCRE_PARTIAL.
1874    
1875           PCRE_ANCHORED           PCRE_ANCHORED
1876    
# Line 1477  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1879  MATCHING A PATTERN: THE TRADITIONAL FUNC
1879         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
1880         unachored at matching time.         unachored at matching time.
1881    
1882             PCRE_BSR_ANYCRLF
1883             PCRE_BSR_UNICODE
1884    
1885           These options (which are mutually exclusive) control what the \R escape
1886           sequence  matches.  The choice is either to match only CR, LF, or CRLF,
1887           or to match any Unicode newline sequence. These  options  override  the
1888           choice that was made or defaulted when the pattern was compiled.
1889    
1890             PCRE_NEWLINE_CR
1891             PCRE_NEWLINE_LF
1892             PCRE_NEWLINE_CRLF
1893             PCRE_NEWLINE_ANYCRLF
1894             PCRE_NEWLINE_ANY
1895    
1896           These  options  override  the  newline  definition  that  was chosen or
1897           defaulted when the pattern was compiled. For details, see the  descrip-
1898           tion  of  pcre_compile()  above.  During  matching,  the newline choice
1899           affects the behaviour of the dot, circumflex,  and  dollar  metacharac-
1900           ters.  It may also alter the way the match position is advanced after a
1901           match failure for an unanchored pattern.
1902    
1903           When PCRE_NEWLINE_CRLF, PCRE_NEWLINE_ANYCRLF,  or  PCRE_NEWLINE_ANY  is
1904           set,  and a match attempt for an unanchored pattern fails when the cur-
1905           rent position is at a  CRLF  sequence,  and  the  pattern  contains  no
1906           explicit  matches  for  CR  or  LF  characters,  the  match position is
1907           advanced by two characters instead of one, in other words, to after the
1908           CRLF.
1909    
1910           The above rule is a compromise that makes the most common cases work as
1911           expected. For example, if the  pattern  is  .+A  (and  the  PCRE_DOTALL
1912           option is not set), it does not match the string "\r\nA" because, after
1913           failing at the start, it skips both the CR and the LF before  retrying.
1914           However,  the  pattern  [\r\n]A does match that string, because it con-
1915           tains an explicit CR or LF reference, and so advances only by one char-
1916           acter after the first failure.
1917    
1918           An explicit match for CR of LF is either a literal appearance of one of
1919           those characters, or one of the \r or  \n  escape  sequences.  Implicit
1920           matches  such  as [^X] do not count, nor does \s (which includes CR and
1921           LF in the characters that it matches).
1922    
1923           Notwithstanding the above, anomalous effects may still occur when  CRLF
1924           is a valid newline sequence and explicit \r or \n escapes appear in the
1925           pattern.
1926    
1927           PCRE_NOTBOL           PCRE_NOTBOL
1928    
1929         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 1522  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1969  MATCHING A PATTERN: THE TRADITIONAL FUNC
1969         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
1970         UTF-8  string is automatically checked when pcre_exec() is subsequently         UTF-8  string is automatically checked when pcre_exec() is subsequently
1971         called.  The value of startoffset is also checked  to  ensure  that  it         called.  The value of startoffset is also checked  to  ensure  that  it
1972         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
1973         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
1974         startoffset  contains  an  invalid  value, PCRE_ERROR_BADUTF8_OFFSET is         main  pcre  page.  If  an  invalid  UTF-8  sequence  of bytes is found,
1975         returned.         pcre_exec() returns the error PCRE_ERROR_BADUTF8. If  startoffset  con-
1976           tains an invalid value, PCRE_ERROR_BADUTF8_OFFSET is returned.
1977         If you already know that your subject is valid, and you  want  to  skip  
1978         these    checks    for   performance   reasons,   you   can   set   the         If  you  already  know that your subject is valid, and you want to skip
1979         PCRE_NO_UTF8_CHECK option when calling pcre_exec(). You might  want  to         these   checks   for   performance   reasons,   you   can    set    the
1980         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
1981         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
1982         string.  However,  you  should  be  sure  that the value of startoffset         making  repeated  calls  to  find  all  the matches in a single subject
1983         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
1984         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
1985         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
1986           value  of startoffset that does not point to the start of a UTF-8 char-
1987         acter, is undefined. Your program may crash.         acter, is undefined. Your program may crash.
1988    
1989           PCRE_PARTIAL           PCRE_PARTIAL
1990    
1991         This  option  turns  on  the  partial  matching feature. If the subject         This option turns on the  partial  matching  feature.  If  the  subject
1992         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-
1993         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
1994         partially matches the pattern and the failure to  match  occurred  only         partially  matches  the  pattern and the failure to match occurred only
1995         because  there were not enough subject characters), pcre_exec() returns         because there were not enough subject characters), pcre_exec()  returns
1996         PCRE_ERROR_PARTIAL instead of PCRE_ERROR_NOMATCH. When PCRE_PARTIAL  is         PCRE_ERROR_PARTIAL  instead of PCRE_ERROR_NOMATCH. When PCRE_PARTIAL is
1997         used,  there  are restrictions on what may appear in the pattern. These         used, there are restrictions on what may appear in the  pattern.  These
1998         are discussed in the pcrepartial documentation.         are discussed in the pcrepartial documentation.
1999    
2000     The string to be matched by pcre_exec()     The string to be matched by pcre_exec()
2001    
2002         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
2003         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
2004         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.
2005         Unlike  the  pattern string, the subject may contain binary zero bytes.         Unlike the pattern string, the subject may contain binary  zero  bytes.
2006         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
2007         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.
2008    
2009         A  non-zero  starting offset is useful when searching for another match         A non-zero starting offset is useful when searching for  another  match
2010         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-
2011         cess.   Setting  startoffset differs from just passing over a shortened         cess.  Setting startoffset differs from just passing over  a  shortened
2012         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
2013         with any kind of lookbehind. For example, consider the pattern         with any kind of lookbehind. For example, consider the pattern
2014    
2015           \Biss\B           \Biss\B
2016    
2017         which  finds  occurrences  of "iss" in the middle of words. (\B matches         which finds occurrences of "iss" in the middle of  words.  (\B  matches
2018         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.)
2019         When  applied  to the string "Mississipi" the first call to pcre_exec()         When applied to the string "Mississipi" the first call  to  pcre_exec()
2020         finds the first occurrence. If pcre_exec() is called  again  with  just         finds  the  first  occurrence. If pcre_exec() is called again with just
2021         the  remainder  of  the  subject,  namely  "issipi", it does not match,         the remainder of the subject,  namely  "issipi",  it  does  not  match,
2022         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
2023         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
2024         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-
2025         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
2026         discover that it is preceded by a letter.         discover that it is preceded by a letter.
2027    
2028         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,
2029         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
2030         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
2031         subject.         subject.
2032    
2033     How pcre_exec() returns captured substrings     How pcre_exec() returns captured substrings
2034    
2035         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
2036         addition, further substrings from the subject  may  be  picked  out  by         addition,  further  substrings  from  the  subject may be picked out by
2037         parts  of  the  pattern.  Following the usage in Jeffrey Friedl's book,         parts of the pattern. Following the usage  in  Jeffrey  Friedl's  book,
2038         this is called "capturing" in what follows, and the  phrase  "capturing         this  is  called "capturing" in what follows, and the phrase "capturing
2039         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-
2040         string. PCRE supports several other kinds of  parenthesized  subpattern         string.  PCRE  supports several other kinds of parenthesized subpattern
2041         that do not cause substrings to be captured.         that do not cause substrings to be captured.
2042    
2043         Captured  substrings are returned to the caller via a vector of integer         Captured substrings are returned to the caller via a vector of  integer
2044         offsets whose address is passed in ovector. The number of  elements  in         offsets  whose  address is passed in ovector. The number of elements in
2045         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.
2046         Note: this argument is NOT the size of ovector in bytes.         Note: this argument is NOT the size of ovector in bytes.
2047    
2048         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-
2049         strings,  each  substring using a pair of integers. The remaining third         strings, each substring using a pair of integers. The  remaining  third
2050         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-
2051         turing  subpatterns, and is not available for passing back information.         turing subpatterns, and is not available for passing back  information.
2052         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
2053         it is not, it is rounded down.         it is not, it is rounded down.
2054    
2055         When  a  match  is successful, information about captured substrings is         When a match is successful, information about  captured  substrings  is
2056         returned in pairs of integers, starting at the  beginning  of  ovector,         returned  in  pairs  of integers, starting at the beginning of ovector,
2057         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
2058         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-
2059         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
2060         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-
2061         tor[1],  identify  the  portion  of  the  subject string matched by the         tor[1], identify the portion of  the  subject  string  matched  by  the
2062         entire pattern. The next pair is used for the first  capturing  subpat-         entire  pattern.  The next pair is used for the first capturing subpat-
2063         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
2064         pairs that have been set. If there are no  capturing  subpatterns,  the         highest numbered pair that has been set. For example, if two substrings
2065         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
2066         first pair of offsets has been set.         subpatterns,  the return value from a successful match is 1, indicating
2067           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.  
2068    
2069         If a capturing subpattern is matched repeatedly, it is the last portion         If a capturing subpattern is matched repeatedly, it is the last portion
2070         of the string that it matched that is returned.         of the string that it matched that is returned.
# Line 1639  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2078  MATCHING A PATTERN: THE TRADITIONAL FUNC
2078         substrings,  PCRE has to get additional memory for use during matching.         substrings,  PCRE has to get additional memory for use during matching.
2079         Thus it is usually advisable to supply an ovector.         Thus it is usually advisable to supply an ovector.
2080    
2081         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
2082         patterns there are in a compiled pattern. The smallest size for ovector         subpatterns  there  are  in  a  compiled pattern. The smallest size for
2083         that will allow for n captured substrings, in addition to  the  offsets         ovector that will allow for n captured substrings, in addition  to  the
2084         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.
2085    
2086           It  is  possible for capturing subpattern number n+1 to match some part
2087           of the subject when subpattern n has not been used at all. For example,
2088           if  the  string  "abc"  is  matched against the pattern (a|(z))(bc) the
2089           return from the function is 4, and subpatterns 1 and 3 are matched, but
2090           2  is  not.  When  this happens, both values in the offset pairs corre-
2091           sponding to unused subpatterns are set to -1.
2092    
2093           Offset values that correspond to unused subpatterns at the end  of  the
2094           expression  are  also  set  to  -1. For example, if the string "abc" is
2095           matched against the pattern (abc)(x(yz)?)? subpatterns 2 and 3 are  not
2096           matched.  The  return  from the function is 2, because the highest used
2097           capturing subpattern number is 1. However, you can refer to the offsets
2098           for  the  second  and third capturing subpatterns if you wish (assuming
2099           the vector is large enough, of course).
2100    
2101     Return values from pcre_exec()         Some convenience functions are provided  for  extracting  the  captured
2102           substrings as separate strings. These are described below.
2103    
2104       Error return values from pcre_exec()
2105    
2106         If  pcre_exec()  fails, it returns a negative number. The following are         If  pcre_exec()  fails, it returns a negative number. The following are
2107         defined in the header file:         defined in the header file:
# Line 1670  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2127  MATCHING A PATTERN: THE TRADITIONAL FUNC
2127         an environment with the other endianness. This is the error  that  PCRE         an environment with the other endianness. This is the error  that  PCRE
2128         gives when the magic number is not present.         gives when the magic number is not present.
2129    
2130           PCRE_ERROR_UNKNOWN_NODE   (-5)           PCRE_ERROR_UNKNOWN_OPCODE (-5)
2131    
2132         While running the pattern match, an unknown item was encountered in the         While running the pattern match, an unknown item was encountered in the
2133         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 1692  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2149  MATCHING A PATTERN: THE TRADITIONAL FUNC
2149    
2150           PCRE_ERROR_MATCHLIMIT     (-8)           PCRE_ERROR_MATCHLIMIT     (-8)
2151    
2152         The  recursion  and backtracking limit, as specified by the match_limit         The  backtracking  limit,  as  specified  by the match_limit field in a
2153         field in a pcre_extra structure (or defaulted)  was  reached.  See  the         pcre_extra structure (or defaulted) was reached.  See  the  description
2154         description above.         above.
2155    
2156           PCRE_ERROR_CALLOUT        (-9)           PCRE_ERROR_CALLOUT        (-9)
2157    
# Line 1733  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2190  MATCHING A PATTERN: THE TRADITIONAL FUNC
2190    
2191         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.
2192    
2193             PCRE_ERROR_RECURSIONLIMIT (-21)
2194    
2195           The internal recursion limit, as specified by the match_limit_recursion
2196           field in a pcre_extra structure (or defaulted)  was  reached.  See  the
2197           description above.
2198    
2199             PCRE_ERROR_BADNEWLINE     (-23)
2200    
2201           An invalid combination of PCRE_NEWLINE_xxx options was given.
2202    
2203           Error numbers -16 to -20 and -22 are not used by pcre_exec().
2204    
2205    
2206  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
2207    
# Line 1753  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER Line 2222  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
2222         string_list() are provided for extracting captured substrings  as  new,         string_list() are provided for extracting captured substrings  as  new,
2223         separate,  zero-terminated strings. These functions identify substrings         separate,  zero-terminated strings. These functions identify substrings
2224         by number. The next section describes functions  for  extracting  named         by number. The next section describes functions  for  extracting  named
2225         substrings.  A  substring  that  contains  a  binary  zero is correctly         substrings.
2226         extracted and has a further zero added on the end, but  the  result  is  
2227         not, of course, a C string.         A  substring that contains a binary zero is correctly extracted and has
2228           a further zero added on the end, but the result is not, of course, a  C
2229           string.   However,  you  can  process such a string by referring to the
2230           length that is  returned  by  pcre_copy_substring()  and  pcre_get_sub-
2231           string().  Unfortunately, the interface to pcre_get_substring_list() is
2232           not adequate for handling strings containing binary zeros, because  the
2233           end of the final string is not independently indicated.
2234    
2235         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-
2236         tions: subject is the subject string that has  just  been  successfully         tions: subject is the subject string that has  just  been  successfully
# Line 1775  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER Line 2250  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
2250         buffersize, while for pcre_get_substring() a new  block  of  memory  is         buffersize, while for pcre_get_substring() a new  block  of  memory  is
2251         obtained  via  pcre_malloc,  and its address is returned via stringptr.         obtained  via  pcre_malloc,  and its address is returned via stringptr.
2252         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
2253         the terminating zero, or one of         the terminating zero, or one of these error codes:
2254    
2255           PCRE_ERROR_NOMEMORY       (-6)           PCRE_ERROR_NOMEMORY       (-6)
2256    
# Line 1791  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER Line 2266  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
2266         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
2267         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
2268         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
2269         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
2270           error code
2271    
2272           PCRE_ERROR_NOMEMORY       (-6)           PCRE_ERROR_NOMEMORY       (-6)
2273    
2274         if the attempt to get the memory block failed.         if the attempt to get the memory block failed.
2275    
2276         When  any of these functions encounter a substring that is unset, which         When any of these functions encounter a substring that is unset,  which
2277         can happen when capturing subpattern number n+1 matches  some  part  of         can  happen  when  capturing subpattern number n+1 matches some part of
2278         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
2279         empty string. This can be distinguished from a genuine zero-length sub-         empty string. This can be distinguished from a genuine zero-length sub-
2280         string  by inspecting the appropriate offset in ovector, which is nega-         string by inspecting the appropriate offset in ovector, which is  nega-
2281         tive for unset substrings.         tive for unset substrings.
2282    
2283         The two convenience functions pcre_free_substring() and  pcre_free_sub-         The  two convenience functions pcre_free_substring() and pcre_free_sub-
2284         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
2285         call  of  pcre_get_substring()  or  pcre_get_substring_list(),  respec-         call  of  pcre_get_substring()  or  pcre_get_substring_list(),  respec-
2286         tively.  They  do  nothing  more  than  call the function pointed to by         tively. They do nothing more than  call  the  function  pointed  to  by
2287         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.
2288         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-
2289         cial  interface  to  another  programming  language  which  cannot  use         cial   interface  to  another  programming  language  that  cannot  use
2290         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-
2291         vided.         vided.
2292    
2293    
# Line 1830  EXTRACTING CAPTURED SUBSTRINGS BY NAME Line 2306  EXTRACTING CAPTURED SUBSTRINGS BY NAME
2306              int stringcount, const char *stringname,              int stringcount, const char *stringname,
2307              const char **stringptr);              const char **stringptr);
2308    
2309         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-
2310         ber.  For example, for this pattern         ber.  For example, for this pattern
2311    
2312           (a+)b(?<xxx>\d+)...           (a+)b(?<xxx>\d+)...
2313    
2314         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
2315         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
2316         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-
2317         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
2318         there is no subpattern of that name.         the subpattern number, or PCRE_ERROR_NOSUBSTRING (-7) if  there  is  no
2319           subpattern of that name.
2320    
2321         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
2322         the functions described in the previous section. For convenience, there         the functions described in the previous section. For convenience, there
# Line 1858  EXTRACTING CAPTURED SUBSTRINGS BY NAME Line 2335  EXTRACTING CAPTURED SUBSTRINGS BY NAME
2335    
2336         These functions call pcre_get_stringnumber(), and if it succeeds,  they         These functions call pcre_get_stringnumber(), and if it succeeds,  they
2337         then  call  pcre_copy_substring() or pcre_get_substring(), as appropri-         then  call  pcre_copy_substring() or pcre_get_substring(), as appropri-
2338         ate.         ate. NOTE: If PCRE_DUPNAMES is set and there are duplicate  names,  the
2339           behaviour may not be what you want (see the next section).
2340    
2341    
2342    DUPLICATE SUBPATTERN NAMES
2343    
2344           int pcre_get_stringtable_entries(const pcre *code,
2345                const char *name, char **first, char **last);
2346    
2347           When  a  pattern  is  compiled with the PCRE_DUPNAMES option, names for
2348           subpatterns are not required to  be  unique.  Normally,  patterns  with
2349           duplicate  names  are such that in any one match, only one of the named
2350           subpatterns participates. An example is shown in the pcrepattern  docu-
2351           mentation.
2352    
2353           When    duplicates   are   present,   pcre_copy_named_substring()   and
2354           pcre_get_named_substring() return the first substring corresponding  to
2355           the  given  name  that  is set. If none are set, PCRE_ERROR_NOSUBSTRING
2356           (-7) is returned; no  data  is  returned.  The  pcre_get_stringnumber()
2357           function  returns one of the numbers that are associated with the name,
2358           but it is not defined which it is.
2359    
2360           If you want to get full details of all captured substrings for a  given
2361           name,  you  must  use  the pcre_get_stringtable_entries() function. The
2362           first argument is the compiled pattern, and the second is the name. The
2363           third  and  fourth  are  pointers to variables which are updated by the
2364           function. After it has run, they point to the first and last entries in
2365           the  name-to-number  table  for  the  given  name.  The function itself
2366           returns the length of each entry,  or  PCRE_ERROR_NOSUBSTRING  (-7)  if
2367           there  are none. The format of the table is described above in the sec-
2368           tion entitled Information about a  pattern.   Given  all  the  relevant
2369           entries  for the name, you can extract each of their numbers, and hence
2370           the captured data, if any.
2371    
2372    
2373  FINDING ALL POSSIBLE MATCHES  FINDING ALL POSSIBLE MATCHES
# Line 1887  MATCHING A PATTERN: THE ALTERNATIVE FUNC Line 2396  MATCHING A PATTERN: THE ALTERNATIVE FUNC
2396              int *workspace, int wscount);              int *workspace, int wscount);
2397    
2398         The  function  pcre_dfa_exec()  is  called  to  match  a subject string         The  function  pcre_dfa_exec()  is  called  to  match  a subject string
2399         against a compiled pattern, using a "DFA" matching algorithm. This  has         against a compiled pattern, using a matching algorithm that  scans  the
2400         different  characteristics to the normal algorithm, and is not compati-         subject  string  just  once, and does not backtrack. This has different
2401         ble with Perl. Some of the features of PCRE patterns are not supported.         characteristics to the normal algorithm, and  is  not  compatible  with
2402         Nevertheless, there are times when this kind of matching can be useful.         Perl.  Some  of the features of PCRE patterns are not supported. Never-
2403         For a discussion of the two matching algorithms, see  the  pcrematching         theless, there are times when this kind of matching can be useful.  For
2404         documentation.         a discussion of the two matching algorithms, see the pcrematching docu-
2405           mentation.
2406    
2407         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
2408         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-
2409         ent  way,  and  this is described below. The other common arguments are         ent way, and this is described below. The other  common  arguments  are
2410         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
2411         repeated here.         repeated here.
2412    
2413         The  two  additional  arguments provide workspace for the function. The         The two additional arguments provide workspace for  the  function.  The
2414         workspace vector should contain at least 20 elements. It  is  used  for         workspace  vector  should  contain at least 20 elements. It is used for
2415         keeping  track  of  multiple  paths  through  the  pattern  tree.  More         keeping  track  of  multiple  paths  through  the  pattern  tree.  More
2416         workspace will be needed for patterns and subjects where  there  are  a         workspace  will  be  needed for patterns and subjects where there are a
2417         lot of possible matches.         lot of potential matches.
2418    
2419         Here is an example of a simple call to pcre_exec():         Here is an example of a simple call to pcre_dfa_exec():
2420    
2421           int rc;           int rc;
2422           int ovector[10];           int ovector[10];
2423           int wspace[20];           int wspace[20];
2424           rc = pcre_exec(           rc = pcre_dfa_exec(
2425             re,             /* result of pcre_compile() */             re,             /* result of pcre_compile() */
2426             NULL,           /* we didn't study the pattern */             NULL,           /* we didn't study the pattern */
2427             "some string",  /* the subject string */             "some string",  /* the subject string */
# Line 1925  MATCHING A PATTERN: THE ALTERNATIVE FUNC Line 2435  MATCHING A PATTERN: THE ALTERNATIVE FUNC
2435    
2436     Option bits for pcre_dfa_exec()     Option bits for pcre_dfa_exec()
2437    
2438         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
2439         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-
2440         PCRE_NOTEOL,     PCRE_NOTEMPTY,    PCRE_NO_UTF8_CHECK,    PCRE_PARTIAL,         LINE_xxx, PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY,  PCRE_NO_UTF8_CHECK,
2441         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
2442         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
2443         repeated here.         not repeated here.
2444    
2445           PCRE_PARTIAL           PCRE_PARTIAL
2446    
2447         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
2448         details   are   slightly   different.  When  PCRE_PARTIAL  is  set  for         details  are  slightly  different.  When  PCRE_PARTIAL   is   set   for
2449         pcre_dfa_exec(), the return code PCRE_ERROR_NOMATCH is  converted  into         pcre_dfa_exec(),  the  return code PCRE_ERROR_NOMATCH is converted into
2450         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
2451         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-
2452         sibility.  The portion of the string that provided the partial match is         sibility. The portion of the string that provided the partial match  is
2453         set as the first matching string.         set as the first matching string.
2454    
2455           PCRE_DFA_SHORTEST           PCRE_DFA_SHORTEST
2456    
2457         Setting the PCRE_DFA_SHORTEST option causes the matching  algorithm  to         Setting  the  PCRE_DFA_SHORTEST option causes the matching algorithm to
2458         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-
2459         algorithm works, this is necessarily the shortest possible match at the         tive  algorithm  works, this is necessarily the shortest possible match
2460         first possible matching point in the subject string.         at the first possible matching point in the subject string.
2461    
2462           PCRE_DFA_RESTART           PCRE_DFA_RESTART
2463    
2464         When  pcre_dfa_exec()  is  called  with  the  PCRE_PARTIAL  option, and         When pcre_dfa_exec()  is  called  with  the  PCRE_PARTIAL  option,  and
2465         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-
2466         tional  subject  characters,  and have it continue with the same match.         tional subject characters, and have it continue with  the  same  match.
2467         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
2468         workspace  and wscount options must reference the same vector as before         workspace and wscount options must reference the same vector as  before
2469         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
2470         match.  There  is  more  discussion of this facility in the pcrepartial         match. There is more discussion of this  facility  in  the  pcrepartial
2471         documentation.         documentation.
2472    
2473     Successful returns from pcre_dfa_exec()     Successful returns from pcre_dfa_exec()
2474    
2475         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-
2476         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
2477         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
2478         matches  are all initial substrings of the longer matches. For example,         matches are all initial substrings of the longer matches. For  example,
2479         if the pattern         if the pattern
2480    
2481           <.*>           <.*>
# Line 1980  MATCHING A PATTERN: THE ALTERNATIVE FUNC Line 2490  MATCHING A PATTERN: THE ALTERNATIVE FUNC
2490           <something> <something else>           <something> <something else>
2491           <something> <something else> <something further>           <something> <something else> <something further>
2492    
2493         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,
2494         which  is  the  number of matched substrings. The substrings themselves         which is the number of matched substrings.  The  substrings  themselves
2495         are returned in ovector. Each string uses two elements;  the  first  is         are  returned  in  ovector. Each string uses two elements; the first is
2496         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
2497         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
2498         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
2499         with the way pcre_exec() returns data, even though the meaning  of  the         compatibility  with  the  way pcre_exec() returns data, even though the
2500         strings is different.)         meaning of the strings is different.)
2501    
2502         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-
2503         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
2504         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
2505         filled with the longest matches.         filled with the longest matches.
2506    
2507     Error returns from pcre_dfa_exec()     Error returns from pcre_dfa_exec()
2508    
2509         The pcre_dfa_exec() function returns a negative number when  it  fails.         The  pcre_dfa_exec()  function returns a negative number when it fails.
2510         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
2511         described above.  There are in addition the following errors  that  are         described  above.   There are in addition the following errors that are
2512         specific to pcre_dfa_exec():         specific to pcre_dfa_exec():
2513    
2514           PCRE_ERROR_DFA_UITEM      (-16)           PCRE_ERROR_DFA_UITEM      (-16)
2515    
2516         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-
2517         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
2518         reference.         reference.
2519    
2520           PCRE_ERROR_DFA_UCOND      (-17)           PCRE_ERROR_DFA_UCOND      (-17)
2521    
2522         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
2523         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
2524         supported.         in a specific group. These are not supported.
2525    
2526           PCRE_ERROR_DFA_UMLIMIT    (-18)           PCRE_ERROR_DFA_UMLIMIT    (-18)
2527    
2528         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
2529         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
2530         (it is meaningless).         (it is meaningless).
2531    
2532           PCRE_ERROR_DFA_WSSIZE     (-19)           PCRE_ERROR_DFA_WSSIZE     (-19)
2533    
2534         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
2535         workspace vector.         workspace vector.
2536    
2537           PCRE_ERROR_DFA_RECURSE    (-20)           PCRE_ERROR_DFA_RECURSE    (-20)
2538    
2539         When a recursive subpattern is processed, the matching  function  calls         When  a  recursive subpattern is processed, the matching function calls
2540         itself  recursively,  using  private vectors for ovector and workspace.         itself recursively, using private vectors for  ovector  and  workspace.
2541         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
2542         should be extremely rare, as a vector of size 1000 is used.         should be extremely rare, as a vector of size 1000 is used.
2543    
 Last updated: 16 May 2005  
 Copyright (c) 1997-2005 University of Cambridge.  
 -----------------------------------------------------------------------------  
2544    
2545    SEE ALSO
2546    
2547           pcrebuild(3), pcrecallout(3), pcrecpp(3)(3), pcrematching(3),  pcrepar-
2548           tial(3),  pcreposix(3), pcreprecompile(3), pcresample(3), pcrestack(3).
2549    
2550    
2551    AUTHOR
2552    
2553           Philip Hazel
2554           University Computing Service
2555           Cambridge CB2 3QH, England.
2556    
2557    
2558    REVISION
2559    
2560           Last updated: 27 November 2007
2561           Copyright (c) 1997-2007 University of Cambridge.
2562    ------------------------------------------------------------------------------
2563    
2564    
2565    PCRECALLOUT(3)                                                  PCRECALLOUT(3)
2566    
2567    
2568  NAME  NAME
# Line 2057  PCRE CALLOUTS Line 2585  PCRE CALLOUTS
2585         default value is zero.  For  example,  this  pattern  has  two  callout         default value is zero.  For  example,  this  pattern  has  two  callout
2586         points:         points:
2587    
2588           (?C1)eabc(?C2)def           (?C1)abc(?C2)def
2589    
2590         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
2591         called, PCRE automatically  inserts  callouts,  all  with  number  255,         called, PCRE automatically  inserts  callouts,  all  with  number  255,
# Line 2132  THE CALLOUT INTERFACE Line 2660  THE CALLOUT INTERFACE
2660         The subject and subject_length fields contain copies of the values that         The subject and subject_length fields contain copies of the values that
2661         were passed to pcre_exec().         were passed to pcre_exec().
2662    
2663         The start_match field contains the offset within the subject  at  which         The start_match field normally contains the offset within  the  subject
2664         the  current match attempt started. If the pattern is not anchored, the         at  which  the  current  match  attempt started. However, if the escape
2665         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
2666         pattern for different starting points in the subject.         modified  starting  point.  If the pattern is not anchored, the callout
2667           function may be called several times from the same point in the pattern
2668           for different starting points in the subject.
2669    
2670         The  current_position  field  contains the offset within the subject of         The  current_position  field  contains the offset within the subject of
2671         the current match pointer.         the current match pointer.
# Line 2188  RETURN VALUES Line 2718  RETURN VALUES
2718         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
2719         itself.         itself.
2720    
 Last updated: 28 February 2005  
 Copyright (c) 1997-2005 University of Cambridge.  
 -----------------------------------------------------------------------------  
2721    
2722    AUTHOR
2723    
2724           Philip Hazel
2725           University Computing Service
2726           Cambridge CB2 3QH, England.
2727    
2728    
2729    REVISION
2730    
2731           Last updated: 29 May 2007
2732           Copyright (c) 1997-2007 University of Cambridge.
2733    ------------------------------------------------------------------------------
2734    
2735    
2736    PCRECOMPAT(3)                                                    PCRECOMPAT(3)
2737    
2738    
2739  NAME  NAME
# Line 2201  NAME Line 2743  NAME
2743  DIFFERENCES BETWEEN PCRE AND PERL  DIFFERENCES BETWEEN PCRE AND PERL
2744    
2745         This  document describes the differences in the ways that PCRE and Perl         This  document describes the differences in the ways that PCRE and Perl
2746         handle regular expressions. The differences  described  here  are  with         handle regular expressions. The differences described here  are  mainly
2747         respect to Perl 5.8.         with  respect  to  Perl 5.8, though PCRE versions 7.0 and later contain
2748           some features that are expected to be in the forthcoming Perl 5.10.
2749         1.  PCRE does not have full UTF-8 support. Details of what it does have  
2750         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
2751           of  what  it does have are given in the section on UTF-8 support in the
2752           main pcre page.
2753    
2754         2. PCRE does not allow repeat quantifiers on lookahead assertions. Perl         2. PCRE does not allow repeat quantifiers on lookahead assertions. Perl
2755         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 2232  DIFFERENCES BETWEEN PCRE AND PERL Line 2776  DIFFERENCES BETWEEN PCRE AND PERL
2776         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
2777         is  built  with Unicode character property support. The properties that         is  built  with Unicode character property support. The properties that
2778         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-
2779         erties such as Lu and Nd.         erties  such  as  Lu and Nd, script names such as Greek or Han, and the
2780           derived properties Any and L&.
2781    
2782         7. PCRE does support the \Q...\E escape for quoting substrings. Charac-         7. PCRE does support the \Q...\E escape for quoting substrings. Charac-
2783         ters in between are treated as literals.  This  is  slightly  different         ters  in  between  are  treated as literals. This is slightly different
2784         from  Perl  in  that  $  and  @ are also handled as literals inside the         from Perl in that $ and @ are  also  handled  as  literals  inside  the
2785         quotes. In Perl, they cause variable interpolation (but of course  PCRE         quotes.  In Perl, they cause variable interpolation (but of course PCRE
2786         does not have variables). Note the following examples:         does not have variables). Note the following examples:
2787    
2788             Pattern            PCRE matches      Perl matches             Pattern            PCRE matches      Perl matches
# Line 2247  DIFFERENCES BETWEEN PCRE AND PERL Line 2792  DIFFERENCES BETWEEN PCRE AND PERL
2792             \Qabc\$xyz\E       abc\$xyz          abc\$xyz             \Qabc\$xyz\E       abc\$xyz          abc\$xyz
2793             \Qabc\E\$\Qxyz\E   abc$xyz           abc$xyz             \Qabc\E\$\Qxyz\E   abc$xyz           abc$xyz
2794    
2795         The  \Q...\E  sequence  is recognized both inside and outside character         The \Q...\E sequence is recognized both inside  and  outside  character
2796         classes.         classes.
2797    
2798         8. Fairly obviously, PCRE does not support the (?{code}) and (?p{code})         8. Fairly obviously, PCRE does not support the (?{code}) and (??{code})
2799         constructions.  However,  there is support for recursive patterns using         constructions. However, there is support for recursive  patterns.  This
2800         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
2801         "callout"  feature allows an external function to be called during pat-         "callout" feature allows an external function to be called during  pat-
2802         tern matching. See the pcrecallout documentation for details.         tern matching. See the pcrecallout documentation for details.
2803    
2804         9. There are some differences that are concerned with the  settings  of         9.  Subpatterns  that  are  called  recursively or as "subroutines" are
2805         captured  strings  when  part  of  a  pattern is repeated. For example,         always treated as atomic groups in  PCRE.  This  is  like  Python,  but
2806         matching "aba" against the  pattern  /^(a(b)?)+$/  in  Perl  leaves  $2         unlike Perl.
2807    
2808           10.  There are some differences that are concerned with the settings of
2809           captured strings when part of  a  pattern  is  repeated.  For  example,
2810           matching  "aba"  against  the  pattern  /^(a(b)?)+$/  in Perl leaves $2
2811         unset, but in PCRE it is set to "b".         unset, but in PCRE it is set to "b".
2812    
2813         10. PCRE provides some extensions to the Perl regular expression facil-         11.  PCRE  does  support  Perl  5.10's  backtracking  verbs  (*ACCEPT),
2814         ities:         (*FAIL),  (*F),  (*COMMIT), (*PRUNE), (*SKIP), and (*THEN), but only in
2815           the forms without an  argument.  PCRE  does  not  support  (*MARK).  If
2816           (*ACCEPT)  is within capturing parentheses, PCRE does not set that cap-
2817           ture group; this is different to Perl.
2818    
2819           12. PCRE provides some extensions to the Perl regular expression facil-
2820           ities.   Perl  5.10  will  include new features that are not in earlier
2821           versions, some of which (such as named parentheses) have been  in  PCRE
2822           for some time. This list is with respect to Perl 5.10:
2823    
2824         (a) Although lookbehind assertions must  match  fixed  length  strings,         (a)  Although  lookbehind  assertions  must match fixed length strings,
2825         each alternative branch of a lookbehind assertion can match a different         each alternative branch of a lookbehind assertion can match a different
2826         length of string. Perl requires them all to have the same length.         length of string. Perl requires them all to have the same length.
2827    
2828         (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 $
2829         meta-character matches only at the very end of the string.         meta-character matches only at the very end of the string.
2830    
2831         (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-
2832         cial meaning is faulted.         cial meaning is faulted. Otherwise, like Perl, the backslash is quietly
2833           ignored.  (Perl can be made to issue a warning.)
2834    
2835         (d) If PCRE_UNGREEDY is set, the greediness of the  repetition  quanti-         (d) If PCRE_UNGREEDY is set, the greediness of the  repetition  quanti-
2836         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 2284  DIFFERENCES BETWEEN PCRE AND PERL Line 2842  DIFFERENCES BETWEEN PCRE AND PERL
2842         (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-
2843         TURE options for pcre_exec() have no Perl equivalents.         TURE options for pcre_exec() have no Perl equivalents.
2844    
2845         (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
2846         pattern  matching  (Perl  can  do  this using the (?p{code}) construct,         CRLF by the PCRE_BSR_ANYCRLF option.
        which PCRE cannot support.)  
2847    
2848         (h) PCRE supports named capturing substrings, using the Python  syntax.         (h) The callout facility is PCRE-specific.
2849    
2850         (i)  PCRE  supports  the  possessive quantifier "++" syntax, taken from         (i) The partial matching facility is PCRE-specific.
        Sun's Java package.  
2851    
2852         (j) The (R) condition, for testing recursion, is a PCRE extension.         (j) Patterns compiled by PCRE can be saved and re-used at a later time,
2853           even on different hosts that have the other endianness.
2854    
2855         (k) The callout facility is PCRE-specific.         (k) The alternative matching function (pcre_dfa_exec())  matches  in  a
2856           different way and is not Perl-compatible.
2857    
2858         (l) The partial matching facility is PCRE-specific.         (l)  PCRE  recognizes some special sequences such as (*CR) at the start
2859           of a pattern that set overall options that cannot be changed within the
2860           pattern.
2861    
        (m) Patterns compiled by PCRE can be saved and re-used at a later time,  
        even on different hosts that have the other endianness.  
2862    
2863         (n)  The  alternative  matching function (pcre_dfa_exec()) matches in a  AUTHOR
        different way and is not Perl-compatible.  
2864    
2865  Last updated: 28 February 2005         Philip Hazel
2866  Copyright (c) 1997-2005 University of Cambridge.         University Computing Service
2867  -----------------------------------------------------------------------------         Cambridge CB2 3QH, England.
2868    
2869    
2870    REVISION
2871    
2872           Last updated: 11 September 2007
2873           Copyright (c) 1997-2007 University of Cambridge.
2874    ------------------------------------------------------------------------------
2875    
2876    
2877    PCREPATTERN(3)                                                  PCREPATTERN(3)
2878    
2879    
2880  NAME  NAME
2881         PCRE - Perl-compatible regular expressions         PCRE - Perl-compatible regular expressions
# Line 2317  NAME Line 2883  NAME
2883    
2884  PCRE REGULAR EXPRESSION DETAILS  PCRE REGULAR EXPRESSION DETAILS
2885    
2886         The  syntax  and semantics of the regular expressions supported by PCRE         The  syntax and semantics of the regular expressions that are supported
2887         are described below. Regular expressions are also described in the Perl         by PCRE are described in detail below. There is a quick-reference  syn-
2888         documentation  and  in  a  number  of books, some of which have copious         tax  summary  in  the  pcresyntax  page. Perl's regular expressions are
2889         examples.  Jeffrey Friedl's "Mastering Regular Expressions",  published         described in its own documentation, and regular expressions in  general
2890         by  O'Reilly, covers regular expressions in great detail. This descrip-         are  covered in a number of books, some of which have copious examples.
2891         tion of PCRE's regular expressions is intended as reference material.         Jeffrey  Friedl's  "Mastering  Regular   Expressions",   published   by
2892           O'Reilly,  covers regular expressions in great detail. This description
2893           of PCRE's regular expressions is intended as reference material.
2894    
2895         The original operation of PCRE was on strings of  one-byte  characters.         The original operation of PCRE was on strings of  one-byte  characters.
2896         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 2336  PCRE REGULAR EXPRESSION DETAILS Line 2904  PCRE REGULAR EXPRESSION DETAILS
2904         ported  by  PCRE when its main matching function, pcre_exec(), is used.         ported  by  PCRE when its main matching function, pcre_exec(), is used.
2905         From  release  6.0,   PCRE   offers   a   second   matching   function,         From  release  6.0,   PCRE   offers   a   second   matching   function,
2906         pcre_dfa_exec(),  which matches using a different algorithm that is not         pcre_dfa_exec(),  which matches using a different algorithm that is not
2907         Perl-compatible. The advantages and disadvantages  of  the  alternative         Perl-compatible. Some of the features discussed below are not available
2908         function, and how it differs from the normal function, are discussed in         when  pcre_dfa_exec()  is used. The advantages and disadvantages of the
2909         the pcrematching page.         alternative function, and how it differs from the normal function,  are
2910           discussed in the pcrematching page.
2911         A regular expression is a pattern that is  matched  against  a  subject  
2912         string  from  left  to right. Most characters stand for themselves in a  
2913         pattern, and match the corresponding characters in the  subject.  As  a  NEWLINE CONVENTIONS
2914    
2915           PCRE  supports five different conventions for indicating line breaks in
2916           strings: a single CR (carriage return) character, a  single  LF  (line-
2917           feed) character, the two-character sequence CRLF, any of the three pre-
2918           ceding, or any Unicode newline sequence. The pcreapi page  has  further
2919           discussion  about newlines, and shows how to set the newline convention
2920           in the options arguments for the compiling and matching functions.
2921    
2922           It is also possible to specify a newline convention by starting a  pat-
2923           tern string with one of the following five sequences:
2924    
2925             (*CR)        carriage return
2926             (*LF)        linefeed
2927             (*CRLF)      carriage return, followed by linefeed
2928             (*ANYCRLF)   any of the three above
2929             (*ANY)       all Unicode newline sequences
2930    
2931           These override the default and the options given to pcre_compile(). For
2932           example, on a Unix system where LF is the default newline sequence, the
2933           pattern
2934    
2935             (*CR)a.b
2936    
2937           changes the convention to CR. That pattern matches "a\nb" because LF is
2938           no longer a newline. Note that these special settings,  which  are  not
2939           Perl-compatible,  are  recognized  only at the very start of a pattern,
2940           and that they must be in upper case.  If  more  than  one  of  them  is
2941           present, the last one is used.
2942    
2943           The  newline  convention  does  not  affect what the \R escape sequence
2944           matches. By default, this is any Unicode  newline  sequence,  for  Perl
2945           compatibility.  However, this can be changed; see the description of \R
2946           in the section entitled "Newline sequences" below. A change of \R  set-
2947           ting can be combined with a change of newline convention.
2948    
2949    
2950    CHARACTERS AND METACHARACTERS
2951    
2952           A  regular  expression  is  a pattern that is matched against a subject
2953           string from left to right. Most characters stand for  themselves  in  a
2954           pattern,  and  match  the corresponding characters in the subject. As a
2955         trivial example, the pattern         trivial example, the pattern
2956    
2957           The quick brown fox           The quick brown fox
2958    
2959         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
2960         caseless matching is specified (the PCRE_CASELESS option), letters  are         caseless  matching is specified (the PCRE_CASELESS option), letters are
2961         matched  independently  of case. In UTF-8 mode, PCRE always understands         matched independently of case. In UTF-8 mode, PCRE  always  understands
2962         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
2963         caseless  matching  is always possible. For characters with higher val-         caseless matching is always possible. For characters with  higher  val-
2964         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
2965         property  support,  but  not  otherwise.   If  you want to use caseless         property support, but not otherwise.   If  you  want  to  use  caseless
2966         matching for characters 128 and above, you must  ensure  that  PCRE  is         matching  for  characters  128  and above, you must ensure that PCRE is
2967         compiled with Unicode property support as well as with UTF-8 support.         compiled with Unicode property support as well as with UTF-8 support.
2968    
2969         The  power  of  regular  expressions  comes from the ability to include         The power of regular expressions comes  from  the  ability  to  include
2970         alternatives and repetitions in the pattern. These are encoded  in  the         alternatives  and  repetitions in the pattern. These are encoded in the
2971         pattern by the use of metacharacters, which do not stand for themselves         pattern by the use of metacharacters, which do not stand for themselves
2972         but instead are interpreted in some special way.         but instead are interpreted in some special way.
2973    
2974         There are two different sets of metacharacters: those that  are  recog-         There  are  two different sets of metacharacters: those that are recog-
2975         nized  anywhere in the pattern except within square brackets, and those         nized anywhere in the pattern except within square brackets, and  those
2976         that are recognized in square brackets. Outside  square  brackets,  the         that  are  recognized  within square brackets. Outside square brackets,
2977         metacharacters are as follows:         the metacharacters are as follows:
2978    
2979           \      general escape character with several uses           \      general escape character with several uses
2980           ^      assert start of string (or line, in multiline mode)           ^      assert start of string (or line, in multiline mode)
# Line 2383  PCRE REGULAR EXPRESSION DETAILS Line 2992  PCRE REGULAR EXPRESSION DETAILS
2992                  also "possessive quantifier"                  also "possessive quantifier"
2993           {      start min/max quantifier           {      start min/max quantifier
2994    
2995         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
2996         class". In a character class the only metacharacters are:         class". In a character class the only metacharacters are:
2997    
2998           \      general escape character           \      general escape character
# Line 2393  PCRE REGULAR EXPRESSION DETAILS Line 3002  PCRE REGULAR EXPRESSION DETAILS
3002                    syntax)                    syntax)
3003           ]      terminates the character class           ]      terminates the character class
3004    
3005         The following sections describe the use of each of the  metacharacters.         The  following sections describe the use of each of the metacharacters.
3006    
3007    
3008  BACKSLASH  BACKSLASH
3009    
3010         The backslash character has several uses. Firstly, if it is followed by         The backslash character has several uses. Firstly, if it is followed by
3011         a non-alphanumeric character, it takes away any  special  meaning  that         a  non-alphanumeric  character,  it takes away any special meaning that
3012         character  may  have.  This  use  of  backslash  as an escape character         character may have. This  use  of  backslash  as  an  escape  character
3013         applies both inside and outside character classes.         applies both inside and outside character classes.
3014    
3015         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
3016         pattern.   This  escaping  action  applies whether or not the following         pattern.  This escaping action applies whether  or  not  the  following
3017         character would otherwise be interpreted as a metacharacter, so  it  is         character  would  otherwise be interpreted as a metacharacter, so it is
3018         always  safe  to  precede  a non-alphanumeric with backslash to specify         always safe to precede a non-alphanumeric  with  backslash  to  specify
3019         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-
3020         slash, you write \\.         slash, you write \\.
3021    
3022         If  a  pattern is compiled with the PCRE_EXTENDED option, whitespace in         If a pattern is compiled with the PCRE_EXTENDED option,  whitespace  in
3023         the pattern (other than in a character class) and characters between  a         the  pattern (other than in a character class) and characters between a
3024         # outside a character class and the next newline character are ignored.         # outside a character class and the next newline are ignored. An escap-
3025         An escaping backslash can be used to include a whitespace or #  charac-         ing  backslash  can  be  used to include a whitespace or # character as
3026         ter as part of the pattern.         part of the pattern.
3027    
3028         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-
3029         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-
3030         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
3031         sequences in PCRE, whereas in Perl, $ and @ cause  variable  interpola-         sequences  in  PCRE, whereas in Perl, $ and @ cause variable interpola-
3032         tion. Note the following examples:         tion. Note the following examples:
3033    
3034           Pattern            PCRE matches   Perl matches           Pattern            PCRE matches   Perl matches
# Line 2429  BACKSLASH Line 3038  BACKSLASH
3038           \Qabc\$xyz\E       abc\$xyz       abc\$xyz           \Qabc\$xyz\E       abc\$xyz       abc\$xyz
3039           \Qabc\E\$\Qxyz\E   abc$xyz        abc$xyz           \Qabc\E\$\Qxyz\E   abc$xyz        abc$xyz
3040    
3041         The  \Q...\E  sequence  is recognized both inside and outside character         The \Q...\E sequence is recognized both inside  and  outside  character
3042         classes.         classes.
3043    
3044     Non-printing characters     Non-printing characters
3045    
3046         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-
3047         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
3048         appearance of non-printing characters, apart from the binary zero  that         appearance  of non-printing characters, apart from the binary zero that
3049         terminates  a  pattern,  but  when  a pattern is being prepared by text         terminates a pattern, but when a pattern  is  being  prepared  by  text
3050         editing, it is usually easier  to  use  one  of  the  following  escape         editing,  it  is  usually  easier  to  use  one of the following escape
3051         sequences than the binary character it represents:         sequences than the binary character it represents:
3052    
3053           \a        alarm, that is, the BEL character (hex 07)           \a        alarm, that is, the BEL character (hex 07)
3054           \cx       "control-x", where x is any character           \cx       "control-x", where x is any character
3055           \e        escape (hex 1B)           \e        escape (hex 1B)
3056           \f        formfeed (hex 0C)           \f        formfeed (hex 0C)
3057           \n        newline (hex 0A)           \n        linefeed (hex 0A)
3058           \r        carriage return (hex 0D)           \r        carriage return (hex 0D)
3059           \t        tab (hex 09)           \t        tab (hex 09)
3060           \ddd      character with octal code ddd, or backreference           \ddd      character with octal code ddd, or backreference
3061           \xhh      character with hex code hh           \xhh      character with hex code hh
3062           \x{hhh..} character with hex code hhh... (UTF-8 mode only)           \x{hhh..} character with hex code hhh..
3063    
3064         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,
3065         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
3066         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;
3067         becomes hex 7B.         becomes hex 7B.
3068    
3069         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
3070         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
3071         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
3072         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,
3073         7FFFFFFF). If characters other than hexadecimal digits  appear  between         the  maximum value in hexadecimal is 7FFFFFFF. Note that this is bigger
3074         \x{  and }, or if there is no terminating }, this form of escape is not         than the largest Unicode code point, which is 10FFFF.
3075         recognized. Instead, the initial \x will  be  interpreted  as  a  basic  
3076         hexadecimal  escape, with no following digits, giving a character whose         If characters other than hexadecimal digits appear between \x{  and  },
3077         value is zero.         or if there is no terminating }, this form of escape is not recognized.
3078           Instead, the initial \x will be  interpreted  as  a  basic  hexadecimal
3079           escape,  with  no  following  digits, giving a character whose value is
3080           zero.
3081    
3082         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
3083         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-
3084         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}.
3085         \x{dc}.  
3086           After \0 up to two further octal digits are read. If  there  are  fewer
3087         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
3088         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
3089         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
3090         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.  
3091    
3092         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-
3093         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 2489  BACKSLASH Line 3099  BACKSLASH
3099    
3100         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
3101         and  there have not been that many capturing subpatterns, PCRE re-reads         and  there have not been that many capturing subpatterns, PCRE re-reads
3102         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-
3103         gle byte from the least significant 8 bits of the value. Any subsequent         erate  a data character. Any subsequent digits stand for themselves. In
3104         digits stand for themselves.  For example:         non-UTF-8 mode, the value of a character specified  in  octal  must  be
3105           less  than  \400.  In  UTF-8 mode, values up to \777 are permitted. For
3106           example:
3107    
3108           \040   is another way of writing a space           \040   is another way of writing a space
3109           \40    is the same, provided there are fewer than 40           \40    is the same, provided there are fewer than 40
# Line 2511  BACKSLASH Line 3123  BACKSLASH
3123         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
3124         leading zero, because no more than three octal digits are ever read.         leading zero, because no more than three octal digits are ever read.
3125    
3126         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
3127         character (in UTF-8 mode) can be used both inside and outside character         inside and outside character classes. In addition, inside  a  character
3128         classes.  In  addition,  inside  a  character class, the sequence \b is         class,  the  sequence \b is interpreted as the backspace character (hex
3129         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"
3130         interpreted  as  the  character  "X".  Outside a character class, these         and  "X", respectively. Outside a character class, these sequences have
3131         sequences have different meanings (see below).         different meanings (see below).
3132    
3133       Absolute and relative back references
3134    
3135           The sequence \g followed by an unsigned or a negative  number,  option-
3136           ally  enclosed  in braces, is an absolute or relative back reference. A
3137           named back reference can be coded as \g{name}. Back references are dis-
3138           cussed later, following the discussion of parenthesized subpatterns.
3139    
3140     Generic character types     Generic character types
3141    
3142         The third use of backslash is for specifying generic  character  types.         Another use of backslash is for specifying generic character types. The
3143         The following are always recognized:         following are always recognized:
3144    
3145           \d     any decimal digit           \d     any decimal digit
3146           \D     any character that is not a decimal digit           \D     any character that is not a decimal digit
3147             \h     any horizontal whitespace character
3148             \H     any character that is not a horizontal whitespace character
3149           \s     any whitespace character           \s     any whitespace character
3150           \S     any character that is not a whitespace character           \S     any character that is not a whitespace character
3151             \v     any vertical whitespace character
3152             \V     any character that is not a vertical whitespace character
3153           \w     any "word" character           \w     any "word" character
3154           \W     any "non-word" character           \W     any "non-word" character
3155    
3156         Each pair of escape sequences partitions the complete set of characters         Each pair of escape sequences partitions the complete set of characters
3157         into two disjoint sets. Any given character matches one, and only  one,         into  two disjoint sets. Any given character matches one, and only one,
3158         of each pair.         of each pair.
3159    
3160         These character type sequences can appear both inside and outside char-         These character type sequences can appear both inside and outside char-
3161         acter classes. They each match one character of the  appropriate  type.         acter  classes.  They each match one character of the appropriate type.
3162         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
3163         of them fail, since there is no character to match.         of them fail, since there is no character to match.
3164    
3165         For compatibility with Perl, \s does not match the VT  character  (code         For  compatibility  with Perl, \s does not match the VT character (code
3166         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
3167         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
3168           "use locale;" is included in a Perl script, \s may match the VT charac-
3169           ter. In PCRE, it never does.
3170    
3171           In  UTF-8 mode, characters with values greater than 128 never match \d,
3172           \s, or \w, and always match \D, \S, and \W. This is true even when Uni-
3173           code  character  property  support is available. These sequences retain
3174           their original meanings from before UTF-8 support was available, mainly
3175           for efficiency reasons.
3176    
3177           The sequences \h, \H, \v, and \V are Perl 5.10 features. In contrast to
3178           the other sequences, these do match certain high-valued  codepoints  in
3179           UTF-8 mode.  The horizontal space characters are:
3180    
3181             U+0009     Horizontal tab
3182             U+0020     Space
3183             U+00A0     Non-break space
3184             U+1680     Ogham space mark
3185             U+180E     Mongolian vowel separator
3186             U+2000     En quad
3187             U+2001     Em quad
3188             U+2002     En space
3189             U+2003     Em space
3190             U+2004     Three-per-em space
3191             U+2005     Four-per-em space
3192             U+2006     Six-per-em space
3193             U+2007     Figure space
3194             U+2008     Punctuation space
3195             U+2009     Thin space
3196             U+200A     Hair space
3197             U+202F     Narrow no-break space
3198             U+205F     Medium mathematical space
3199             U+3000     Ideographic space
3200    
3201           The vertical space characters are:
3202    
3203             U+000A     Linefeed
3204             U+000B     Vertical tab
3205             U+000C     Formfeed
3206             U+000D     Carriage return
3207             U+0085     Next line
3208             U+2028     Line separator
3209             U+2029     Paragraph separator
3210    
3211         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
3212         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-
3213         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-
3214         specific  matching is taking place (see "Locale support" in the pcreapi         specific matching is taking place (see "Locale support" in the  pcreapi
3215         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
3216         codes  greater  than  128  are used for accented letters, and these are         systems, or "french" in Windows, some character codes greater than  128
3217         matched by \w.         are  used for accented letters, and these are matched by \w. The use of
3218           locales with Unicode is discouraged.
3219    
3220       Newline sequences
3221    
3222           Outside a character class, by default, the escape sequence  \R  matches
3223           any Unicode newline sequence. This is a Perl 5.10 feature. In non-UTF-8
3224           mode \R is equivalent to the following:
3225    
3226             (?>\r\n|\n|\x0b|\f|\r|\x85)
3227    
3228           This is an example of an "atomic group", details  of  which  are  given
3229           below.  This particular group matches either the two-character sequence
3230           CR followed by LF, or  one  of  the  single  characters  LF  (linefeed,
3231           U+000A), VT (vertical tab, U+000B), FF (formfeed, U+000C), CR (carriage
3232           return, U+000D), or NEL (next line, U+0085). The two-character sequence
3233           is treated as a single unit that cannot be split.
3234    
3235           In  UTF-8  mode, two additional characters whose codepoints are greater
3236           than 255 are added: LS (line separator, U+2028) and PS (paragraph sepa-
3237           rator,  U+2029).   Unicode character property support is not needed for
3238           these characters to be recognized.
3239    
3240           It is possible to restrict \R to match only CR, LF, or CRLF (instead of
3241           the  complete  set  of  Unicode  line  endings)  by  setting the option
3242           PCRE_BSR_ANYCRLF either at compile time or when the pattern is matched.
3243           (BSR is an abbrevation for "backslash R".) This can be made the default
3244           when PCRE is built; if this is the case, the  other  behaviour  can  be
3245           requested  via  the  PCRE_BSR_UNICODE  option.   It is also possible to
3246           specify these settings by starting a pattern string  with  one  of  the
3247           following sequences:
3248    
3249             (*BSR_ANYCRLF)   CR, LF, or CRLF only
3250             (*BSR_UNICODE)   any Unicode newline sequence
3251    
3252           These override the default and the options given to pcre_compile(), but
3253           they can be overridden by options given to pcre_exec(). Note that these
3254           special settings, which are not Perl-compatible, are recognized only at
3255           the very start of a pattern, and that they must be in  upper  case.  If
3256           more  than  one  of  them is present, the last one is used. They can be
3257           combined with a change of newline convention, for  example,  a  pattern
3258           can start with:
3259    
3260         In UTF-8 mode, characters with values greater than 128 never match  \d,           (*ANY)(*BSR_ANYCRLF)
3261         \s, or \w, and always match \D, \S, and \W. This is true even when Uni-  
3262         code character property support is available.         Inside a character class, \R matches the letter "R".
3263    
3264     Unicode character properties     Unicode character properties
3265    
3266         When PCRE is built with Unicode character property support, three addi-         When PCRE is built with Unicode character property support, three addi-
3267         tional  escape sequences to match generic character types are available         tional escape sequences that match characters with specific  properties
3268         when UTF-8 mode is selected. They are:         are  available.   When not in UTF-8 mode, these sequences are of course
3269           limited to testing characters whose codepoints are less than  256,  but
3270          \p{xx}   a character with the xx property         they do work in this mode.  The extra escape sequences are:
3271          \P{xx}   a character without the xx property  
3272          \X       an extended Unicode sequence           \p{xx}   a character with the xx property
3273             \P{xx}   a character without the xx property
3274         The property names represented by xx above are limited to  the  Unicode           \X       an extended Unicode sequence
3275         general  category properties. Each character has exactly one such prop-  
3276         erty, specified by a two-letter abbreviation.  For  compatibility  with         The  property  names represented by xx above are limited to the Unicode
3277         Perl,  negation  can be specified by including a circumflex between the         script names, the general category properties, and "Any", which matches
3278         opening brace and the property name. For example, \p{^Lu} is  the  same         any character (including newline). Other properties such as "InMusical-
3279         as \P{Lu}.         Symbols" are not currently supported by PCRE. Note  that  \P{Any}  does
3280           not match any characters, so always causes a match failure.
3281         If  only  one  letter  is  specified with \p or \P, it includes all the  
3282         properties that start with that letter. In this case, in the absence of         Sets of Unicode characters are defined as belonging to certain scripts.
3283         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.
3284         two examples have the same effect:         For example:
3285    
3286             \p{Greek}
3287             \P{Han}
3288    
3289           Those  that are not part of an identified script are lumped together as
3290           "Common". The current list of scripts is:
3291    
3292           Arabic,  Armenian,  Balinese,  Bengali,  Bopomofo,  Braille,  Buginese,
3293           Buhid,   Canadian_Aboriginal,   Cherokee,  Common,  Coptic,  Cuneiform,
3294           Cypriot, Cyrillic, Deseret, Devanagari, Ethiopic, Georgian, Glagolitic,
3295           Gothic,  Greek, Gujarati, Gurmukhi, Han, Hangul, Hanunoo, Hebrew, Hira-
3296           gana, Inherited, Kannada,  Katakana,  Kharoshthi,  Khmer,  Lao,  Latin,
3297           Limbu,  Linear_B,  Malayalam,  Mongolian,  Myanmar,  New_Tai_Lue,  Nko,
3298           Ogham, Old_Italic, Old_Persian, Oriya, Osmanya,  Phags_Pa,  Phoenician,
3299           Runic,  Shavian,  Sinhala,  Syloti_Nagri,  Syriac,  Tagalog,  Tagbanwa,
3300           Tai_Le, Tamil, Telugu, Thaana, Thai, Tibetan, Tifinagh, Ugaritic, Yi.
3301    
3302           Each character has exactly one general category property, specified  by
3303           a two-letter abbreviation. For compatibility with Perl, negation can be
3304           specified by including a circumflex between the opening brace  and  the
3305           property name. For example, \p{^Lu} is the same as \P{Lu}.
3306    
3307           If only one letter is specified with \p or \P, it includes all the gen-
3308           eral category properties that start with that letter. In this case,  in
3309           the  absence of negation, the curly brackets in the escape sequence are
3310           optional; these two examples have the same effect:
3311    
3312           \p{L}           \p{L}
3313           \pL           \pL
3314    
3315         The following property codes are supported:         The following general category property codes are supported:
3316    
3317           C     Other           C     Other
3318           Cc    Control           Cc    Control
# Line 2626  BACKSLASH Line 3358  BACKSLASH
3358           Zp    Paragraph separator           Zp    Paragraph separator
3359           Zs    Space separator           Zs    Space separator
3360    
3361         Extended properties such as "Greek" or "InMusicalSymbols" are not  sup-         The special property L& is also supported: it matches a character  that
3362         ported by PCRE.         has  the  Lu,  Ll, or Lt property, in other words, a letter that is not
3363           classified as a modifier or "other".
3364    
3365           The Cs (Surrogate) property applies only to  characters  in  the  range
3366           U+D800  to  U+DFFF. Such characters are not valid in UTF-8 strings (see
3367           RFC 3629) and so cannot be tested by PCRE, unless UTF-8 validity check-
3368           ing  has  been  turned off (see the discussion of PCRE_NO_UTF8_CHECK in
3369           the pcreapi page).
3370    
3371           The long synonyms for these properties  that  Perl  supports  (such  as
3372           \p{Letter})  are  not  supported by PCRE, nor is it permitted to prefix
3373           any of these properties with "Is".
3374    
3375           No character that is in the Unicode table has the Cn (unassigned) prop-
3376           erty.  Instead, this property is assumed for any code point that is not
3377           in the Unicode table.
3378    
3379         Specifying  caseless  matching  does not affect these escape sequences.         Specifying caseless matching does not affect  these  escape  sequences.
3380         For example, \p{Lu} always matches only upper case letters.         For example, \p{Lu} always matches only upper case letters.
3381    
3382         The \X escape matches any number of Unicode  characters  that  form  an         The  \X  escape  matches  any number of Unicode characters that form an
3383         extended Unicode sequence. \X is equivalent to         extended Unicode sequence. \X is equivalent to
3384    
3385           (?>\PM\pM*)           (?>\PM\pM*)
3386    
3387         That  is,  it matches a character without the "mark" property, followed         That is, it matches a character without the "mark"  property,  followed
3388         by zero or more characters with the "mark"  property,  and  treats  the         by  zero  or  more  characters with the "mark" property, and treats the
3389         sequence  as  an  atomic group (see below).  Characters with the "mark"         sequence as an atomic group (see below).  Characters  with  the  "mark"
3390         property are typically accents that affect the preceding character.         property  are  typically  accents  that affect the preceding character.
3391           None of them have codepoints less than 256, so  in  non-UTF-8  mode  \X
3392           matches any one character.
3393    
3394         Matching characters by Unicode property is not fast, because  PCRE  has         Matching  characters  by Unicode property is not fast, because PCRE has
3395         to  search  a  structure  that  contains data for over fifteen thousand         to search a structure that contains  data  for  over  fifteen  thousand
3396         characters. That is why the traditional escape sequences such as \d and         characters. That is why the traditional escape sequences such as \d and
3397         \w do not use Unicode properties in PCRE.         \w do not use Unicode properties in PCRE.
3398    
3399       Resetting the match start
3400    
3401           The escape sequence \K, which is a Perl 5.10 feature, causes any previ-
3402           ously  matched  characters  not  to  be  included  in the final matched
3403           sequence. For example, the pattern:
3404    
3405             foo\Kbar
3406    
3407           matches "foobar", but reports that it has matched "bar".  This  feature
3408           is  similar  to  a lookbehind assertion (described below).  However, in
3409           this case, the part of the subject before the real match does not  have
3410           to  be of fixed length, as lookbehind assertions do. The use of \K does
3411           not interfere with the setting of captured  substrings.   For  example,
3412           when the pattern
3413    
3414             (foo)\Kbar
3415    
3416           matches "foobar", the first substring is still set to "foo".
3417    
3418     Simple assertions     Simple assertions
3419    
3420         The fourth use of backslash is for certain simple assertions. An asser-         The  final use of backslash is for certain simple assertions. An asser-
3421         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
3422         a  match, without consuming any characters from the subject string. The         a  match, without consuming any characters from the subject string. The
3423         use of subpatterns for more complicated assertions is described  below.         use of subpatterns for more complicated assertions is described  below.
# Line 2657  BACKSLASH Line 3425  BACKSLASH
3425    
3426           \b     matches at a word boundary           \b     matches at a word boundary
3427           \B     matches when not at a word boundary           \B     matches when not at a word boundary
3428           \A     matches at start of subject           \A     matches at the start of the subject
3429           \Z     matches at end of subject or before newline at end           \Z     matches at the end of the subject
3430           \z     matches at end of subject                   also matches before a newline at the end of the subject
3431           \G     matches at first matching position in subject           \z     matches only at the end of the subject
3432             \G     matches at the first matching position in the subject
3433    
3434         These  assertions may not appear in character classes (but note that \b         These  assertions may not appear in character classes (but note that \b
3435         has a different meaning, namely the backspace character, inside a char-         has a different meaning, namely the backspace character, inside a char-
# Line 2680  BACKSLASH Line 3449  BACKSLASH
3449         However, if the startoffset argument of pcre_exec() is non-zero,  indi-         However, if the startoffset argument of pcre_exec() is non-zero,  indi-
3450         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
3451         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
3452         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
3453         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.
3454         the end.  
3455           The \G assertion is true only when the current matching position is  at
3456         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
3457         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
3458         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-  
3459         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-
3460         mentation where \G can be useful.         mentation where \G can be useful.
3461    
3462         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
3463         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
3464         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
3465         previously  matched  string was empty. Because PCRE does just one match         previously matched string was empty. Because PCRE does just  one  match
3466         at a time, it cannot reproduce this behaviour.         at a time, it cannot reproduce this behaviour.
3467    
3468         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
3469         anchored to the starting match position, and the "anchored" flag is set         anchored to the starting match position, and the "anchored" flag is set
3470         in the compiled regular expression.         in the compiled regular expression.
3471    
# Line 2705  BACKSLASH Line 3473  BACKSLASH
3473  CIRCUMFLEX AND DOLLAR  CIRCUMFLEX AND DOLLAR
3474    
3475         Outside a character class, in the default matching mode, the circumflex         Outside a character class, in the default matching mode, the circumflex
3476         character  is  an  assertion  that is true only if the current matching         character is an assertion that is true only  if  the  current  matching
3477         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-
3478         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
3479         PCRE_MULTILINE option is unset. Inside a  character  class,  circumflex         PCRE_MULTILINE  option  is  unset. Inside a character class, circumflex
3480         has an entirely different meaning (see below).         has an entirely different meaning (see below).
3481    
3482         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
3483         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
3484         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
3485         branch. If all possible alternatives start with a circumflex, that  is,         branch.  If all possible alternatives start with a circumflex, that is,
3486         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-
3487         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
3488         constructs that can cause a pattern to be anchored.)         constructs that can cause a pattern to be anchored.)
3489    
3490         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
3491         matching point is at the end of  the  subject  string,  or  immediately         matching  point  is  at  the  end of the subject string, or immediately
3492         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
3493         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
3494         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
3495         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.  
3496    
3497         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
3498         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
3499         compile time. This does not affect the \Z assertion.         compile time. This does not affect the \Z assertion.
3500    
3501         The meanings of the circumflex and dollar characters are changed if the         The meanings of the circumflex and dollar characters are changed if the
3502         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
3503         ately  after  and  immediately  before  an  internal newline character,         matches  immediately after internal newlines as well as at the start of
3504         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
3505         ject  string.  For  example,  the  pattern  /^abc$/ matches the subject         string.  A dollar matches before any newlines in the string, as well as
3506         string "def\nabc" (where \n represents a newline character)  in  multi-         at the very end, when PCRE_MULTILINE is set. When newline is  specified
3507         line mode, but not otherwise.  Consequently, patterns that are anchored         as  the  two-character  sequence CRLF, isolated CR and LF characters do
3508         in single line mode because all branches start with ^ are not  anchored         not indicate newlines.
3509         in  multiline  mode,  and  a  match for circumflex is possible when the  
3510         startoffset  argument  of  pcre_exec()  is  non-zero.   The   PCRE_DOL-         For example, the pattern /^abc$/ matches the subject string  "def\nabc"
3511         LAR_ENDONLY option is ignored if PCRE_MULTILINE is set.         (where  \n  represents a newline) in multiline mode, but not otherwise.
3512           Consequently, patterns that are anchored in single  line  mode  because
3513         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
3514         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
3515         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
3516         not.         PCRE_MULTILINE is set.
3517    
3518           Note that the sequences \A, \Z, and \z can be used to match  the  start
3519           and  end of the subject in both modes, and if all branches of a pattern
3520           start with \A it is always anchored, whether or not  PCRE_MULTILINE  is
3521           set.
3522    
3523    
3524  FULL STOP (PERIOD, DOT)  FULL STOP (PERIOD, DOT)
3525    
3526         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-
3527         ter  in  the  subject,  including a non-printing character, but not (by         ter in the subject string except (by default) a character  that  signi-
3528         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
3529         which might be more than one byte long, except (by default) newline. If         more than one byte long.
3530         the PCRE_DOTALL option is set, dots match newlines as  well.  The  han-  
3531         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
3532         dollar, the only relationship being  that  they  both  involve  newline         that  character; when the two-character sequence CRLF is used, dot does
3533         characters. Dot has no special meaning in a character class.         not match CR if it is immediately followed  by  LF,  but  otherwise  it
3534           matches  all characters (including isolated CRs and LFs). When any Uni-
3535           code line endings are being recognized, dot does not match CR or LF  or
3536           any of the other line ending characters.
3537    
3538           The  behaviour  of  dot  with regard to newlines can be changed. If the
3539           PCRE_DOTALL option is set, a dot matches  any  one  character,  without
3540           exception. If the two-character sequence CRLF is present in the subject
3541           string, it takes two dots to match it.
3542    
3543           The handling of dot is entirely independent of the handling of  circum-
3544           flex  and  dollar,  the  only relationship being that they both involve
3545           newlines. Dot has no special meaning in a character class.
3546    
3547    
3548  MATCHING A SINGLE BYTE  MATCHING A SINGLE BYTE
3549    
3550         Outside a character class, the escape sequence \C matches any one byte,         Outside a character class, the escape sequence \C matches any one byte,
3551         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
3552         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
3553         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-
3554         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-
3555         this reason, the \C escape sequence is best avoided.         formed  UTF-8  string.  For this reason, the \C escape sequence is best
3556           avoided.
3557    
3558         PCRE does not allow \C to appear in  lookbehind  assertions  (described         PCRE does not allow \C to appear in  lookbehind  assertions  (described
3559         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 2815  SQUARE BRACKETS AND CHARACTER CLASSES Line 3600  SQUARE BRACKETS AND CHARACTER CLASSES
3600         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
3601         support.         support.
3602    
3603         The newline character is never treated in any special way in  character         Characters that might indicate line breaks are  never  treated  in  any
3604         classes,  whatever  the  setting  of  the PCRE_DOTALL or PCRE_MULTILINE         special  way  when  matching  character  classes,  whatever line-ending
3605         options is. A class such as [^a] will always match a newline.         sequence is in  use,  and  whatever  setting  of  the  PCRE_DOTALL  and
3606           PCRE_MULTILINE options is used. A class such as [^a] always matches one
3607           of these characters.
3608    
3609         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-
3610         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 2843  SQUARE BRACKETS AND CHARACTER CLASSES Line 3630  SQUARE BRACKETS AND CHARACTER CLASSES
3630         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,
3631         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
3632         to  [][\\^_`wxyzabc],  matched  caselessly,  and  in non-UTF-8 mode, if         to  [][\\^_`wxyzabc],  matched  caselessly,  and  in non-UTF-8 mode, if
3633         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
3634         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
3635         concept of case for characters with values greater than 128  only  when         concept of case for characters with values greater than 128  only  when
3636         it is compiled with Unicode property support.         it is compiled with Unicode property support.
# Line 2918  VERTICAL BAR Line 3705  VERTICAL BAR
3705    
3706         matches  either "gilbert" or "sullivan". Any number of alternatives may         matches  either "gilbert" or "sullivan". Any number of alternatives may
3707         appear, and an empty  alternative  is  permitted  (matching  the  empty         appear, and an empty  alternative  is  permitted  (matching  the  empty
3708         string).   The  matching  process  tries each alternative in turn, from         string). The matching process tries each alternative in turn, from left
3709         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
3710         tives  are within a subpattern (defined below), "succeeds" means match-         are  within a subpattern (defined below), "succeeds" means matching the
3711         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.  
3712    
3713    
3714  INTERNAL OPTION SETTING  INTERNAL OPTION SETTING
3715    
3716         The  settings  of  the  PCRE_CASELESS, PCRE_MULTILINE, PCRE_DOTALL, and         The  settings  of  the  PCRE_CASELESS, PCRE_MULTILINE, PCRE_DOTALL, and
3717         PCRE_EXTENDED options can be changed  from  within  the  pattern  by  a         PCRE_EXTENDED options (which are Perl-compatible) can be  changed  from
3718         sequence  of  Perl  option  letters  enclosed between "(?" and ")". The         within  the  pattern  by  a  sequence  of  Perl option letters enclosed
3719         option letters are         between "(?" and ")".  The option letters are
3720    
3721           i  for PCRE_CASELESS           i  for PCRE_CASELESS
3722           m  for PCRE_MULTILINE           m  for PCRE_MULTILINE
# Line 2944  INTERNAL OPTION SETTING Line 3730  INTERNAL OPTION SETTING
3730         is also permitted. If a  letter  appears  both  before  and  after  the         is also permitted. If a  letter  appears  both  before  and  after  the
3731         hyphen, the option is unset.         hyphen, the option is unset.
3732    
3733           The  PCRE-specific options PCRE_DUPNAMES, PCRE_UNGREEDY, and PCRE_EXTRA
3734           can be changed in the same way as the Perl-compatible options by  using
3735           the characters J, U and X respectively.
3736    
3737         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-
3738         tern parentheses), the change applies to the remainder of  the  pattern         tern parentheses), the change applies to the remainder of  the  pattern
3739         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,
3740         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
3741         in data extracted by the pcre_fullinfo() function).         in data extracted by the pcre_fullinfo() function).
3742    
3743         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
3744         rent pattern that follows it, so         subpatterns) affects only that part of the current pattern that follows
3745           it, so
3746    
3747           (a(?i)b)c           (a(?i)b)c
3748    
3749         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
3750         used).   By  this means, options can be made to have different settings         used).  By this means, options can be made to have  different  settings
3751         in different parts of the pattern. Any changes made in one  alternative         in  different parts of the pattern. Any changes made in one alternative
3752         do  carry  on  into subsequent branches within the same subpattern. For         do carry on into subsequent branches within the  same  subpattern.  For
3753         example,         example,
3754    
3755           (a(?i)b|c)           (a(?i)b|c)
3756    
3757         matches "ab", "aB", "c", and "C", even though  when  matching  "C"  the         matches  "ab",  "aB",  "c",  and "C", even though when matching "C" the
3758         first  branch  is  abandoned before the option setting. This is because         first branch is abandoned before the option setting.  This  is  because
3759         the effects of option settings happen at compile time. There  would  be         the  effects  of option settings happen at compile time. There would be
3760         some very weird behaviour otherwise.         some very weird behaviour otherwise.
3761    
3762         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
3763         in the same way as the Perl-compatible options by using the  characters         application  when  the  compile  or match functions are called. In some
3764         U  and X respectively. The (?X) flag setting is special in that it must         cases the pattern can contain special  leading  sequences  to  override
3765         always occur earlier in the pattern than any of the additional features         what  the  application  has set or what has been defaulted. Details are
3766         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.  
3767    
3768    
3769  SUBPATTERNS  SUBPATTERNS
# Line 2986  SUBPATTERNS Line 3776  SUBPATTERNS
3776           cat(aract|erpillar|)           cat(aract|erpillar|)
3777    
3778         matches  one  of the words "cat", "cataract", or "caterpillar". Without         matches  one  of the words "cat", "cataract", or "caterpillar". Without
3779         the parentheses, it would match "cataract",  "erpillar"  or  the  empty         the parentheses, it would match  "cataract",  "erpillar"  or  an  empty
3780         string.         string.
3781    
3782         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 3015  SUBPATTERNS Line 3805  SUBPATTERNS
3805           the ((?:red|white) (king|queen))           the ((?:red|white) (king|queen))
3806    
3807         the captured substrings are "white queen" and "queen", and are numbered         the captured substrings are "white queen" and "queen", and are numbered
3808         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.  
3809    
3810         As  a  convenient shorthand, if any option settings are required at the         As  a  convenient shorthand, if any option settings are required at the
3811