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

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

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

revision 776 by ph10, Thu Dec 1 11:02:56 2011 UTC revision 964 by ph10, Fri May 4 13:03:39 2012 UTC
# Line 1  Line 1 
1  .TH PCREAPI 3  .TH PCREAPI 3 "04 May 2012" "PCRE 8.31"
2  .SH NAME  .SH NAME
3  PCRE - Perl-compatible regular expressions  PCRE - Perl-compatible regular expressions
4    .sp
5    .B #include <pcre.h>
6    .
7    .
8  .SH "PCRE NATIVE API BASIC FUNCTIONS"  .SH "PCRE NATIVE API BASIC FUNCTIONS"
9  .rs  .rs
10  .sp  .sp
 .B #include <pcre.h>  
 .PP  
11  .SM  .SM
12  .B pcre *pcre_compile(const char *\fIpattern\fP, int \fIoptions\fP,  .B pcre *pcre_compile(const char *\fIpattern\fP, int \fIoptions\fP,
13  .ti +5n  .ti +5n
# Line 32  PCRE - Perl-compatible regular expressio Line 34  PCRE - Perl-compatible regular expressio
34  .B "const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,  .B "const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,
35  .ti +5n  .ti +5n
36  .B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);  .B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);
 .  
 .  
 .SH "PCRE NATIVE API AUXILIARY FUNCTIONS"  
 .rs  
 .sp  
 .B pcre_jit_stack *pcre_jit_stack_alloc(int \fIstartsize\fP, int \fImaxsize\fP);  
 .PP  
 .B void pcre_jit_stack_free(pcre_jit_stack *\fIstack\fP);  
 .PP  
 .B void pcre_assign_jit_stack(pcre_extra *\fIextra\fP,  
 .ti +5n  
 .B pcre_jit_callback \fIcallback\fP, void *\fIdata\fP);  
37  .PP  .PP
38  .B int pcre_dfa_exec(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"  .B int pcre_dfa_exec(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"
39  .ti +5n  .ti +5n
# Line 52  PCRE - Perl-compatible regular expressio Line 42  PCRE - Perl-compatible regular expressio
42  .B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,  .B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP,
43  .ti +5n  .ti +5n
44  .B int *\fIworkspace\fP, int \fIwscount\fP);  .B int *\fIworkspace\fP, int \fIwscount\fP);
45  .PP  .
46    .
47    .SH "PCRE NATIVE API STRING EXTRACTION FUNCTIONS"
48    .rs
49    .sp
50  .B int pcre_copy_named_substring(const pcre *\fIcode\fP,  .B int pcre_copy_named_substring(const pcre *\fIcode\fP,
51  .ti +5n  .ti +5n
52  .B const char *\fIsubject\fP, int *\fIovector\fP,  .B const char *\fIsubject\fP, int *\fIovector\fP,
# Line 96  PCRE - Perl-compatible regular expressio Line 90  PCRE - Perl-compatible regular expressio
90  .B void pcre_free_substring(const char *\fIstringptr\fP);  .B void pcre_free_substring(const char *\fIstringptr\fP);
91  .PP  .PP
92  .B void pcre_free_substring_list(const char **\fIstringptr\fP);  .B void pcre_free_substring_list(const char **\fIstringptr\fP);
93    .
94    .
95    .SH "PCRE NATIVE API AUXILIARY FUNCTIONS"
96    .rs
97    .sp
98    .B pcre_jit_stack *pcre_jit_stack_alloc(int \fIstartsize\fP, int \fImaxsize\fP);
99    .PP
100    .B void pcre_jit_stack_free(pcre_jit_stack *\fIstack\fP);
101    .PP
102    .B void pcre_assign_jit_stack(pcre_extra *\fIextra\fP,
103    .ti +5n
104    .B pcre_jit_callback \fIcallback\fP, void *\fIdata\fP);
105  .PP  .PP
106  .B const unsigned char *pcre_maketables(void);  .B const unsigned char *pcre_maketables(void);
107  .PP  .PP
# Line 103  PCRE - Perl-compatible regular expressio Line 109  PCRE - Perl-compatible regular expressio
109  .ti +5n  .ti +5n
110  .B int \fIwhat\fP, void *\fIwhere\fP);  .B int \fIwhat\fP, void *\fIwhere\fP);
111  .PP  .PP
 .B int pcre_info(const pcre *\fIcode\fP, int *\fIoptptr\fP, int  
 .B *\fIfirstcharptr\fP);  
 .PP  
112  .B int pcre_refcount(pcre *\fIcode\fP, int \fIadjust\fP);  .B int pcre_refcount(pcre *\fIcode\fP, int \fIadjust\fP);
113  .PP  .PP
114  .B int pcre_config(int \fIwhat\fP, void *\fIwhere\fP);  .B int pcre_config(int \fIwhat\fP, void *\fIwhere\fP);
115  .PP  .PP
116  .B char *pcre_version(void);  .B const char *pcre_version(void);
117    .PP
118    .B int pcre_pattern_to_host_byte_order(pcre *\fIcode\fP,
119    .ti +5n
120    .B pcre_extra *\fIextra\fP, const unsigned char *\fItables\fP);
121  .  .
122  .  .
123  .SH "PCRE NATIVE API INDIRECTED FUNCTIONS"  .SH "PCRE NATIVE API INDIRECTED FUNCTIONS"
# Line 127  PCRE - Perl-compatible regular expressio Line 134  PCRE - Perl-compatible regular expressio
134  .B int (*pcre_callout)(pcre_callout_block *);  .B int (*pcre_callout)(pcre_callout_block *);
135  .  .
136  .  .
137    .SH "PCRE 8-BIT AND 16-BIT LIBRARIES"
138    .rs
139    .sp
140    From release 8.30, PCRE can be compiled as a library for handling 16-bit
141    character strings as well as, or instead of, the original library that handles
142    8-bit character strings. To avoid too much complication, this document
143    describes the 8-bit versions of the functions, with only occasional references
144    to the 16-bit library.
145    .P
146    The 16-bit functions operate in the same way as their 8-bit counterparts; they
147    just use different data types for their arguments and results, and their names
148    start with \fBpcre16_\fP instead of \fBpcre_\fP. For every option that has UTF8
149    in its name (for example, PCRE_UTF8), there is a corresponding 16-bit name with
150    UTF8 replaced by UTF16. This facility is in fact just cosmetic; the 16-bit
151    option names define the same bit values.
152    .P
153    References to bytes and UTF-8 in this document should be read as references to
154    16-bit data quantities and UTF-16 when using the 16-bit library, unless
155    specified otherwise. More details of the specific differences for the 16-bit
156    library are given in the
157    .\" HREF
158    \fBpcre16\fP
159    .\"
160    page.
161    .
162    .
163  .SH "PCRE API OVERVIEW"  .SH "PCRE API OVERVIEW"
164  .rs  .rs
165  .sp  .sp
166  PCRE has its own native API, which is described in this document. There are  PCRE has its own native API, which is described in this document. There are
167  also some wrapper functions that correspond to the POSIX regular expression  also some wrapper functions (for the 8-bit library only) that correspond to the
168  API, but they do not give access to all the functionality. They are described  POSIX regular expression API, but they do not give access to all the
169  in the  functionality. They are described in the
170  .\" HREF  .\" HREF
171  \fBpcreposix\fP  \fBpcreposix\fP
172  .\"  .\"
173  documentation. Both of these APIs define a set of C function calls. A C++  documentation. Both of these APIs define a set of C function calls. A C++
174  wrapper is also distributed with PCRE. It is documented in the  wrapper (again for the 8-bit library only) is also distributed with PCRE. It is
175    documented in the
176  .\" HREF  .\" HREF
177  \fBpcrecpp\fP  \fBpcrecpp\fP
178  .\"  .\"
179  page.  page.
180  .P  .P
181  The native API C function prototypes are defined in the header file  The native API C function prototypes are defined in the header file
182  \fBpcre.h\fP, and on Unix systems the library itself is called \fBlibpcre\fP.  \fBpcre.h\fP, and on Unix-like systems the (8-bit) library itself is called
183  It can normally be accessed by adding \fB-lpcre\fP to the command for linking  \fBlibpcre\fP. It can normally be accessed by adding \fB-lpcre\fP to the
184  an application that uses PCRE. The header file defines the macros PCRE_MAJOR  command for linking an application that uses PCRE. The header file defines the
185  and PCRE_MINOR to contain the major and minor release numbers for the library.  macros PCRE_MAJOR and PCRE_MINOR to contain the major and minor release numbers
186  Applications can use these to include support for different releases of PCRE.  for the library. Applications can use these to include support for different
187    releases of PCRE.
188  .P  .P
189  In a Windows environment, if you want to statically link an application program  In a Windows environment, if you want to statically link an application program
190  against a non-dll \fBpcre.a\fP file, you must define PCRE_STATIC before  against a non-dll \fBpcre.a\fP file, you must define PCRE_STATIC before
# Line 218  specialist use. Most commonly, no specia Line 253  specialist use. Most commonly, no specia
253  internal tables that are generated when PCRE is built are used.  internal tables that are generated when PCRE is built are used.
254  .P  .P
255  The function \fBpcre_fullinfo()\fP is used to find out information about a  The function \fBpcre_fullinfo()\fP is used to find out information about a
256  compiled pattern; \fBpcre_info()\fP is an obsolete version that returns only  compiled pattern. The function \fBpcre_version()\fP returns a pointer to a
257  some of the available information, but is retained for backwards compatibility.  string containing the version of PCRE and its date of release.
 The function \fBpcre_version()\fP returns a pointer to a string containing the  
 version of PCRE and its date of release.  
