/[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 123 by ph10, Mon Mar 12 15:19:06 2007 UTC revision 656 by ph10, Sat Aug 13 12:27:51 2011 UTC
# Line 2  Line 2 
2  This file contains a concatenation of the PCRE man pages, converted to plain  This file contains a concatenation of the PCRE man pages, converted to plain
3  text format for ease of searching with a text editor, or for use on systems  text format for ease of searching with a text editor, or for use on systems
4  that do not have a man page processor. The small individual files that give  that do not have a man page processor. The small individual files that give
5  synopses of each function in the library have not been included. There are  synopses of each function in the library have not been included. Neither has
6  separate text files for the pcregrep and pcretest commands.  the pcredemo program. There are separate text files for the pcregrep and
7    pcretest commands.
8  -----------------------------------------------------------------------------  -----------------------------------------------------------------------------
9    
10    
# Line 18  INTRODUCTION Line 19  INTRODUCTION
19    
20         The  PCRE  library is a set of functions that implement regular expres-         The  PCRE  library is a set of functions that implement regular expres-
21         sion pattern matching using the same syntax and semantics as Perl, with         sion pattern matching using the same syntax and semantics as Perl, with
22         just  a  few differences. (Certain features that appeared in Python and         just  a few differences. Some features that appeared in Python and PCRE
23         PCRE before they appeared in Perl are also available using  the  Python         before they appeared in Perl are also available using the  Python  syn-
24         syntax.)         tax,  there  is  some  support for one or two .NET and Oniguruma syntax
25           items, and there is an option for requesting some  minor  changes  that
26         The  current  implementation of PCRE (release 7.x) corresponds approxi-         give better JavaScript compatibility.
27         mately with Perl 5.10, including support for UTF-8 encoded strings  and  
28         Unicode general category properties. However, UTF-8 and Unicode support         The  current implementation of PCRE corresponds approximately with Perl
29         has to be explicitly enabled; it is not the default. The Unicode tables         5.12, including support for UTF-8 encoded strings and  Unicode  general
30         correspond to Unicode release 5.0.0.         category  properties.  However,  UTF-8  and  Unicode  support has to be
31           explicitly enabled; it is not the default. The  Unicode  tables  corre-
32           spond to Unicode release 6.0.0.
33    
34         In  addition to the Perl-compatible matching function, PCRE contains an         In  addition to the Perl-compatible matching function, PCRE contains an
35         alternative matching function that matches the same  compiled  patterns         alternative function that matches the same compiled patterns in a  dif-
36         in  a different way. In certain circumstances, the alternative function         ferent way. In certain circumstances, the alternative function has some
37         has some advantages. For a discussion of the two  matching  algorithms,         advantages.  For a discussion of the two matching algorithms,  see  the
38         see the pcrematching page.         pcrematching page.
39    
40         PCRE  is  written  in C and released as a C library. A number of people         PCRE  is  written  in C and released as a C library. A number of people
41         have written wrappers and interfaces of various kinds.  In  particular,         have written wrappers and interfaces of various kinds.  In  particular,
# Line 45  INTRODUCTION Line 48  INTRODUCTION
48    
49         Details of exactly which Perl regular expression features are  and  are         Details of exactly which Perl regular expression features are  and  are
50         not supported by PCRE are given in separate documents. See the pcrepat-         not supported by PCRE are given in separate documents. See the pcrepat-
51         tern and pcrecompat pages.         tern and pcrecompat pages. There is a syntax summary in the  pcresyntax
52           page.
53    
54         Some features of PCRE can be included, excluded, or  changed  when  the         Some  features  of  PCRE can be included, excluded, or changed when the
55         library  is  built.  The pcre_config() function makes it possible for a         library is built. The pcre_config() function makes it  possible  for  a
56         client to discover which features are  available.  The  features  them-         client  to  discover  which  features are available. The features them-
57         selves  are described in the pcrebuild page. Documentation about build-         selves are described in the pcrebuild page. Documentation about  build-
58         ing PCRE for various operating systems can be found in the README  file         ing  PCRE  for various operating systems can be found in the README and
59         in the source distribution.         NON-UNIX-USE files in the source distribution.
60    
61         The  library  contains  a number of undocumented internal functions and         The library contains a number of undocumented  internal  functions  and
62         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
63         functions,  but  which  are  not  intended for use by external callers.         functions, but which are not intended  for  use  by  external  callers.
64         Their names all begin with "_pcre_", which hopefully will  not  provoke         Their  names  all begin with "_pcre_", which hopefully will not provoke
65         any name clashes. In some environments, it is possible to control which         any name clashes. In some environments, it is possible to control which
66         external symbols are exported when a shared library is  built,  and  in         external  symbols  are  exported when a shared library is built, and in
67         these cases the undocumented symbols are not exported.         these cases the undocumented symbols are not exported.
68    
69    
70  USER DOCUMENTATION  USER DOCUMENTATION
71    
72         The  user  documentation  for PCRE comprises a number of different sec-         The user documentation for PCRE comprises a number  of  different  sec-
73         tions. In the "man" format, each of these is a separate "man page".  In         tions.  In the "man" format, each of these is a separate "man page". In
74         the  HTML  format, each is a separate page, linked from the index page.         the HTML format, each is a separate page, linked from the  index  page.
75         In the plain text format, all the sections are concatenated,  for  ease         In  the  plain  text format, all the sections, except the pcredemo sec-
76         of searching. The sections are as follows:         tion, are concatenated, for ease of searching. The sections are as fol-
77           lows:
78    
79           pcre              this document           pcre              this document
80             pcre-config       show PCRE installation configuration information
81           pcreapi           details of PCRE's native C API           pcreapi           details of PCRE's native C API
82           pcrebuild         options for building PCRE           pcrebuild         options for building PCRE
83           pcrecallout       details of the callout feature           pcrecallout       details of the callout feature
84           pcrecompat        discussion of Perl compatibility           pcrecompat        discussion of Perl compatibility
85           pcrecpp           details of the C++ wrapper           pcrecpp           details of the C++ wrapper
86             pcredemo          a demonstration C program that uses PCRE
87           pcregrep          description of the pcregrep command           pcregrep          description of the pcregrep command
88           pcrematching      discussion of the two matching algorithms           pcrematching      discussion of the two matching algorithms
89           pcrepartial       details of the partial matching facility           pcrepartial       details of the partial matching facility
# Line 85  USER DOCUMENTATION Line 92  USER DOCUMENTATION
92           pcreperform       discussion of performance issues           pcreperform       discussion of performance issues
93           pcreposix         the POSIX-compatible C API           pcreposix         the POSIX-compatible C API
94           pcreprecompile    details of saving and re-using precompiled patterns           pcreprecompile    details of saving and re-using precompiled patterns
95           pcresample        discussion of the sample program           pcresample        discussion of the pcredemo program
96           pcrestack         discussion of stack usage           pcrestack         discussion of stack usage
97             pcresyntax        quick syntax reference
98           pcretest          description of the pcretest testing command           pcretest          description of the pcretest testing command
99    
100         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
101         each C library function, listing its arguments and results.         each C library function, listing its arguments and results.
102    
103    
104  LIMITATIONS  LIMITATIONS
105    
106         There  are some size limitations in PCRE but it is hoped that they will         There are some size limitations in PCRE but it is hoped that they  will
107         never in practice be relevant.         never in practice be relevant.
108    
109         The maximum length of a compiled pattern is 65539 (sic) bytes  if  PCRE         The  maximum  length of a compiled pattern is 65539 (sic) bytes if PCRE
110         is compiled with the default internal linkage size of 2. If you want to         is compiled with the default internal linkage size of 2. If you want to
111         process regular expressions that are truly enormous,  you  can  compile         process  regular  expressions  that are truly enormous, you can compile
112         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
113         the source distribution and the pcrebuild documentation  for  details).         the  source  distribution and the pcrebuild documentation for details).
114         In  these  cases the limit is substantially larger.  However, the speed         In these cases the limit is substantially larger.  However,  the  speed
115         of execution is slower.         of execution is slower.
116    
117         All values in repeating quantifiers must be less than 65536. The  maxi-         All values in repeating quantifiers must be less than 65536.
        mum  compiled  length  of  subpattern  with an explicit repeat count is  
        30000 bytes. The maximum number of capturing subpatterns is 65535.  
118    
119         There is no limit to the number of parenthesized subpatterns, but there         There is no limit to the number of parenthesized subpatterns, but there
120         can be no more than 65535 capturing subpatterns.         can be no more than 65535 capturing subpatterns.
# Line 116  LIMITATIONS Line 122  LIMITATIONS
122         The maximum length of name for a named subpattern is 32 characters, and         The maximum length of name for a named subpattern is 32 characters, and
123         the maximum number of named subpatterns is 10000.         the maximum number of named subpatterns is 10000.
124    
125         The maximum length of a subject string is the largest  positive  number         The  maximum  length of a subject string is the largest positive number
126         that  an integer variable can hold. However, when using the traditional         that an integer variable can hold. However, when using the  traditional
127         matching function, PCRE uses recursion to handle subpatterns and indef-         matching function, PCRE uses recursion to handle subpatterns and indef-
128         inite  repetition.  This means that the available stack space may limit         inite repetition.  This means that the available stack space may  limit
129         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.
130         For a discussion of stack issues, see the pcrestack documentation.         For a discussion of stack issues, see the pcrestack documentation.
131    
132    
133  UTF-8 AND UNICODE PROPERTY SUPPORT  UTF-8 AND UNICODE PROPERTY SUPPORT
134    
135         From  release  3.3,  PCRE  has  had  some support for character strings         From release 3.3, PCRE has  had  some  support  for  character  strings
136         encoded in the UTF-8 format. For release 4.0 this was greatly  extended         encoded  in the UTF-8 format. For release 4.0 this was greatly extended
137         to  cover  most common requirements, and in release 5.0 additional sup-         to cover most common requirements, and in release 5.0  additional  sup-
138         port for Unicode general category properties was added.         port for Unicode general category properties was added.
139    
140         In order process UTF-8 strings, you must build PCRE  to  include  UTF-8         In  order  process  UTF-8 strings, you must build PCRE to include UTF-8
141         support  in  the  code,  and, in addition, you must call pcre_compile()         support in the code, and, in addition,  you  must  call  pcre_compile()
142         with the PCRE_UTF8 option flag. When you do this, both the pattern  and         with  the  PCRE_UTF8  option  flag,  or the pattern must start with the
143         any  subject  strings  that are matched against it are treated as UTF-8         sequence (*UTF8). When either of these is the case,  both  the  pattern
144         strings instead of just strings of bytes.         and  any  subject  strings  that  are matched against it are treated as
145           UTF-8 strings instead of strings of 1-byte characters.
146    
147         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,
148         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
# Line 154  UTF-8 AND UNICODE PROPERTY SUPPORT Line 161  UTF-8 AND UNICODE PROPERTY SUPPORT
161         optionally be prefixed by "Is", for compatibility with Perl  5.6.  PCRE         optionally be prefixed by "Is", for compatibility with Perl  5.6.  PCRE
162         does not support this.         does not support this.
163    
164         The following comments apply when PCRE is running in UTF-8 mode:     Validity of UTF-8 strings
165    
166           When  you  set  the  PCRE_UTF8 flag, the strings passed as patterns and
167           subjects are (by default) checked for validity on entry to the relevant
168           functions.  From  release 7.3 of PCRE, the check is according the rules
169           of RFC 3629, which are themselves derived from the  Unicode  specifica-
170           tion.  Earlier  releases  of PCRE followed the rules of RFC 2279, which
171           allows the full range of 31-bit values (0 to 0x7FFFFFFF).  The  current
172           check allows only values in the range U+0 to U+10FFFF, excluding U+D800
173           to U+DFFF.
174    
175           The excluded code points are the "Low Surrogate Area"  of  Unicode,  of
176           which  the Unicode Standard says this: "The Low Surrogate Area does not
177           contain any  character  assignments,  consequently  no  character  code
178           charts or namelists are provided for this area. Surrogates are reserved
179           for use with UTF-16 and then must be used in pairs."  The  code  points
180           that  are  encoded  by  UTF-16  pairs are available as independent code
181           points in the UTF-8 encoding. (In  other  words,  the  whole  surrogate
182           thing is a fudge for UTF-16 which unfortunately messes up UTF-8.)
183    
184           If an invalid UTF-8 string is passed to PCRE, an error return is given.
185           At compile time, the only additional information is the offset  to  the
186           first byte of the failing character. The runtime functions (pcre_exec()
187           and pcre_dfa_exec()), pass back this information  as  well  as  a  more
188           detailed  reason  code if the caller has provided memory in which to do
189           this.
190    
191           In some situations, you may already know that your strings  are  valid,
192           and  therefore  want  to  skip these checks in order to improve perfor-
193           mance. If you set the PCRE_NO_UTF8_CHECK flag at compile time or at run
194           time,  PCRE  assumes  that  the pattern or subject it is given (respec-
195           tively) contains only valid UTF-8 codes. In  this  case,  it  does  not
196           diagnose an invalid UTF-8 string.
197    
198           If  you  pass  an  invalid UTF-8 string when PCRE_NO_UTF8_CHECK is set,
199           what happens depends on why the string is invalid. If the  string  con-
200           forms to the "old" definition of UTF-8 (RFC 2279), it is processed as a
201           string of characters in the range 0  to  0x7FFFFFFF.  In  other  words,
202           apart from the initial validity test, PCRE (when in UTF-8 mode) handles
203           strings according to the more liberal rules of RFC  2279.  However,  if
204           the  string does not even conform to RFC 2279, the result is undefined.
205           Your program may crash.
206    
207           If you want to process strings  of  values  in  the  full  range  0  to
208           0x7FFFFFFF,  encoded in a UTF-8-like manner as per the old RFC, you can
209           set PCRE_NO_UTF8_CHECK to bypass the more restrictive test. However, in
210           this situation, you will have to apply your own validity check.
211    
212         1.  When you set the PCRE_UTF8 flag, the strings passed as patterns and     General comments about UTF-8 mode
        subjects are checked for validity on entry to the  relevant  functions.  
        If an invalid UTF-8 string is passed, an error return is given. In some  
        situations, you may already know  that  your  strings  are  valid,  and  
        therefore want to skip these checks in order to improve performance. If  
        you set the PCRE_NO_UTF8_CHECK flag at compile time  or  at  run  time,  
        PCRE  assumes  that  the  pattern or subject it is given (respectively)  
        contains only valid UTF-8 codes. In this case, it does not diagnose  an  
        invalid  UTF-8 string. If you pass an invalid UTF-8 string to PCRE when  
        PCRE_NO_UTF8_CHECK is set, the results are undefined. Your program  may  
        crash.  
213    
214         2.  An  unbraced  hexadecimal  escape sequence (such as \xb3) matches a         1.  An  unbraced  hexadecimal  escape sequence (such as \xb3) matches a
215         two-byte UTF-8 character if the value is greater than 127.         two-byte UTF-8 character if the value is greater than 127.
216    
217         3. Octal numbers up to \777 are recognized, and  match  two-byte  UTF-8         2. Octal numbers up to \777 are recognized, and  match  two-byte  UTF-8
218         characters for values greater than \177.         characters for values greater than \177.
219    
220         4.  Repeat quantifiers apply to complete UTF-8 characters, not to indi-         3.  Repeat quantifiers apply to complete UTF-8 characters, not to indi-
221         vidual bytes, for example: \x{100}{3}.         vidual bytes, for example: \x{100}{3}.
222    
223         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-
224         gle byte.         gle byte.
225    
226         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
227         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
228         not available in the alternative matching function, pcre_dfa_exec().         not available in the alternative matching function, pcre_dfa_exec().
229    
230         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
231         test characters of any code value, but the characters that PCRE  recog-         test characters of any code value, but, by default, the characters that
232         nizes  as  digits,  spaces,  or  word characters remain the same set as         PCRE  recognizes  as digits, spaces, or word characters remain the same
233         before, all with values less than 256. This remains true even when PCRE         set as before, all with values less than 256. This  remains  true  even
234         includes  Unicode  property support, because to do otherwise would slow         when  PCRE  is built to include Unicode property support, because to do
235         down PCRE in many common cases. If you really want to test for a  wider         otherwise would slow down PCRE in many common cases. Note in particular
236         sense  of,  say,  "digit",  you must use Unicode property tests such as         that this applies to \b and \B, because they are defined in terms of \w
237         \p{Nd}.         and \W. If you really want to test for a wider sense of, say,  "digit",
238           you  can  use  explicit Unicode property tests such as \p{Nd}. Alterna-
239         8. Similarly, characters that match the POSIX named  character  classes         tively, if you set the PCRE_UCP option,  the  way  that  the  character
240         are all low-valued characters.         escapes  work  is changed so that Unicode properties are used to deter-
241           mine which characters match. There are more details in the  section  on
242         9.  Case-insensitive  matching  applies only to characters whose values         generic character types in the pcrepattern documentation.
243         are less than 128, unless PCRE is built with Unicode property  support.  
244         Even  when  Unicode  property support is available, PCRE still uses its         7.  Similarly,  characters that match the POSIX named character classes
245         own character tables when checking the case of  low-valued  characters,         are all low-valued characters, unless the PCRE_UCP option is set.
246         so  as not to degrade performance.  The Unicode property information is  
247         used only for characters with higher values. Even when Unicode property         8. However, the horizontal and  vertical  whitespace  matching  escapes
248         support is available, PCRE supports case-insensitive matching only when         (\h,  \H,  \v, and \V) do match all the appropriate Unicode characters,
249         there is a one-to-one mapping between a letter's  cases.  There  are  a         whether or not PCRE_UCP is set.
250         small  number  of  many-to-one  mappings in Unicode; these are not sup-  
251         ported by PCRE.         9. Case-insensitive matching applies only to  characters  whose  values
252           are  less than 128, unless PCRE is built with Unicode property support.
253           Even when Unicode property support is available, PCRE  still  uses  its
254           own  character  tables when checking the case of low-valued characters,
255           so as not to degrade performance.  The Unicode property information  is
256           used only for characters with higher values. Furthermore, PCRE supports
257           case-insensitive matching only  when  there  is  a  one-to-one  mapping
258           between  a letter's cases. There are a small number of many-to-one map-
259           pings in Unicode; these are not supported by PCRE.
260    
261    
262  AUTHOR  AUTHOR
# Line 215  AUTHOR Line 266  AUTHOR
266         Cambridge CB2 3QH, England.         Cambridge CB2 3QH, England.
267    
268         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,
269         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,
270         name, separated by a dot, at the domain ucs.cam.ac.uk.         followed by the two digits 10, at the domain cam.ac.uk.
271    
272    
273  REVISION  REVISION
274    
275         Last updated: 06 March 2007         Last updated: 07 May 2011
276         Copyright (c) 1997-2007 University of Cambridge.         Copyright (c) 1997-2011 University of Cambridge.
277  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
278    
279    
280  PCREBUILD(3)                                                      PCREBUILD(3)  PCREBUILD(3)                                                      PCREBUILD(3)
281    
282    
# Line 236  NAME Line 287  NAME
287  PCRE BUILD-TIME OPTIONS  PCRE BUILD-TIME OPTIONS
288    
289         This  document  describes  the  optional  features  of PCRE that can be         This  document  describes  the  optional  features  of PCRE that can be
290         selected when the library is compiled. They are all selected, or  dese-         selected when the library is compiled. It assumes use of the  configure
291         lected, by providing options to the configure script that is run before         script,  where the optional features are selected or deselected by pro-
292         the make command. The complete list of  options  for  configure  (which         viding options to configure before running the make  command.  However,
293         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
294         directory) can be obtained by running         environments using the GUI facility of cmake-gui if you are using CMake
295           instead of configure to build PCRE.
296    
297           There  is  a  lot more information about building PCRE in non-Unix-like
298           environments in the file called NON_UNIX_USE, which is part of the PCRE
299           distribution.  You  should consult this file as well as the README file
300           if you are building in a non-Unix-like environment.
301    
302           The complete list of options for configure (which includes the standard
303           ones  such  as  the  selection  of  the  installation directory) can be
304           obtained by running
305    
306           ./configure --help           ./configure --help
307    
308         The following sections describe certain options whose names begin  with         The following sections include  descriptions  of  options  whose  names
309         --enable  or  --disable. These settings specify changes to the defaults         begin with --enable or --disable. These settings specify changes to the
310         for the configure command. Because of the  way  that  configure  works,         defaults for the configure command. Because of the way  that  configure
311         --enable  and  --disable  always  come  in  pairs, so the complementary         works,  --enable  and --disable always come in pairs, so the complemen-
312         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
313         not described.         is not described.
314    
315    
316    BUILDING SHARED AND STATIC LIBRARIES
317    
318           The  PCRE building process uses libtool to build both shared and static
319           Unix libraries by default. You can suppress one of these by adding  one
320           of
321    
322             --disable-shared
323             --disable-static
324    
325           to the configure command, as required.
326    
327    
328  C++ SUPPORT  C++ SUPPORT
# Line 265  C++ SUPPORT Line 338  C++ SUPPORT
338    
339  UTF-8 SUPPORT  UTF-8 SUPPORT
340    
341         To build PCRE with support for UTF-8 character strings, add         To build PCRE with support for UTF-8 Unicode character strings, add
342    
343           --enable-utf8           --enable-utf8
344    
345         to  the  configure  command.  Of  itself, this does not make PCRE treat         to  the  configure  command.  Of  itself, this does not make PCRE treat
346         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
347         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()
348         function.         or pcre_compile2() functions.
349    
350           If you set --enable-utf8 when compiling in an EBCDIC environment,  PCRE
351           expects its input to be either ASCII or UTF-8 (depending on the runtime
352           option). It is not possible to support both EBCDIC and UTF-8  codes  in
353           the  same  version  of  the  library.  Consequently,  --enable-utf8 and
354           --enable-ebcdic are mutually exclusive.
355    
356    
357  UNICODE CHARACTER PROPERTY SUPPORT  UNICODE CHARACTER PROPERTY SUPPORT
# Line 288  UNICODE CHARACTER PROPERTY SUPPORT Line 367  UNICODE CHARACTER PROPERTY SUPPORT
367         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
368         not explicitly requested it.         not explicitly requested it.
369    
370         Including  Unicode  property  support  adds around 90K of tables to the         Including  Unicode  property  support  adds around 30K of tables to the
371         PCRE library, approximately doubling its size. Only the  general  cate-         PCRE library. Only the general category properties such as  Lu  and  Nd
372         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.  
373    
374    
375  CODE VALUE OF NEWLINE  CODE VALUE OF NEWLINE
376    
377         By default, PCRE interprets character 10 (linefeed, LF)  as  indicating         By  default,  PCRE interprets the linefeed (LF) character as indicating
378         the  end  of  a line. This is the normal newline character on Unix-like         the end of a line. This is the normal newline  character  on  Unix-like
379         systems. You can compile PCRE to use character 13 (carriage return, CR)         systems.  You  can compile PCRE to use carriage return (CR) instead, by
380         instead, by adding         adding
381    
382           --enable-newline-is-cr           --enable-newline-is-cr
383    
384         to  the  configure  command.  There  is  also  a --enable-newline-is-lf         to the  configure  command.  There  is  also  a  --enable-newline-is-lf
385         option, which explicitly specifies linefeed as the newline character.         option, which explicitly specifies linefeed as the newline character.
386    
387         Alternatively, you can specify that line endings are to be indicated by         Alternatively, you can specify that line endings are to be indicated by
# Line 313  CODE VALUE OF NEWLINE Line 391  CODE VALUE OF NEWLINE
391    
392         to the configure command. There is a fourth option, specified by         to the configure command. There is a fourth option, specified by
393    
394             --enable-newline-is-anycrlf
395    
396           which causes PCRE to recognize any of the three sequences  CR,  LF,  or
397           CRLF as indicating a line ending. Finally, a fifth option, specified by
398    
399           --enable-newline-is-any           --enable-newline-is-any
400    
401         which causes PCRE to recognize any Unicode newline sequence.         causes PCRE to recognize any Unicode newline sequence.
402    
403         Whatever  line  ending convention is selected when PCRE is built can be         Whatever  line  ending convention is selected when PCRE is built can be
404         overridden when the library functions are called. At build time  it  is         overridden when the library functions are called. At build time  it  is
405         conventional to use the standard for your operating system.         conventional to use the standard for your operating system.
406    
407    
408  BUILDING SHARED AND STATIC LIBRARIES  WHAT \R MATCHES
409    
410         The  PCRE building process uses libtool to build both shared and static         By  default,  the  sequence \R in a pattern matches any Unicode newline
411         Unix libraries by default. You can suppress one of these by adding  one         sequence, whatever has been selected as the line  ending  sequence.  If
412         of         you specify
413    
414           --disable-shared           --enable-bsr-anycrlf
          --disable-static  
415    
416         to the configure command, as required.         the  default  is changed so that \R matches only CR, LF, or CRLF. What-
417           ever is selected when PCRE is built can be overridden when the  library
418           functions are called.
419    
420    
421  POSIX MALLOC USAGE  POSIX MALLOC USAGE
# Line 357  HANDLING VERY LARGE PATTERNS Line 441  HANDLING VERY LARGE PATTERNS
441         nation metacharacter). By default, two-byte values are used  for  these         nation metacharacter). By default, two-byte values are used  for  these
442         offsets,  leading  to  a  maximum size for a compiled pattern of around         offsets,  leading  to  a  maximum size for a compiled pattern of around
443         64K. This is sufficient to handle all but the most  gigantic  patterns.         64K. This is sufficient to handle all but the most  gigantic  patterns.
444         Nevertheless,  some  people do want to process enormous patterns, so it         Nevertheless,  some  people do want to process truyl enormous patterns,
445         is possible to compile PCRE to use three-byte or four-byte  offsets  by         so it is possible to compile PCRE to use three-byte or  four-byte  off-
446         adding a setting such as         sets by adding a setting such as
447    
448           --with-link-size=3           --with-link-size=3
449    
# Line 367  HANDLING VERY LARGE PATTERNS Line 451  HANDLING VERY LARGE PATTERNS
451         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
452         additional bytes when handling them.         additional bytes when handling them.
453    
        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.  
   
454    
455  AVOIDING EXCESSIVE STACK USAGE  AVOIDING EXCESSIVE STACK USAGE
456    
457         When matching with the pcre_exec() function, PCRE implements backtrack-         When matching with the pcre_exec() function, PCRE implements backtrack-
458         ing  by  making recursive calls to an internal function called match().         ing by making recursive calls to an internal function  called  match().
459         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-
460         verely  limit  PCRE's operation. (The Unix environment does not usually         verely limit PCRE's operation. (The Unix environment does  not  usually
461         suffer from this problem, but it may sometimes be necessary to increase         suffer from this problem, but it may sometimes be necessary to increase
462         the  maximum  stack size.  There is a discussion in the pcrestack docu-         the maximum stack size.  There is a discussion in the  pcrestack  docu-
463         mentation.) An alternative approach to recursion that uses memory  from         mentation.)  An alternative approach to recursion that uses memory from
464         the  heap  to remember data, instead of using recursive function calls,         the heap to remember data, instead of using recursive  function  calls,
465         has been implemented to work round the problem of limited  stack  size.         has  been  implemented to work round the problem of limited stack size.
466         If you want to build a version of PCRE that works this way, add         If you want to build a version of PCRE that works this way, add
467    
468           --disable-stack-for-recursion           --disable-stack-for-recursion
469    
470         to  the  configure  command. With this configuration, PCRE will use the         to the configure command. With this configuration, PCRE  will  use  the
471         pcre_stack_malloc and pcre_stack_free variables to call memory  manage-         pcre_stack_malloc  and pcre_stack_free variables to call memory manage-
472         ment  functions.  Separate  functions are provided because the usage is         ment functions. By default these point to malloc() and free(), but  you
473         very predictable: the block sizes requested are always  the  same,  and         can replace the pointers so that your own functions are used instead.
474         the  blocks  are always freed in reverse order. A calling program might  
475         be able to implement optimized functions that perform better  than  the         Separate  functions  are  provided  rather  than  using pcre_malloc and
476         standard  malloc()  and  free()  functions.  PCRE  runs noticeably more         pcre_free because the  usage  is  very  predictable:  the  block  sizes
477         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
478         function; it is not relevant for the the pcre_dfa_exec() function.         reverse order. A calling program might be able to  implement  optimized
479           functions  that  perform  better  than  malloc()  and free(). PCRE runs
480           noticeably more slowly when built in this way. This option affects only
481           the pcre_exec() function; it is not relevant for pcre_dfa_exec().
482    
483    
484  LIMITING PCRE RESOURCE USAGE  LIMITING PCRE RESOURCE USAGE
# Line 429  LIMITING PCRE RESOURCE USAGE Line 511  LIMITING PCRE RESOURCE USAGE
511         time.         time.
512    
513    
514    CREATING CHARACTER TABLES AT BUILD TIME
515    
516           PCRE uses fixed tables for processing characters whose code values  are
517           less  than 256. By default, PCRE is built with a set of tables that are
518           distributed in the file pcre_chartables.c.dist. These  tables  are  for
519           ASCII codes only. If you add
520    
521             --enable-rebuild-chartables
522    
523           to  the  configure  command, the distributed tables are no longer used.
524           Instead, a program called dftables is compiled and  run.  This  outputs
525           the source for new set of tables, created in the default locale of your
526           C runtime system. (This method of replacing the tables does not work if
527           you  are cross compiling, because dftables is run on the local host. If
528           you need to create alternative tables when cross  compiling,  you  will
529           have to do so "by hand".)
530    
531    
532  USING EBCDIC CODE  USING EBCDIC CODE
533    
534         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
535         character  code  is  ASCII  (or Unicode, which is a superset of ASCII).         character code is ASCII (or Unicode, which is  a  superset  of  ASCII).
536         PCRE can, however, be compiled to  run  in  an  EBCDIC  environment  by         This  is  the  case for most computer operating systems. PCRE can, how-
537         adding         ever, be compiled to run in an EBCDIC environment by adding
538    
539           --enable-ebcdic           --enable-ebcdic
540    
541         to the configure command.         to the configure command. This setting implies --enable-rebuild-charta-
542           bles.  You  should  only  use  it if you know that you are in an EBCDIC
543           environment (for example,  an  IBM  mainframe  operating  system).  The
544           --enable-ebcdic option is incompatible with --enable-utf8.
545    
546    
547    PCREGREP OPTIONS FOR COMPRESSED FILE SUPPORT
548    
549           By default, pcregrep reads all files as plain text. You can build it so
550           that it recognizes files whose names end in .gz or .bz2, and reads them
551           with libz or libbz2, respectively, by adding one or both of
552    
553             --enable-pcregrep-libz
554             --enable-pcregrep-libbz2
555    
556           to the configure command. These options naturally require that the rel-
557           evant libraries are installed on your system. Configuration  will  fail
558           if they are not.
559    
560    
561    PCREGREP BUFFER SIZE
562    
563           pcregrep  uses  an internal buffer to hold a "window" on the file it is
564           scanning, in order to be able to output "before" and "after" lines when
565           it  finds  a match. The size of the buffer is controlled by a parameter
566           whose default value is 20K. The buffer itself is three times this size,
567           but because of the way it is used for holding "before" lines, the long-
568           est line that is guaranteed to be processable is  the  parameter  size.
569           You can change the default parameter value by adding, for example,
570    
571             --with-pcregrep-bufsize=50K
572    
573           to the configure command. The caller of pcregrep can, however, override
574           this value by specifying a run-time option.
575    
576    
577    PCRETEST OPTION FOR LIBREADLINE SUPPORT
578    
579           If you add
580    
581             --enable-pcretest-libreadline
582    
583           to the configure command,  pcretest  is  linked  with  the  libreadline
584           library,  and  when its input is from a terminal, it reads it using the
585           readline() function. This provides line-editing and history facilities.
586           Note that libreadline is GPL-licensed, so if you distribute a binary of
587           pcretest linked in this way, there may be licensing issues.
588    
589           Setting this option causes the -lreadline option to  be  added  to  the
590           pcretest  build.  In many operating environments with a sytem-installed
591           libreadline this is sufficient. However, in some environments (e.g.  if
592           an  unmodified  distribution version of readline is in use), some extra
593           configuration may be necessary. The INSTALL file for  libreadline  says
594           this:
595    
596             "Readline uses the termcap functions, but does not link with the
597             termcap or curses library itself, allowing applications which link
598             with readline the to choose an appropriate library."
599    
600           If  your environment has not been set up so that an appropriate library
601           is automatically included, you may need to add something like
602    
603             LIBS="-ncurses"
604    
605           immediately before the configure command.
606    
607    
608  SEE ALSO  SEE ALSO
# Line 455  AUTHOR Line 619  AUTHOR
619    
620  REVISION  REVISION
621    
622         Last updated: 06 March 2007         Last updated: 02 August 2011
623         Copyright (c) 1997-2007 University of Cambridge.         Copyright (c) 1997-2011 University of Cambridge.
624  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
625    
626    
627  PCREMATCHING(3)                                                PCREMATCHING(3)  PCREMATCHING(3)                                                PCREMATCHING(3)
628    
629    
# Line 508  REGULAR EXPRESSIONS AS TREES Line 672  REGULAR EXPRESSIONS AS TREES
672    
673  THE STANDARD MATCHING ALGORITHM  THE STANDARD MATCHING ALGORITHM
674    
675         In the terminology of Jeffrey Friedl's book Mastering  Regular  Expres-         In the terminology of Jeffrey Friedl's book "Mastering Regular  Expres-
676         sions,  the  standard  algorithm  is  an "NFA algorithm". It conducts a         sions",  the  standard  algorithm  is an "NFA algorithm". It conducts a
677         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
678         single path through the tree, checking that the subject matches what is         single path through the tree, checking that the subject matches what is
679         required. When there is a mismatch, the algorithm  tries  any  alterna-         required. When there is a mismatch, the algorithm  tries  any  alterna-
# Line 543  THE ALTERNATIVE MATCHING ALGORITHM Line 707  THE ALTERNATIVE MATCHING ALGORITHM
707         though  it is not implemented as a traditional finite state machine (it         though  it is not implemented as a traditional finite state machine (it
708         keeps multiple states active simultaneously).         keeps multiple states active simultaneously).
709    
710           Although the general principle of this matching algorithm  is  that  it
711           scans  the subject string only once, without backtracking, there is one
712           exception: when a lookaround assertion is encountered,  the  characters
713           following  or  preceding  the  current  point  have to be independently
714           inspected.
715    
716         The scan continues until either the end of the subject is  reached,  or         The scan continues until either the end of the subject is  reached,  or
717         there  are  no more unterminated paths. At this point, terminated paths         there  are  no more unterminated paths. At this point, terminated paths
718         represent the different matching possibilities (if there are none,  the         represent the different matching possibilities (if there are none,  the
719         match  has  failed).   Thus,  if there is more than one possible match,         match  has  failed).   Thus,  if there is more than one possible match,
720         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-
721         est.  In PCRE, there is an option to stop the algorithm after the first         est.  The  matches are returned in decreasing order of length. There is
722         match (which is necessarily the shortest) has been found.         an option to stop the algorithm after the first match (which is  neces-
723           sarily the shortest) is found.
724    
725         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
726         subject. If the pattern         subject. If the pattern
727    
728           cat(er(pillar)?)           cat(er(pillar)?)?
729    
730         is  matched  against the string "the caterpillar catchment", the result         is matched against the string "the caterpillar catchment",  the  result
731         will be the three strings "cat", "cater", and "caterpillar" that  start         will  be the three strings "caterpillar", "cater", and "cat" that start
732         at the fourth character of the subject. The algorithm does not automat-         at the fifth character of the subject. The algorithm does not automati-
733         ically move on to find matches that start at later positions.         cally move on to find matches that start at later positions.
734    
735         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
736         supported by the alternative matching algorithm. They are as follows:         supported by the alternative matching algorithm. They are as follows:
737    
738         1.  Because  the  algorithm  finds  all possible matches, the greedy or         1. Because the algorithm finds all  possible  matches,  the  greedy  or
739         ungreedy nature of repetition quantifiers is not relevant.  Greedy  and         ungreedy  nature  of repetition quantifiers is not relevant. Greedy and
740         ungreedy quantifiers are treated in exactly the same way. However, pos-         ungreedy quantifiers are treated in exactly the same way. However, pos-
741         sessive quantifiers can make a difference when what follows could  also         sessive  quantifiers can make a difference when what follows could also
742         match what is quantified, for example in a pattern like this:         match what is quantified, for example in a pattern like this:
743    
744           ^a++\w!           ^a++\w!
745    
746         This  pattern matches "aaab!" but not "aaa!", which would be matched by         This pattern matches "aaab!" but not "aaa!", which would be matched  by
747         a non-possessive quantifier. Similarly, if an atomic group is  present,         a  non-possessive quantifier. Similarly, if an atomic group is present,
748         it  is matched as if it were a standalone pattern at the current point,         it is matched as if it were a standalone pattern at the current  point,
749         and the longest match is then "locked in" for the rest of  the  overall         and  the  longest match is then "locked in" for the rest of the overall
750         pattern.         pattern.
751    
752         2. When dealing with multiple paths through the tree simultaneously, it         2. When dealing with multiple paths through the tree simultaneously, it
753         is not straightforward to keep track of  captured  substrings  for  the         is  not  straightforward  to  keep track of captured substrings for the
754         different  matching  possibilities,  and  PCRE's implementation of this         different matching possibilities, and  PCRE's  implementation  of  this
755         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-
756         strings are available.         strings are available.
757    
758         3.  Because no substrings are captured, back references within the pat-         3. Because no substrings are captured, back references within the  pat-
759         tern are not supported, and cause errors if encountered.         tern are not supported, and cause errors if encountered.
760    
761         4. For the same reason, conditional expressions that use  a  backrefer-         4.  For  the same reason, conditional expressions that use a backrefer-
762         ence  as  the  condition or test for a specific group recursion are not         ence as the condition or test for a specific group  recursion  are  not
763         supported.         supported.
764    
765         5. Callouts are supported, but the value of the  capture_top  field  is         5.  Because  many  paths  through the tree may be active, the \K escape
766           sequence, which resets the start of the match when encountered (but may
767           be  on  some  paths  and not on others), is not supported. It causes an
768           error if encountered.
769    
770           6. Callouts are supported, but the value of the  capture_top  field  is
771         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.
772    
773         6.  The \C escape sequence, which (in the standard algorithm) matches a         7.  The \C escape sequence, which (in the standard algorithm) matches a
774         single byte, even in UTF-8 mode, is not supported because the  alterna-         single byte, even in UTF-8 mode, is not supported because the  alterna-
775         tive  algorithm  moves  through  the  subject string one character at a         tive  algorithm  moves  through  the  subject string one character at a
776         time, for all active paths through the tree.         time, for all active paths through the tree.
777    
778           8. Except for (*FAIL), the backtracking control verbs such as  (*PRUNE)
779           are  not  supported.  (*FAIL)  is supported, and behaves like a failing
780           negative assertion.
781    
782    
783  ADVANTAGES OF THE ALTERNATIVE ALGORITHM  ADVANTAGES OF THE ALTERNATIVE ALGORITHM
784    
# Line 610  ADVANTAGES OF THE ALTERNATIVE ALGORITHM Line 790  ADVANTAGES OF THE ALTERNATIVE ALGORITHM
790         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
791         things with callouts.         things with callouts.
792    
793         2. There is much better support for partial matching. The  restrictions         2. Because the alternative algorithm  scans  the  subject  string  just
        on  the content of the pattern that apply when using the standard algo-  
        rithm for partial matching do not apply to the  alternative  algorithm.  
        For  non-anchored patterns, the starting position of a partial match is  
        available.  
   
        3. Because the alternative algorithm  scans  the  subject  string  just  