258  .P  .P
259  The function \fBpcre_refcount()\fP maintains a reference count in a data block  The function \fBpcre_refcount()\fP maintains a reference count in a data block
260  containing a compiled pattern. This is provided for the benefit of  containing a compiled pattern. This is provided for the benefit of
# Line 332  which it was compiled. Details are given Line 365  which it was compiled. Details are given
365  .\" HREF  .\" HREF
366  \fBpcreprecompile\fP  \fBpcreprecompile\fP
367  .\"  .\"
368  documentation. However, compiling a regular expression with one version of PCRE  documentation, which includes a description of the
369  for use with a different version is not guaranteed to work and may cause  \fBpcre_pattern_to_host_byte_order()\fP function. However, compiling a regular
370  crashes.  expression with one version of PCRE for use with a different version is not
371    guaranteed to work and may cause crashes.
372  .  .
373  .  .
374  .SH "CHECKING BUILD-TIME OPTIONS"  .SH "CHECKING BUILD-TIME OPTIONS"
# Line 351  documentation has more details about the Line 385  documentation has more details about the
385  .P  .P
386  The first argument for \fBpcre_config()\fP is an integer, specifying which  The first argument for \fBpcre_config()\fP is an integer, specifying which
387  information is required; the second argument is a pointer to a variable into  information is required; the second argument is a pointer to a variable into
388  which the information is placed. The following information is available:  which the information is placed. The returned value is zero on success, or the
389    negative error code PCRE_ERROR_BADOPTION if the value in the first argument is
390    not recognized. The following information is available:
391  .sp  .sp
392    PCRE_CONFIG_UTF8    PCRE_CONFIG_UTF8
393  .sp  .sp
394  The output is an integer that is set to one if UTF-8 support is available;  The output is an integer that is set to one if UTF-8 support is available;
395  otherwise it is set to zero.  otherwise it is set to zero. If this option is given to the 16-bit version of
396    this function, \fBpcre16_config()\fP, the result is PCRE_ERROR_BADOPTION.
397    .sp
398      PCRE_CONFIG_UTF16
399    .sp
400    The output is an integer that is set to one if UTF-16 support is available;
401    otherwise it is set to zero. This value should normally be given to the 16-bit
402    version of this function, \fBpcre16_config()\fP. If it is given to the 8-bit
403    version of this function, the result is PCRE_ERROR_BADOPTION.
404  .sp  .sp
405    PCRE_CONFIG_UNICODE_PROPERTIES    PCRE_CONFIG_UNICODE_PROPERTIES
406  .sp  .sp
# Line 368  properties is available; otherwise it is Line 412  properties is available; otherwise it is
412  The output is an integer that is set to one if support for just-in-time  The output is an integer that is set to one if support for just-in-time
413  compiling is available; otherwise it is set to zero.  compiling is available; otherwise it is set to zero.
414  .sp  .sp
415      PCRE_CONFIG_JITTARGET
416    .sp
417    The output is a pointer to a zero-terminated "const char *" string. If JIT
418    support is available, the string contains the name of the architecture for
419    which the JIT compiler is configured, for example "x86 32bit (little endian +
420    unaligned)". If JIT support is not available, the result is NULL.
421    .sp
422    PCRE_CONFIG_NEWLINE    PCRE_CONFIG_NEWLINE
423  .sp  .sp
424  The output is an integer whose value specifies the default character sequence  The output is an integer whose value specifies the default character sequence
# Line 387  or CRLF. The default can be overridden w Line 438  or CRLF. The default can be overridden w
438    PCRE_CONFIG_LINK_SIZE    PCRE_CONFIG_LINK_SIZE
439  .sp  .sp
440  The output is an integer that contains the number of bytes used for internal  The output is an integer that contains the number of bytes used for internal
441  linkage in compiled regular expressions. The value is 2, 3, or 4. Larger values  linkage in compiled regular expressions. For the 8-bit library, the value can
442  allow larger regular expressions to be compiled, at the expense of slower  be 2, 3, or 4. For the 16-bit library, the value is either 2 or 4 and is still
443  matching. The default value of 2 is sufficient for all but the most massive  a number of bytes. The default value of 2 is sufficient for all but the most
444  patterns, since it allows the compiled pattern to be up to 64K in size.  massive patterns, since it allows the compiled pattern to be up to 64K in size.
445    Larger values allow larger regular expressions to be compiled, at the expense
446    of slower matching.
447  .sp  .sp
448    PCRE_CONFIG_POSIX_MALLOC_THRESHOLD    PCRE_CONFIG_POSIX_MALLOC_THRESHOLD
449  .sp  .sp
# Line 473  documentation). For those options that c Line 526  documentation). For those options that c
526  the pattern, the contents of the \fIoptions\fP argument specifies their  the pattern, the contents of the \fIoptions\fP argument specifies their
527  settings at the start of compilation and execution. The PCRE_ANCHORED,  settings at the start of compilation and execution. The PCRE_ANCHORED,
528  PCRE_BSR_\fIxxx\fP, PCRE_NEWLINE_\fIxxx\fP, PCRE_NO_UTF8_CHECK, and  PCRE_BSR_\fIxxx\fP, PCRE_NEWLINE_\fIxxx\fP, PCRE_NO_UTF8_CHECK, and
529  PCRE_NO_START_OPT options can be set at the time of matching as well as at  PCRE_NO_START_OPTIMIZE options can be set at the time of matching as well as at
530  compile time.  compile time.
531  .P  .P
532  If \fIerrptr\fP is NULL, \fBpcre_compile()\fP returns NULL immediately.  If \fIerrptr\fP is NULL, \fBpcre_compile()\fP returns NULL immediately.
# Line 484  not try to free it. Normally, the offset Line 537  not try to free it. Normally, the offset
537  byte that was being processed when the error was discovered is placed in the  byte that was being processed when the error was discovered is placed in the
538  variable pointed to by \fIerroffset\fP, which must not be NULL (if it is, an  variable pointed to by \fIerroffset\fP, which must not be NULL (if it is, an
539  immediate error is given). However, for an invalid UTF-8 string, the offset is  immediate error is given). However, for an invalid UTF-8 string, the offset is
540  that of the first byte of the failing character. Also, some errors are not  that of the first byte of the failing character.
 detected until checks are carried out when the whole pattern has been scanned;  
 in these cases the offset passed back is the length of the pattern.  
541  .P  .P
542  Note that the offset is in bytes, not characters, even in UTF-8 mode. It may  Some errors are not detected until the whole pattern has been scanned; in these
543  sometimes point into the middle of a UTF-8 character.  cases, the offset passed back is the length of the pattern. Note that the
544    offset is in bytes, not characters, even in UTF-8 mode. It may sometimes point
545    into the middle of a UTF-8 character.
546  .P  .P
547  If \fBpcre_compile2()\fP is used instead of \fBpcre_compile()\fP, and the  If \fBpcre_compile2()\fP is used instead of \fBpcre_compile()\fP, and the
548  \fIerrorcodeptr\fP argument is not NULL, a non-zero error code number is  \fIerrorcodeptr\fP argument is not NULL, a non-zero error code number is
# Line 644  string (by default this causes the curre Line 697  string (by default this causes the curre
697  pattern such as (\e1)(a) succeeds when this option is set (assuming it can find  pattern such as (\e1)(a) succeeds when this option is set (assuming it can find
698  an "a" in the subject), whereas it fails by default, for Perl compatibility.  an "a" in the subject), whereas it fails by default, for Perl compatibility.
699  .P  .P
700  (3) \eU matches an upper case "U" character; by default \eU causes a compile  (3) \eU matches an upper case "U" character; by default \eU causes a compile
701  time error (Perl uses \eU to upper case subsequent characters).  time error (Perl uses \eU to upper case subsequent characters).
702  .P  .P
703  (4) \eu matches a lower case "u" character unless it is followed by four  (4) \eu matches a lower case "u" character unless it is followed by four
704  hexadecimal digits, in which case the hexadecimal number defines the code point  hexadecimal digits, in which case the hexadecimal number defines the code point
705  to match. By default, \eu causes a compile time error (Perl uses it to upper  to match. By default, \eu causes a compile time error (Perl uses it to upper
706  case the following character).  case the following character).
707  .P  .P
708  (5) \ex matches a lower case "x" character unless it is followed by two  (5) \ex matches a lower case "x" character unless it is followed by two
709  hexadecimal digits, in which case the hexadecimal number defines the code point  hexadecimal digits, in which case the hexadecimal number defines the code point
710  to match. By default, as in Perl, a hexadecimal number is always expected after  to match. By default, as in Perl, a hexadecimal number is always expected after
711  \ex, but it may have zero, one, or two digits (so, for example, \exz matches a  \ex, but it may have zero, one, or two digits (so, for example, \exz matches a
712  binary zero character followed by z).  binary zero character followed by z).
713  .sp  .sp
714    PCRE_MULTILINE    PCRE_MULTILINE
# Line 689  preceding sequences should be recognized Line 742  preceding sequences should be recognized
742  that any Unicode newline sequence should be recognized. The Unicode newline  that any Unicode newline sequence should be recognized. The Unicode newline
743  sequences are the three just mentioned, plus the single characters VT (vertical  sequences are the three just mentioned, plus the single characters VT (vertical
744  tab, U+000B), FF (formfeed, U+000C), NEL (next line, U+0085), LS (line  tab, U+000B), FF (formfeed, U+000C), NEL (next line, U+0085), LS (line
745  separator, U+2028), and PS (paragraph separator, U+2029). The last two are  separator, U+2028), and PS (paragraph separator, U+2029). For the 8-bit
746  recognized only in UTF-8 mode.  library, the last two are recognized only in UTF-8 mode.
747  .P  .P
748  The newline setting in the options word uses three bits that are treated  The newline setting in the options word uses three bits that are treated
749  as a number, giving eight possibilities. Currently only six are used (default  as a number, giving eight possibilities. Currently only six are used (default
# Line 755  with Perl. It can also be set by a (?U) Line 808  with Perl. It can also be set by a (?U)
808    PCRE_UTF8    PCRE_UTF8
809  .sp  .sp
810  This option causes PCRE to regard both the pattern and the subject as strings  This option causes PCRE to regard both the pattern and the subject as strings
811  of UTF-8 characters instead of single-byte character strings. However, it is  of UTF-8 characters instead of single-byte strings. However, it is available
812  available only when PCRE is built to include UTF-8 support. If not, the use  only when PCRE is built to include UTF support. If not, the use of this option
813  of this option provokes an error. Details of how this option changes the  provokes an error. Details of how this option changes the behaviour of PCRE are
814  behaviour of PCRE are given in the  given in the
815  .\" HREF  .\" HREF
816  \fBpcreunicode\fP  \fBpcreunicode\fP
817  .\"  .\"
# Line 766  page. Line 819  page.
819  .sp  .sp
820    PCRE_NO_UTF8_CHECK    PCRE_NO_UTF8_CHECK
821  .sp  .sp
822  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
823  automatically checked. There is a discussion about the  string is automatically checked. There is a discussion about the
824  .\" HTML <a href="pcre.html#utf8strings">  .\" HTML <a href="pcreunicode.html#utf8strings">
825  .\" </a>  .\" </a>
826  validity of UTF-8 strings  validity of UTF-8 strings
827  .\"  .\"
828  in the main  in the
829  .\" HREF  .\" HREF
830  \fBpcre\fP  \fBpcreunicode\fP
831  .\"  .\"
832  page. If an invalid UTF-8 sequence of bytes is found, \fBpcre_compile()\fP  page. If an invalid UTF-8 sequence is found, \fBpcre_compile()\fP returns an
833  returns an error. If you already know that your pattern is valid, and you want  error. If you already know that your pattern is valid, and you want to skip
834  to skip this check for performance reasons, you can set the PCRE_NO_UTF8_CHECK  this check for performance reasons, you can set the PCRE_NO_UTF8_CHECK option.
835  option. When it is set, the effect of passing an invalid UTF-8 string as a  When it is set, the effect of passing an invalid UTF-8 string as a pattern is
836  pattern is undefined. It may cause your program to crash. Note that this option  undefined. It may cause your program to crash. Note that this option can also
837  can also be passed to \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP, to suppress  be passed to \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP, to suppress the
838  the UTF-8 validity checking of subject strings.  validity checking of subject strings.
839  .  .
840  .  .
841  .SH "COMPILATION ERROR CODES"  .SH "COMPILATION ERROR CODES"
# Line 790  the UTF-8 validity checking of subject s Line 843  the UTF-8 validity checking of subject s
843  .sp  .sp
844  The following table lists the error codes than may be returned by  The following table lists the error codes than may be returned by
845  \fBpcre_compile2()\fP, along with the error messages that may be returned by  \fBpcre_compile2()\fP, along with the error messages that may be returned by
846  both compiling functions. As PCRE has developed, some error codes have fallen  both compiling functions. Note that error messages are always 8-bit ASCII
847  out of use. To avoid confusion, they have not been re-used.  strings, even in 16-bit mode. As PCRE has developed, some error codes have
848    fallen out of use. To avoid confusion, they have not been re-used.
849  .sp  .sp
850     0  no error     0  no error
851     1  \e at end of pattern     1  \e at end of pattern
# Line 825  out of use. To avoid confusion, they hav Line 879  out of use. To avoid confusion, they hav
879    29  (?R or (?[+-]digits must be followed by )    29  (?R or (?[+-]digits must be followed by )
880    30  unknown POSIX class name    30  unknown POSIX class name
881    31  POSIX collating elements are not supported    31  POSIX collating elements are not supported
882    32  this version of PCRE is not compiled with PCRE_UTF8 support    32  this version of PCRE is compiled without UTF support
883    33  [this code is not in use]    33  [this code is not in use]
884    34  character value in \ex{...} sequence is too large    34  character value in \ex{...} sequence is too large
885    35  invalid condition (?(0)    35  invalid condition (?(0)
# Line 837  out of use. To avoid confusion, they hav Line 891  out of use. To avoid confusion, they hav
891    41  unrecognized character after (?P    41  unrecognized character after (?P
892    42  syntax error in subpattern name (missing terminator)    42  syntax error in subpattern name (missing terminator)
893    43  two named subpatterns have the same name    43  two named subpatterns have the same name
894    44  invalid UTF-8 string    44  invalid UTF-8 string (specifically UTF-8)
895    45  support for \eP, \ep, and \eX has not been compiled    45  support for \eP, \ep, and \eX has not been compiled
896    46  malformed \eP or \ep sequence    46  malformed \eP or \ep sequence
897    47  unknown property name after \eP or \ep    47  unknown property name after \eP or \ep
898    48  subpattern name is too long (maximum 32 characters)    48  subpattern name is too long (maximum 32 characters)
899    49  too many named subpatterns (maximum 10000)    49  too many named subpatterns (maximum 10000)
900    50  [this code is not in use]    50  [this code is not in use]
901    51  octal value is greater than \e377 (not in UTF-8 mode)    51  octal value is greater than \e377 in 8-bit non-UTF-8 mode
902    52  internal error: overran compiling workspace    52  internal error: overran compiling workspace
903    53  internal error: previously-checked referenced subpattern    53  internal error: previously-checked referenced subpattern
904          not found          not found
# Line 863  out of use. To avoid confusion, they hav Line 917  out of use. To avoid confusion, they hav
917    65  different names for subpatterns of the same number are    65  different names for subpatterns of the same number are
918          not allowed          not allowed
919    66  (*MARK) must have an argument    66  (*MARK) must have an argument
920    67  this version of PCRE is not compiled with PCRE_UCP support    67  this version of PCRE is not compiled with Unicode property
921            support
922    68  \ec must be followed by an ASCII character    68  \ec must be followed by an ASCII character
923    69  \ek is not followed by a braced, angle-bracketed, or quoted name    69  \ek is not followed by a braced, angle-bracketed, or quoted name
924      70  internal error: unknown opcode in find_fixedlength()
925      71  \eN is not supported in a class
926      72  too many forward references
927      73  disallowed Unicode code point (>= 0xd800 && <= 0xdfff)
928      74  invalid UTF-16 string (specifically UTF-16)
929      75  name is too long in (*MARK), (*PRUNE), (*SKIP), or (*THEN)
930  .sp  .sp
931  The numbers 32 and 10000 in errors 48 and 49 are defaults; different values may  The numbers 32 and 10000 in errors 48 and 49 are defaults; different values may
932  be used if the limits were changed when PCRE was built.  be used if the limits were changed when PCRE was built.
# Line 902  If studying the pattern does not produce Line 963  If studying the pattern does not produce
963  wants to pass any of the other fields to \fBpcre_exec()\fP or  wants to pass any of the other fields to \fBpcre_exec()\fP or
964  \fBpcre_dfa_exec()\fP, it must set up its own \fBpcre_extra\fP block.  \fBpcre_dfa_exec()\fP, it must set up its own \fBpcre_extra\fP block.
965  .P  .P
966  The second argument of \fBpcre_study()\fP contains option bits. There is only  The second argument of \fBpcre_study()\fP contains option bits. There are three
967  one option: PCRE_STUDY_JIT_COMPILE. If this is set, and the just-in-time  options:
968  compiler is available, the pattern is further compiled into machine code that  .sp
969  executes much faster than the \fBpcre_exec()\fP matching function. If    PCRE_STUDY_JIT_COMPILE
970  the just-in-time compiler is not available, this option is ignored. All other    PCRE_STUDY_JIT_PARTIAL_HARD_COMPILE
971  bits in the \fIoptions\fP argument must be zero.    PCRE_STUDY_JIT_PARTIAL_SOFT_COMPILE
972    .sp
973    If any of these are set, and the just-in-time compiler is available, the
974    pattern is further compiled into machine code that executes much faster than
975    the \fBpcre_exec()\fP interpretive matching function. If the just-in-time
976    compiler is not available, these options are ignored. All other bits in the
977    \fIoptions\fP argument must be zero.
978  .P  .P
979  JIT compilation is a heavyweight optimization. It can take some time for  JIT compilation is a heavyweight optimization. It can take some time for
980  patterns to be analyzed, and for one-off matches and simple patterns the  patterns to be analyzed, and for one-off matches and simple patterns the
# Line 931  When you are finished with a pattern, yo Line 998  When you are finished with a pattern, yo
998  study data by calling \fBpcre_free_study()\fP. This function was added to the  study data by calling \fBpcre_free_study()\fP. This function was added to the
999  API for release 8.20. For earlier versions, the memory could be freed with  API for release 8.20. For earlier versions, the memory could be freed with
1000  \fBpcre_free()\fP, just like the pattern itself. This will still work in cases  \fBpcre_free()\fP, just like the pattern itself. This will still work in cases
1001  where PCRE_STUDY_JIT_COMPILE is not used, but it is advisable to change to the  where JIT optimization is not used, but it is advisable to change to the new
1002  new function when convenient.  function when convenient.
1003  .P  .P
1004  This is a typical way in which \fBpcre_study\fP() is used (except that in a  This is a typical way in which \fBpcre_study\fP() is used (except that in a
1005  real application there should be tests for errors):  real application there should be tests for errors):
# Line 962  in a calling program via the \fBpcre_ful Line 1029  in a calling program via the \fBpcre_ful
1029  Studying a pattern is also useful for non-anchored patterns that do not have a  Studying a pattern is also useful for non-anchored patterns that do not have a
1030  single fixed starting character. A bitmap of possible starting bytes is  single fixed starting character. A bitmap of possible starting bytes is
1031  created. This speeds up finding a position in the subject at which to start  created. This speeds up finding a position in the subject at which to start
1032  matching.  matching. (In 16-bit mode, the bitmap is used for 16-bit values less than 256.)
1033  .P  .P
1034  These two optimizations apply to both \fBpcre_exec()\fP and  These two optimizations apply to both \fBpcre_exec()\fP and
1035  \fBpcre_dfa_exec()\fP. However, they are not used by \fBpcre_exec()\fP if  \fBpcre_dfa_exec()\fP, and the information is also used by the JIT compiler.
1036  \fBpcre_study()\fP is called with the PCRE_STUDY_JIT_COMPILE option, and  The optimizations can be disabled by setting the PCRE_NO_START_OPTIMIZE option
1037  just-in-time compiling is successful. The optimizations can be disabled by  when calling \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP, but if this is done,
1038  setting the PCRE_NO_START_OPTIMIZE option when calling \fBpcre_exec()\fP or  JIT execution is also disabled. You might want to do this if your pattern
1039  \fBpcre_dfa_exec()\fP. You might want to do this if your pattern contains  contains callouts or (*MARK) and you want to make use of these facilities in
1040  callouts or (*MARK) (which cannot be handled by the JIT compiler), and you want  cases where matching fails. See the discussion of PCRE_NO_START_OPTIMIZE
 to make use of these facilities in cases where matching fails. See the  
 discussion of PCRE_NO_START_OPTIMIZE  
1041  .\" HTML <a href="#execoptions">  .\" HTML <a href="#execoptions">
1042  .\" </a>  .\" </a>
1043  below.  below.
# Line 985  below. Line 1050  below.
1050  .sp  .sp
1051  PCRE handles caseless matching, and determines whether characters are letters,  PCRE handles caseless matching, and determines whether characters are letters,
1052  digits, or whatever, by reference to a set of tables, indexed by character  digits, or whatever, by reference to a set of tables, indexed by character
1053  value. When running in UTF-8 mode, this applies only to characters with codes  value. When running in UTF-8 mode, this applies only to characters
1054  less than 128. By default, higher-valued codes never match escapes such as \ew  with codes less than 128. By default, higher-valued codes never match escapes
1055  or \ed, but they can be tested with \ep if PCRE is built with Unicode character  such as \ew or \ed, but they can be tested with \ep if PCRE is built with
1056  property support. Alternatively, the PCRE_UCP option can be set at compile  Unicode character property support. Alternatively, the PCRE_UCP option can be
1057  time; this causes \ew and friends to use Unicode property support instead of  set at compile time; this causes \ew and friends to use Unicode property
1058  built-in tables. The use of locales with Unicode is discouraged. If you are  support instead of built-in tables. The use of locales with Unicode is
1059  handling characters with codes greater than 128, you should either use UTF-8  discouraged. If you are handling characters with codes greater than 128, you
1060  and Unicode, or use locales, but not try to mix the two.  should either use UTF-8 and Unicode, or use locales, but not try to mix the
1061    two.
1062  .P  .P
1063  PCRE contains an internal set of tables that are used when the final argument  PCRE contains an internal set of tables that are used when the final argument
1064  of \fBpcre_compile()\fP is NULL. These are sufficient for many applications.  of \fBpcre_compile()\fP is NULL. These are sufficient for many applications.
# Line 1046  below in the section on matching a patte Line 1112  below in the section on matching a patte
1112  .B int \fIwhat\fP, void *\fIwhere\fP);  .B int \fIwhat\fP, void *\fIwhere\fP);
1113  .PP  .PP
1114  The \fBpcre_fullinfo()\fP function returns information about a compiled  The \fBpcre_fullinfo()\fP function returns information about a compiled
1115  pattern. It replaces the obsolete \fBpcre_info()\fP function, which is  pattern. It replaces the \fBpcre_info()\fP function, which was removed from the
1116  nevertheless retained for backwards compability (and is documented below).  library at version 8.30, after more than 10 years of obsolescence.
1117  .P  .P
1118  The first argument for \fBpcre_fullinfo()\fP is a pointer to the compiled  The first argument for \fBpcre_fullinfo()\fP is a pointer to the compiled
1119  pattern. The second argument is the result of \fBpcre_study()\fP, or NULL if  pattern. The second argument is the result of \fBpcre_study()\fP, or NULL if
# Line 1056  information is required, and the fourth Line 1122  information is required, and the fourth
1122  to receive the data. The yield of the function is zero for success, or one of  to receive the data. The yield of the function is zero for success, or one of
1123  the following negative numbers:  the following negative numbers:
1124  .sp  .sp
1125    PCRE_ERROR_NULL       the argument \fIcode\fP was NULL    PCRE_ERROR_NULL           the argument \fIcode\fP was NULL
1126                          the argument \fIwhere\fP was NULL                              the argument \fIwhere\fP was NULL
1127    PCRE_ERROR_BADMAGIC   the "magic number" was not found    PCRE_ERROR_BADMAGIC       the "magic number" was not found
1128    PCRE_ERROR_BADOPTION  the value of \fIwhat\fP was invalid    PCRE_ERROR_BADENDIANNESS  the pattern was compiled with different
1129                                endianness
1130      PCRE_ERROR_BADOPTION      the value of \fIwhat\fP was invalid
1131  .sp  .sp
1132  The "magic number" is placed at the start of each compiled pattern as an simple  The "magic number" is placed at the start of each compiled pattern as an simple
1133  check against passing an arbitrary memory pointer. Here is a typical call of  check against passing an arbitrary memory pointer. The endianness error can
1134  \fBpcre_fullinfo()\fP, to obtain the length of the compiled pattern:  occur if a compiled pattern is saved and reloaded on a different host. Here is
1135    a typical call of \fBpcre_fullinfo()\fP, to obtain the length of the compiled
1136    pattern:
1137  .sp  .sp
1138    int rc;    int rc;
1139    size_t length;    size_t length;
# Line 1097  a NULL table pointer. Line 1167  a NULL table pointer.
1167  .sp  .sp
1168    PCRE_INFO_FIRSTBYTE    PCRE_INFO_FIRSTBYTE
1169  .sp  .sp
1170  Return information about the first byte of any matched string, for a  Return information about the first data unit of any matched string, for a
1171  non-anchored pattern. The fourth argument should point to an \fBint\fP  non-anchored pattern. (The name of this option refers to the 8-bit library,
1172  variable. (This option used to be called PCRE_INFO_FIRSTCHAR; the old name is  where data units are bytes.) The fourth argument should point to an \fBint\fP
1173  still recognized for backwards compatibility.)  variable.
1174    .P
1175    If there is a fixed first value, for example, the letter "c" from a pattern
1176    such as (cat|cow|coyote), its value is returned. In the 8-bit library, the
1177    value is always less than 256; in the 16-bit library the value can be up to
1178    0xffff.
1179  .P  .P
1180  If there is a fixed first byte, for example, from a pattern such as  If there is no fixed first value, and if either
 (cat|cow|coyote), its value is returned. Otherwise, if either  
1181  .sp  .sp
1182  (a) the pattern was compiled with the PCRE_MULTILINE option, and every branch  (a) the pattern was compiled with the PCRE_MULTILINE option, and every branch
1183  starts with "^", or  starts with "^", or
# Line 1118  returned. For anchored patterns, -2 is r Line 1192  returned. For anchored patterns, -2 is r
1192    PCRE_INFO_FIRSTTABLE    PCRE_INFO_FIRSTTABLE
1193  .sp  .sp
1194  If the pattern was studied, and this resulted in the construction of a 256-bit  If the pattern was studied, and this resulted in the construction of a 256-bit
1195  table indicating a fixed set of bytes for the first byte in any matching  table indicating a fixed set of values for the first data unit in any matching
1196  string, a pointer to the table is returned. Otherwise NULL is returned. The  string, a pointer to the table is returned. Otherwise NULL is returned. The
1197  fourth argument should point to an \fBunsigned char *\fP variable.  fourth argument should point to an \fBunsigned char *\fP variable.
1198  .sp  .sp
# Line 1136  Return 1 if the (?J) or (?-J) option set Line 1210  Return 1 if the (?J) or (?-J) option set
1210  .sp  .sp
1211    PCRE_INFO_JIT    PCRE_INFO_JIT
1212  .sp  .sp
1213  Return 1 if the pattern was studied with the PCRE_STUDY_JIT_COMPILE option, and  Return 1 if the pattern was studied with one of the JIT options, and
1214  just-in-time compiling was successful. The fourth argument should point to an  just-in-time compiling was successful. The fourth argument should point to an
1215  \fBint\fP variable. A return value of 0 means that JIT support is not available  \fBint\fP variable. A return value of 0 means that JIT support is not available
1216  in this version of PCRE, or that the pattern was not studied with the  in this version of PCRE, or that the pattern was not studied with a JIT option,
1217  PCRE_STUDY_JIT_COMPILE option, or that the JIT compiler could not handle this  or that the JIT compiler could not handle this particular pattern. See the
 particular pattern. See the  
1218  .\" HREF  .\" HREF
1219  \fBpcrejit\fP  \fBpcrejit\fP
1220  .\"  .\"
1221  documentation for details of what can and cannot be handled.  documentation for details of what can and cannot be handled.
1222  .sp  .sp
1223      PCRE_INFO_JITSIZE
1224    .sp
1225    If the pattern was successfully studied with a JIT option, return the size of
1226    the JIT compiled code, otherwise return zero. The fourth argument should point
1227    to a \fBsize_t\fP variable.
1228    .sp
1229    PCRE_INFO_LASTLITERAL    PCRE_INFO_LASTLITERAL
1230  .sp  .sp
1231  Return the value of the rightmost literal byte that must exist in any matched  Return the value of the rightmost literal data unit that must exist in any
1232  string, other than at its start, if such a byte has been recorded. The fourth  matched string, other than at its start, if such a value has been recorded. The
1233  argument should point to an \fBint\fP variable. If there is no such byte, -1 is  fourth argument should point to an \fBint\fP variable. If there is no such
1234  returned. For anchored patterns, a last literal byte is recorded only if it  value, -1 is returned. For anchored patterns, a last literal value is recorded
1235  follows something of variable length. For example, for the pattern  only if it follows something of variable length. For example, for the pattern
1236  /^a\ed+z\ed+/ the returned value is "z", but for /^a\edz\ed/ the returned value  /^a\ed+z\ed+/ the returned value is "z", but for /^a\edz\ed/ the returned value
1237  is -1.  is -1.
1238  .sp  .sp
1239      PCRE_INFO_MAXLOOKBEHIND
1240    .sp
1241    Return the number of characters (NB not bytes) in the longest lookbehind
1242    assertion in the pattern. Note that the simple assertions \eb and \eB require a
1243    one-character lookbehind. This information is useful when doing multi-segment
1244    matching using the partial matching facilities.
1245    .sp
1246    PCRE_INFO_MINLENGTH    PCRE_INFO_MINLENGTH
1247  .sp  .sp
1248  If the pattern was studied and a minimum length for matching subject strings  If the pattern was studied and a minimum length for matching subject strings
1249  was computed, its value is returned. Otherwise the returned value is -1. The  was computed, its value is returned. Otherwise the returned value is -1. The
1250  value is a number of characters, not bytes (this may be relevant in UTF-8  value is a number of characters, which in UTF-8 mode may be different from the
1251  mode). The fourth argument should point to an \fBint\fP variable. A  number of bytes. The fourth argument should point to an \fBint\fP variable. A
1252  non-negative value is a lower bound to the length of any matching string. There  non-negative value is a lower bound to the length of any matching string. There
1253  may not be any strings of that length that do actually match, but every string  may not be any strings of that length that do actually match, but every string
1254  that does match is at least that long.  that does match is at least that long.
# Line 1185  The map consists of a number of fixed-si Line 1271  The map consists of a number of fixed-si
1271  the number of entries, and PCRE_INFO_NAMEENTRYSIZE gives the size of each  the number of entries, and PCRE_INFO_NAMEENTRYSIZE gives the size of each
1272  entry; both of these return an \fBint\fP value. The entry size depends on the  entry; both of these return an \fBint\fP value. The entry size depends on the
1273  length of the longest name. PCRE_INFO_NAMETABLE returns a pointer to the first  length of the longest name. PCRE_INFO_NAMETABLE returns a pointer to the first
1274  entry of the table (a pointer to \fBchar\fP). The first two bytes of each entry  entry of the table. This is a pointer to \fBchar\fP in the 8-bit library, where
1275  are the number of the capturing parenthesis, most significant byte first. The  the first two bytes of each entry are the number of the capturing parenthesis,
1276  rest of the entry is the corresponding name, zero terminated.  most significant byte first. In the 16-bit library, the pointer points to
1277    16-bit data units, the first of which contains the parenthesis number. The rest
1278    of the entry is the corresponding name, zero terminated.
1279  .P  .P
1280  The names are in alphabetical order. Duplicate names may appear if (?| is used  The names are in alphabetical order. Duplicate names may appear if (?| is used
1281  to create multiple groups with the same number, as described in the  to create multiple groups with the same number, as described in the
# Line 1206  table in the order in which they were fo Line 1294  table in the order in which they were fo
1294  necessarily the case because later subpatterns may have lower numbers.  necessarily the case because later subpatterns may have lower numbers.
1295  .P  .P
1296  As a simple example of the name/number table, consider the following pattern  As a simple example of the name/number table, consider the following pattern
1297  (assume PCRE_EXTENDED is set, so white space - including newlines - is  after compilation by the 8-bit library (assume PCRE_EXTENDED is set, so white
1298  ignored):  space - including newlines - is ignored):
1299  .sp  .sp
1300  .\" JOIN  .\" JOIN
1301    (?<date> (?<year>(\ed\ed)?\ed\ed) -    (?<date> (?<year>(\ed\ed)?\ed\ed) -
# Line 1262  For such patterns, the PCRE_ANCHORED bit Line 1350  For such patterns, the PCRE_ANCHORED bit
1350  .sp  .sp
1351    PCRE_INFO_SIZE    PCRE_INFO_SIZE
1352  .sp  .sp
1353  Return the size of the compiled pattern. The fourth argument should point to a  Return the size of the compiled pattern in bytes (for both libraries). The
1354  \fBsize_t\fP variable. This value does not include the size of the \fBpcre\fP  fourth argument should point to a \fBsize_t\fP variable. This value does not
1355  structure that is returned by \fBpcre_compile()\fP. The value that is passed as  include the size of the \fBpcre\fP structure that is returned by
1356  the argument to \fBpcre_malloc()\fP when \fBpcre_compile()\fP is getting memory  \fBpcre_compile()\fP. The value that is passed as the argument to
1357  in which to place the compiled data is the value returned by this option plus  \fBpcre_malloc()\fP when \fBpcre_compile()\fP is getting memory in which to
1358  the size of the \fBpcre\fP structure. Studying a compiled pattern, with or  place the compiled data is the value returned by this option plus the size of
1359  without JIT, does not alter the value returned by this option.  the \fBpcre\fP structure. Studying a compiled pattern, with or without JIT,
1360    does not alter the value returned by this option.
1361  .sp  .sp
1362    PCRE_INFO_STUDYSIZE    PCRE_INFO_STUDYSIZE
1363  .sp  .sp
1364  Return the size of the data block pointed to by the \fIstudy_data\fP field in a  Return the size in bytes of the data block pointed to by the \fIstudy_data\fP
1365  \fBpcre_extra\fP block. If \fBpcre_extra\fP is NULL, or there is no study data,  field in a \fBpcre_extra\fP block. If \fBpcre_extra\fP is NULL, or there is no
1366  zero is returned. The fourth argument should point to a \fBsize_t\fP variable.  study data, zero is returned. The fourth argument should point to a
1367  The \fIstudy_data\fP field is set by \fBpcre_study()\fP to record information  \fBsize_t\fP variable. The \fIstudy_data\fP field is set by \fBpcre_study()\fP
1368  that will speed up matching (see the section entitled  to record information that will speed up matching (see the section entitled
1369  .\" HTML <a href="#studyingapattern">  .\" HTML <a href="#studyingapattern">
1370  .\" </a>  .\" </a>
1371  "Studying a pattern"  "Studying a pattern"
# Line 1289  is made available via this option so tha Line 1378  is made available via this option so tha
1378  documentation for details).  documentation for details).
1379  .  .
1380  .  .
 .SH "OBSOLETE INFO FUNCTION"  
 .rs  
 .sp  
 .B int pcre_info(const pcre *\fIcode\fP, int *\fIoptptr\fP, int  
 .B *\fIfirstcharptr\fP);  
 .PP  
 The \fBpcre_info()\fP function is now obsolete because its interface is too  
 restrictive to return all the available data about a compiled pattern. New  
 programs should use \fBpcre_fullinfo()\fP instead. The yield of  
 \fBpcre_info()\fP is the number of capturing subpatterns, or one of the  
 following negative numbers:  
 .sp  
   PCRE_ERROR_NULL       the argument \fIcode\fP was NULL  
   PCRE_ERROR_BADMAGIC   the "magic number" was not found  
 .sp  
 If the \fIoptptr\fP argument is not NULL, a copy of the options with which the  
 pattern was compiled is placed in the integer it points to (see  
 PCRE_INFO_OPTIONS above).  
 .P  
 If the pattern is not anchored and the \fIfirstcharptr\fP argument is not NULL,  
 it is used to pass back information about the first character of any matched  
 string (see PCRE_INFO_FIRSTBYTE above).  
 .  
 .  
1381  .SH "REFERENCE COUNTS"  .SH "REFERENCE COUNTS"
1382  .rs  .rs
1383  .sp  .sp
# Line 1405  fields (not necessarily in this order): Line 1470  fields (not necessarily in this order):
1470    const unsigned char *\fItables\fP;    const unsigned char *\fItables\fP;
1471    unsigned char **\fImark\fP;    unsigned char **\fImark\fP;
1472  .sp  .sp
1473  The \fIflags\fP field is a bitmap that specifies which of the other fields  In the 16-bit version of this structure, the \fImark\fP field has type
1474  are set. The flag bits are:  "PCRE_UCHAR16 **".
1475    .P
1476    The \fIflags\fP field is used to specify which of the other fields are set. The
1477    flag bits are:
1478  .sp  .sp
1479    PCRE_EXTRA_STUDY_DATA    PCRE_EXTRA_CALLOUT_DATA
1480    PCRE_EXTRA_EXECUTABLE_JIT    PCRE_EXTRA_EXECUTABLE_JIT
1481      PCRE_EXTRA_MARK
1482    PCRE_EXTRA_MATCH_LIMIT    PCRE_EXTRA_MATCH_LIMIT
1483    PCRE_EXTRA_MATCH_LIMIT_RECURSION    PCRE_EXTRA_MATCH_LIMIT_RECURSION
1484    PCRE_EXTRA_CALLOUT_DATA    PCRE_EXTRA_STUDY_DATA
1485    PCRE_EXTRA_TABLES    PCRE_EXTRA_TABLES
   PCRE_EXTRA_MARK  
1486  .sp  .sp
1487  Other flag bits should be set to zero. The \fIstudy_data\fP field and sometimes  Other flag bits should be set to zero. The \fIstudy_data\fP field and sometimes
1488  the \fIexecutable_jit\fP field are set in the \fBpcre_extra\fP block that is  the \fIexecutable_jit\fP field are set in the \fBpcre_extra\fP block that is
1489  returned by \fBpcre_study()\fP, together with the appropriate flag bits. You  returned by \fBpcre_study()\fP, together with the appropriate flag bits. You
1490  should not set these yourself, but you may add to the block by setting the  should not set these yourself, but you may add to the block by setting other
1491  other fields and their corresponding flag bits.  fields and their corresponding flag bits.
1492  .P  .P
1493  The \fImatch_limit\fP field provides a means of preventing PCRE from using up a  The \fImatch_limit\fP field provides a means of preventing PCRE from using up a
1494  vast amount of resources when running patterns that are not going to match,  vast amount of resources when running patterns that are not going to match,
# Line 1435  patterns that are not anchored, the coun Line 1503  patterns that are not anchored, the coun
1503  in the subject string.  in the subject string.
1504  .P  .P
1505  When \fBpcre_exec()\fP is called with a pattern that was successfully studied  When \fBpcre_exec()\fP is called with a pattern that was successfully studied
1506  with the PCRE_STUDY_JIT_COMPILE option, the way that the matching is executed  with a JIT option, the way that the matching is executed is entirely different.
1507  is entirely different. However, there is still the possibility of runaway  However, there is still the possibility of runaway matching that goes on for a
1508  matching that goes on for a very long time, and so the \fImatch_limit\fP value  very long time, and so the \fImatch_limit\fP value is also used in this case
1509  is also used in this case (but in a different way) to limit how long the  (but in a different way) to limit how long the matching can continue.
 matching can continue.  
1510  .P  .P
1511  The default value for the limit can be set when PCRE is built; the default  The default value for the limit can be set when PCRE is built; the default
1512  default is 10 million, which handles all but the most extreme cases. You can  default is 10 million, which handles all but the most extreme cases. You can
# Line 1457  This limit is of use only if it is set s Line 1524  This limit is of use only if it is set s
1524  Limiting the recursion depth limits the amount of machine stack that can be  Limiting the recursion depth limits the amount of machine stack that can be
1525  used, or, when PCRE has been compiled to use memory on the heap instead of the  used, or, when PCRE has been compiled to use memory on the heap instead of the
1526  stack, the amount of heap memory that can be used. This limit is not relevant,  stack, the amount of heap memory that can be used. This limit is not relevant,
1527  and is ignored, if the pattern was successfully studied with  and is ignored, when matching is done using JIT compiled code.
 PCRE_STUDY_JIT_COMPILE.  
1528  .P  .P
1529  The default value for \fImatch_limit_recursion\fP can be set when PCRE is  The default value for \fImatch_limit_recursion\fP can be set when PCRE is
1530  built; the default default is the same value as the default for  built; the default default is the same value as the default for
# Line 1489  called. See the Line 1555  called. See the
1555  documentation for a discussion of saving compiled patterns for later use.  documentation for a discussion of saving compiled patterns for later use.
1556  .P  .P
1557  If PCRE_EXTRA_MARK is set in the \fIflags\fP field, the \fImark\fP field must  If PCRE_EXTRA_MARK is set in the \fIflags\fP field, the \fImark\fP field must
1558  be set to point to a \fBchar *\fP variable. If the pattern contains any  be set to point to a suitable variable. If the pattern contains any
1559  backtracking control verbs such as (*MARK:NAME), and the execution ends up with  backtracking control verbs such as (*MARK:NAME), and the execution ends up with
1560  a name to pass back, a pointer to the name string (zero terminated) is placed  a name to pass back, a pointer to the name string (zero terminated) is placed
1561  in the variable pointed to by the \fImark\fP field. The names are within the  in the variable pointed to by the \fImark\fP field. The names are within the
1562  compiled pattern; if you wish to retain such a name you must copy it before  compiled pattern; if you wish to retain such a name you must copy it before
1563  freeing the memory of a compiled pattern. If there is no name to pass back, the  freeing the memory of a compiled pattern. If there is no name to pass back, the
1564  variable pointed to by the \fImark\fP field set to NULL. For details of the  variable pointed to by the \fImark\fP field is set to NULL. For details of the
1565  backtracking control verbs, see the section entitled  backtracking control verbs, see the section entitled
1566  .\" HTML <a href="pcrepattern#backtrackcontrol">  .\" HTML <a href="pcrepattern#backtrackcontrol">
1567  .\" </a>  .\" </a>
# Line 1515  documentation. Line 1581  documentation.
1581  The unused bits of the \fIoptions\fP argument for \fBpcre_exec()\fP must be  The unused bits of the \fIoptions\fP argument for \fBpcre_exec()\fP must be
1582  zero. The only bits that may be set are PCRE_ANCHORED, PCRE_NEWLINE_\fIxxx\fP,  zero. The only bits that may be set are PCRE_ANCHORED, PCRE_NEWLINE_\fIxxx\fP,
1583  PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NOTEMPTY_ATSTART,  PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NOTEMPTY_ATSTART,
1584  PCRE_NO_START_OPTIMIZE, PCRE_NO_UTF8_CHECK, PCRE_PARTIAL_SOFT, and  PCRE_NO_START_OPTIMIZE, PCRE_NO_UTF8_CHECK, PCRE_PARTIAL_HARD, and
1585  PCRE_PARTIAL_HARD.  PCRE_PARTIAL_SOFT.
1586  .P  .P
1587  If the pattern was successfully studied with the PCRE_STUDY_JIT_COMPILE option,  If the pattern was successfully studied with one of the just-in-time (JIT)
1588  the only supported options for JIT execution are PCRE_NO_UTF8_CHECK,  compile options, the only supported options for JIT execution are
1589  PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, and PCRE_NOTEMPTY_ATSTART. Note in  PCRE_NO_UTF8_CHECK, PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY,
1590  particular that partial matching is not supported. If an unsupported option is  PCRE_NOTEMPTY_ATSTART, PCRE_PARTIAL_HARD, and PCRE_PARTIAL_SOFT. If an
1591  used, JIT execution is disabled and the normal interpretive code in  unsupported option is used, JIT execution is disabled and the normal
1592  \fBpcre_exec()\fP is run.  interpretive code in \fBpcre_exec()\fP is run.
1593  .sp  .sp
1594    PCRE_ANCHORED    PCRE_ANCHORED
1595  .sp  .sp
# Line 1642  causing performance to suffer, but ensur Line 1708  causing performance to suffer, but ensur
1708  "no match", the callouts do occur, and that items such as (*COMMIT) and (*MARK)  "no match", the callouts do occur, and that items such as (*COMMIT) and (*MARK)
1709  are considered at every possible starting position in the subject string. If  are considered at every possible starting position in the subject string. If
1710  PCRE_NO_START_OPTIMIZE is set at compile time, it cannot be unset at matching  PCRE_NO_START_OPTIMIZE is set at compile time, it cannot be unset at matching
1711  time.  time. The use of PCRE_NO_START_OPTIMIZE disables JIT execution; when it is set,
1712    matching is always done using interpretively.
1713  .P  .P
1714  Setting PCRE_NO_START_OPTIMIZE can change the outcome of a matching operation.  Setting PCRE_NO_START_OPTIMIZE can change the outcome of a matching operation.
1715  Consider the pattern  Consider the pattern
# Line 1675  returned. Line 1742  returned.
1742  .sp  .sp
1743  When PCRE_UTF8 is set at compile time, the validity of the subject as a UTF-8  When PCRE_UTF8 is set at compile time, the validity of the subject as a UTF-8
1744  string is automatically checked when \fBpcre_exec()\fP is subsequently called.  string is automatically checked when \fBpcre_exec()\fP is subsequently called.
1745  The value of \fIstartoffset\fP is also checked to ensure that it points to the  The entire string is checked before any other processing takes place. The value
1746  start of a UTF-8 character. There is a discussion about the validity of UTF-8  of \fIstartoffset\fP is also checked to ensure that it points to the start of a
1747  strings in the  UTF-8 character. There is a discussion about the
1748  .\" HTML <a href="pcre.html#utf8strings">  .\" HTML <a href="pcreunicode.html#utf8strings">
1749  .\" </a>  .\" </a>
1750  section on UTF-8 support  validity of UTF-8 strings
1751  .\"  .\"
1752  in the main  in the
1753  .\" HREF  .\" HREF
1754  \fBpcre\fP  \fBpcreunicode\fP
1755  .\"  .\"
1756  page. If an invalid UTF-8 sequence of bytes is found, \fBpcre_exec()\fP returns  page. If an invalid sequence of bytes is found, \fBpcre_exec()\fP returns the
1757  the error PCRE_ERROR_BADUTF8 or, if PCRE_PARTIAL_HARD is set and the problem is  error PCRE_ERROR_BADUTF8 or, if PCRE_PARTIAL_HARD is set and the problem is a
1758  a truncated UTF-8 character at the end of the subject, PCRE_ERROR_SHORTUTF8. In  truncated character at the end of the subject, PCRE_ERROR_SHORTUTF8. In both
1759  both cases, information about the precise nature of the error may also be  cases, information about the precise nature of the error may also be returned
1760  returned (see the descriptions of these errors in the section entitled \fIError  (see the descriptions of these errors in the section entitled \fIError return
1761  return values from\fP \fBpcre_exec()\fP  values from\fP \fBpcre_exec()\fP
1762  .\" HTML <a href="#errorlist">  .\" HTML <a href="#errorlist">
1763  .\" </a>  .\" </a>
1764  below).  below).
# Line 1705  checks for performance reasons, you can Line 1772  checks for performance reasons, you can
1772  calling \fBpcre_exec()\fP. You might want to do this for the second and  calling \fBpcre_exec()\fP. You might want to do this for the second and
1773  subsequent calls to \fBpcre_exec()\fP if you are making repeated calls to find  subsequent calls to \fBpcre_exec()\fP if you are making repeated calls to find
1774  all the matches in a single subject string. However, you should be sure that  all the matches in a single subject string. However, you should be sure that
1775  the value of \fIstartoffset\fP points to the start of a UTF-8 character (or the  the value of \fIstartoffset\fP points to the start of a character (or the end
1776  end of the subject). When PCRE_NO_UTF8_CHECK is set, the effect of passing an  of the subject). When PCRE_NO_UTF8_CHECK is set, the effect of passing an
1777  invalid UTF-8 string as a subject or an invalid value of \fIstartoffset\fP is  invalid string as a subject or an invalid value of \fIstartoffset\fP is
1778  undefined. Your program may crash.  undefined. Your program may crash.
1779  .sp  .sp
1780    PCRE_PARTIAL_HARD    PCRE_PARTIAL_HARD
# Line 1742  documentation. Line 1809  documentation.
1809  .rs  .rs
1810  .sp  .sp
1811  The subject string is passed to \fBpcre_exec()\fP as a pointer in  The subject string is passed to \fBpcre_exec()\fP as a pointer in
1812  \fIsubject\fP, a length (in bytes) in \fIlength\fP, and a starting byte offset  \fIsubject\fP, a length in bytes in \fIlength\fP, and a starting byte offset
1813  in \fIstartoffset\fP. If this is negative or greater than the length of the  in \fIstartoffset\fP. If this is negative or greater than the length of the
1814  subject, \fBpcre_exec()\fP returns PCRE_ERROR_BADOFFSET. When the starting  subject, \fBpcre_exec()\fP returns PCRE_ERROR_BADOFFSET. When the starting
1815  offset is zero, the search for a match starts at the beginning of the subject,  offset is zero, the search for a match starts at the beginning of the subject,
# Line 1830  string that it matched that is returned. Line 1897  string that it matched that is returned.
1897  .P  .P
1898  If the vector is too small to hold all the captured substring offsets, it is  If the vector is too small to hold all the captured substring offsets, it is
1899  used as far as possible (up to two-thirds of its length), and the function  used as far as possible (up to two-thirds of its length), and the function
1900  returns a value of zero. If neither the actual string matched not any captured  returns a value of zero. If neither the actual string matched nor any captured
1901  substrings are of interest, \fBpcre_exec()\fP may be called with \fIovector\fP  substrings are of interest, \fBpcre_exec()\fP may be called with \fIovector\fP
1902  passed as NULL and \fIovecsize\fP as zero. However, if the pattern contains  passed as NULL and \fIovecsize\fP as zero. However, if the pattern contains
1903  back references and the \fIovector\fP is not big enough to remember the related  back references and the \fIovector\fP is not big enough to remember the related
# Line 2030  time. Line 2097  time.
2097  .sp  .sp
2098    PCRE_ERROR_JIT_STACKLIMIT (-27)    PCRE_ERROR_JIT_STACKLIMIT (-27)
2099  .sp  .sp
2100  This error is returned when a pattern that was successfully studied using the  This error is returned when a pattern that was successfully studied using a
2101  PCRE_STUDY_JIT_COMPILE option is being matched, but the memory available for  JIT compile option is being matched, but the memory available for the
2102  the just-in-time processing stack is not large enough. See the  just-in-time processing stack is not large enough. See the
2103  .\" HREF  .\" HREF
2104  \fBpcrejit\fP  \fBpcrejit\fP
2105  .\"  .\"
2106  documentation for more details.  documentation for more details.
2107    .sp
2108      PCRE_ERROR_BADMODE        (-28)
2109    .sp
2110    This error is given if a pattern that was compiled by the 8-bit library is
2111    passed to a 16-bit library function, or vice versa.
2112    .sp
2113      PCRE_ERROR_BADENDIANNESS  (-29)
2114    .sp
2115    This error is given if a pattern that was compiled and saved is reloaded on a
2116    host with different endianness. The utility function
2117    \fBpcre_pattern_to_host_byte_order()\fP can be used to convert such a pattern
2118    so that it runs on the new host.
2119  .P  .P
2120  Error numbers -16 to -20 and -22 are not used by \fBpcre_exec()\fP.  Error numbers -16 to -20, -22, and -30 are not used by \fBpcre_exec()\fP.
2121  .  .
2122  .  .
2123  .\" HTML <a name="badutf8reasons"></a>  .\" HTML <a name="badutf8reasons"></a>
2124  .SS "Reason codes for invalid UTF-8 strings"  .SS "Reason codes for invalid UTF-8 strings"
2125  .rs  .rs
2126  .sp  .sp
2127    This section applies only to the 8-bit library. The corresponding information
2128    for the 16-bit library is given in the
2129    .\" HREF
2130    \fBpcre16\fP
2131    .\"
2132    page.
2133    .P
2134  When \fBpcre_exec()\fP returns either PCRE_ERROR_BADUTF8 or  When \fBpcre_exec()\fP returns either PCRE_ERROR_BADUTF8 or
2135  PCRE_ERROR_SHORTUTF8, and the size of the output vector (\fIovecsize\fP) is at  PCRE_ERROR_SHORTUTF8, and the size of the output vector (\fIovecsize\fP) is at
2136  least 2, the offset of the start of the invalid UTF-8 character is placed in  least 2, the offset of the start of the invalid UTF-8 character is placed in
# Line 2342  other alternatives. Ultimately, when it Line 2428  other alternatives. Ultimately, when it
2428  will yield PCRE_ERROR_NOMATCH.  will yield PCRE_ERROR_NOMATCH.
2429  .  .
2430  .  .
2431    .SH "OBTAINING AN ESTIMATE OF STACK USAGE"
2432    .rs
2433    .sp
2434    Matching certain patterns using \fBpcre_exec()\fP can use a lot of process
2435    stack, which in certain environments can be rather limited in size. Some users
2436    find it helpful to have an estimate of the amount of stack that is used by
2437    \fBpcre_exec()\fP, to help them set recursion limits, as described in the
2438    .\" HREF
2439    \fBpcrestack\fP
2440    .\"
2441    documentation. The estimate that is output by \fBpcretest\fP when called with
2442    the \fB-m\fP and \fB-C\fP options is obtained by calling \fBpcre_exec\fP with
2443    the values NULL, NULL, NULL, -999, and -999 for its first five arguments.
2444    .P
2445    Normally, if its first argument is NULL, \fBpcre_exec()\fP immediately returns
2446    the negative error code PCRE_ERROR_NULL, but with this special combination of
2447    arguments, it returns instead a negative number whose absolute value is the
2448    approximate stack frame size in bytes. (A negative number is used so that it is
2449    clear that no match has happened.) The value is approximate because in some
2450    cases, recursive calls to \fBpcre_exec()\fP occur when there are one or two
2451    additional variables on the stack.
2452    .P
2453    If PCRE has been compiled to use the heap instead of the stack for recursion,
2454    the value returned is the size of each block that is obtained from the heap.
2455    .
2456    .
2457  .\" HTML <a name="dfamatch"></a>  .\" HTML <a name="dfamatch"></a>
2458  .SH "MATCHING A PATTERN: THE ALTERNATIVE FUNCTION"  .SH "MATCHING A PATTERN: THE ALTERNATIVE FUNCTION"
2459  .rs  .rs
# Line 2523  When a recursive subpattern is processed Line 2635  When a recursive subpattern is processed
2635  recursively, using private vectors for \fIovector\fP and \fIworkspace\fP. This  recursively, using private vectors for \fIovector\fP and \fIworkspace\fP. This
2636  error is given if the output vector is not large enough. This should be  error is given if the output vector is not large enough. This should be
2637  extremely rare, as a vector of size 1000 is used.  extremely rare, as a vector of size 1000 is used.
2638    .sp
2639      PCRE_ERROR_DFA_BADRESTART (-30)
2640    .sp
2641    When \fBpcre_dfa_exec()\fP is called with the \fBPCRE_DFA_RESTART\fP option,
2642    some plausibility checks are made on the contents of the workspace, which
2643    should contain data about the previous partial match. If any of these checks
2644    fail, this error is given.
2645  .  .
2646  .  .
2647  .SH "SEE ALSO"  .SH "SEE ALSO"
2648  .rs  .rs
2649  .sp  .sp
2650  \fBpcrebuild\fP(3), \fBpcrecallout\fP(3), \fBpcrecpp(3)\fP(3),  \fBpcre16\fP(3), \fBpcrebuild\fP(3), \fBpcrecallout\fP(3), \fBpcrecpp(3)\fP(3),
2651  \fBpcrematching\fP(3), \fBpcrepartial\fP(3), \fBpcreposix\fP(3),  \fBpcrematching\fP(3), \fBpcrepartial\fP(3), \fBpcreposix\fP(3),
2652  \fBpcreprecompile\fP(3), \fBpcresample\fP(3), \fBpcrestack\fP(3).  \fBpcreprecompile\fP(3), \fBpcresample\fP(3), \fBpcrestack\fP(3).
2653  .  .
# Line 2547  Cambridge CB2 3QH, England. Line 2666  Cambridge CB2 3QH, England.
2666  .rs  .rs
2667  .sp  .sp
2668  .nf  .nf
2669  Last updated: 01 December 2011  Last updated: 04 May 2012
2670  Copyright (c) 1997-2011 University of Cambridge.  Copyright (c) 1997-2012 University of Cambridge.
2671  .fi  .fi

Legend:
Removed from v.776  
changed lines
  Added in v.964

  ViewVC Help
Powered by ViewVC 1.1.5