794         once,  and  never  needs to backtrack, it is possible to pass very long         once,  and  never  needs to backtrack, it is possible to pass very long
795         subject strings to the matching function in  several  pieces,  checking         subject strings to the matching function in  several  pieces,  checking
796         for partial matching each time.         for  partial  matching  each time. Although it is possible to do multi-
797           segment matching using the standard algorithm (pcre_exec()), by retain-
798           ing  partially matched substrings, it is more complicated. The pcrepar-
799           tial documentation gives details  of  partial  matching  and  discusses
800           multi-segment matching.
801    
802    
803  DISADVANTAGES OF THE ALTERNATIVE ALGORITHM  DISADVANTAGES OF THE ALTERNATIVE ALGORITHM
# Line 645  AUTHOR Line 823  AUTHOR
823    
824  REVISION  REVISION
825    
826         Last updated: 06 March 2007         Last updated: 17 November 2010
827         Copyright (c) 1997-2007 University of Cambridge.         Copyright (c) 1997-2010 University of Cambridge.
828  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
829    
830    
831  PCREAPI(3)                                                          PCREAPI(3)  PCREAPI(3)                                                          PCREAPI(3)
832    
833    
# Line 753  PCRE API OVERVIEW Line 931  PCRE API OVERVIEW
931         bers for the library.  Applications can use these  to  include  support         bers for the library.  Applications can use these  to  include  support
932         for different releases of PCRE.         for different releases of PCRE.
933    
934           In a Windows environment, if you want to statically link an application
935           program against a non-dll pcre.a  file,  you  must  define  PCRE_STATIC
936           before  including  pcre.h or pcrecpp.h, because otherwise the pcre_mal-
937           loc()   and   pcre_free()   exported   functions   will   be   declared
938           __declspec(dllimport), with unwanted results.
939    
940         The   functions   pcre_compile(),  pcre_compile2(),  pcre_study(),  and         The   functions   pcre_compile(),  pcre_compile2(),  pcre_study(),  and
941         pcre_exec() are used for compiling and matching regular expressions  in         pcre_exec() are used for compiling and matching regular expressions  in
942         a  Perl-compatible  manner. A sample program that demonstrates the sim-         a  Perl-compatible  manner. A sample program that demonstrates the sim-
943         plest way of using them is provided in the file  called  pcredemo.c  in         plest way of using them is provided in the file  called  pcredemo.c  in
944         the  source distribution. The pcresample documentation describes how to         the PCRE source distribution. A listing of this program is given in the
945         run it.         pcredemo documentation, and the pcresample documentation describes  how
946           to compile and run it.
947    
948         A second matching function, pcre_dfa_exec(), which is not Perl-compati-         A second matching function, pcre_dfa_exec(), which is not Perl-compati-
949         ble,  is  also provided. This uses a different algorithm for the match-         ble, is also provided. This uses a different algorithm for  the  match-
950         ing. The alternative algorithm finds all possible matches (at  a  given         ing.  The  alternative algorithm finds all possible matches (at a given
951         point  in  the subject), and scans the subject just once. However, this         point in the subject), and scans the subject just  once  (unless  there
952         algorithm does not return captured substrings. A description of the two         are  lookbehind  assertions).  However,  this algorithm does not return
953         matching  algorithms and their advantages and disadvantages is given in         captured substrings. A description of the two matching  algorithms  and
954         the pcrematching documentation.         their  advantages  and disadvantages is given in the pcrematching docu-
955           mentation.
956    
957         In addition to the main compiling and  matching  functions,  there  are         In addition to the main compiling and  matching  functions,  there  are
958         convenience functions for extracting captured substrings from a subject         convenience functions for extracting captured substrings from a subject
# Line 828  PCRE API OVERVIEW Line 1014  PCRE API OVERVIEW
1014    
1015  NEWLINES  NEWLINES
1016    
1017         PCRE  supports four different conventions for indicating line breaks in         PCRE  supports five different conventions for indicating line breaks in
1018         strings: a single CR (carriage return) character, a  single  LF  (line-         strings: a single CR (carriage return) character, a  single  LF  (line-
1019         feed)  character,  the two-character sequence CRLF, or any Unicode new-         feed) character, the two-character sequence CRLF, any of the three pre-
1020         line sequence.  The Unicode newline sequences are the three  just  men-         ceding, or any Unicode newline sequence. The Unicode newline  sequences
1021         tioned, plus the single characters VT (vertical tab, U+000B), FF (form-         are  the  three just mentioned, plus the single characters VT (vertical
1022         feed, U+000C), NEL (next line, U+0085), LS  (line  separator,  U+2028),         tab, U+000B), FF (formfeed, U+000C), NEL (next line, U+0085), LS  (line
1023         and PS (paragraph separator, U+2029).         separator, U+2028), and PS (paragraph separator, U+2029).
1024    
1025         Each  of  the first three conventions is used by at least one operating         Each  of  the first three conventions is used by at least one operating
1026         system as its standard newline sequence. When PCRE is built, a  default         system as its standard newline sequence. When PCRE is built, a  default
# Line 842  NEWLINES Line 1028  NEWLINES
1028         dard. When PCRE is run, the default can be overridden,  either  when  a         dard. When PCRE is run, the default can be overridden,  either  when  a
1029         pattern is compiled, or when it is matched.         pattern is compiled, or when it is matched.
1030    
1031           At compile time, the newline convention can be specified by the options
1032           argument of pcre_compile(), or it can be specified by special  text  at
1033           the start of the pattern itself; this overrides any other settings. See
1034           the pcrepattern page for details of the special character sequences.
1035    
1036         In the PCRE documentation the word "newline" is used to mean "the char-         In the PCRE documentation the word "newline" is used to mean "the char-
1037         acter or pair of characters that indicate a line break". The choice  of         acter  or pair of characters that indicate a line break". The choice of
1038         newline  convention  affects  the  handling of the dot, circumflex, and         newline convention affects the handling of  the  dot,  circumflex,  and
1039         dollar metacharacters, the handling of #-comments in /x mode, and, when         dollar metacharacters, the handling of #-comments in /x mode, and, when
1040         CRLF  is a recognized line ending sequence, the match position advance-         CRLF is a recognized line ending sequence, the match position  advance-
1041         ment for a non-anchored pattern. The choice of newline convention  does         ment for a non-anchored pattern. There is more detail about this in the
1042         not affect the interpretation of the \n or \r escape sequences.         section on pcre_exec() options below.
1043    
1044           The choice of newline convention does not affect the interpretation  of
1045           the  \n  or  \r  escape  sequences, nor does it affect what \R matches,
1046           which is controlled in a similar way, but by separate options.
1047    
1048    
1049  MULTITHREADING  MULTITHREADING
1050    
1051         The  PCRE  functions  can be used in multi-threading applications, with         The PCRE functions can be used in  multi-threading  applications,  with
1052         the  proviso  that  the  memory  management  functions  pointed  to  by         the  proviso  that  the  memory  management  functions  pointed  to  by
1053         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
1054         callout function pointed to by pcre_callout, are shared by all threads.         callout function pointed to by pcre_callout, are shared by all threads.
# Line 868  SAVING PRECOMPILED PATTERNS FOR LATER US Line 1063  SAVING PRECOMPILED PATTERNS FOR LATER US
1063         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
1064         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
1065         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
1066         pcreprecompile documentation.         pcreprecompile documentation. However, compiling a  regular  expression
1067           with  one version of PCRE for use with a different version is not guar-
1068           anteed to work and may cause crashes.
1069    
1070    
1071  CHECKING BUILD-TIME OPTIONS  CHECKING BUILD-TIME OPTIONS
# Line 899  CHECKING BUILD-TIME OPTIONS Line 1096  CHECKING BUILD-TIME OPTIONS
1096    
1097         The output is an integer whose value specifies  the  default  character         The output is an integer whose value specifies  the  default  character
1098         sequence  that is recognized as meaning "newline". The four values that         sequence  that is recognized as meaning "newline". The four values that
1099         are supported are: 10 for LF, 13 for CR, 3338 for CRLF, and -1 for ANY.         are supported are: 10 for LF, 13 for CR, 3338 for CRLF, -2 for ANYCRLF,
1100         The default should normally be the standard sequence for your operating         and  -1  for  ANY.  Though they are derived from ASCII, the same values
1101         system.         are returned in EBCDIC environments. The default should normally corre-
1102           spond to the standard sequence for your operating system.
1103    
1104             PCRE_CONFIG_BSR
1105    
1106           The output is an integer whose value indicates what character sequences
1107           the \R escape sequence matches by default. A value of 0 means  that  \R
1108           matches  any  Unicode  line ending sequence; a value of 1 means that \R
1109           matches only CR, LF, or CRLF. The default can be overridden when a pat-
1110           tern is compiled or matched.
1111    
1112           PCRE_CONFIG_LINK_SIZE           PCRE_CONFIG_LINK_SIZE
1113    
1114         The output is an integer that contains the number  of  bytes  used  for         The  output  is  an  integer that contains the number of bytes used for
1115         internal linkage in compiled regular expressions. The value is 2, 3, or         internal linkage in compiled regular expressions. The value is 2, 3, or
1116         4. Larger values allow larger regular expressions to  be  compiled,  at         4.  Larger  values  allow larger regular expressions to be compiled, at
1117         the  expense  of  slower matching. The default value of 2 is sufficient         the expense of slower matching. The default value of  2  is  sufficient
1118         for all but the most massive patterns, since  it  allows  the  compiled         for  all  but  the  most massive patterns, since it allows the compiled
1119         pattern to be up to 64K in size.         pattern to be up to 64K in size.
1120    
1121           PCRE_CONFIG_POSIX_MALLOC_THRESHOLD           PCRE_CONFIG_POSIX_MALLOC_THRESHOLD
1122    
1123         The  output  is  an integer that contains the threshold above which the         The output is an integer that contains the threshold  above  which  the
1124         POSIX interface uses malloc() for output vectors. Further  details  are         POSIX  interface  uses malloc() for output vectors. Further details are
1125         given in the pcreposix documentation.         given in the pcreposix documentation.
1126    
1127           PCRE_CONFIG_MATCH_LIMIT           PCRE_CONFIG_MATCH_LIMIT
1128    
1129         The output is an integer that gives the default limit for the number of         The output is a long integer that gives the default limit for the  num-
1130         internal matching function calls in a  pcre_exec()  execution.  Further         ber  of  internal  matching  function calls in a pcre_exec() execution.
1131         details are given with pcre_exec() below.         Further details are given with pcre_exec() below.
1132    
1133           PCRE_CONFIG_MATCH_LIMIT_RECURSION           PCRE_CONFIG_MATCH_LIMIT_RECURSION
1134    
1135         The  output is an integer that gives the default limit for the depth of         The output is a long integer that gives the default limit for the depth
1136         recursion when calling the internal matching function in a  pcre_exec()         of   recursion  when  calling  the  internal  matching  function  in  a
1137         execution. Further details are given with pcre_exec() below.         pcre_exec() execution.  Further  details  are  given  with  pcre_exec()
1138           below.
1139    
1140           PCRE_CONFIG_STACKRECURSE           PCRE_CONFIG_STACKRECURSE
1141    
# Line 955  COMPILING A PATTERN Line 1162  COMPILING A PATTERN
1162         Either of the functions pcre_compile() or pcre_compile2() can be called         Either of the functions pcre_compile() or pcre_compile2() can be called
1163         to compile a pattern into an internal form. The only difference between         to compile a pattern into an internal form. The only difference between
1164         the  two interfaces is that pcre_compile2() has an additional argument,         the  two interfaces is that pcre_compile2() has an additional argument,
1165         errorcodeptr, via which a numerical error code can be returned.         errorcodeptr, via which a numerical error  code  can  be  returned.  To
1166           avoid  too  much repetition, we refer just to pcre_compile() below, but
1167           the information applies equally to pcre_compile2().
1168    
1169         The pattern is a C string terminated by a binary zero, and is passed in         The pattern is a C string terminated by a binary zero, and is passed in
1170         the  pattern  argument.  A  pointer to a single block of memory that is         the  pattern  argument.  A  pointer to a single block of memory that is
# Line 972  COMPILING A PATTERN Line 1181  COMPILING A PATTERN
1181    
1182         The options argument contains various bit settings that affect the com-         The options argument contains various bit settings that affect the com-
1183         pilation. It should be zero if no options are required.  The  available         pilation. It should be zero if no options are required.  The  available
1184         options  are  described  below. Some of them, in particular, those that         options  are  described  below. Some of them (in particular, those that
1185         are compatible with Perl, can also be set and  unset  from  within  the         are compatible with Perl, but some others as well) can also be set  and
1186         pattern  (see  the  detailed  description in the pcrepattern documenta-         unset  from  within  the  pattern  (see the detailed description in the
1187         tion). For these options, the contents of the options  argument  speci-         pcrepattern documentation). For those options that can be different  in
1188         fies  their initial settings at the start of compilation and execution.         different  parts  of  the pattern, the contents of the options argument
1189         The PCRE_ANCHORED and PCRE_NEWLINE_xxx options can be set at  the  time         specifies their settings at the start of compilation and execution. The
1190         of matching as well as at compile time.         PCRE_ANCHORED,  PCRE_BSR_xxx, PCRE_NEWLINE_xxx, PCRE_NO_UTF8_CHECK, and
1191           PCRE_NO_START_OPT options can be set at the time of matching as well as
1192           at compile time.
1193    
1194         If errptr is NULL, pcre_compile() returns NULL immediately.  Otherwise,         If errptr is NULL, pcre_compile() returns NULL immediately.  Otherwise,
1195         if compilation of a pattern fails,  pcre_compile()  returns  NULL,  and         if compilation of a pattern fails,  pcre_compile()  returns  NULL,  and
1196         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-
1197         sage. This is a static string that is part of the library. You must not         sage. This is a static string that is part of the library. You must not
1198         try to free it. The offset from the start of the pattern to the charac-         try  to  free it. Normally, the offset from the start of the pattern to
1199         ter where the error was discovered is placed in the variable pointed to         the byte that was being processed when  the  error  was  discovered  is
1200         by  erroffset,  which must not be NULL. If it is, an immediate error is         placed  in the variable pointed to by erroffset, which must not be NULL
1201         given.         (if it is, an immediate error is given). However, for an invalid  UTF-8
1202           string,  the offset is that of the first byte of the failing character.
1203         If pcre_compile2() is used instead of pcre_compile(),  and  the  error-         Also, some errors are not detected until checks are  carried  out  when
1204         codeptr  argument is not NULL, a non-zero error code number is returned         the  whole  pattern  has been scanned; in these cases the offset passed
1205         via this argument in the event of an error. This is in addition to  the         back is the length of the pattern.
1206    
1207           Note that the offset is in bytes, not characters, even in  UTF-8  mode.
1208           It may sometimes point into the middle of a UTF-8 character.
1209    
1210           If  pcre_compile2()  is  used instead of pcre_compile(), and the error-
1211           codeptr argument is not NULL, a non-zero error code number is  returned
1212           via  this argument in the event of an error. This is in addition to the
1213         textual error message. Error codes and messages are listed below.         textual error message. Error codes and messages are listed below.
1214    
1215         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
1216         character tables that are  built  when  PCRE  is  compiled,  using  the         character  tables  that  are  built  when  PCRE  is compiled, using the
1217         default  C  locale.  Otherwise, tableptr must be an address that is the         default C locale. Otherwise, tableptr must be an address  that  is  the
1218         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
1219         compiled  pattern,  and used again by pcre_exec(), unless another table         compiled pattern, and used again by pcre_exec(), unless  another  table
1220         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
1221         support below.         support below.
1222    
1223         This  code  fragment  shows a typical straightforward call to pcre_com-         This code fragment shows a typical straightforward  call  to  pcre_com-
1224         pile():         pile():
1225    
1226           pcre *re;           pcre *re;
# Line 1015  COMPILING A PATTERN Line 1233  COMPILING A PATTERN
1233             &erroffset,       /* for error offset */             &erroffset,       /* for error offset */
1234             NULL);            /* use default character tables */             NULL);            /* use default character tables */
1235    
1236         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
1237         file:         file:
1238    
1239           PCRE_ANCHORED           PCRE_ANCHORED
1240    
1241         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
1242         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
1243         that  is being searched (the "subject string"). This effect can also be         that is being searched (the "subject string"). This effect can also  be
1244         achieved by appropriate constructs in the pattern itself, which is  the         achieved  by appropriate constructs in the pattern itself, which is the
1245         only way to do it in Perl.         only way to do it in Perl.
1246    
1247           PCRE_AUTO_CALLOUT           PCRE_AUTO_CALLOUT
1248    
1249         If this bit is set, pcre_compile() automatically inserts callout items,         If this bit is set, pcre_compile() automatically inserts callout items,
1250         all with number 255, before each pattern item. For  discussion  of  the         all  with  number  255, before each pattern item. For discussion of the
1251         callout facility, see the pcrecallout documentation.         callout facility, see the pcrecallout documentation.
1252    
1253             PCRE_BSR_ANYCRLF
1254             PCRE_BSR_UNICODE
1255    
1256           These options (which are mutually exclusive) control what the \R escape
1257           sequence  matches.  The choice is either to match only CR, LF, or CRLF,
1258           or to match any Unicode newline sequence. The default is specified when
1259           PCRE is built. It can be overridden from within the pattern, or by set-
1260           ting an option when a compiled pattern is matched.
1261    
1262           PCRE_CASELESS           PCRE_CASELESS
1263    
1264         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
1265         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
1266         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
1267         always understands the concept of case for characters whose values  are         always  understands the concept of case for characters whose values are
1268         less  than 128, so caseless matching is always possible. For characters         less than 128, so caseless matching is always possible. For  characters
1269         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-
1270         piled  with Unicode property support, but not otherwise. If you want to         piled with Unicode property support, but not otherwise. If you want  to
1271         use caseless matching for characters 128 and  above,  you  must  ensure         use  caseless  matching  for  characters 128 and above, you must ensure
1272         that  PCRE  is  compiled  with Unicode property support as well as with         that PCRE is compiled with Unicode property support  as  well  as  with
1273         UTF-8 support.         UTF-8 support.
1274    
1275           PCRE_DOLLAR_ENDONLY           PCRE_DOLLAR_ENDONLY
1276    
1277         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
1278         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
1279         matches immediately before a newline at the end of the string (but  not         matches  immediately before a newline at the end of the string (but not
1280         before  any  other newlines). The PCRE_DOLLAR_ENDONLY option is ignored         before any other newlines). The PCRE_DOLLAR_ENDONLY option  is  ignored
1281         if PCRE_MULTILINE is set.  There is no equivalent  to  this  option  in         if  PCRE_MULTILINE  is  set.   There is no equivalent to this option in
1282         Perl, and no way to set it within a pattern.         Perl, and no way to set it within a pattern.
1283    
1284           PCRE_DOTALL           PCRE_DOTALL
1285    
1286         If this bit is set, a dot metacharater in the pattern matches all char-         If this bit is set, a dot metacharacter in the pattern matches a  char-
1287         acters, including those that indicate newline. Without it, a  dot  does         acter of any value, including one that indicates a newline. However, it
1288         not  match  when  the  current position is at a newline. This option is         only ever matches one character, even if newlines are  coded  as  CRLF.
1289         equivalent to Perl's /s option, and it can be changed within a  pattern         Without  this option, a dot does not match when the current position is
1290         by  a (?s) option setting. A negative class such as [^a] always matches         at a newline. This option is equivalent to Perl's /s option, and it can
1291         newline characters, independent of the setting of this option.         be  changed within a pattern by a (?s) option setting. A negative class
1292           such as [^a] always matches newline characters, independent of the set-
1293           ting of this option.
1294    
1295           PCRE_DUPNAMES           PCRE_DUPNAMES
1296    
1297         If this bit is set, names used to identify capturing  subpatterns  need         If  this  bit is set, names used to identify capturing subpatterns need
1298         not be unique. This can be helpful for certain types of pattern when it         not be unique. This can be helpful for certain types of pattern when it
1299         is known that only one instance of the named  subpattern  can  ever  be         is  known  that  only  one instance of the named subpattern can ever be
1300         matched.  There  are  more details of named subpatterns below; see also         matched. There are more details of named subpatterns  below;  see  also
1301         the pcrepattern documentation.         the pcrepattern documentation.
1302    
1303           PCRE_EXTENDED           PCRE_EXTENDED
1304    
1305         If this bit is set, whitespace  data  characters  in  the  pattern  are         If  this  bit  is  set,  whitespace  data characters in the pattern are
1306         totally ignored except when escaped or inside a character class. White-         totally ignored except when escaped or inside a character class. White-
1307         space does not include the VT character (code 11). In addition, charac-         space does not include the VT character (code 11). In addition, charac-
1308         ters between an unescaped # outside a character class and the next new-         ters between an unescaped # outside a character class and the next new-
1309         line, inclusive, are also ignored. This  is  equivalent  to  Perl's  /x         line,  inclusive,  are  also  ignored.  This is equivalent to Perl's /x
1310         option,  and  it  can be changed within a pattern by a (?x) option set-         option, and it can be changed within a pattern by a  (?x)  option  set-
1311         ting.         ting.
1312    
1313           Which  characters  are  interpreted  as  newlines  is controlled by the
1314           options passed to pcre_compile() or by a special sequence at the  start
1315           of  the  pattern, as described in the section entitled "Newline conven-
1316           tions" in the pcrepattern documentation. Note that the end of this type
1317           of  comment  is  a  literal  newline  sequence  in  the pattern; escape
1318           sequences that happen to represent a newline do not count.
1319    
1320         This option makes it possible to include  comments  inside  complicated         This option makes it possible to include  comments  inside  complicated
1321         patterns.   Note,  however,  that this applies only to data characters.         patterns.   Note,  however,  that this applies only to data characters.
1322         Whitespace  characters  may  never  appear  within  special   character         Whitespace  characters  may  never  appear  within  special   character
1323         sequences  in  a  pattern,  for  example  within the sequence (?( which         sequences in a pattern, for example within the sequence (?( that intro-
1324         introduces a conditional subpattern.         duces a conditional subpattern.
1325    
1326           PCRE_EXTRA           PCRE_EXTRA
1327    
# Line 1095  COMPILING A PATTERN Line 1331  COMPILING A PATTERN
1331         letter  that  has  no  special  meaning causes an error, thus reserving         letter  that  has  no  special  meaning causes an error, thus reserving
1332         these combinations for future expansion. By  default,  as  in  Perl,  a         these combinations for future expansion. By  default,  as  in  Perl,  a
1333         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
1334         literal. (Perl can, however, be persuaded to give a warning for  this.)         literal. (Perl can, however, be persuaded to give an error for this, by
1335         There  are  at  present no other features controlled by this option. It         running  it with the -w option.) There are at present no other features
1336         can also be set by a (?X) option setting within a pattern.         controlled by this option. It can also be set by a (?X) option  setting
1337           within a pattern.
1338    
1339           PCRE_FIRSTLINE           PCRE_FIRSTLINE
1340    
1341         If this option is set, an  unanchored  pattern  is  required  to  match         If  this  option  is  set,  an  unanchored pattern is required to match
1342         before  or  at  the  first  newline  in  the subject string, though the         before or at the first  newline  in  the  subject  string,  though  the
1343         matched text may continue over the newline.         matched text may continue over the newline.
1344    
1345             PCRE_JAVASCRIPT_COMPAT
1346    
1347           If this option is set, PCRE's behaviour is changed in some ways so that
1348           it is compatible with JavaScript rather than Perl. The changes  are  as
1349           follows:
1350    
1351           (1)  A  lone  closing square bracket in a pattern causes a compile-time
1352           error, because this is illegal in JavaScript (by default it is  treated
1353           as a data character). Thus, the pattern AB]CD becomes illegal when this
1354           option is set.
1355    
1356           (2) At run time, a back reference to an unset subpattern group  matches
1357           an  empty  string (by default this causes the current matching alterna-
1358           tive to fail). A pattern such as (\1)(a) succeeds when this  option  is
1359           set  (assuming  it can find an "a" in the subject), whereas it fails by
1360           default, for Perl compatibility.
1361    
1362           PCRE_MULTILINE           PCRE_MULTILINE
1363    
1364         By default, PCRE treats the subject string as consisting  of  a  single         By default, PCRE treats the subject string as consisting  of  a  single
# Line 1125  COMPILING A PATTERN Line 1379  COMPILING A PATTERN
1379           PCRE_NEWLINE_CR           PCRE_NEWLINE_CR
1380           PCRE_NEWLINE_LF           PCRE_NEWLINE_LF
1381           PCRE_NEWLINE_CRLF           PCRE_NEWLINE_CRLF
1382             PCRE_NEWLINE_ANYCRLF
1383           PCRE_NEWLINE_ANY           PCRE_NEWLINE_ANY
1384    
1385         These  options  override the default newline definition that was chosen         These  options  override the default newline definition that was chosen
1386         when PCRE was built. Setting the first or the second specifies  that  a         when PCRE was built. Setting the first or the second specifies  that  a
1387         newline  is  indicated  by a single character (CR or LF, respectively).         newline  is  indicated  by a single character (CR or LF, respectively).
1388         Setting PCRE_NEWLINE_CRLF specifies that a newline is indicated by  the         Setting PCRE_NEWLINE_CRLF specifies that a newline is indicated by  the
1389         two-character  CRLF  sequence.  Setting PCRE_NEWLINE_ANY specifies that         two-character  CRLF  sequence.  Setting  PCRE_NEWLINE_ANYCRLF specifies
1390         any Unicode newline sequence should be recognized. The Unicode  newline         that any of the three preceding sequences should be recognized. Setting
1391         sequences  are  the three just mentioned, plus the single characters VT         PCRE_NEWLINE_ANY  specifies that any Unicode newline sequence should be
1392         (vertical tab, U+000B), FF (formfeed, U+000C), NEL (next line, U+0085),         recognized. The Unicode newline sequences are the three just mentioned,
1393         LS  (line separator, U+2028), and PS (paragraph separator, U+2029). The         plus  the  single  characters  VT (vertical tab, U+000B), FF (formfeed,
1394         last two are recognized only in UTF-8 mode.         U+000C), NEL (next line, U+0085), LS (line separator, U+2028),  and  PS
1395           (paragraph  separator,  U+2029).  The  last  two are recognized only in
1396           UTF-8 mode.
1397    
1398         The newline setting in the  options  word  uses  three  bits  that  are         The newline setting in the  options  word  uses  three  bits  that  are
1399         treated  as  a  number, giving eight possibilities. Currently only five         treated as a number, giving eight possibilities. Currently only six are
1400         are used (default plus the four values above). This means that  if  you         used (default plus the five values above). This means that if  you  set
1401         set  more  than  one  newline option, the combination may or may not be         more  than one newline option, the combination may or may not be sensi-
1402         sensible. For example, PCRE_NEWLINE_CR with PCRE_NEWLINE_LF is  equiva-         ble. For example, PCRE_NEWLINE_CR with PCRE_NEWLINE_LF is equivalent to
1403         lent  to PCRE_NEWLINE_CRLF, but other combinations yield unused numbers         PCRE_NEWLINE_CRLF,  but other combinations may yield unused numbers and
1404         and cause an error.         cause an error.
1405    
1406         The only time that a line break is specially recognized when  compiling         The only time that a line break in a pattern  is  specially  recognized
1407         a  pattern  is  if  PCRE_EXTENDED  is set, and an unescaped # outside a         when  compiling  is when PCRE_EXTENDED is set. CR and LF are whitespace
1408         character class is encountered. This indicates  a  comment  that  lasts         characters, and so are ignored in this mode. Also, an unescaped #  out-
1409         until  after the next line break sequence. In other circumstances, line         side  a  character class indicates a comment that lasts until after the
1410         break  sequences  are  treated  as  literal  data,   except   that   in         next line break sequence. In other circumstances, line break  sequences
1411         PCRE_EXTENDED mode, both CR and LF are treated as whitespace characters         in patterns are treated as literal data.
        and are therefore ignored.  
1412    
1413         The newline option that is set at compile time becomes the default that         The newline option that is set at compile time becomes the default that
1414         is  used for pcre_exec() and pcre_dfa_exec(), but it can be overridden.         is used for pcre_exec() and pcre_dfa_exec(), but it can be overridden.
1415    
1416           PCRE_NO_AUTO_CAPTURE           PCRE_NO_AUTO_CAPTURE
1417    
# Line 1165  COMPILING A PATTERN Line 1421  COMPILING A PATTERN
1421         be  used  for  capturing  (and  they acquire numbers in the usual way).         be  used  for  capturing  (and  they acquire numbers in the usual way).
1422         There is no equivalent of this option in Perl.         There is no equivalent of this option in Perl.
1423    
1424             NO_START_OPTIMIZE
1425    
1426           This is an option that acts at matching time; that is, it is really  an
1427           option  for  pcre_exec()  or  pcre_dfa_exec().  If it is set at compile
1428           time, it is remembered with the compiled pattern and assumed at  match-
1429           ing  time.  For  details  see  the discussion of PCRE_NO_START_OPTIMIZE
1430           below.
1431    
1432             PCRE_UCP
1433    
1434           This option changes the way PCRE processes \B, \b, \D, \d, \S, \s,  \W,
1435           \w,  and  some  of  the POSIX character classes. By default, only ASCII
1436           characters are recognized, but if PCRE_UCP is set,  Unicode  properties
1437           are  used instead to classify characters. More details are given in the
1438           section on generic character types in the pcrepattern page. If you  set
1439           PCRE_UCP,  matching  one of the items it affects takes much longer. The
1440           option is available only if PCRE has been compiled with  Unicode  prop-
1441           erty support.
1442    
1443           PCRE_UNGREEDY           PCRE_UNGREEDY
1444    
1445         This option inverts the "greediness" of the quantifiers  so  that  they         This  option  inverts  the "greediness" of the quantifiers so that they
1446         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
1447         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
1448         within the pattern.         within the pattern.
1449    
1450           PCRE_UTF8           PCRE_UTF8
1451    
1452         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
1453         strings of UTF-8 characters instead of single-byte  character  strings.         strings  of  UTF-8 characters instead of single-byte character strings.
1454         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-
1455         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
1456         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
1457         UTF-8 support in the main pcre page.         UTF-8 support in the main pcre page.
1458    
1459           PCRE_NO_UTF8_CHECK           PCRE_NO_UTF8_CHECK
1460    
1461         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
1462         automatically  checked. If an invalid UTF-8 sequence of bytes is found,         automatically checked. There is a  discussion  about  the  validity  of
1463         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
1464         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
1465         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-
1466         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
1467         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
1468         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
1469         ing of subject strings.         can  also be passed to pcre_exec() and pcre_dfa_exec(), to suppress the
1470           UTF-8 validity checking of subject strings.
1471    
1472    
1473  COMPILATION ERROR CODES  COMPILATION ERROR CODES
# Line 1213  COMPILATION ERROR CODES Line 1489  COMPILATION ERROR CODES
1489            9  nothing to repeat            9  nothing to repeat
1490           10  [this code is not in use]           10  [this code is not in use]
1491           11  internal error: unexpected repeat           11  internal error: unexpected repeat
1492           12  unrecognized character after (?           12  unrecognized character after (? or (?-
1493           13  POSIX named classes are supported only within a class           13  POSIX named classes are supported only within a class
1494           14  missing )           14  missing )
1495           15  reference to non-existent subpattern           15  reference to non-existent subpattern
# Line 1221  COMPILATION ERROR CODES Line 1497  COMPILATION ERROR CODES
1497           17  unknown option bit(s) set           17  unknown option bit(s) set
1498           18  missing ) after comment           18  missing ) after comment
1499           19  [this code is not in use]           19  [this code is not in use]
1500           20  regular expression too large           20  regular expression is too large
1501           21  failed to get memory           21  failed to get memory
1502           22  unmatched parentheses           22  unmatched parentheses
1503           23  internal error: code overflow           23  internal error: code overflow
# Line 1230  COMPILATION ERROR CODES Line 1506  COMPILATION ERROR CODES
1506           26  malformed number or name after (?(           26  malformed number or name after (?(
1507           27  conditional group contains more than two branches           27  conditional group contains more than two branches
1508           28  assertion expected after (?(           28  assertion expected after (?(
1509           29  (?R or (?digits must be followed by )           29  (?R or (?[+-]digits must be followed by )
1510           30  unknown POSIX class name           30  unknown POSIX class name
1511           31  POSIX collating elements are not supported           31  POSIX collating elements are not supported
1512           32  this version of PCRE is not compiled with PCRE_UTF8 support           32  this version of PCRE is not compiled with PCRE_UTF8 support
# Line 1238  COMPILATION ERROR CODES Line 1514  COMPILATION ERROR CODES
1514           34  character value in \x{...} sequence is too large           34  character value in \x{...} sequence is too large
1515           35  invalid condition (?(0)           35  invalid condition (?(0)
1516           36  \C not allowed in lookbehind assertion           36  \C not allowed in lookbehind assertion
1517           37  PCRE does not support \L, \l, \N, \U, or \u           37  PCRE does not support \L, \l, \N{name}, \U, or \u
1518           38  number after (?C is > 255           38  number after (?C is > 255
1519           39  closing ) for (?C expected           39  closing ) for (?C expected
1520           40  recursive call could loop indefinitely           40  recursive call could loop indefinitely
# Line 1250  COMPILATION ERROR CODES Line 1526  COMPILATION ERROR CODES
1526           46  malformed \P or \p sequence           46  malformed \P or \p sequence
1527           47  unknown property name after \P or \p           47  unknown property name after \P or \p
1528           48  subpattern name is too long (maximum 32 characters)           48  subpattern name is too long (maximum 32 characters)
1529           49  too many named subpatterns (maximum 10,000)           49  too many named subpatterns (maximum 10000)
1530           50  repeated subpattern is too long           50  [this code is not in use]
1531           51  octal value is greater than \377 (not in UTF-8 mode)           51  octal value is greater than \377 (not in UTF-8 mode)
1532           52  internal error: overran compiling workspace           52  internal error: overran compiling workspace
1533           53   internal  error:  previously-checked  referenced  subpattern not           53  internal error: previously-checked referenced subpattern
1534         found                 not found
1535           54  DEFINE group contains more than one branch           54  DEFINE group contains more than one branch
1536           55  repeating a DEFINE group is not allowed           55  repeating a DEFINE group is not allowed
1537           56  inconsistent NEWLINE options"           56  inconsistent NEWLINE options
1538             57  \g is not followed by a braced, angle-bracketed, or quoted
1539                   name/number or by a plain number
1540             58  a numbered reference must not be zero
1541             59  an argument is not allowed for (*ACCEPT), (*FAIL), or (*COMMIT)
1542             60  (*VERB) not recognized
1543             61  number is too big
1544             62  subpattern name expected
1545             63  digit expected after (?+
1546             64  ] is an invalid data character in JavaScript compatibility mode
1547             65  different names for subpatterns of the same number are
1548                   not allowed
1549             66  (*MARK) must have an argument
1550             67  this version of PCRE is not compiled with PCRE_UCP support
1551             68  \c must be followed by an ASCII character
1552             69  \k is not followed by a braced, angle-bracketed, or quoted name
1553    
1554           The  numbers  32  and 10000 in errors 48 and 49 are defaults; different
1555           values may be used if the limits were changed when PCRE was built.
1556    
1557    
1558  STUDYING A PATTERN  STUDYING A PATTERN
# Line 1275  STUDYING A PATTERN Line 1569  STUDYING A PATTERN
1569         the results of the study.         the results of the study.
1570    
1571         The  returned  value  from  pcre_study()  can  be  passed  directly  to         The  returned  value  from  pcre_study()  can  be  passed  directly  to
1572         pcre_exec().  However,  a  pcre_extra  block also contains other fields         pcre_exec()  or  pcre_dfa_exec(). However, a pcre_extra block also con-
1573         that can be set by the caller before the block  is  passed;  these  are         tains other fields that can be set by the caller before  the  block  is
1574         described below in the section on matching a pattern.         passed; these are described below in the section on matching a pattern.
1575    
1576         If  studying  the  pattern  does not produce any additional information         If  studying  the  pattern  does  not  produce  any useful information,
1577         pcre_study() returns NULL. In that circumstance, if the calling program         pcre_study() returns NULL. In that circumstance, if the calling program
1578         wants  to  pass  any of the other fields to pcre_exec(), it must set up         wants   to   pass   any   of   the   other  fields  to  pcre_exec()  or
1579         its own pcre_extra block.         pcre_dfa_exec(), it must set up its own pcre_extra block.
1580    
1581         The second argument of pcre_study() contains option bits.  At  present,         The second argument of pcre_study() contains option bits.  At  present,
1582         no options are defined, and this argument should always be zero.         no options are defined, and this argument should always be zero.
# Line 1302  STUDYING A PATTERN Line 1596  STUDYING A PATTERN
1596             0,              /* no options exist */             0,              /* no options exist */
1597             &error);        /* set to NULL or points to a message */             &error);        /* set to NULL or points to a message */
1598    
1599         At present, studying a pattern is useful only for non-anchored patterns         Studying a pattern does two things: first, a lower bound for the length
1600         that  do not have a single fixed starting character. A bitmap of possi-         of subject string that is needed to match the pattern is computed. This
1601         ble starting bytes is created.         does not mean that there are any strings of that length that match, but
1602           it  does  guarantee that no shorter strings match. The value is used by
1603           pcre_exec() and pcre_dfa_exec() to avoid  wasting  time  by  trying  to
1604           match  strings  that are shorter than the lower bound. You can find out
1605           the value in a calling program via the pcre_fullinfo() function.
1606    
1607           Studying a pattern is also useful for non-anchored patterns that do not
1608           have  a  single fixed starting character. A bitmap of possible starting
1609           bytes is created. This speeds up finding a position in the  subject  at
1610           which to start matching.
1611    
1612           The  two  optimizations  just  described can be disabled by setting the
1613           PCRE_NO_START_OPTIMIZE   option    when    calling    pcre_exec()    or
1614           pcre_dfa_exec().  You  might  want  to do this if your pattern contains
1615           callouts or (*MARK), and you want to make use of  these  facilities  in
1616           cases  where  matching fails. See the discussion of PCRE_NO_START_OPTI-
1617           MIZE below.
1618    
1619    
1620  LOCALE SUPPORT  LOCALE SUPPORT
1621    
1622         PCRE handles caseless matching, and determines whether  characters  are         PCRE handles caseless matching, and determines whether  characters  are
1623         letters  digits,  or whatever, by reference to a set of tables, indexed         letters,  digits, or whatever, by reference to a set of tables, indexed
1624         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
1625         characters  with  codes  less than 128. Higher-valued codes never match         characters  with  codes  less than 128. By default, higher-valued codes
1626         escapes such as \w or \d, but can be tested with \p if  PCRE  is  built         never match escapes such as \w or \d, but they can be tested with \p if
1627         with  Unicode  character property support. The use of locales with Uni-         PCRE  is  built with Unicode character property support. Alternatively,
1628         code is discouraged.         the PCRE_UCP option can be set at compile  time;  this  causes  \w  and
1629           friends to use Unicode property support instead of built-in tables. The
1630         An internal set of tables is created in the default C locale when  PCRE         use of locales with Unicode is discouraged. If you are handling charac-
1631         is  built.  This  is  used when the final argument of pcre_compile() is         ters  with codes greater than 128, you should either use UTF-8 and Uni-
1632         NULL, and is sufficient for many applications. An  alternative  set  of         code, or use locales, but not try to mix the two.
1633         tables  can,  however, be supplied. These may be created in a different  
1634         locale from the default. As more and more applications change to  using         PCRE contains an internal set of tables that are used  when  the  final
1635         Unicode, the need for this locale support is expected to die away.         argument  of  pcre_compile()  is  NULL.  These  are sufficient for many
1636           applications.  Normally, the internal tables recognize only ASCII char-
1637         External  tables  are  built by calling the pcre_maketables() function,         acters. However, when PCRE is built, it is possible to cause the inter-
1638         which has no arguments, in the relevant locale. The result can then  be         nal tables to be rebuilt in the default "C" locale of the local system,
1639         passed  to  pcre_compile()  or  pcre_exec()  as often as necessary. For         which may cause them to be different.
1640         example, to build and use tables that are appropriate  for  the  French  
1641         locale  (where  accented  characters  with  values greater than 128 are         The  internal tables can always be overridden by tables supplied by the
1642           application that calls PCRE. These may be created in a different locale
1643           from  the  default.  As more and more applications change to using Uni-
1644           code, the need for this locale support is expected to die away.
1645    
1646           External tables are built by calling  the  pcre_maketables()  function,
1647           which  has no arguments, in the relevant locale. The result can then be
1648           passed to pcre_compile() or pcre_exec()  as  often  as  necessary.  For
1649           example,  to  build  and use tables that are appropriate for the French
1650           locale (where accented characters with  values  greater  than  128  are
1651         treated as letters), the following code could be used:         treated as letters), the following code could be used:
1652    
1653           setlocale(LC_CTYPE, "fr_FR");           setlocale(LC_CTYPE, "fr_FR");
1654           tables = pcre_maketables();           tables = pcre_maketables();
1655           re = pcre_compile(..., tables);           re = pcre_compile(..., tables);
1656    
1657           The  locale  name "fr_FR" is used on Linux and other Unix-like systems;
1658           if you are using Windows, the name for the French locale is "french".
1659    
1660         When pcre_maketables() runs, the tables are built  in  memory  that  is         When pcre_maketables() runs, the tables are built  in  memory  that  is
1661         obtained  via  pcre_malloc. It is the caller's responsibility to ensure         obtained  via  pcre_malloc. It is the caller's responsibility to ensure
1662         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 1437  INFORMATION ABOUT A PATTERN Line 1759  INFORMATION ABOUT A PATTERN
1759         returned. The fourth argument should point to an unsigned char *  vari-         returned. The fourth argument should point to an unsigned char *  vari-
1760         able.         able.
1761    
1762             PCRE_INFO_HASCRORLF
1763    
1764           Return  1  if  the  pattern  contains any explicit matches for CR or LF
1765           characters, otherwise 0. The fourth argument should  point  to  an  int
1766           variable.  An explicit match is either a literal CR or LF character, or
1767           \r or \n.
1768    
1769             PCRE_INFO_JCHANGED
1770    
1771           Return 1 if the (?J) or (?-J) option setting is used  in  the  pattern,
1772           otherwise  0. The fourth argument should point to an int variable. (?J)
1773           and (?-J) set and unset the local PCRE_DUPNAMES option, respectively.
1774    
1775           PCRE_INFO_LASTLITERAL           PCRE_INFO_LASTLITERAL
1776    
1777         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
1778         matched string, other than at its  start,  if  such  a  byte  has  been         matched  string,  other  than  at  its  start,  if such a byte has been
1779         recorded. The fourth argument should point to an int variable. If there         recorded. The fourth argument should point to an int variable. If there
1780         is no such byte, -1 is returned. For anchored patterns, a last  literal         is  no such byte, -1 is returned. For anchored patterns, a last literal
1781         byte  is  recorded only if it follows something of variable length. For         byte is recorded only if it follows something of variable  length.  For
1782         example, for the pattern /^a\d+z\d+/ the returned value is "z", but for         example, for the pattern /^a\d+z\d+/ the returned value is "z", but for
1783         /^a\dz\d/ the returned value is -1.         /^a\dz\d/ the returned value is -1.
1784    
1785             PCRE_INFO_MINLENGTH
1786    
1787           If the pattern was studied and a minimum length  for  matching  subject
1788           strings  was  computed,  its  value is returned. Otherwise the returned
1789           value is -1. The value is a number of characters, not bytes  (this  may
1790           be  relevant in UTF-8 mode). The fourth argument should point to an int
1791           variable. A non-negative value is a lower bound to the  length  of  any
1792           matching  string.  There  may not be any strings of that length that do
1793           actually match, but every string that does match is at least that long.
1794    
1795           PCRE_INFO_NAMECOUNT           PCRE_INFO_NAMECOUNT
1796           PCRE_INFO_NAMEENTRYSIZE           PCRE_INFO_NAMEENTRYSIZE
1797           PCRE_INFO_NAMETABLE           PCRE_INFO_NAMETABLE
1798    
1799         PCRE  supports the use of named as well as numbered capturing parenthe-         PCRE supports the use of named as well as numbered capturing  parenthe-
1800         ses. The names are just an additional way of identifying the  parenthe-         ses.  The names are just an additional way of identifying the parenthe-
1801         ses, which still acquire numbers. Several convenience functions such as         ses, which still acquire numbers. Several convenience functions such as
1802         pcre_get_named_substring() are provided for  extracting  captured  sub-         pcre_get_named_substring()  are  provided  for extracting captured sub-
1803         strings  by  name. It is also possible to extract the data directly, by         strings by name. It is also possible to extract the data  directly,  by
1804         first converting the name to a number in order to  access  the  correct         first  converting  the  name to a number in order to access the correct
1805         pointers in the output vector (described with pcre_exec() below). To do         pointers in the output vector (described with pcre_exec() below). To do
1806         the conversion, you need  to  use  the  name-to-number  map,  which  is         the  conversion,  you  need  to  use  the  name-to-number map, which is
1807         described by these three values.         described by these three values.
1808    
1809         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
1810         gives the number of entries, and PCRE_INFO_NAMEENTRYSIZE gives the size         gives the number of entries, and PCRE_INFO_NAMEENTRYSIZE gives the size
1811         of  each  entry;  both  of  these  return  an int value. The entry size         of each entry; both of these  return  an  int  value.  The  entry  size
1812         depends on the length of the longest name. PCRE_INFO_NAMETABLE  returns         depends  on the length of the longest name. PCRE_INFO_NAMETABLE returns
1813         a  pointer  to  the  first  entry of the table (a pointer to char). The         a pointer to the first entry of the table  (a  pointer  to  char).  The
1814         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-
1815         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-
1816         sponding name, zero terminated. The names are  in  alphabetical  order.         sponding name, zero terminated.
1817         When PCRE_DUPNAMES is set, duplicate names are in order of their paren-  
1818         theses numbers. For example, consider  the  following  pattern  (assume         The  names are in alphabetical order. Duplicate names may appear if (?|
1819         PCRE_EXTENDED  is  set,  so  white  space  -  including  newlines  - is         is used to create multiple groups with the same number, as described in
1820         ignored):         the  section  on  duplicate subpattern numbers in the pcrepattern page.
1821           Duplicate names for subpatterns with different  numbers  are  permitted
1822           only  if  PCRE_DUPNAMES  is  set. In all cases of duplicate names, they
1823           appear in the table in the order in which they were found in  the  pat-
1824           tern.  In  the  absence  of (?| this is the order of increasing number;
1825           when (?| is used this is not necessarily the case because later subpat-
1826           terns may have lower numbers.
1827    
1828           As  a  simple  example of the name/number table, consider the following
1829           pattern (assume PCRE_EXTENDED is set, so white space -  including  new-
1830           lines - is ignored):
1831    
1832           (?<date> (?<year>(\d\d)?\d\d) -           (?<date> (?<year>(\d\d)?\d\d) -
1833           (?<month>\d\d) - (?<day>\d\d) )           (?<month>\d\d) - (?<day>\d\d) )
1834    
1835         There are four named subpatterns, so the table has  four  entries,  and         There  are  four  named subpatterns, so the table has four entries, and
1836         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,
1837         with non-printing bytes shows in hexadecimal, and undefined bytes shown         with non-printing bytes shows in hexadecimal, and undefined bytes shown
1838         as ??:         as ??:
1839    
# Line 1487  INFORMATION ABOUT A PATTERN Line 1842  INFORMATION ABOUT A PATTERN
1842           00 04 m  o  n  t  h  00           00 04 m  o  n  t  h  00
1843           00 02 y  e  a  r  00 ??           00 02 y  e  a  r  00 ??
1844    
1845         When  writing  code  to  extract  data from named subpatterns using the         When writing code to extract data  from  named  subpatterns  using  the
1846         name-to-number map, remember that the length of the entries  is  likely         name-to-number  map,  remember that the length of the entries is likely
1847         to be different for each compiled pattern.         to be different for each compiled pattern.
1848    
1849             PCRE_INFO_OKPARTIAL
1850    
1851           Return 1  if  the  pattern  can  be  used  for  partial  matching  with
1852           pcre_exec(),  otherwise  0.  The fourth argument should point to an int
1853           variable. From  release  8.00,  this  always  returns  1,  because  the
1854           restrictions  that  previously  applied  to  partial matching have been
1855           lifted. The pcrepartial documentation gives details of  partial  match-
1856           ing.
1857    
1858           PCRE_INFO_OPTIONS           PCRE_INFO_OPTIONS
1859    
1860         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
1861         fourth argument should point to an unsigned long  int  variable.  These         fourth argument should point to an unsigned long  int  variable.  These
1862         option bits are those specified in the call to pcre_compile(), modified         option bits are those specified in the call to pcre_compile(), modified
1863         by any top-level option settings within the pattern itself.         by any top-level option settings at the start of the pattern itself. In
1864           other  words,  they are the options that will be in force when matching
1865           starts. For example, if the pattern /(?im)abc(?-i)d/ is  compiled  with
1866           the  PCRE_EXTENDED option, the result is PCRE_CASELESS, PCRE_MULTILINE,
1867           and PCRE_EXTENDED.
1868    
1869         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
1870         alternatives begin with one of the following:         alternatives begin with one of the following:
# Line 1520  INFORMATION ABOUT A PATTERN Line 1888  INFORMATION ABOUT A PATTERN
1888           PCRE_INFO_STUDYSIZE           PCRE_INFO_STUDYSIZE
1889    
1890         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
1891         a pcre_extra block. That is,  it  is  the  value  that  was  passed  to         a pcre_extra block. If pcre_extra is NULL, or there is no  study  data,
1892         pcre_malloc() when PCRE was getting memory into which to place the data         zero  is  returned.  The fourth argument should point to a size_t vari-
1893         created by pcre_study(). The fourth argument should point to  a  size_t         able.  The study_data field is set by pcre_study() to  record  informa-
1894         variable.         tion  that will speed up matching (see the section entitled "Studying a
1895           pattern" above). The format of the study_data block is private, but its
1896           length  is  made  available via this option so that it can be saved and
1897           restored (see the pcreprecompile documentation for details).
1898    
1899    
1900  OBSOLETE INFO FUNCTION  OBSOLETE INFO FUNCTION
1901    
1902         int pcre_info(const pcre *code, int *optptr, int *firstcharptr);         int pcre_info(const pcre *code, int *optptr, int *firstcharptr);
1903    
1904         The  pcre_info()  function is now obsolete because its interface is too         The pcre_info() function is now obsolete because its interface  is  too
1905         restrictive to return all the available data about a compiled  pattern.         restrictive  to return all the available data about a compiled pattern.
1906         New   programs   should  use  pcre_fullinfo()  instead.  The  yield  of         New  programs  should  use  pcre_fullinfo()  instead.  The   yield   of
1907         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-
1908         lowing negative numbers:         lowing negative numbers:
1909    
1910           PCRE_ERROR_NULL       the argument code was NULL           PCRE_ERROR_NULL       the argument code was NULL
1911           PCRE_ERROR_BADMAGIC   the "magic number" was not found           PCRE_ERROR_BADMAGIC   the "magic number" was not found
1912    
1913         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
1914         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
1915         PCRE_INFO_OPTIONS above).         PCRE_INFO_OPTIONS above).
1916    
1917         If  the  pattern  is  not anchored and the firstcharptr argument is not         If the pattern is not anchored and the  firstcharptr  argument  is  not
1918         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
1919         any matched string (see PCRE_INFO_FIRSTBYTE above).         any matched string (see PCRE_INFO_FIRSTBYTE above).
1920    
1921    
# Line 1552  REFERENCE COUNTS Line 1923  REFERENCE COUNTS
1923    
1924         int pcre_refcount(pcre *code, int adjust);         int pcre_refcount(pcre *code, int adjust);
1925    
1926         The  pcre_refcount()  function is used to maintain a reference count in         The pcre_refcount() function is used to maintain a reference  count  in
1927         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
1928         benefit  of  applications  that  operate  in an object-oriented manner,         benefit of applications that  operate  in  an  object-oriented  manner,
1929         where different parts of the application may be using the same compiled         where different parts of the application may be using the same compiled
1930         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.
1931    
1932         When a pattern is compiled, the reference count field is initialized to         When a pattern is compiled, the reference count field is initialized to
1933         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
1934         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
1935         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
1936         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
1937         is outside these limits, it is forced to the appropriate limit value.         is outside these limits, it is forced to the appropriate limit value.
1938    
1939         Except when it is zero, the reference count is not correctly  preserved         Except  when it is zero, the reference count is not correctly preserved
1940         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
1941         whose byte-order is different. (This seems a highly unlikely scenario.)         whose byte-order is different. (This seems a highly unlikely scenario.)
1942    
1943    
# Line 1578  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1949  MATCHING A PATTERN: THE TRADITIONAL FUNC
1949    
1950         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
1951         compiled pattern, which is passed in the code argument. If the  pattern         compiled pattern, which is passed in the code argument. If the  pattern
1952         has been studied, the result of the study should be passed in the extra         was  studied,  the  result  of  the study should be passed in the extra
1953         argument. This function is the main matching facility of  the  library,         argument. This function is the main matching facility of  the  library,
1954         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
1955         an alternative matching function, which is described below in the  sec-         an alternative matching function, which is described below in the  sec-
# Line 1618  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1989  MATCHING A PATTERN: THE TRADITIONAL FUNC
1989           unsigned long int match_limit_recursion;           unsigned long int match_limit_recursion;
1990           void *callout_data;           void *callout_data;
1991           const unsigned char *tables;           const unsigned char *tables;
1992             unsigned char **mark;
1993    
1994         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
1995         are set. The flag bits are:         are set. The flag bits are:
# Line 1627  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 1999  MATCHING A PATTERN: THE TRADITIONAL FUNC
1999           PCRE_EXTRA_MATCH_LIMIT_RECURSION           PCRE_EXTRA_MATCH_LIMIT_RECURSION
2000           PCRE_EXTRA_CALLOUT_DATA           PCRE_EXTRA_CALLOUT_DATA
2001           PCRE_EXTRA_TABLES           PCRE_EXTRA_TABLES
2002             PCRE_EXTRA_MARK
2003    
2004         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
2005         the  pcre_extra  block  that is returned by pcre_study(), together with         the  pcre_extra  block  that is returned by pcre_study(), together with
# Line 1637  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2010  MATCHING A PATTERN: THE TRADITIONAL FUNC
2010         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
2011         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
2012         match, but which have a very large number  of  possibilities  in  their         match, but which have a very large number  of  possibilities  in  their
2013         search  trees.  The  classic  example  is  the  use of nested unlimited         search  trees. The classic example is a pattern that uses nested unlim-
2014         repeats.         ited repeats.
2015    
2016         Internally, PCRE uses a function called match() which it calls  repeat-         Internally, PCRE uses a function called match() which it calls  repeat-
2017         edly  (sometimes  recursively). The limit set by match_limit is imposed         edly  (sometimes  recursively). The limit set by match_limit is imposed
# Line 1660  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2033  MATCHING A PATTERN: THE TRADITIONAL FUNC
2033         the  total number of calls, because not all calls to match() are recur-         the  total number of calls, because not all calls to match() are recur-
2034         sive.  This limit is of use only if it is set smaller than match_limit.         sive.  This limit is of use only if it is set smaller than match_limit.
2035    
2036         Limiting  the  recursion  depth  limits the amount of stack that can be         Limiting the recursion depth limits the amount of  stack  that  can  be
2037         used, or, when PCRE has been compiled to use memory on the heap instead         used, or, when PCRE has been compiled to use memory on the heap instead
2038         of the stack, the amount of heap memory that can be used.         of the stack, the amount of heap memory that can be used.
2039    
2040         The  default  value  for  match_limit_recursion can be set when PCRE is         The default value for match_limit_recursion can be  set  when  PCRE  is
2041         built; the default default  is  the  same  value  as  the  default  for         built;  the  default  default  is  the  same  value  as the default for
2042         match_limit.  You can override the default by suppling pcre_exec() with         match_limit. You can override the default by suppling pcre_exec()  with
2043         a  pcre_extra  block  in  which  match_limit_recursion  is   set,   and         a   pcre_extra   block  in  which  match_limit_recursion  is  set,  and
2044         PCRE_EXTRA_MATCH_LIMIT_RECURSION  is  set  in  the  flags field. If the         PCRE_EXTRA_MATCH_LIMIT_RECURSION is set in  the  flags  field.  If  the
2045         limit is exceeded, pcre_exec() returns PCRE_ERROR_RECURSIONLIMIT.         limit is exceeded, pcre_exec() returns PCRE_ERROR_RECURSIONLIMIT.
2046    
2047         The pcre_callout field is used in conjunction with the  "callout"  fea-         The  callout_data  field is used in conjunction with the "callout" fea-
2048         ture, which is described in the pcrecallout documentation.         ture, and is described in the pcrecallout documentation.
2049    
2050         The  tables  field  is  used  to  pass  a  character  tables pointer to         The tables field  is  used  to  pass  a  character  tables  pointer  to
2051         pcre_exec(); this overrides the value that is stored with the  compiled         pcre_exec();  this overrides the value that is stored with the compiled
2052         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
2053         custom tables were supplied to pcre_compile() via  its  tableptr  argu-         custom  tables  were  supplied to pcre_compile() via its tableptr argu-
2054         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
2055         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-
2056         using  patterns  that  have been saved after compiling with an external         using patterns that have been saved after compiling  with  an  external
2057         set of tables, because the external tables  might  be  at  a  different         set  of  tables,  because  the  external tables might be at a different
2058         address  when  pcre_exec() is called. See the pcreprecompile documenta-         address when pcre_exec() is called. See the  pcreprecompile  documenta-
2059         tion for a discussion of saving compiled patterns for later use.         tion for a discussion of saving compiled patterns for later use.
2060    
2061           If  PCRE_EXTRA_MARK  is  set in the flags field, the mark field must be
2062           set to point to a char * variable. If the pattern  contains  any  back-
2063           tracking  control verbs such as (*MARK:NAME), and the execution ends up
2064           with a name to pass back, a pointer to the  name  string  (zero  termi-
2065           nated)  is  placed  in  the  variable pointed to by the mark field. The
2066           names are within the compiled pattern; if you wish  to  retain  such  a
2067           name  you must copy it before freeing the memory of a compiled pattern.
2068           If there is no name to pass back, the variable pointed to by  the  mark
2069           field  set  to NULL. For details of the backtracking control verbs, see
2070           the section entitled "Backtracking control" in the pcrepattern documen-
2071           tation.
2072    
2073     Option bits for pcre_exec()     Option bits for pcre_exec()
2074    
2075         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.
2076         The  only  bits  that  may  be set are PCRE_ANCHORED, PCRE_NEWLINE_xxx,         The only bits that may  be  set  are  PCRE_ANCHORED,  PCRE_NEWLINE_xxx,
2077         PCRE_NOTBOL,   PCRE_NOTEOL,   PCRE_NOTEMPTY,   PCRE_NO_UTF8_CHECK   and         PCRE_NOTBOL,    PCRE_NOTEOL,    PCRE_NOTEMPTY,   PCRE_NOTEMPTY_ATSTART,
2078         PCRE_PARTIAL.         PCRE_NO_START_OPTIMIZE,  PCRE_NO_UTF8_CHECK,   PCRE_PARTIAL_SOFT,   and
2079           PCRE_PARTIAL_HARD.
2080    
2081           PCRE_ANCHORED           PCRE_ANCHORED
2082    
# Line 1699  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2085  MATCHING A PATTERN: THE TRADITIONAL FUNC
2085         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
2086         unachored at matching time.         unachored at matching time.
2087    
2088             PCRE_BSR_ANYCRLF
2089             PCRE_BSR_UNICODE
2090    
2091           These options (which are mutually exclusive) control what the \R escape
2092           sequence  matches.  The choice is either to match only CR, LF, or CRLF,
2093           or to match any Unicode newline sequence. These  options  override  the
2094           choice that was made or defaulted when the pattern was compiled.
2095    
2096           PCRE_NEWLINE_CR           PCRE_NEWLINE_CR
2097           PCRE_NEWLINE_LF           PCRE_NEWLINE_LF
2098           PCRE_NEWLINE_CRLF           PCRE_NEWLINE_CRLF
2099             PCRE_NEWLINE_ANYCRLF
2100           PCRE_NEWLINE_ANY           PCRE_NEWLINE_ANY
2101    
2102         These options override  the  newline  definition  that  was  chosen  or         These  options  override  the  newline  definition  that  was chosen or
2103         defaulted  when the pattern was compiled. For details, see the descrip-         defaulted when the pattern was compiled. For details, see the  descrip-
2104         tion of pcre_compile()  above.  During  matching,  the  newline  choice         tion  of  pcre_compile()  above.  During  matching,  the newline choice
2105         affects  the  behaviour  of the dot, circumflex, and dollar metacharac-         affects the behaviour of the dot, circumflex,  and  dollar  metacharac-
2106         ters. It may also alter the way the match position is advanced after  a         ters.  It may also alter the way the match position is advanced after a
2107         match  failure  for  an  unanchored  pattern. When PCRE_NEWLINE_CRLF or         match failure for an unanchored pattern.
2108         PCRE_NEWLINE_ANY is set, and a match attempt  fails  when  the  current  
2109         position  is  at a CRLF sequence, the match position is advanced by two         When PCRE_NEWLINE_CRLF, PCRE_NEWLINE_ANYCRLF,  or  PCRE_NEWLINE_ANY  is
2110         characters instead of one, in other words, to after the CRLF.         set,  and a match attempt for an unanchored pattern fails when the cur-
2111           rent position is at a  CRLF  sequence,  and  the  pattern  contains  no
2112           explicit  matches  for  CR  or  LF  characters,  the  match position is
2113           advanced by two characters instead of one, in other words, to after the
2114           CRLF.
2115    
2116           The above rule is a compromise that makes the most common cases work as
2117           expected. For example, if the  pattern  is  .+A  (and  the  PCRE_DOTALL
2118           option is not set), it does not match the string "\r\nA" because, after
2119           failing at the start, it skips both the CR and the LF before  retrying.
2120           However,  the  pattern  [\r\n]A does match that string, because it con-
2121           tains an explicit CR or LF reference, and so advances only by one char-
2122           acter after the first failure.
2123    
2124           An explicit match for CR of LF is either a literal appearance of one of
2125           those characters, or one of the \r or  \n  escape  sequences.  Implicit
2126           matches  such  as [^X] do not count, nor does \s (which includes CR and
2127           LF in the characters that it matches).
2128    
2129           Notwithstanding the above, anomalous effects may still occur when  CRLF
2130           is a valid newline sequence and explicit \r or \n escapes appear in the
2131           pattern.
2132    
2133           PCRE_NOTBOL           PCRE_NOTBOL
2134    
# Line 1740  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2156  MATCHING A PATTERN: THE TRADITIONAL FUNC
2156    
2157           a?b?           a?b?
2158    
2159         is applied to a string not beginning with "a" or "b",  it  matches  the         is applied to a string not beginning with "a" or  "b",  it  matches  an
2160         empty  string at the start of the subject. With PCRE_NOTEMPTY set, this         empty  string at the start of the subject. With PCRE_NOTEMPTY set, this
2161         match is not valid, so PCRE searches further into the string for occur-         match is not valid, so PCRE searches further into the string for occur-
2162         rences of "a" or "b".         rences of "a" or "b".
2163    
2164         Perl has no direct equivalent of PCRE_NOTEMPTY, but it does make a spe-           PCRE_NOTEMPTY_ATSTART
2165         cial case of a pattern match of the empty  string  within  its  split()  
2166         function,  and  when  using  the /g modifier. It is possible to emulate         This  is  like PCRE_NOTEMPTY, except that an empty string match that is
2167         Perl's behaviour after matching a null string by first trying the match         not at the start of  the  subject  is  permitted.  If  the  pattern  is
2168         again at the same offset with PCRE_NOTEMPTY and PCRE_ANCHORED, and then         anchored, such a match can occur only if the pattern contains \K.
2169         if that fails by advancing the starting offset (see below)  and  trying  
2170         an ordinary match again. There is some code that demonstrates how to do         Perl     has    no    direct    equivalent    of    PCRE_NOTEMPTY    or
2171         this in the pcredemo.c sample program.         PCRE_NOTEMPTY_ATSTART, but it does make a special  case  of  a  pattern
2172           match  of  the empty string within its split() function, and when using
2173           the /g modifier. It is  possible  to  emulate  Perl's  behaviour  after
2174           matching a null string by first trying the match again at the same off-
2175           set with PCRE_NOTEMPTY_ATSTART and  PCRE_ANCHORED,  and  then  if  that
2176           fails, by advancing the starting offset (see below) and trying an ordi-
2177           nary match again. There is some code that demonstrates how to  do  this
2178           in  the  pcredemo sample program. In the most general case, you have to
2179           check to see if the newline convention recognizes CRLF  as  a  newline,
2180           and  if so, and the current character is CR followed by LF, advance the
2181           starting offset by two characters instead of one.
2182    
2183             PCRE_NO_START_OPTIMIZE
2184    
2185           There are a number of optimizations that pcre_exec() uses at the  start
2186           of  a  match,  in  order to speed up the process. For example, if it is
2187           known that an unanchored match must start with a specific character, it
2188           searches  the  subject  for that character, and fails immediately if it
2189           cannot find it, without actually running the  main  matching  function.
2190           This means that a special item such as (*COMMIT) at the start of a pat-
2191           tern is not considered until after a suitable starting  point  for  the
2192           match  has been found. When callouts or (*MARK) items are in use, these
2193           "start-up" optimizations can cause them to be skipped if the pattern is
2194           never  actually  used.  The start-up optimizations are in effect a pre-
2195           scan of the subject that takes place before the pattern is run.
2196    
2197           The PCRE_NO_START_OPTIMIZE option disables the start-up  optimizations,
2198           possibly  causing  performance  to  suffer,  but ensuring that in cases
2199           where the result is "no match", the callouts do occur, and  that  items
2200           such as (*COMMIT) and (*MARK) are considered at every possible starting
2201           position in the subject string. If  PCRE_NO_START_OPTIMIZE  is  set  at
2202           compile time, it cannot be unset at matching time.
2203    
2204           Setting  PCRE_NO_START_OPTIMIZE  can  change  the outcome of a matching
2205           operation.  Consider the pattern
2206    
2207             (*COMMIT)ABC
2208    
2209           When this is compiled, PCRE records the fact that a  match  must  start
2210           with  the  character  "A".  Suppose the subject string is "DEFABC". The
2211           start-up optimization scans along the subject, finds "A" and  runs  the
2212           first  match attempt from there. The (*COMMIT) item means that the pat-
2213           tern must match the current starting position, which in this  case,  it
2214           does.  However,  if  the  same match is run with PCRE_NO_START_OPTIMIZE
2215           set, the initial scan along the subject string  does  not  happen.  The
2216           first  match  attempt  is  run  starting  from "D" and when this fails,
2217           (*COMMIT) prevents any further matches  being  tried,  so  the  overall
2218           result  is  "no  match". If the pattern is studied, more start-up opti-
2219           mizations may be used. For example, a minimum length  for  the  subject
2220           may be recorded. Consider the pattern
2221    
2222             (*MARK:A)(X|Y)
2223    
2224           The  minimum  length  for  a  match is one character. If the subject is
2225           "ABC", there will be attempts to  match  "ABC",  "BC",  "C",  and  then
2226           finally  an empty string.  If the pattern is studied, the final attempt
2227           does not take place, because PCRE knows that the subject is too  short,
2228           and  so  the  (*MARK) is never encountered.  In this case, studying the
2229           pattern does not affect the overall match result, which  is  still  "no
2230           match", but it does affect the auxiliary information that is returned.
2231    
2232           PCRE_NO_UTF8_CHECK           PCRE_NO_UTF8_CHECK
2233    
2234         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
2235         UTF-8  string is automatically checked when pcre_exec() is subsequently         UTF-8 string is automatically checked when pcre_exec() is  subsequently
2236         called.  The value of startoffset is also checked  to  ensure  that  it         called.   The  value  of  startoffset is also checked to ensure that it
2237         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
2238         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
2239         startoffset  contains  an  invalid  value, PCRE_ERROR_BADUTF8_OFFSET is         main pcre page. If  an  invalid  UTF-8  sequence  of  bytes  is  found,
2240         returned.         pcre_exec()  returns  the  error  PCRE_ERROR_BADUTF8  or,  if PCRE_PAR-
2241           TIAL_HARD is set and the problem is a truncated UTF-8 character at  the
2242           end  of  the  subject, PCRE_ERROR_SHORTUTF8. In both cases, information
2243           about the precise nature of the error may also  be  returned  (see  the
2244           descriptions  of these errors in the section entitled Error return val-
2245           ues from pcre_exec() below).  If startoffset contains a value that does
2246           not  point to the start of a UTF-8 character (or to the end of the sub-
2247           ject), PCRE_ERROR_BADUTF8_OFFSET is returned.
2248    
2249         If you already know that your subject is valid, and you  want  to  skip         If you already know that your subject is valid, and you  want  to  skip
2250         these    checks    for   performance   reasons,   you   can   set   the         these    checks    for   performance   reasons,   you   can   set   the
# Line 1770  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2252  MATCHING A PATTERN: THE TRADITIONAL FUNC
2252         do  this  for the second and subsequent calls to pcre_exec() if you are         do  this  for the second and subsequent calls to pcre_exec() if you are
2253         making repeated calls to find all  the  matches  in  a  single  subject         making repeated calls to find all  the  matches  in  a  single  subject
2254         string.  However,  you  should  be  sure  that the value of startoffset         string.  However,  you  should  be  sure  that the value of startoffset
2255         points to the start of a UTF-8 character.  When  PCRE_NO_UTF8_CHECK  is         points to the start of a UTF-8 character (or the end of  the  subject).
2256         set,  the  effect of passing an invalid UTF-8 string as a subject, or a         When  PCRE_NO_UTF8_CHECK is set, the effect of passing an invalid UTF-8
2257         value of startoffset that does not point to the start of a UTF-8  char-         string as a subject or an invalid value of  startoffset  is  undefined.
2258         acter, is undefined. Your program may crash.         Your program may crash.
2259    
2260           PCRE_PARTIAL           PCRE_PARTIAL_HARD
2261             PCRE_PARTIAL_SOFT
2262         This  option  turns  on  the  partial  matching feature. If the subject  
2263         string fails to match the pattern, but at some point during the  match-         These  options turn on the partial matching feature. For backwards com-
2264         ing  process  the  end of the subject was reached (that is, the subject         patibility, PCRE_PARTIAL is a synonym for PCRE_PARTIAL_SOFT. A  partial
2265         partially matches the pattern and the failure to  match  occurred  only         match  occurs if the end of the subject string is reached successfully,
2266         because  there were not enough subject characters), pcre_exec() returns         but there are not enough subject characters to complete the  match.  If
2267         PCRE_ERROR_PARTIAL instead of PCRE_ERROR_NOMATCH. When PCRE_PARTIAL  is         this happens when PCRE_PARTIAL_SOFT (but not PCRE_PARTIAL_HARD) is set,
2268         used,  there  are restrictions on what may appear in the pattern. These         matching continues by testing any remaining alternatives.  Only  if  no
2269         are discussed in the pcrepartial documentation.         complete  match  can be found is PCRE_ERROR_PARTIAL returned instead of
2270           PCRE_ERROR_NOMATCH. In other words,  PCRE_PARTIAL_SOFT  says  that  the
2271           caller  is  prepared to handle a partial match, but only if no complete
2272           match can be found.
2273    
2274           If PCRE_PARTIAL_HARD is set, it overrides  PCRE_PARTIAL_SOFT.  In  this
2275           case,  if  a  partial  match  is found, pcre_exec() immediately returns
2276           PCRE_ERROR_PARTIAL, without  considering  any  other  alternatives.  In
2277           other  words, when PCRE_PARTIAL_HARD is set, a partial match is consid-
2278           ered to be more important that an alternative complete match.
2279    
2280           In both cases, the portion of the string that was  inspected  when  the
2281           partial match was found is set as the first matching string. There is a
2282           more detailed discussion of partial and  multi-segment  matching,  with
2283           examples, in the pcrepartial documentation.
2284    
2285     The string to be matched by pcre_exec()     The string to be matched by pcre_exec()
2286    
2287         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
2288         length  in  length, and a starting byte offset in startoffset. In UTF-8         length (in bytes) in length, and a starting byte offset in startoffset.
2289         mode, the byte offset must point to the start  of  a  UTF-8  character.         If  this  is  negative  or  greater  than  the  length  of the subject,
2290         Unlike  the  pattern string, the subject may contain binary zero bytes.         pcre_exec() returns PCRE_ERROR_BADOFFSET. When the starting  offset  is
2291         When the starting offset is zero, the search for a match starts at  the         zero,  the  search  for a match starts at the beginning of the subject,
2292         beginning of the subject, and this is by far the most common case.         and this is by far the most common case. In UTF-8 mode, the byte offset
2293           must  point  to  the start of a UTF-8 character (or the end of the sub-
2294           ject). Unlike the pattern string, the subject may contain  binary  zero
2295           bytes.
2296    
2297         A  non-zero  starting offset is useful when searching for another match         A  non-zero  starting offset is useful when searching for another match
2298         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-
# Line 1814  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2313  MATCHING A PATTERN: THE TRADITIONAL FUNC
2313         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
2314         discover that it is preceded by a letter.         discover that it is preceded by a letter.
2315    
2316         If a non-zero starting offset is passed when the pattern  is  anchored,         Finding all the matches in a subject is tricky  when  the  pattern  can
2317           match an empty string. It is possible to emulate Perl's /g behaviour by
2318           first  trying  the  match  again  at  the   same   offset,   with   the
2319           PCRE_NOTEMPTY_ATSTART  and  PCRE_ANCHORED  options,  and  then  if that
2320           fails, advancing the starting  offset  and  trying  an  ordinary  match
2321           again. There is some code that demonstrates how to do this in the pcre-
2322           demo sample program. In the most general case, you have to check to see
2323           if  the newline convention recognizes CRLF as a newline, and if so, and
2324           the current character is CR followed by LF, advance the starting offset
2325           by two characters instead of one.
2326    
2327           If  a  non-zero starting offset is passed when the pattern is anchored,
2328         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
2329         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
2330         subject.         subject.
2331    
2332     How pcre_exec() returns captured substrings     How pcre_exec() returns captured substrings
2333    
2334         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
2335         addition, further substrings from the subject  may  be  picked  out  by         addition,  further  substrings  from  the  subject may be picked out by
2336         parts  of  the  pattern.  Following the usage in Jeffrey Friedl's book,         parts of the pattern. Following the usage  in  Jeffrey  Friedl's  book,
2337         this is called "capturing" in what follows, and the  phrase  "capturing         this  is  called "capturing" in what follows, and the phrase "capturing
2338         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-
2339         string. PCRE supports several other kinds of  parenthesized  subpattern         string.  PCRE  supports several other kinds of parenthesized subpattern
2340         that do not cause substrings to be captured.         that do not cause substrings to be captured.
2341    
2342         Captured  substrings are returned to the caller via a vector of integer         Captured substrings are returned to the caller via a vector of integers
2343         offsets whose address is passed in ovector. The number of  elements  in         whose  address is passed in ovector. The number of elements in the vec-
2344         the  vector is passed in ovecsize, which must be a non-negative number.         tor is passed in ovecsize, which must be a non-negative  number.  Note:
2345         Note: this argument is NOT the size of ovector in bytes.         this argument is NOT the size of ovector in bytes.
2346    
2347         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-
2348         strings,  each  substring using a pair of integers. The remaining third         strings, each substring using a pair of integers. The  remaining  third
2349         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-
2350         turing  subpatterns, and is not available for passing back information.         turing subpatterns, and is not available for passing back  information.
2351         The length passed in ovecsize should always be a multiple of three.  If         The  number passed in ovecsize should always be a multiple of three. If
2352         it is not, it is rounded down.         it is not, it is rounded down.
2353    
2354         When  a  match  is successful, information about captured substrings is         When a match is successful, information about  captured  substrings  is
2355         returned in pairs of integers, starting at the  beginning  of  ovector,         returned  in  pairs  of integers, starting at the beginning of ovector,
2356         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
2357         element of a pair is set to the offset of the first character in a sub-         element  of  each pair is set to the byte offset of the first character
2358         string,  and  the  second  is  set to the offset of the first character         in a substring, and the second is set to the byte offset of  the  first
2359         after the end of a substring. The  first  pair,  ovector[0]  and  ovec-         character  after  the end of a substring. Note: these values are always
2360         tor[1],  identify  the  portion  of  the  subject string matched by the         byte offsets, even in UTF-8 mode. They are not character counts.
2361         entire pattern. The next pair is used for the first  capturing  subpat-  
2362         tern, and so on. The value returned by pcre_exec() is one more than the         The first pair of integers, ovector[0]  and  ovector[1],  identify  the
2363         highest numbered pair that has been set. For example, if two substrings         portion  of  the subject string matched by the entire pattern. The next
2364         have  been captured, the returned value is 3. If there are no capturing         pair is used for the first capturing subpattern, and so on.  The  value
2365         subpatterns, the return value from a successful match is 1,  indicating         returned by pcre_exec() is one more than the highest numbered pair that
2366         that just the first pair of offsets has been set.         has been set.  For example, if two substrings have been  captured,  the
2367           returned  value is 3. If there are no capturing subpatterns, the return
2368           value from a successful match is 1, indicating that just the first pair
2369           of offsets has been set.
2370    
2371         If a capturing subpattern is matched repeatedly, it is the last portion         If a capturing subpattern is matched repeatedly, it is the last portion
2372         of the string that it matched that is returned.         of the string that it matched that is returned.
2373    
2374         If the vector is too small to hold all the captured substring  offsets,         If the vector is too small to hold all the captured substring  offsets,
2375         it is used as far as possible (up to two-thirds of its length), and the         it is used as far as possible (up to two-thirds of its length), and the
2376         function returns a value of zero. In particular, if the substring  off-         function returns a value of zero. If the substring offsets are  not  of
2377         sets are not of interest, pcre_exec() may be called with ovector passed         interest,  pcre_exec()  may  be  called with ovector passed as NULL and
2378         as NULL and ovecsize as zero. However, if  the  pattern  contains  back         ovecsize as zero. However, if the pattern contains back references  and
2379         references  and  the  ovector is not big enough to remember the related         the  ovector is not big enough to remember the related substrings, PCRE
2380         substrings, PCRE has to get additional memory for use during  matching.         has to get additional memory for use during matching. Thus it  is  usu-
2381         Thus it is usually advisable to supply an ovector.         ally advisable to supply an ovector.
2382    
2383         The  pcre_info()  function  can  be used to find out how many capturing         The pcre_fullinfo() function can be used to find out how many capturing
2384         subpatterns there are in a compiled  pattern.  The  smallest  size  for         subpatterns there are in a compiled  pattern.  The  smallest  size  for
2385         ovector  that  will allow for n captured substrings, in addition to the         ovector  that  will allow for n captured substrings, in addition to the
2386         offsets 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.
# Line 1883  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2396  MATCHING A PATTERN: THE TRADITIONAL FUNC
2396         expression are also set to -1. For example,  if  the  string  "abc"  is         expression are also set to -1. For example,  if  the  string  "abc"  is
2397         matched  against the pattern (abc)(x(yz)?)? subpatterns 2 and 3 are not         matched  against the pattern (abc)(x(yz)?)? subpatterns 2 and 3 are not
2398         matched. The return from the function is 2, because  the  highest  used         matched. The return from the function is 2, because  the  highest  used
2399         capturing subpattern number is 1. However, you can refer to the offsets         capturing  subpattern  number  is 1, and the offsets for for the second
2400         for the second and third capturing subpatterns if  you  wish  (assuming         and third capturing subpatterns (assuming the vector is  large  enough,
2401         the vector is large enough, of course).         of course) are set to -1.
2402    
2403           Note: Elements of ovector that do not correspond to capturing parenthe-
2404           ses in the pattern are never changed. That is, if a pattern contains  n
2405           capturing parentheses, no more than ovector[0] to ovector[2n+1] are set
2406           by pcre_exec(). The other elements retain whatever values  they  previ-
2407           ously had.
2408    
2409         Some  convenience  functions  are  provided for extracting the captured         Some  convenience  functions  are  provided for extracting the captured
2410         substrings as separate strings. These are described below.         substrings as separate strings. These are described below.
# Line 1930  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2449  MATCHING A PATTERN: THE TRADITIONAL FUNC
2449         purpose.  If the call via pcre_malloc() fails, this error is given. The         purpose.  If the call via pcre_malloc() fails, this error is given. The
2450         memory is automatically freed at the end of matching.         memory is automatically freed at the end of matching.
2451    
2452           This error is also given if pcre_stack_malloc() fails  in  pcre_exec().
2453           This  can happen only when PCRE has been compiled with --disable-stack-
2454           for-recursion.
2455    
2456           PCRE_ERROR_NOSUBSTRING    (-7)           PCRE_ERROR_NOSUBSTRING    (-7)
2457    
2458         This error is used by the pcre_copy_substring(),  pcre_get_substring(),         This error is used by the pcre_copy_substring(),  pcre_get_substring(),
# Line 1951  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2474  MATCHING A PATTERN: THE TRADITIONAL FUNC
2474           PCRE_ERROR_BADUTF8        (-10)           PCRE_ERROR_BADUTF8        (-10)
2475    
2476         A string that contains an invalid UTF-8 byte sequence was passed  as  a         A string that contains an invalid UTF-8 byte sequence was passed  as  a
2477         subject.         subject,  and the PCRE_NO_UTF8_CHECK option was not set. If the size of
2478           the output vector (ovecsize) is at least 2,  the  byte  offset  to  the
2479           start  of  the  the invalid UTF-8 character is placed in the first ele-
2480           ment, and a reason code is placed in the  second  element.  The  reason
2481           codes are listed in the following section.  For backward compatibility,
2482           if PCRE_PARTIAL_HARD is set and the problem is a truncated UTF-8  char-
2483           acter   at   the   end   of   the   subject  (reason  codes  1  to  5),
2484           PCRE_ERROR_SHORTUTF8 is returned instead of PCRE_ERROR_BADUTF8.
2485    
2486           PCRE_ERROR_BADUTF8_OFFSET (-11)           PCRE_ERROR_BADUTF8_OFFSET (-11)
2487    
2488         The UTF-8 byte sequence that was passed as a subject was valid, but the         The UTF-8 byte sequence that was passed as a subject  was  checked  and
2489           found  to be valid (the PCRE_NO_UTF8_CHECK option was not set), but the
2490         value of startoffset did not point to the beginning of a UTF-8  charac-         value of startoffset did not point to the beginning of a UTF-8  charac-
2491         ter.         ter or the end of the subject.
2492    
2493           PCRE_ERROR_PARTIAL        (-12)           PCRE_ERROR_PARTIAL        (-12)
2494    
# Line 1966  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2497  MATCHING A PATTERN: THE TRADITIONAL FUNC
2497    
2498           PCRE_ERROR_BADPARTIAL     (-13)           PCRE_ERROR_BADPARTIAL     (-13)
2499    
2500         The PCRE_PARTIAL option was used with  a  compiled  pattern  containing         This code is no longer in  use.  It  was  formerly  returned  when  the
2501         items  that are not supported for partial matching. See the pcrepartial         PCRE_PARTIAL  option  was used with a compiled pattern containing items
2502         documentation for details of partial matching.         that were  not  supported  for  partial  matching.  From  release  8.00
2503           onwards, there are no restrictions on partial matching.
2504    
2505           PCRE_ERROR_INTERNAL       (-14)           PCRE_ERROR_INTERNAL       (-14)
2506    
2507         An unexpected internal error has occurred. This error could  be  caused         An  unexpected  internal error has occurred. This error could be caused
2508         by a bug in PCRE or by overwriting of the compiled pattern.         by a bug in PCRE or by overwriting of the compiled pattern.
2509    
2510           PCRE_ERROR_BADCOUNT       (-15)           PCRE_ERROR_BADCOUNT       (-15)
2511    
2512         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.
2513    
2514           PCRE_ERROR_RECURSIONLIMIT (-21)           PCRE_ERROR_RECURSIONLIMIT (-21)
2515    
# Line 1985  MATCHING A PATTERN: THE TRADITIONAL FUNC Line 2517  MATCHING A PATTERN: THE TRADITIONAL FUNC
2517         field  in  a  pcre_extra  structure (or defaulted) was reached. See the         field  in  a  pcre_extra  structure (or defaulted) was reached. See the
2518         description above.         description above.
2519    
          PCRE_ERROR_NULLWSLIMIT    (-22)  
   
        When a group that can match an empty  substring  is  repeated  with  an  
        unbounded  upper  limit, the subject position at the start of the group  
        must be remembered, so that a test for an empty string can be made when  
        the  end  of the group is reached. Some workspace is required for this;  
        if it runs out, this error is given.  
   
2520           PCRE_ERROR_BADNEWLINE     (-23)           PCRE_ERROR_BADNEWLINE     (-23)
2521    
2522         An invalid combination of PCRE_NEWLINE_xxx options was given.         An invalid combination of PCRE_NEWLINE_xxx options was given.
2523    
2524         Error numbers -16 to -20 are not used by pcre_exec().           PCRE_ERROR_BADOFFSET      (-24)
2525    
2526           The value of startoffset was negative or greater than the length of the
2527           subject, that is, the value in length.
2528    
2529             PCRE_ERROR_SHORTUTF8      (-25)
2530    
2531           This  error  is returned instead of PCRE_ERROR_BADUTF8 when the subject
2532           string ends with a truncated UTF-8 character and the  PCRE_PARTIAL_HARD
2533           option  is  set.   Information  about  the  failure  is returned as for
2534           PCRE_ERROR_BADUTF8. It is in fact sufficient to detect this  case,  but
2535           this  special error code for PCRE_PARTIAL_HARD precedes the implementa-
2536           tion of returned information; it is retained for backwards  compatibil-
2537           ity.
2538    
2539             PCRE_ERROR_RECURSELOOP    (-26)
2540    
2541           This error is returned when pcre_exec() detects a recursion loop within
2542           the pattern. Specifically, it means that either the whole pattern or  a
2543           subpattern  has been called recursively for the second time at the same
2544           position in the subject string. Some simple patterns that might do this
2545           are  detected  and faulted at compile time, but more complicated cases,
2546           in particular mutual recursions between two different subpatterns, can-
2547           not be detected until run time.
2548    
2549           Error numbers -16 to -20 and -22 are not used by pcre_exec().
2550    
2551       Reason codes for invalid UTF-8 strings
2552    
2553           When pcre_exec() returns either PCRE_ERROR_BADUTF8 or PCRE_ERROR_SHORT-
2554           UTF8, and the size of the output vector (ovecsize) is at least  2,  the
2555           offset  of  the  start  of the invalid UTF-8 character is placed in the
2556           first output vector element (ovector[0]) and a reason code is placed in
2557           the  second  element  (ovector[1]). The reason codes are given names in
2558           the pcre.h header file:
2559    
2560             PCRE_UTF8_ERR1
2561             PCRE_UTF8_ERR2
2562             PCRE_UTF8_ERR3
2563             PCRE_UTF8_ERR4
2564             PCRE_UTF8_ERR5
2565    
2566           The string ends with a truncated UTF-8 character;  the  code  specifies
2567           how  many bytes are missing (1 to 5). Although RFC 3629 restricts UTF-8
2568           characters to be no longer than 4 bytes, the  encoding  scheme  (origi-
2569           nally  defined  by  RFC  2279)  allows  for  up to 6 bytes, and this is
2570           checked first; hence the possibility of 4 or 5 missing bytes.
2571    
2572             PCRE_UTF8_ERR6
2573             PCRE_UTF8_ERR7
2574             PCRE_UTF8_ERR8
2575             PCRE_UTF8_ERR9
2576             PCRE_UTF8_ERR10
2577    
2578           The two most significant bits of the 2nd, 3rd, 4th, 5th, or 6th byte of
2579           the  character  do  not have the binary value 0b10 (that is, either the
2580           most significant bit is 0, or the next bit is 1).
2581    
2582             PCRE_UTF8_ERR11
2583             PCRE_UTF8_ERR12
2584    
2585           A character that is valid by the RFC 2279 rules is either 5 or 6  bytes
2586           long; these code points are excluded by RFC 3629.
2587    
2588             PCRE_UTF8_ERR13
2589    
2590           A  4-byte character has a value greater than 0x10fff; these code points
2591           are excluded by RFC 3629.
2592    
2593             PCRE_UTF8_ERR14
2594    
2595           A 3-byte character has a value in the  range  0xd800  to  0xdfff;  this
2596           range  of code points are reserved by RFC 3629 for use with UTF-16, and
2597           so are excluded from UTF-8.
2598    
2599             PCRE_UTF8_ERR15
2600             PCRE_UTF8_ERR16
2601             PCRE_UTF8_ERR17
2602             PCRE_UTF8_ERR18
2603             PCRE_UTF8_ERR19
2604    
2605           A 2-, 3-, 4-, 5-, or 6-byte character is "overlong", that is, it  codes
2606           for  a  value that can be represented by fewer bytes, which is invalid.
2607           For example, the two bytes 0xc0, 0xae give the value 0x2e,  whose  cor-
2608           rect coding uses just one byte.
2609    
2610             PCRE_UTF8_ERR20
2611    
2612           The two most significant bits of the first byte of a character have the
2613           binary value 0b10 (that is, the most significant bit is 1 and the  sec-
2614           ond  is  0). Such a byte can only validly occur as the second or subse-
2615           quent byte of a multi-byte character.
2616    
2617             PCRE_UTF8_ERR21
2618    
2619           The first byte of a character has the value 0xfe or 0xff. These  values
2620           can never occur in a valid UTF-8 string.
2621    
2622    
2623  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
# Line 2013  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER Line 2633  EXTRACTING CAPTURED SUBSTRINGS BY NUMBER
2633         int pcre_get_substring_list(const char *subject,         int pcre_get_substring_list(const char *subject,
2634              int *ovector, int stringcount, const char ***listptr);              int *ovector, int stringcount, const char ***listptr);
2635    
2636         Captured substrings can be  accessed  directly  by  using  the  offsets         Captured  substrings  can  be  accessed  directly  by using the offsets
2637         returned  by  pcre_exec()  in  ovector.  For convenience, the functions         returned by pcre_exec() in  ovector.  For  convenience,  the  functions
2638         pcre_copy_substring(),    pcre_get_substring(),    and    pcre_get_sub-         pcre_copy_substring(),    pcre_get_substring(),    and    pcre_get_sub-
2639         string_list()  are  provided for extracting captured substrings as new,         string_list() are provided for extracting captured substrings  as  new,
2640         separate, zero-terminated strings. These functions identify  substrings         separate,  zero-terminated strings. These functions identify substrings
2641         by  number.  The  next section describes functions for extracting named         by number. The next section describes functions  for  extracting  named
2642         substrings.         substrings.
2643    
2644         A substring that contains a binary zero is correctly extracted and  has         A  substring that contains a binary zero is correctly extracted and has
2645         a  further zero added on the end, but the result is not, of course, a C         a further zero added on the end, but the result is not, of course, a  C
2646         string.  However, you can process such a string  by  referring  to  the         string.   However,  you  can  process such a string by referring to the
2647         length  that  is  returned  by  pcre_copy_substring() and pcre_get_sub-         length that is  returned  by  pcre_copy_substring()  and  pcre_get_sub-
2648         string().  Unfortunately, the interface to pcre_get_substring_list() is         string().  Unfortunately, the interface to pcre_get_substring_list() is
2649         not  adequate for handling strings containing binary zeros, because the         not adequate for handling strings containing binary zeros, because  the
2650         end of the final string is not independently indicated.         end of the final string is not independently indicated.
2651    
2652         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-
2653         tions:  subject  is  the subject string that has just been successfully         tions: subject is the subject string that has  just  been  successfully
2654         matched, ovector is a pointer to the vector of integer offsets that was         matched, ovector is a pointer to the vector of integer offsets that was
2655         passed to pcre_exec(), and stringcount is the number of substrings that         passed to pcre_exec(), and stringcount is the number of substrings that
2656         were captured by the match, including the substring  that  matched  the         were  captured  by  the match, including the substring that matched the
2657         entire regular expression. This is the value returned by pcre_exec() if         entire regular expression. This is the value returned by pcre_exec() if
2658         it is greater than zero. If pcre_exec() returned zero, indicating  that         it  is greater than zero. If pcre_exec() returned zero, indicating that
2659         it  ran out of space in ovector, the value passed as stringcount should         it ran out of space in ovector, the value passed as stringcount  should
2660         be the number of elements in the vector divided by three.         be the number of elements in the vector divided by three.
2661    
2662         The functions pcre_copy_substring() and pcre_get_substring() extract  a         The  functions pcre_copy_substring() and pcre_get_substring() extract a
2663         single  substring,  whose  number  is given as stringnumber. A value of         single substring, whose number is given as  stringnumber.  A  value  of
2664         zero extracts the substring that matched the  entire  pattern,  whereas         zero  extracts  the  substring that matched the entire pattern, whereas
2665         higher  values  extract  the  captured  substrings.  For pcre_copy_sub-         higher values  extract  the  captured  substrings.  For  pcre_copy_sub-
2666         string(), the string is placed in buffer,  whose  length  is  given  by         string(),  the  string  is  placed  in buffer, whose length is given by
2667         buffersize,  while  for  pcre_get_substring()  a new block of memory is         buffersize, while for pcre_get_substring() a new  block  of  memory  is
2668         obtained via pcre_malloc, and its address is  returned  via  stringptr.         obtained  via  pcre_malloc,  and its address is returned via stringptr.
2669         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
2670         the terminating zero, or one of these error codes:         the terminating zero, or one of these error codes:
2671    
2672           PCRE_ERROR_NOMEMORY       (-6)           PCRE_ERROR_NOMEMORY       (-6)
2673    
2674         The buffer was too small for pcre_copy_substring(), or the  attempt  to         The  buffer  was too small for pcre_copy_substring(), or the attempt to
2675         get memory failed for pcre_get_substring().         get memory failed for pcre_get_substring().
2676    
2677           PCRE_ERROR_NOSUBSTRING    (-7)           PCRE_ERROR_NOSUBSTRING    (-7)
2678    
2679         There is no substring whose number is stringnumber.         There is no substring whose number is stringnumber.
2680    
2681         The  pcre_get_substring_list()  function  extracts  all  available sub-         The pcre_get_substring_list()  function  extracts  all  available  sub-
2682         strings and builds a list of pointers to them. All this is  done  in  a         strings  and  builds  a list of pointers to them. All this is done in a
2683         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
2684         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
2685         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
2686         pointer. The yield of the function is zero if all  went  well,  or  the         pointer.  The  yield  of  the function is zero if all went well, or the
2687         error code         error code
2688    
2689           PCRE_ERROR_NOMEMORY       (-6)           PCRE_ERROR_NOMEMORY       (-6)
2690    
2691         if the attempt to get the memory block failed.         if the attempt to get the memory block failed.
2692    
2693         When  any of these functions encounter a substring that is unset, which         When any of these functions encounter a substring that is unset,  which
2694         can happen when capturing subpattern number n+1 matches  some  part  of         can  happen  when  capturing subpattern number n+1 matches some part of
2695         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
2696         empty string. This can be distinguished from a genuine zero-length sub-         empty string. This can be distinguished from a genuine zero-length sub-
2697         string  by inspecting the appropriate offset in ovector, which is nega-         string by inspecting the appropriate offset in ovector, which is  nega-
2698         tive for unset substrings.         tive for unset substrings.
2699    
2700         The two convenience functions pcre_free_substring() and  pcre_free_sub-         The  two convenience functions pcre_free_substring() and pcre_free_sub-
2701         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
2702         call  of  pcre_get_substring()  or  pcre_get_substring_list(),  respec-         call  of  pcre_get_substring()  or  pcre_get_substring_list(),  respec-
2703         tively.  They  do  nothing  more  than  call the function pointed to by         tively. They do nothing more than  call  the  function  pointed  to  by
2704         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.
2705         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-
2706         cial  interface  to  another  programming  language  that  cannot   use         cial   interface  to  another  programming  language  that  cannot  use
2707         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-
2708         vided.         vided.
2709    
2710    
# Line 2103  EXTRACTING CAPTURED SUBSTRINGS BY NAME Line 2723  EXTRACTING CAPTURED SUBSTRINGS BY NAME
2723              int stringcount, const char *stringname,              int stringcount, const char *stringname,
2724              const char **stringptr);              const char **stringptr);
2725    
2726         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-
2727         ber.  For example, for this pattern         ber.  For example, for this pattern
2728    
2729           (a+)b(?<xxx>\d+)...           (a+)b(?<xxx>\d+)...
# Line 2112  EXTRACTING CAPTURED SUBSTRINGS BY NAME Line 2732  EXTRACTING CAPTURED SUBSTRINGS BY NAME
2732         be unique (PCRE_DUPNAMES was not set), you can find the number from the         be unique (PCRE_DUPNAMES was not set), you can find the number from the
2733         name by calling pcre_get_stringnumber(). The first argument is the com-         name by calling pcre_get_stringnumber(). The first argument is the com-
2734         piled pattern, and the second is the name. The yield of the function is         piled pattern, and the second is the name. The yield of the function is
2735         the  subpattern  number,  or PCRE_ERROR_NOSUBSTRING (-7) if there is no         the subpattern number, or PCRE_ERROR_NOSUBSTRING (-7) if  there  is  no
2736         subpattern of that name.         subpattern of that name.
2737    
2738         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
2739         the functions described in the previous section. For convenience, there         the functions described in the previous section. For convenience, there
2740         are also two functions that do the whole job.         are also two functions that do the whole job.
2741    
2742         Most   of   the   arguments    of    pcre_copy_named_substring()    and         Most    of    the    arguments   of   pcre_copy_named_substring()   and
2743         pcre_get_named_substring()  are  the  same  as  those for the similarly         pcre_get_named_substring() are the same  as  those  for  the  similarly
2744         named functions that extract by number. As these are described  in  the         named  functions  that extract by number. As these are described in the
2745         previous  section,  they  are not re-described here. There are just two         previous section, they are not re-described here. There  are  just  two
2746         differences:         differences:
2747    
2748         First, instead of a substring number, a substring name is  given.  Sec-         First,  instead  of a substring number, a substring name is given. Sec-
2749         ond, there is an extra argument, given at the start, which is a pointer         ond, there is an extra argument, given at the start, which is a pointer
2750         to the compiled pattern. This is needed in order to gain access to  the         to  the compiled pattern. This is needed in order to gain access to the
2751         name-to-number translation table.         name-to-number translation table.
2752    
2753         These  functions call pcre_get_stringnumber(), and if it succeeds, they         These functions call pcre_get_stringnumber(), and if it succeeds,  they
2754         then call pcre_copy_substring() or pcre_get_substring(),  as  appropri-         then  call  pcre_copy_substring() or pcre_get_substring(), as appropri-
2755         ate.         ate. NOTE: If PCRE_DUPNAMES is set and there are duplicate  names,  the
2756           behaviour may not be what you want (see the next section).
2757    
2758           Warning: If the pattern uses the (?| feature to set up multiple subpat-
2759           terns with the same number, as described in the  section  on  duplicate
2760           subpattern  numbers  in  the  pcrepattern page, you cannot use names to
2761           distinguish the different subpatterns, because names are  not  included
2762           in  the compiled code. The matching process uses only numbers. For this
2763           reason, the use of different names for subpatterns of the  same  number
2764           causes an error at compile time.
2765    
2766    
2767  DUPLICATE SUBPATTERN NAMES  DUPLICATE SUBPATTERN NAMES
# Line 2141  DUPLICATE SUBPATTERN NAMES Line 2770  DUPLICATE SUBPATTERN NAMES
2770              const char *name, char **first, char **last);              const char *name, char **first, char **last);
2771    
2772         When  a  pattern  is  compiled with the PCRE_DUPNAMES option, names for         When  a  pattern  is  compiled with the PCRE_DUPNAMES option, names for
2773         subpatterns are not required to  be  unique.  Normally,  patterns  with         subpatterns are not required to be unique. (Duplicate names are  always
2774         duplicate  names  are such that in any one match, only one of the named         allowed  for subpatterns with the same number, created by using the (?|
2775         subpatterns participates. An example is shown in the pcrepattern  docu-         feature. Indeed, if such subpatterns are named, they  are  required  to
2776         mentation. When duplicates are present, pcre_copy_named_substring() and         use the same names.)
2777    
2778           Normally, patterns with duplicate names are such that in any one match,
2779           only one of the named subpatterns participates. An example is shown  in
2780           the pcrepattern documentation.
2781    
2782           When    duplicates   are   present,   pcre_copy_named_substring()   and
2783         pcre_get_named_substring() return the first substring corresponding  to         pcre_get_named_substring() return the first substring corresponding  to
2784         the  given  name  that  is  set.  If  none  are set, an empty string is         the  given  name  that  is set. If none are set, PCRE_ERROR_NOSUBSTRING
2785         returned.  The pcre_get_stringnumber() function returns one of the num-         (-7) is returned; no  data  is  returned.  The  pcre_get_stringnumber()
2786         bers  that are associated with the name, but it is not defined which it         function  returns one of the numbers that are associated with the name,
2787         is.         but it is not defined which it is.
2788    
2789         If you want to get full details of all captured substrings for a  given         If you want to get full details of all captured substrings for a  given
2790         name,  you  must  use  the pcre_get_stringtable_entries() function. The         name,  you  must  use  the pcre_get_stringtable_entries() function. The
# Line 2159  DUPLICATE SUBPATTERN NAMES Line 2794  DUPLICATE SUBPATTERN NAMES
2794         the  name-to-number  table  for  the  given  name.  The function itself         the  name-to-number  table  for  the  given  name.  The function itself
2795         returns the length of each entry,  or  PCRE_ERROR_NOSUBSTRING  (-7)  if         returns the length of each entry,  or  PCRE_ERROR_NOSUBSTRING  (-7)  if
2796         there  are none. The format of the table is described above in the sec-         there  are none. The format of the table is described above in the sec-
2797         tion entitled Information about a  pattern.   Given  all  the  relevant         tion entitled Information about a pattern above.  Given all  the  rele-
2798         entries  for the name, you can extract each of their numbers, and hence         vant  entries  for the name, you can extract each of their numbers, and
2799         the captured data, if any.         hence the captured data, if any.
2800    
2801    
2802  FINDING ALL POSSIBLE MATCHES  FINDING ALL POSSIBLE MATCHES
# Line 2195  MATCHING A PATTERN: THE ALTERNATIVE FUNC Line 2830  MATCHING A PATTERN: THE ALTERNATIVE FUNC
2830         characteristics to the normal algorithm, and  is  not  compatible  with         characteristics to the normal algorithm, and  is  not  compatible  with
2831         Perl.  Some  of the features of PCRE patterns are not supported. Never-         Perl.  Some  of the features of PCRE patterns are not supported. Never-
2832         theless, there are times when this kind of matching can be useful.  For         theless, there are times when this kind of matching can be useful.  For
2833         a discussion of the two matching algorithms, see the pcrematching docu-         a  discussion  of  the  two matching algorithms, and a list of features
2834         mentation.         that pcre_dfa_exec() does not support, see the pcrematching  documenta-
2835           tion.
2836    
2837         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
2838         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-
2839         ent way, and this is described below. The other  common  arguments  are         ent  way,  and  this is described below. The other common arguments are
2840         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
2841         repeated here.         repeated here.
2842    
2843         The two additional arguments provide workspace for  the  function.  The         The  two  additional  arguments provide workspace for the function. The
2844         workspace  vector  should  contain at least 20 elements. It is used for         workspace vector should contain at least 20 elements. It  is  used  for
2845         keeping  track  of  multiple  paths  through  the  pattern  tree.  More         keeping  track  of  multiple  paths  through  the  pattern  tree.  More
2846         workspace  will  be  needed for patterns and subjects where there are a         workspace will be needed for patterns and subjects where  there  are  a
2847         lot of potential matches.         lot of potential matches.
2848    
2849         Here is an example of a simple call to pcre_dfa_exec():         Here is an example of a simple call to pcre_dfa_exec():
# Line 2229  MATCHING A PATTERN: THE ALTERNATIVE FUNC Line 2865  MATCHING A PATTERN: THE ALTERNATIVE FUNC
2865    
2866     Option bits for pcre_dfa_exec()     Option bits for pcre_dfa_exec()
2867    
2868         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
2869         zero.  The  only  bits  that  may  be  set are PCRE_ANCHORED, PCRE_NEW-         zero. The only bits  that  may  be  set  are  PCRE_ANCHORED,  PCRE_NEW-
2870         LINE_xxx, PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY,  PCRE_NO_UTF8_CHECK,         LINE_xxx,        PCRE_NOTBOL,        PCRE_NOTEOL,        PCRE_NOTEMPTY,
2871         PCRE_PARTIAL, PCRE_DFA_SHORTEST, and PCRE_DFA_RESTART. All but the last         PCRE_NOTEMPTY_ATSTART,      PCRE_NO_UTF8_CHECK,       PCRE_BSR_ANYCRLF,
2872         three of these are the same as for pcre_exec(), so their description is         PCRE_BSR_UNICODE,  PCRE_NO_START_OPTIMIZE, PCRE_PARTIAL_HARD, PCRE_PAR-
2873         not repeated here.         TIAL_SOFT, PCRE_DFA_SHORTEST, and PCRE_DFA_RESTART.  All but  the  last
2874           four  of  these  are  exactly  the  same  as  for pcre_exec(), so their
2875           PCRE_PARTIAL         description is not repeated here.
2876    
2877         This  has  the  same general effect as it does for pcre_exec(), but the           PCRE_PARTIAL_HARD
2878         details  are  slightly  different.  When  PCRE_PARTIAL   is   set   for           PCRE_PARTIAL_SOFT
2879         pcre_dfa_exec(),  the  return code PCRE_ERROR_NOMATCH is converted into  
2880         PCRE_ERROR_PARTIAL if the end of the subject  is  reached,  there  have         These have the same general effect as they do for pcre_exec(), but  the
2881         been no complete matches, but there is still at least one matching pos-         details  are  slightly  different.  When  PCRE_PARTIAL_HARD  is set for
2882         sibility. The portion of the string that provided the partial match  is         pcre_dfa_exec(), it returns PCRE_ERROR_PARTIAL if the end of  the  sub-
2883         set as the first matching string.         ject  is  reached  and there is still at least one matching possibility
2884           that requires additional characters. This happens even if some complete
2885           matches have also been found. When PCRE_PARTIAL_SOFT is set, the return
2886           code PCRE_ERROR_NOMATCH is converted into PCRE_ERROR_PARTIAL if the end
2887           of  the  subject  is  reached, there have been no complete matches, but
2888           there is still at least one matching possibility. The  portion  of  the
2889           string  that  was inspected when the longest partial match was found is
2890           set as the first matching string  in  both  cases.   There  is  a  more
2891           detailed  discussion  of partial and multi-segment matching, with exam-
2892           ples, in the pcrepartial documentation.
2893    
2894           PCRE_DFA_SHORTEST           PCRE_DFA_SHORTEST
2895    
2896         Setting  the  PCRE_DFA_SHORTEST option causes the matching algorithm to         Setting the PCRE_DFA_SHORTEST option causes the matching  algorithm  to
2897         stop as soon as it has found one match. Because of the way the alterna-         stop as soon as it has found one match. Because of the way the alterna-
2898         tive  algorithm  works, this is necessarily the shortest possible match         tive algorithm works, this is necessarily the shortest  possible  match
2899         at the first possible matching point in the subject string.         at the first possible matching point in the subject string.
2900    
2901           PCRE_DFA_RESTART           PCRE_DFA_RESTART
2902    
2903         When pcre_dfa_exec()  is  called  with  the  PCRE_PARTIAL  option,  and         When pcre_dfa_exec() returns a partial match, it is possible to call it
2904         returns  a  partial  match, it is possible to call it again, with addi-         again, with additional subject characters, and have  it  continue  with
2905         tional subject characters, and have it continue with  the  same  match.         the  same match. The PCRE_DFA_RESTART option requests this action; when
2906         The  PCRE_DFA_RESTART  option requests this action; when it is set, the         it is set, the workspace and wscount options must  reference  the  same
2907         workspace and wscount options must reference the same vector as  before         vector  as  before  because data about the match so far is left in them
2908         because  data  about  the  match so far is left in them after a partial         after a partial match. There is more discussion of this facility in the
2909         match. There is more discussion of this  facility  in  the  pcrepartial         pcrepartial documentation.
        documentation.  
2910    
2911     Successful returns from pcre_dfa_exec()     Successful returns from pcre_dfa_exec()
2912    
# Line 2339  MATCHING A PATTERN: THE ALTERNATIVE FUNC Line 2983  MATCHING A PATTERN: THE ALTERNATIVE FUNC
2983  SEE ALSO  SEE ALSO
2984    
2985         pcrebuild(3), pcrecallout(3), pcrecpp(3)(3), pcrematching(3),  pcrepar-         pcrebuild(3), pcrecallout(3), pcrecpp(3)(3), pcrematching(3),  pcrepar-
2986         tial(3),  pcreposix(3), pcreprecompile(3), pcresample(3), pcrestack(3).         tial(3), pcreposix(3), pcreprecompile(3), pcresample(3), pcrestack(3).
2987    
2988    
2989  AUTHOR  AUTHOR
# Line 2351  AUTHOR Line 2995  AUTHOR
2995    
2996  REVISION  REVISION
2997    
2998         Last updated: 06 March 2007         Last updated: 13 August 2011
2999         Copyright (c) 1997-2007 University of Cambridge.         Copyright (c) 1997-2011 University of Cambridge.
3000  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
3001    
3002    
3003  PCRECALLOUT(3)                                                  PCRECALLOUT(3)  PCRECALLOUT(3)                                                  PCRECALLOUT(3)
3004    
3005    
# Line 2379  PCRE CALLOUTS Line 3023  PCRE CALLOUTS
3023         default value is zero.  For  example,  this  pattern  has  two  callout         default value is zero.  For  example,  this  pattern  has  two  callout
3024         points:         points:
3025    
3026           (?C1)eabc(?C2)def           (?C1)abc(?C2)def
3027    
3028         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() or
3029         called, PCRE automatically  inserts  callouts,  all  with  number  255,         pcre_compile2() is called, PCRE  automatically  inserts  callouts,  all
3030         before  each  item in the pattern. For example, if PCRE_AUTO_CALLOUT is         with  number  255,  before  each  item  in the pattern. For example, if
3031         used with the pattern         PCRE_AUTO_CALLOUT is used with the pattern
3032    
3033           A(\d{2}|--)           A(\d{2}|--)
3034    
# Line 2403  PCRE CALLOUTS Line 3047  PCRE CALLOUTS
3047  MISSING CALLOUTS  MISSING CALLOUTS
3048    
3049         You  should  be  aware  that,  because of optimizations in the way PCRE         You  should  be  aware  that,  because of optimizations in the way PCRE
3050         matches patterns, callouts sometimes do not happen. For example, if the         matches patterns by default, callouts  sometimes  do  not  happen.  For
3051         pattern is         example, if the pattern is
3052    
3053           ab(?C4)cd           ab(?C4)cd
3054    
# Line 2413  MISSING CALLOUTS Line 3057  MISSING CALLOUTS
3057         ever  start,  and  the  callout is never reached. However, with "abyd",         ever  start,  and  the  callout is never reached. However, with "abyd",
3058         though the result is still no match, the callout is obeyed.         though the result is still no match, the callout is obeyed.
3059    
3060           If the pattern is studied, PCRE knows the minimum length of a  matching
3061           string,  and will immediately give a "no match" return without actually
3062           running a match if the subject is not long enough, or,  for  unanchored
3063           patterns, if it has been scanned far enough.
3064    
3065           You  can disable these optimizations by passing the PCRE_NO_START_OPTI-
3066           MIZE option to pcre_compile(), pcre_exec(), or pcre_dfa_exec(),  or  by
3067           starting the pattern with (*NO_START_OPT). This slows down the matching
3068           process, but does ensure that callouts such as the  example  above  are
3069           obeyed.
3070    
3071    
3072  THE CALLOUT INTERFACE  THE CALLOUT INTERFACE
3073    
3074         During matching, when PCRE reaches a callout point, the external  func-         During  matching, when PCRE reaches a callout point, the external func-
3075         tion  defined by pcre_callout is called (if it is set). This applies to         tion defined by pcre_callout is called (if it is set). This applies  to
3076         both the pcre_exec() and the pcre_dfa_exec()  matching  functions.  The         both  the  pcre_exec()  and the pcre_dfa_exec() matching functions. The
3077         only  argument  to  the callout function is a pointer to a pcre_callout         only argument to the callout function is a pointer  to  a  pcre_callout
3078         block. This structure contains the following fields:         block. This structure contains the following fields:
3079    
3080           int          version;           int         version;
3081           int          callout_number;           int         callout_number;
3082           int         *offset_vector;           int        *offset_vector;
3083           const char  *subject;           const char *subject;
3084           int          subject_length;           int         subject_length;
3085           int          start_match;           int         start_match;
3086           int          current_position;           int         current_position;
3087           int          capture_top;           int         capture_top;
3088           int          capture_last;           int         capture_last;
3089           void        *callout_data;           void       *callout_data;
3090           int          pattern_position;           int         pattern_position;
3091           int          next_item_length;           int         next_item_length;
3092             const unsigned char *mark;
3093         The version field is an integer containing the version  number  of  the  
3094         block  format. The initial version was 0; the current version is 1. The         The  version  field  is an integer containing the version number of the
3095         version number will change again in future  if  additional  fields  are         block format. The initial version was 0; the current version is 2.  The
3096           version  number  will  change  again in future if additional fields are
3097         added, but the intention is never to remove any of the existing fields.         added, but the intention is never to remove any of the existing fields.
3098    
3099         The callout_number field contains the number of the  callout,  as  com-         The callout_number field contains the number of the  callout,  as  com-
# Line 2454  THE CALLOUT INTERFACE Line 3110  THE CALLOUT INTERFACE
3110         The subject and subject_length fields contain copies of the values that         The subject and subject_length fields contain copies of the values that
3111         were passed to pcre_exec().         were passed to pcre_exec().
3112    
3113         The start_match field contains the offset within the subject  at  which         The start_match field normally contains the offset within  the  subject
3114         the  current match attempt started. If the pattern is not anchored, the         at  which  the  current  match  attempt started. However, if the escape
3115         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
3116         pattern for different starting points in the subject.         modified  starting  point.  If the pattern is not anchored, the callout
3117           function may be called several times from the same point in the pattern
3118           for different starting points in the subject.
3119    
3120         The  current_position  field  contains the offset within the subject of         The  current_position  field  contains the offset within the subject of
3121         the current match pointer.         the current match pointer.
# Line 2494  THE CALLOUT INTERFACE Line 3152  THE CALLOUT INTERFACE
3152         in  distinguishing between different automatic callouts, which all have         in  distinguishing between different automatic callouts, which all have
3153         the same callout number. However, they are set for all callouts.         the same callout number. However, they are set for all callouts.
3154    
3155           The mark field is present from version 2 of the pcre_callout structure.
3156           In  callouts  from pcre_exec() it contains a pointer to the zero-termi-
3157           nated name of the most recently passed (*MARK) item in  the  match,  or
3158           NULL if there are no (*MARK)s in the current matching path. In callouts
3159           from pcre_dfa_exec() this field always contains NULL.
3160    
3161    
3162  RETURN VALUES  RETURN VALUES
3163    
# Line 2502  RETURN VALUES Line 3166  RETURN VALUES
3166         zero, matching fails at the current point, but  the  testing  of  other         zero, matching fails at the current point, but  the  testing  of  other
3167         matching possibilities goes ahead, just as if a lookahead assertion had         matching possibilities goes ahead, just as if a lookahead assertion had
3168         failed. If the value is less than zero, the  match  is  abandoned,  and         failed. If the value is less than zero, the  match  is  abandoned,  and
3169         pcre_exec() (or pcre_dfa_exec()) returns the negative value.         pcre_exec() or pcre_dfa_exec() returns the negative value.
3170    
3171         Negative   values   should   normally   be   chosen  from  the  set  of         Negative   values   should   normally   be   chosen  from  the  set  of
3172         PCRE_ERROR_xxx values. In particular, PCRE_ERROR_NOMATCH forces a stan-         PCRE_ERROR_xxx values. In particular, PCRE_ERROR_NOMATCH forces a stan-
# Line 2520  AUTHOR Line 3184  AUTHOR
3184    
3185  REVISION  REVISION
3186    
3187         Last updated: 06 March 2007         Last updated: 31 July 2011
3188         Copyright (c) 1997-2007 University of Cambridge.         Copyright (c) 1997-2011 University of Cambridge.
3189  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
3190    
3191    
3192  PCRECOMPAT(3)                                                    PCRECOMPAT(3)  PCRECOMPAT(3)                                                    PCRECOMPAT(3)
3193    
3194    
# Line 2535  NAME Line 3199  NAME
3199  DIFFERENCES BETWEEN PCRE AND PERL  DIFFERENCES BETWEEN PCRE AND PERL
3200    
3201         This  document describes the differences in the ways that PCRE and Perl         This  document describes the differences in the ways that PCRE and Perl
3202         handle regular expressions. The differences described here  are  mainly         handle regular expressions. The differences  described  here  are  with
3203         with  respect  to  Perl 5.8, though PCRE version 7.0 contains some fea-         respect to Perl versions 5.10 and above.
        tures that are expected to be in the forthcoming Perl 5.10.  
3204    
3205         1. PCRE has only a subset of Perl's UTF-8 and Unicode support.  Details         1.  PCRE has only a subset of Perl's UTF-8 and Unicode support. Details
3206         of  what  it does have are given in the section on UTF-8 support in the         of what it does have are given in the section on UTF-8 support  in  the
3207         main pcre page.         main pcre page.
3208    
3209         2. PCRE does not allow repeat quantifiers on lookahead assertions. Perl         2. PCRE allows repeat quantifiers only on parenthesized assertions, but
3210         permits  them,  but they do not mean what you might think. For example,         they do not mean what you might think. For example, (?!a){3}  does  not
3211         (?!a){3} does not assert that the next three characters are not "a". It         assert that the next three characters are not "a". It just asserts that
3212         just asserts that the next character is not "a" three times.         the next character is not "a" three times (in principle: PCRE optimizes
3213           this to run the assertion just once). Perl allows repeat quantifiers on
3214         3.  Capturing  subpatterns  that occur inside negative lookahead asser-         other assertions such as \b, but these do not seem to have any use.
3215         tions are counted, but their entries in the offsets  vector  are  never  
3216         set.  Perl sets its numerical variables from any such patterns that are         3. Capturing subpatterns that occur inside  negative  lookahead  asser-
3217           tions  are  counted,  but their entries in the offsets vector are never
3218           set. Perl sets its numerical variables from any such patterns that  are
3219         matched before the assertion fails to match something (thereby succeed-         matched before the assertion fails to match something (thereby succeed-
3220         ing),  but  only  if the negative lookahead assertion contains just one         ing), but only if the negative lookahead assertion  contains  just  one
3221         branch.         branch.
3222    
3223         4. Though binary zero characters are supported in the  subject  string,         4.  Though  binary zero characters are supported in the subject string,
3224         they are not allowed in a pattern string because it is passed as a nor-         they are not allowed in a pattern string because it is passed as a nor-
3225         mal C string, terminated by zero. The escape sequence \0 can be used in         mal C string, terminated by zero. The escape sequence \0 can be used in
3226         the pattern to represent a binary zero.         the pattern to represent a binary zero.
3227    
3228         5.  The  following Perl escape sequences are not supported: \l, \u, \L,         5. The following Perl escape sequences are not supported: \l,  \u,  \L,
3229         \U, and \N. In fact these are implemented by Perl's general string-han-         \U,  and  \N when followed by a character name or Unicode value. (\N on
3230         dling  and are not part of its pattern matching engine. If any of these         its own, matching a non-newline character, is supported.) In fact these
3231         are encountered by PCRE, an error is generated.         are  implemented  by Perl's general string-handling and are not part of
3232           its pattern matching engine. If any of these are encountered  by  PCRE,
3233         6. The Perl escape sequences \p, \P, and \X are supported only if  PCRE         an error is generated.
3234         is  built  with Unicode character property support. The properties that  
3235         can be tested with \p and \P are limited to the general category  prop-         6.  The Perl escape sequences \p, \P, and \X are supported only if PCRE
3236         erties  such  as  Lu and Nd, script names such as Greek or Han, and the         is built with Unicode character property support. The  properties  that
3237         derived properties Any and L&.         can  be tested with \p and \P are limited to the general category prop-
3238           erties such as Lu and Nd, script names such as Greek or  Han,  and  the
3239           derived  properties  Any  and  L&. PCRE does support the Cs (surrogate)
3240           property, which Perl does not; the  Perl  documentation  says  "Because
3241           Perl hides the need for the user to understand the internal representa-
3242           tion of Unicode characters, there is no need to implement the  somewhat
3243           messy concept of surrogates."
3244    
3245           7.  PCRE implements a simpler version of \X than Perl, which changed to
3246           make \X match what Unicode calls an "extended grapheme  cluster".  This
3247           is  more  complicated  than an extended Unicode sequence, which is what
3248           PCRE matches.
3249    
3250         7. PCRE does support the \Q...\E escape for quoting substrings. Charac-         8. PCRE does support the \Q...\E escape for quoting substrings. Charac-
3251         ters  in  between  are  treated as literals. This is slightly different         ters  in  between  are  treated as literals. This is slightly different
3252         from Perl in that $ and @ are  also  handled  as  literals  inside  the         from Perl in that $ and @ are  also  handled  as  literals  inside  the
3253         quotes.  In Perl, they cause variable interpolation (but of course PCRE         quotes.  In Perl, they cause variable interpolation (but of course PCRE
# Line 2587  DIFFERENCES BETWEEN PCRE AND PERL Line 3263  DIFFERENCES BETWEEN PCRE AND PERL
3263         The \Q...\E sequence is recognized both inside  and  outside  character         The \Q...\E sequence is recognized both inside  and  outside  character
3264         classes.         classes.
3265    
3266         8. Fairly obviously, PCRE does not support the (?{code}) and (??{code})         9. Fairly obviously, PCRE does not support the (?{code}) and (??{code})
3267         constructions. However, there is support for recursive  patterns.  This         constructions. However, there is support for recursive  patterns.  This
3268         is  not available in Perl 5.8, but will be in Perl 5.10. Also, the PCRE         is  not  available  in Perl 5.8, but it is in Perl 5.10. Also, the PCRE
3269         "callout" feature allows an external function to be called during  pat-         "callout" feature allows an external function to be called during  pat-
3270         tern matching. See the pcrecallout documentation for details.         tern matching. See the pcrecallout documentation for details.
3271    
3272         9.  Subpatterns  that  are  called  recursively or as "subroutines" are         10.  Subpatterns  that  are  called recursively or as "subroutines" are
3273         always treated as atomic groups in  PCRE.  This  is  like  Python,  but         always treated as atomic groups in  PCRE.  This  is  like  Python,  but
3274         unlike Perl.         unlike  Perl. There is a discussion of an example that explains this in
3275           more detail in the section on recursion differences from  Perl  in  the
3276           pcrepattern page.
3277    
3278         10.  There are some differences that are concerned with the settings of         11.  There are some differences that are concerned with the settings of
3279         captured strings when part of  a  pattern  is  repeated.  For  example,         captured strings when part of  a  pattern  is  repeated.  For  example,
3280         matching  "aba"  against  the  pattern  /^(a(b)?)+$/  in Perl leaves $2         matching  "aba"  against  the  pattern  /^(a(b)?)+$/  in Perl leaves $2
3281         unset, but in PCRE it is set to "b".         unset, but in PCRE it is set to "b".
3282    
3283         11. PCRE provides some extensions to the Perl regular expression facil-         12. PCRE's handling of duplicate subpattern numbers and duplicate  sub-
3284         ities.   Perl  5.10  will  include new features that are not in earlier         pattern names is not as general as Perl's. This is a consequence of the
3285         versions, some of which (such as named parentheses) have been  in  PCRE         fact the PCRE works internally just with numbers, using an external ta-
3286         for some time. This list is with respect to Perl 5.10:         ble  to  translate  between numbers and names. In particular, a pattern
3287           such as (?|(?<a>A)|(?<b)B), where the two  capturing  parentheses  have
3288         (a)  Although  lookbehind  assertions  must match fixed length strings,         the  same  number  but different names, is not supported, and causes an
3289         each alternative branch of a lookbehind assertion can match a different         error at compile time. If it were allowed, it would not be possible  to
3290         length of string. Perl requires them all to have the same length.         distinguish  which  parentheses matched, because both names map to cap-
3291           turing subpattern number 1. To avoid this confusing situation, an error
3292           is given at compile time.
3293    
3294           13.  Perl  recognizes  comments  in some places that PCRE does not, for
3295           example, between the ( and ? at the start of a subpattern.  If  the  /x
3296           modifier  is set, Perl allows whitespace between ( and ? but PCRE never
3297           does, even if the PCRE_EXTENDED option is set.
3298    
3299           14. PCRE provides some extensions to the Perl regular expression facil-
3300           ities.   Perl  5.10  includes new features that are not in earlier ver-
3301           sions of Perl, some of which (such as named parentheses) have  been  in
3302           PCRE for some time. This list is with respect to Perl 5.10:
3303    
3304           (a)  Although  lookbehind  assertions  in  PCRE must match fixed length
3305           strings, each alternative branch of a lookbehind assertion can match  a
3306           different  length  of  string.  Perl requires them all to have the same
3307           length.
3308    
3309         (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  $
3310         meta-character matches only at the very end of the string.         meta-character matches only at the very end of the string.
3311    
3312         (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-
3313         cial  meaning  is  faulted.  Otherwise,  like  Perl,  the  backslash is         cial meaning is faulted. Otherwise, like Perl, the backslash is quietly
3314         ignored. (Perl can be made to issue a warning.)         ignored.  (Perl can be made to issue a warning.)
3315    
3316         (d) If PCRE_UNGREEDY is set, the greediness of the  repetition  quanti-         (d)  If  PCRE_UNGREEDY is set, the greediness of the repetition quanti-
3317         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-
3318         lowed by a question mark they are.         lowed by a question mark they are.
3319    
3320         (e) PCRE_ANCHORED can be used at matching time to force a pattern to be         (e) PCRE_ANCHORED can be used at matching time to force a pattern to be
3321         tried only at the first matching position in the subject string.         tried only at the first matching position in the subject string.
3322    
3323         (f)  The PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, and PCRE_NO_AUTO_CAP-         (f) The PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NOTEMPTY_ATSTART,
3324         TURE options for pcre_exec() have no Perl equivalents.         and  PCRE_NO_AUTO_CAPTURE  options for pcre_exec() have no Perl equiva-
3325           lents.
3326    
3327           (g) The \R escape sequence can be restricted to match only CR,  LF,  or
3328           CRLF by the PCRE_BSR_ANYCRLF option.
3329    
3330         (g) The callout facility is PCRE-specific.         (h) The callout facility is PCRE-specific.
3331    
3332         (h) The partial matching facility is PCRE-specific.         (i) The partial matching facility is PCRE-specific.
3333    
3334         (i) Patterns compiled by PCRE can be saved and re-used at a later time,         (j) Patterns compiled by PCRE can be saved and re-used at a later time,
3335         even on different hosts that have the other endianness.         even on different hosts that have the other endianness.
3336    
3337         (j)  The  alternative  matching function (pcre_dfa_exec()) matches in a         (k) The alternative matching function (pcre_dfa_exec())  matches  in  a
3338         different way and is not Perl-compatible.         different way and is not Perl-compatible.
3339    
3340           (l)  PCRE  recognizes some special sequences such as (*CR) at the start
3341           of a pattern that set overall options that cannot be changed within the
3342           pattern.
3343    
3344    
3345  AUTHOR  AUTHOR
3346    
# Line 2648  AUTHOR Line 3351  AUTHOR
3351    
3352  REVISION  REVISION
3353    
3354         Last updated: 06 March 2007         Last updated: 24 July 2011
3355         Copyright (c) 1997-2007 University of Cambridge.         Copyright (c) 1997-2011 University of Cambridge.
3356  ------------------------------------------------------------------------------  ------------------------------------------------------------------------------
3357    
3358    
3359  PCREPATTERN(3)                                                  PCREPATTERN(3)  PCREPATTERN(3)                                                  PCREPATTERN(3)
3360    
3361    
# Line 2662  NAME Line 3365  NAME
3365    
3366  PCRE REGULAR EXPRESSION DETAILS  PCRE REGULAR EXPRESSION DETAILS
3367    
3368         The  syntax  and semantics of the regular expressions supported by PCRE         The  syntax and semantics of the regular expressions that are supported
3369         are described below. Regular expressions are also described in the Perl         by PCRE are described in detail below. There is a quick-reference  syn-
3370         documentation  and  in  a  number  of books, some of which have copious         tax summary in the pcresyntax page. PCRE tries to match Perl syntax and
3371         examples.  Jeffrey Friedl's "Mastering Regular Expressions",  published         semantics as closely as it can. PCRE  also  supports  some  alternative
3372         by  O'Reilly, covers regular expressions in great detail. This descrip-         regular  expression  syntax (which does not conflict with the Perl syn-
3373         tion of PCRE's regular expressions is intended as reference material.         tax) in order to provide some compatibility with regular expressions in
3374           Python, .NET, and Oniguruma.
3375    
3376           Perl's  regular expressions are described in its own documentation, and
3377           regular expressions in general are covered in a number of  books,  some
3378           of  which  have  copious  examples. Jeffrey Friedl's "Mastering Regular
3379           Expressions", published by  O'Reilly,  covers  regular  expressions  in
3380           great  detail.  This  description  of  PCRE's  regular  expressions  is
3381           intended as reference material.
3382    
3383         The original operation of PCRE was on strings of  one-byte  characters.         The original operation of PCRE was on strings of  one-byte  characters.
3384         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
3385         this, you must build PCRE to  include  UTF-8  support,  and  then  call         this, PCRE must be built to include UTF-8 support, and  you  must  call
3386         pcre_compile()  with  the  PCRE_UTF8  option.  How this affects pattern         pcre_compile()  or  pcre_compile2() with the PCRE_UTF8 option. There is
3387         matching is mentioned in several places below. There is also a  summary         also a special sequence that can be given at the start of a pattern:
3388         of  UTF-8  features  in  the  section on UTF-8 support in the main pcre  
3389         page.           (*UTF8)
3390    
3391           Starting a pattern with this sequence  is  equivalent  to  setting  the
3392           PCRE_UTF8  option.  This  feature  is  not Perl-compatible. How setting
3393           UTF-8 mode affects pattern matching  is  mentioned  in  several  places
3394           below.  There  is  also  a  summary of UTF-8 features in the section on
3395           UTF-8 support in the main pcre page.
3396    
3397         The remainder of this document discusses the  patterns  that  are  sup-         Another special sequence that may appear at the start of a  pattern  or
3398         ported  by  PCRE when its main matching function, pcre_exec(), is used.         in combination with (*UTF8) is:
3399         From  release  6.0,   PCRE   offers   a   second   matching   function,  
3400         pcre_dfa_exec(),  which matches using a different algorithm that is not           (*UCP)
3401         Perl-compatible. The advantages and disadvantages  of  the  alternative  
3402         function, and how it differs from the normal function, are discussed in         This  has  the  same  effect  as setting the PCRE_UCP option: it causes
3403         the pcrematching page.         sequences such as \d and \w to  use  Unicode  properties  to  determine
3404           character types, instead of recognizing only characters with codes less
3405           than 128 via a lookup table.
3406    
3407           If a pattern starts with (*NO_START_OPT), it has  the  same  effect  as
3408           setting the PCRE_NO_START_OPTIMIZE option either at compile or matching
3409           time. There are also some more of these special sequences that are con-
3410           cerned with the handling of newlines; they are described below.
3411    
3412           The  remainder  of  this  document discusses the patterns that are sup-
3413           ported by PCRE when its main matching function, pcre_exec(),  is  used.
3414           From   release   6.0,   PCRE   offers   a   second  matching  function,
3415           pcre_dfa_exec(), which matches using a different algorithm that is  not
3416           Perl-compatible. Some of the features discussed below are not available
3417           when pcre_dfa_exec() is used. The advantages and disadvantages  of  the
3418           alternative  function, and how it differs from the normal function, are
3419           discussed in the pcrematching page.
3420    
3421    
3422    NEWLINE CONVENTIONS
3423    
3424           PCRE supports five different conventions for indicating line breaks  in
3425           strings:  a  single  CR (carriage return) character, a single LF (line-
3426           feed) character, the two-character sequence CRLF, any of the three pre-
3427           ceding,  or  any Unicode newline sequence. The pcreapi page has further
3428           discussion about newlines, and shows how to set the newline  convention
3429           in the options arguments for the compiling and matching functions.
3430    
3431           It  is also possible to specify a newline convention by starting a pat-
3432           tern string with one of the following five sequences:
3433    
3434             (*CR)        carriage return
3435             (*LF)        linefeed
3436             (*CRLF)      carriage return, followed by linefeed
3437             (*ANYCRLF)   any of the three above
3438             (*ANY)       all Unicode newline sequences
3439    
3440           These override the default and the options given to  pcre_compile()  or
3441           pcre_compile2().  For example, on a Unix system where LF is the default
3442           newline sequence, the pattern
3443    
3444             (*CR)a.b
3445    
3446           changes the convention to CR. That pattern matches "a\nb" because LF is
3447           no  longer  a  newline. Note that these special settings, which are not
3448           Perl-compatible, are recognized only at the very start  of  a  pattern,
3449           and  that  they  must  be  in  upper  case. If more than one of them is
3450           present, the last one is used.
3451    
3452           The newline convention affects the interpretation of the dot  metachar-
3453           acter  when  PCRE_DOTALL is not set, and also the behaviour of \N. How-
3454           ever, it does not affect  what  the  \R  escape  sequence  matches.  By
3455           default,  this is any Unicode newline sequence, for Perl compatibility.
3456           However, this can be changed; see the description of \R in the  section
3457           entitled  "Newline sequences" below. A change of \R setting can be com-
3458           bined with a change of newline convention.
3459    
3460    
3461  CHARACTERS AND METACHARACTERS  CHARACTERS AND METACHARACTERS
# Line 2741  CHARACTERS AND METACHARACTERS Line 3513  CHARACTERS AND METACHARACTERS
3513                    syntax)                    syntax)
3514           ]      terminates the character class           ]      terminates the character class
3515    
3516         The following sections describe the use of each of the  metacharacters.         The following sections describe the use of each of the metacharacters.
3517    
3518    
3519  BACKSLASH  BACKSLASH
3520    
3521         The backslash character has several uses. Firstly, if it is followed by         The backslash character has several uses. Firstly, if it is followed by
3522         a non-alphanumeric character, it takes away any  special  meaning  that         a character that is not a number or a letter, it takes away any special
3523         character  may  have.  This  use  of  backslash  as an escape character         meaning that character may have. This use of  backslash  as  an  escape
3524         applies both inside and outside character classes.         character applies both inside and outside character classes.
3525    
3526         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
3527         pattern.   This  escaping  action  applies whether or not the following         pattern.  This escaping action applies whether  or  not  the  following
3528         character would otherwise be interpreted as a metacharacter, so  it  is         character  would  otherwise be interpreted as a metacharacter, so it is
3529         always  safe  to  precede  a non-alphanumeric with backslash to specify         always safe to precede a non-alphanumeric  with  backslash  to  specify
3530         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-
3531         slash, you write \\.         slash, you write \\.
3532    
3533         If  a  pattern is compiled with the PCRE_EXTENDED option, whitespace in         In UTF-8 mode, only ASCII numbers and letters have any special  meaning
3534         the pattern (other than in a character class) and characters between  a         after  a  backslash.  All  other characters (in particular, those whose
3535           codepoints are greater than 127) are treated as literals.
3536    
3537           If a pattern is compiled with the PCRE_EXTENDED option,  whitespace  in
3538           the  pattern (other than in a character class) and characters between a
3539         # outside a character class and the next newline are ignored. An escap-         # outside a character class and the next newline are ignored. An escap-
3540         ing backslash can be used to include a whitespace  or  #  character  as         ing  backslash  can  be  used to include a whitespace or # character as
3541         part of the pattern.         part of the pattern.
3542    
3543         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-
3544         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-
3545         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
3546         sequences in PCRE, whereas in Perl, $ and @ cause  variable  interpola-         sequences  in  PCRE, whereas in Perl, $ and @ cause variable interpola-
3547         tion. Note the following examples:         tion. Note the following examples:
3548    
3549           Pattern            PCRE matches   Perl matches           Pattern            PCRE matches   Perl matches
# Line 2777  BACKSLASH Line 3553  BACKSLASH
3553           \Qabc\$xyz\E       abc\$xyz       abc\$xyz           \Qabc\$xyz\E       abc\$xyz       abc\$xyz
3554           \Qabc\E\$\Qxyz\E   abc$xyz        abc$xyz           \Qabc\E\$\Qxyz\E   abc$xyz        abc$xyz
3555    
3556         The  \Q...\E  sequence  is recognized both inside and outside character         The \Q...\E sequence is recognized both inside  and  outside  character
3557         classes.         classes.   An  isolated \E that is not preceded by \Q is ignored. If \Q
3558           is not followed by \E later in the pattern, the literal  interpretation
3559           continues  to  the  end  of  the pattern (that is, \E is assumed at the
3560           end). If the isolated \Q is inside a character class,  this  causes  an
3561           error, because the character class is not terminated.
3562    
3563     Non-printing characters     Non-printing characters
3564    
3565         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-
3566         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
3567         appearance of non-printing characters, apart from the binary zero  that         appearance  of non-printing characters, apart from the binary zero that
3568         terminates  a  pattern,  but  when  a pattern is being prepared by text         terminates a pattern, but when a pattern  is  being  prepared  by  text
3569         editing, it is usually easier  to  use  one  of  the  following  escape         editing,  it  is  often  easier  to  use  one  of  the following escape
3570         sequences than the binary character it represents:         sequences than the binary character it represents:
3571    
3572           \a        alarm, that is, the BEL character (hex 07)           \a        alarm, that is, the BEL character (hex 07)
3573           \cx       "control-x", where x is any character           \cx       "control-x", where x is any ASCII character
3574           \e        escape (hex 1B)           \e        escape (hex 1B)
3575           \f        formfeed (hex 0C)           \f        formfeed (hex 0C)
3576           \n        newline (hex 0A)           \n        linefeed (hex 0A)
3577           \r        carriage return (hex 0D)           \r        carriage return (hex 0D)
3578           \t        tab (hex 09)           \t        tab (hex 09)
3579           \ddd      character with octal code ddd, or backreference           \ddd      character with octal code ddd, or back reference
3580           \xhh      character with hex code hh           \xhh      character with hex code hh
3581           \x{hhh..} character with hex code hhh..           \x{hhh..} character with hex code hhh..
3582    
3583         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,
3584         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
3585         inverted.   Thus  \cz becomes hex 1A, but \c{ becomes hex 3B, while \c;         inverted.  Thus \cz becomes hex 1A (z is 7A), but \c{ becomes hex 3B ({
3586         becomes hex 7B.         is  7B),  while  \c; becomes hex 7B (; is 3B). If the byte following \c
3587           has a value greater than 127, a compile-time error occurs.  This  locks
3588         After \x, from zero to two hexadecimal digits are read (letters can  be         out  non-ASCII  characters in both byte mode and UTF-8 mode. (When PCRE
3589         in  upper  or  lower case). Any number of hexadecimal digits may appear         is compiled in EBCDIC mode, all byte values are  valid.  A  lower  case
3590         between \x{ and }, but the value of the character  code  must  be  less         letter is converted to upper case, and then the 0xc0 bits are flipped.)
3591         than 256 in non-UTF-8 mode, and less than 2**31 in UTF-8 mode (that is,  
3592         the maximum hexadecimal value is 7FFFFFFF). If  characters  other  than         After  \x, from zero to two hexadecimal digits are read (letters can be
3593         hexadecimal  digits  appear between \x{ and }, or if there is no termi-         in upper or lower case). Any number of hexadecimal  digits  may  appear
3594         nating }, this form of escape is not recognized.  Instead, the  initial         between  \x{  and  },  but the value of the character code must be less
3595         \x will be interpreted as a basic hexadecimal escape, with no following         than 256 in non-UTF-8 mode, and less than 2**31 in UTF-8 mode. That is,
3596         digits, giving a character whose value is zero.         the  maximum value in hexadecimal is 7FFFFFFF. Note that this is bigger
3597           than the largest Unicode code point, which is 10FFFF.
3598    
3599           If characters other than hexadecimal digits appear between \x{  and  },
3600           or if there is no terminating }, this form of escape is not recognized.
3601           Instead, the initial \x will be  interpreted  as  a  basic  hexadecimal
3602           escape,  with  no  following  digits, giving a character whose value is
3603           zero.
3604    
3605         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
3606         two  syntaxes  for  \x. There is no difference in the way they are han-         two  syntaxes  for  \x. There is no difference in the way they are han-
# Line 2862  BACKSLASH Line 3649  BACKSLASH
3649         All the sequences that define a single character value can be used both         All the sequences that define a single character value can be used both
3650         inside and outside character classes. In addition, inside  a  character         inside and outside character classes. In addition, inside  a  character
3651         class,  the  sequence \b is interpreted as the backspace character (hex         class,  the  sequence \b is interpreted as the backspace character (hex
3652         08), and the sequences \R and \X are interpreted as the characters  "R"         08). The sequences \B, \N, \R, and \X are not special inside a  charac-
3653         and  "X", respectively. Outside a character class, these sequences have         ter  class.  Like  any  other  unrecognized  escape sequences, they are
3654         different meanings (see below).         treated as the literal characters "B", "N", "R", and  "X"  by  default,
3655           but cause an error if the PCRE_EXTRA option is set. Outside a character
3656           class, these sequences have different meanings.
3657    
3658     Absolute and relative back references     Absolute and relative back references
3659    
3660         The sequence \g followed by a positive or negative  number,  optionally         The sequence \g followed by an unsigned or a negative  number,  option-
3661         enclosed  in  braces,  is  an absolute or relative back reference. Back         ally  enclosed  in braces, is an absolute or relative back reference. A
3662         references are discussed later, following the discussion  of  parenthe-         named back reference can be coded as \g{name}. Back references are dis-
3663         sized subpatterns.         cussed later, following the discussion of parenthesized subpatterns.
3664    
3665       Absolute and relative subroutine calls
3666    
3667           For  compatibility with Oniguruma, the non-Perl syntax \g followed by a
3668           name or a number enclosed either in angle brackets or single quotes, is
3669           an  alternative  syntax for referencing a subpattern as a "subroutine".
3670           Details are discussed later.   Note  that  \g{...}  (Perl  syntax)  and
3671           \g<...>  (Oniguruma  syntax)  are  not synonymous. The former is a back
3672           reference; the latter is a subroutine call.
3673    
3674     Generic character types     Generic character types
3675    
3676         Another use of backslash is for specifying generic character types. The         Another use of backslash is for specifying generic character types:
        following are always recognized:  
3677    
3678           \d     any decimal digit           \d     any decimal digit
3679           \D     any character that is not a decimal digit           \D     any character that is not a decimal digit
3680             \h     any horizontal whitespace character
3681             \H     any character that is not a horizontal whitespace character
3682           \s     any whitespace character           \s     any whitespace character
3683           \S     any character that is not a whitespace character           \S     any character that is not a whitespace character
3684             \v     any vertical whitespace character
3685             \V     any character that is not a vertical whitespace character
3686           \w     any "word" character           \w     any "word" character
3687           \W     any "non-word" character           \W     any "non-word" character
3688    
3689         Each pair of escape sequences partitions the complete set of characters         There is also the single sequence \N, which matches a non-newline char-
3690         into  two disjoint sets. Any given character matches one, and only one,         acter.   This  is the same as the "." metacharacter when PCRE_DOTALL is
3691         of each pair.         not set.
3692    
3693         These character type sequences can appear both inside and outside char-         Each pair of lower and upper case escape sequences partitions the  com-
3694         acter  classes.  They each match one character of the appropriate type.         plete  set  of  characters  into two disjoint sets. Any given character
3695         If the current matching point is at the end of the subject string,  all         matches one, and only one, of each pair. The sequences can appear  both
3696         of them fail, since there is no character to match.         inside  and outside character classes. They each match one character of
3697           the appropriate type. If the current matching point is at  the  end  of
3698         For  compatibility  with Perl, \s does not match the VT character (code         the  subject string, all of them fail, because there is no character to
3699         11).  This makes it different from the the POSIX "space" class. The  \s         match.
3700         characters  are  HT (9), LF (10), FF (12), CR (13), and space (32). (If  
3701           For compatibility with Perl, \s does not match the VT  character  (code
3702           11).   This makes it different from the the POSIX "space" class. The \s
3703           characters are HT (9), LF (10), FF (12), CR (13), and  space  (32).  If
3704         "use locale;" is included in a Perl script, \s may match the VT charac-         "use locale;" is included in a Perl script, \s may match the VT charac-
3705         ter. In PCRE, it never does.)         ter. In PCRE, it never does.
3706    
3707         A "word" character is an underscore or any character less than 256 that         A "word" character is an underscore or any character that is  a  letter
3708         is a letter or digit. The definition of  letters  and  digits  is  con-         or  digit.   By  default,  the definition of letters and digits is con-
3709         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-
3710         specific matching is taking place (see "Locale support" in the  pcreapi         specific  matching is taking place (see "Locale support" in the pcreapi
3711         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
3712         codes greater than 128 are used for accented  letters,  and  these  are         systems,  or "french" in Windows, some character codes greater than 128
3713         matched by \w.         are used for accented letters, and these are then matched  by  \w.  The
3714           use of locales with Unicode is discouraged.
3715         In  UTF-8 mode, characters with values greater than 128 never match \d,  
3716         \s, or \w, and always match \D, \S, and \W. This is true even when Uni-         By  default,  in  UTF-8  mode,  characters with values greater than 128
3717         code  character  property support is available. The use of locales with         never match \d, \s, or \w, and always  match  \D,  \S,  and  \W.  These
3718         Unicode is discouraged.         sequences  retain their original meanings from before UTF-8 support was
3719           available, mainly for efficiency reasons. However, if PCRE is  compiled
3720           with  Unicode property support, and the PCRE_UCP option is set, the be-
3721           haviour is changed so that Unicode properties  are  used  to  determine
3722           character types, as follows:
3723    
3724             \d  any character that \p{Nd} matches (decimal digit)
3725             \s  any character that \p{Z} matches, plus HT, LF, FF, CR
3726             \w  any character that \p{L} or \p{N} matches, plus underscore
3727    
3728           The  upper case escapes match the inverse sets of characters. Note that
3729           \d matches only decimal digits, whereas \w matches any  Unicode  digit,
3730           as  well as any Unicode letter, and underscore. Note also that PCRE_UCP
3731           affects \b, and \B because they are defined in  terms  of  \w  and  \W.
3732           Matching these sequences is noticeably slower when PCRE_UCP is set.
3733    
3734           The  sequences  \h, \H, \v, and \V are features that were added to Perl
3735           at release 5.10. In contrast to the other sequences, which  match  only
3736           ASCII  characters  by  default,  these always match certain high-valued
3737           codepoints in UTF-8 mode, whether or not PCRE_UCP is set. The  horizon-
3738           tal space characters are:
3739    
3740             U+0009     Horizontal tab
3741             U+0020     Space
3742             U+00A0     Non-break space
3743             U+1680     Ogham space mark
3744             U+180E     Mongolian vowel separator
3745             U+2000     En quad
3746             U+2001     Em quad
3747             U+2002     En space
3748             U+2003     Em space
3749             U+2004     Three-per-em space
3750             U+2005     Four-per-em space
3751             U+2006     Six-per-em space
3752             U+2007     Figure space
3753             U+2008     Punctuation space
3754             U+2009     Thin space
3755             U+200A     Hair space
3756             U+202F     Narrow no-break space
3757             U+205F     Medium mathematical space
3758             U+3000     Ideographic space
3759    
3760           The vertical space characters are:
3761    
3762             U+000A     Linefeed
3763             U+000B     Vertical tab
3764             U+000C     Formfeed
3765             U+000D     Carriage return
3766             U+0085     Next line
3767             U+2028     Line separator
3768             U+2029     Paragraph separator
3769    
3770     Newline sequences     Newline sequences
3771    
3772         Outside a character class, the escape sequence \R matches  any  Unicode         Outside  a  character class, by default, the escape sequence \R matches
3773         newline sequence. This is an extension to Perl. In non-UTF-8 mode \R is         any Unicode newline sequence. In non-UTF-8 mode \R is equivalent to the
3774         equivalent to the following:         following:
3775    
3776           (?>\r\n|\n|\x0b|\f|\r|\x85)           (?>\r\n|\n|\x0b|\f|\r|\x85)
3777    
3778         This is an example of an "atomic group", details  of  which  are  given         This  is  an  example  of an "atomic group", details of which are given
3779         below.  This particular group matches either the two-character sequence         below.  This particular group matches either the two-character sequence
3780         CR followed by LF, or  one  of  the  single  characters  LF  (linefeed,         CR  followed  by  LF,  or  one  of  the single characters LF (linefeed,
3781         U+000A), VT (vertical tab, U+000B), FF (formfeed, U+000C), CR (carriage         U+000A), VT (vertical tab, U+000B), FF (formfeed, U+000C), CR (carriage
3782         return, U+000D), or NEL (next line, U+0085). The two-character sequence         return, U+000D), or NEL (next line, U+0085). The two-character sequence
3783         is treated as a single unit that cannot be split.         is treated as a single unit that cannot be split.
3784    
3785         In  UTF-8  mode, two additional characters whose codepoints are greater         In UTF-8 mode, two additional characters whose codepoints  are  greater
3786         than 255 are added: LS (line separator, U+2028) and PS (paragraph sepa-         than 255 are added: LS (line separator, U+2028) and PS (paragraph sepa-
3787         rator,  U+2029).   Unicode character property support is not needed for         rator, U+2029).  Unicode character property support is not  needed  for
3788         these characters to be recognized.         these characters to be recognized.
3789    
3790         Inside a character class, \R matches the letter "R".         It is possible to restrict \R to match only CR, LF, or CRLF (instead of
3791           the complete set  of  Unicode  line  endings)  by  setting  the  option
3792           PCRE_BSR_ANYCRLF either at compile time or when the pattern is matched.
3793           (BSR is an abbrevation for "backslash R".) This can be made the default
3794           when  PCRE  is  built;  if this is the case, the other behaviour can be
3795           requested via the PCRE_BSR_UNICODE option.   It  is  also  possible  to
3796           specify  these  settings  by  starting a pattern string with one of the
3797           following sequences:
3798    
3799             (*BSR_ANYCRLF)   CR, LF, or CRLF only
3800             (*BSR_UNICODE)   any Unicode newline sequence
3801    
3802           These override the default and the options given to  pcre_compile()  or
3803           pcre_compile2(),  but  they  can  be  overridden  by  options  given to
3804           pcre_exec() or pcre_dfa_exec(). Note that these special settings, which
3805           are  not  Perl-compatible,  are  recognized only at the very start of a
3806           pattern, and that they must be in upper case. If more than one of  them
3807           is present, the last one is used. They can be combined with a change of
3808           newline convention; for example, a pattern can start with:
3809    
3810             (*ANY)(*BSR_ANYCRLF)
3811    
3812           They can also be combined with the (*UTF8) or (*UCP) special sequences.
3813           Inside  a  character  class,  \R  is  treated as an unrecognized escape
3814           sequence, and so matches the letter "R" by default, but causes an error
3815           if PCRE_EXTRA is set.
3816    
3817     Unicode character properties     Unicode character properties
3818    
3819         When PCRE is built with Unicode character property support, three addi-         When PCRE is built with Unicode character property support, three addi-
3820         tional  escape  sequences  to  match character properties are available         tional escape sequences that match characters with specific  properties
3821         when UTF-8 mode is selected. They are:         are  available.   When not in UTF-8 mode, these sequences are of course
3822           limited to testing characters whose codepoints are less than  256,  but
3823           they do work in this mode.  The extra escape sequences are:
3824    
3825           \p{xx}   a character with the xx property           \p{xx}   a character with the xx property
3826           \P{xx}   a character without the xx property           \P{xx}   a character without the xx property
3827           \X       an extended Unicode sequence           \X       an extended Unicode sequence
3828    
3829         The property names represented by xx above are limited to  the  Unicode         The  property  names represented by xx above are limited to the Unicode
3830         script names, the general category properties, and "Any", which matches         script names, the general category properties, "Any", which matches any
3831         any character (including newline). Other properties such as "InMusical-         character   (including  newline),  and  some  special  PCRE  properties
3832         Symbols"  are  not  currently supported by PCRE. Note that \P{Any} does         (described in the next section).  Other Perl properties such as  "InMu-
3833         not match any characters, so always causes a match failure.         sicalSymbols"  are  not  currently supported by PCRE. Note that \P{Any}
3834           does not match any characters, so always causes a match failure.
3835    
3836         Sets of Unicode characters are defined as belonging to certain scripts.         Sets of Unicode characters are defined as belonging to certain scripts.
3837         A  character from one of these sets can be matched using a script name.         A  character from one of these sets can be matched using a script name.
# Line 2961  BACKSLASH Line 3843  BACKSLASH
3843         Those that are not part of an identified script are lumped together  as         Those that are not part of an identified script are lumped together  as
3844         "Common". The current list of scripts is:         "Common". The current list of scripts is:
3845    
3846         Arabic,  Armenian,  Balinese,  Bengali,  Bopomofo,  Braille,  Buginese,         Arabic, Armenian, Avestan, Balinese, Bamum, Bengali, Bopomofo, Braille,
3847         Buhid,  Canadian_Aboriginal,  Cherokee,  Common,   Coptic,   Cuneiform,         Buginese, Buhid, Canadian_Aboriginal, Carian, Cham,  Cherokee,  Common,
3848         Cypriot, Cyrillic, Deseret, Devanagari, Ethiopic, Georgian, Glagolitic,         Coptic,   Cuneiform,  Cypriot,  Cyrillic,  Deseret,  Devanagari,  Egyp-
3849         Gothic, Greek, Gujarati, Gurmukhi, Han, Hangul, Hanunoo, Hebrew,  Hira-         tian_Hieroglyphs,  Ethiopic,  Georgian,  Glagolitic,   Gothic,   Greek,
3850         gana,  Inherited,  Kannada,  Katakana,  Kharoshthi,  Khmer, Lao, Latin,         Gujarati,  Gurmukhi,  Han,  Hangul,  Hanunoo,  Hebrew,  Hiragana, Impe-
3851         Limbu,  Linear_B,  Malayalam,  Mongolian,  Myanmar,  New_Tai_Lue,  Nko,         rial_Aramaic, Inherited, Inscriptional_Pahlavi, Inscriptional_Parthian,
3852         Ogham,  Old_Italic,  Old_Persian, Oriya, Osmanya, Phags_Pa, Phoenician,         Javanese,  Kaithi, Kannada, Katakana, Kayah_Li, Kharoshthi, Khmer, Lao,
3853         Runic,  Shavian,  Sinhala,  Syloti_Nagri,  Syriac,  Tagalog,  Tagbanwa,         Latin,  Lepcha,  Limbu,  Linear_B,  Lisu,  Lycian,  Lydian,  Malayalam,
3854         Tai_Le, Tamil, Telugu, Thaana, Thai, Tibetan, Tifinagh, Ugaritic, Yi.         Meetei_Mayek,  Mongolian, Myanmar, New_Tai_Lue, Nko, Ogham, Old_Italic,
3855           Old_Persian, Old_South_Arabian, Old_Turkic, Ol_Chiki,  Oriya,  Osmanya,
3856         Each  character has exactly one general category property, specified by         Phags_Pa,  Phoenician,  Rejang,  Runic, Samaritan, Saurashtra, Shavian,
3857