/[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 567 by ph10, Sat Nov 6 17:10:00 2010 UTC revision 707 by ph10, Fri Sep 23 10:32:53 2011 UTC
# Line 1  Line 1 
1  .TH PCREAPI 3  .TH PCREAPI 3
2  .SH NAME  .SH NAME
3  PCRE - Perl-compatible regular expressions  PCRE - Perl-compatible regular expressions
4  .SH "PCRE NATIVE API"  .SH "PCRE NATIVE API BASIC FUNCTIONS"
5  .rs  .rs
6  .sp  .sp
7  .B #include <pcre.h>  .B #include <pcre.h>
# Line 25  PCRE - Perl-compatible regular expressio Line 25  PCRE - Perl-compatible regular expressio
25  .ti +5n  .ti +5n
26  .B const char **\fIerrptr\fP);  .B const char **\fIerrptr\fP);
27  .PP  .PP
28    .B void pcre_free_study(pcre_extra *\fIextra\fP);
29    .PP
30  .B int pcre_exec(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"  .B int pcre_exec(const pcre *\fIcode\fP, "const pcre_extra *\fIextra\fP,"
31  .ti +5n  .ti +5n
32  .B "const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,  .B "const char *\fIsubject\fP," int \fIlength\fP, int \fIstartoffset\fP,
33  .ti +5n  .ti +5n
34  .B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);  .B int \fIoptions\fP, int *\fIovector\fP, int \fIovecsize\fP);
35    .
36    .
37    .SH "PCRE NATIVE API AUXILIARY FUNCTIONS"
38    .rs
39    .sp
40    .B pcre_jit_stack *pcre_jit_stack_alloc(int \fIstartsize\fP, int \fImaxsize\fP);
41    .PP
42    .B void pcre_jit_stack_free(pcre_jit_stack *\fIstack\fP);
43    .PP
44    .B void pcre_assign_jit_stack(pcre_extra *\fIextra\fP,
45    .ti +5n
46    .B pcre_jit_callback \fIcallback\fP, void *\fIdata\fP);
47  .PP  .PP
48  .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,"
49  .ti +5n  .ti +5n
# Line 97  PCRE - Perl-compatible regular expressio Line 111  PCRE - Perl-compatible regular expressio
111  .B int pcre_config(int \fIwhat\fP, void *\fIwhere\fP);  .B int pcre_config(int \fIwhat\fP, void *\fIwhere\fP);
112  .PP  .PP
113  .B char *pcre_version(void);  .B char *pcre_version(void);
114  .PP  .
115    .
116    .SH "PCRE NATIVE API INDIRECTED FUNCTIONS"
117    .rs
118    .sp
119  .B void *(*pcre_malloc)(size_t);  .B void *(*pcre_malloc)(size_t);
120  .PP  .PP
121  .B void (*pcre_free)(void *);  .B void (*pcre_free)(void *);
# Line 114  PCRE - Perl-compatible regular expressio Line 132  PCRE - Perl-compatible regular expressio
132  .sp  .sp
133  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
134  also some wrapper functions that correspond to the POSIX regular expression  also some wrapper functions that correspond to the POSIX regular expression
135  API. These are described in the  API, but they do not give access to all the functionality. They are described
136    in the
137  .\" HREF  .\" HREF
138  \fBpcreposix\fP  \fBpcreposix\fP
139  .\"  .\"
140  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++
141  wrapper is distributed with PCRE. It is documented in the  wrapper is also distributed with PCRE. It is documented in the
142  .\" HREF  .\" HREF
143  \fBpcrecpp\fP  \fBpcrecpp\fP
144  .\"  .\"
# Line 152  documentation, and the Line 171  documentation, and the
171  .\"  .\"
172  documentation describes how to compile and run it.  documentation describes how to compile and run it.
173  .P  .P
174    Just-in-time compiler support is an optional feature of PCRE that can be built
175    in appropriate hardware environments. It greatly speeds up the matching
176    performance of many patterns. Simple programs can easily request that it be
177    used if available, by setting an option that is ignored when it is not
178    relevant. More complicated programs might need to make use of the functions
179    \fBpcre_jit_stack_alloc()\fP, \fBpcre_jit_stack_free()\fP, and
180    \fBpcre_assign_jit_stack()\fP in order to control the JIT code's memory usage.
181    These functions are discussed in the
182    .\" HREF
183    \fBpcrejit\fP
184    .\"
185    documentation.
186    .P
187  A second matching function, \fBpcre_dfa_exec()\fP, which is not  A second matching function, \fBpcre_dfa_exec()\fP, which is not
188  Perl-compatible, is also provided. This uses a different algorithm for the  Perl-compatible, is also provided. This uses a different algorithm for the
189  matching. The alternative algorithm finds all possible matches (at a given  matching. The alternative algorithm finds all possible matches (at a given
# Line 282  callout function pointed to by \fBpcre_c Line 314  callout function pointed to by \fBpcre_c
314  .P  .P
315  The compiled form of a regular expression is not altered during matching, so  The compiled form of a regular expression is not altered during matching, so
316  the same compiled pattern can safely be used by several threads at once.  the same compiled pattern can safely be used by several threads at once.
317    .P
318    If the just-in-time optimization feature is being used, it needs separate
319    memory stack areas for each thread. See the
320    .\" HREF
321    \fBpcrejit\fP
322    .\"
323    documentation for more details.
324  .  .
325  .  .
326  .SH "SAVING PRECOMPILED PATTERNS FOR LATER USE"  .SH "SAVING PRECOMPILED PATTERNS FOR LATER USE"
# Line 324  otherwise it is set to zero. Line 363  otherwise it is set to zero.
363  The output is an integer that is set to one if support for Unicode character  The output is an integer that is set to one if support for Unicode character
364  properties is available; otherwise it is set to zero.  properties is available; otherwise it is set to zero.
365  .sp  .sp
366      PCRE_CONFIG_JIT
367    .sp
368    The output is an integer that is set to one if support for just-in-time
369    compiling is available; otherwise it is set to zero.
370    .sp
371    PCRE_CONFIG_NEWLINE    PCRE_CONFIG_NEWLINE
372  .sp  .sp
373  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 428  within the pattern (see the detailed des Line 472  within the pattern (see the detailed des
472  documentation). For those options that can be different in different parts of  documentation). For those options that can be different in different parts of
473  the pattern, the contents of the \fIoptions\fP argument specifies their  the pattern, the contents of the \fIoptions\fP argument specifies their
474  settings at the start of compilation and execution. The PCRE_ANCHORED,  settings at the start of compilation and execution. The PCRE_ANCHORED,
475  PCRE_BSR_\fIxxx\fP, and PCRE_NEWLINE_\fIxxx\fP options can be set at the time  PCRE_BSR_\fIxxx\fP, PCRE_NEWLINE_\fIxxx\fP, PCRE_NO_UTF8_CHECK, and
476  of matching as well as at compile time.  PCRE_NO_START_OPT options can be set at the time of matching as well as at
477    compile time.
478  .P  .P
479  If \fIerrptr\fP is NULL, \fBpcre_compile()\fP returns NULL immediately.  If \fIerrptr\fP is NULL, \fBpcre_compile()\fP returns NULL immediately.
480  Otherwise, if compilation of a pattern fails, \fBpcre_compile()\fP returns  Otherwise, if compilation of a pattern fails, \fBpcre_compile()\fP returns
481  NULL, and sets the variable pointed to by \fIerrptr\fP to point to a textual  NULL, and sets the variable pointed to by \fIerrptr\fP to point to a textual
482  error message. This is a static string that is part of the library. You must  error message. This is a static string that is part of the library. You must
483  not try to free it. The byte offset from the start of the pattern to the  not try to free it. Normally, the offset from the start of the pattern to the
484  character that was being processed when the error was discovered is placed in  byte that was being processed when the error was discovered is placed in the
485  the variable pointed to by \fIerroffset\fP, which must not be NULL. If it is,  variable pointed to by \fIerroffset\fP, which must not be NULL (if it is, an
486  an immediate error is given. Some errors are not detected until checks are  immediate error is given). However, for an invalid UTF-8 string, the offset is
487  carried out when the whole pattern has been scanned; in this case the offset is  that of the first byte of the failing character. Also, some errors are not
488  set to the end of the pattern.  detected until checks are carried out when the whole pattern has been scanned;
489    in these cases the offset passed back is the length of the pattern.
490    .P
491    Note that the offset is in bytes, not characters, even in UTF-8 mode. It may
492    sometimes point into the middle of a UTF-8 character.
493  .P  .P
494  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
495  \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 519  pattern. Line 568  pattern.
568  .sp  .sp
569    PCRE_DOTALL    PCRE_DOTALL
570  .sp  .sp
571  If this bit is set, a dot metacharater in the pattern matches all characters,  If this bit is set, a dot metacharacter in the pattern matches a character of
572  including those that indicate newline. Without it, a dot does not match when  any value, including one that indicates a newline. However, it only ever
573  the current position is at a newline. This option is equivalent to Perl's /s  matches one character, even if newlines are coded as CRLF. Without this option,
574  option, and it can be changed within a pattern by a (?s) option setting. A  a dot does not match when the current position is at a newline. This option is
575  negative class such as [^a] always matches newline characters, independent of  equivalent to Perl's /s option, and it can be changed within a pattern by a
576  the setting of this option.  (?s) option setting. A negative class such as [^a] always matches newline
577    characters, independent of the setting of this option.
578  .sp  .sp
579    PCRE_DUPNAMES    PCRE_DUPNAMES
580  .sp  .sp
# Line 546  unescaped # outside a character class an Line 596  unescaped # outside a character class an
596  ignored. This is equivalent to Perl's /x option, and it can be changed within a  ignored. This is equivalent to Perl's /x option, and it can be changed within a
597  pattern by a (?x) option setting.  pattern by a (?x) option setting.
598  .P  .P
599    Which characters are interpreted as newlines is controlled by the options
600    passed to \fBpcre_compile()\fP or by a special sequence at the start of the
601    pattern, as described in the section entitled
602    .\" HTML <a href="pcrepattern.html#newlines">
603    .\" </a>
604    "Newline conventions"
605    .\"
606    in the \fBpcrepattern\fP documentation. Note that the end of this type of
607    comment is a literal newline sequence in the pattern; escape sequences that
608    happen to represent a newline do not count.
609    .P
610  This option makes it possible to include comments inside complicated patterns.  This option makes it possible to include comments inside complicated patterns.
611  Note, however, that this applies only to data characters. Whitespace characters  Note, however, that this applies only to data characters. Whitespace characters
612  may never appear within special character sequences in a pattern, for example  may never appear within special character sequences in a pattern, for example
613  within the sequence (?( which introduces a conditional subpattern.  within the sequence (?( that introduces a conditional subpattern.
614  .sp  .sp
615    PCRE_EXTRA    PCRE_EXTRA
616  .sp  .sp
# Line 624  option, the combination may or may not b Line 685  option, the combination may or may not b
685  PCRE_NEWLINE_CR with PCRE_NEWLINE_LF is equivalent to PCRE_NEWLINE_CRLF, but  PCRE_NEWLINE_CR with PCRE_NEWLINE_LF is equivalent to PCRE_NEWLINE_CRLF, but
686  other combinations may yield unused numbers and cause an error.  other combinations may yield unused numbers and cause an error.
687  .P  .P
688  The only time that a line break is specially recognized when compiling a  The only time that a line break in a pattern is specially recognized when
689  pattern is if PCRE_EXTENDED is set, and an unescaped # outside a character  compiling is when PCRE_EXTENDED is set. CR and LF are whitespace characters,
690  class is encountered. This indicates a comment that lasts until after the next  and so are ignored in this mode. Also, an unescaped # outside a character class
691  line break sequence. In other circumstances, line break sequences are treated  indicates a comment that lasts until after the next line break sequence. In
692  as literal data, except that in PCRE_EXTENDED mode, both CR and LF are treated  other circumstances, line break sequences in patterns are treated as literal
693  as whitespace characters and are therefore ignored.  data.
694  .P  .P
695  The newline option that is set at compile time becomes the default that is used  The newline option that is set at compile time becomes the default that is used
696  for \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP, but it can be overridden.  for \fBpcre_exec()\fP and \fBpcre_dfa_exec()\fP, but it can be overridden.
# Line 642  were followed by ?: but named parenthese Line 703  were followed by ?: but named parenthese
703  they acquire numbers in the usual way). There is no equivalent of this option  they acquire numbers in the usual way). There is no equivalent of this option
704  in Perl.  in Perl.
705  .sp  .sp
706      NO_START_OPTIMIZE
707    .sp
708    This is an option that acts at matching time; that is, it is really an option
709    for \fBpcre_exec()\fP or \fBpcre_dfa_exec()\fP. If it is set at compile time,
710    it is remembered with the compiled pattern and assumed at matching time. For
711    details see the discussion of PCRE_NO_START_OPTIMIZE
712    .\" HTML <a href="#execoptions">
713    .\" </a>
714    below.
715    .\"
716    .sp
717    PCRE_UCP    PCRE_UCP
718  .sp  .sp
719  This option changes the way PCRE processes \eb, \ed, \es, \ew, and some of the  This option changes the way PCRE processes \eB, \eb, \eD, \ed, \eS, \es, \eW,
720  POSIX character classes. By default, only ASCII characters are recognized, but  \ew, and some of the POSIX character classes. By default, only ASCII characters
721  if PCRE_UCP is set, Unicode properties are used instead to classify characters.  are recognized, but if PCRE_UCP is set, Unicode properties are used instead to
722  More details are given in the section on  classify characters. More details are given in the section on
723  .\" HTML <a href="pcre.html#genericchartypes">  .\" HTML <a href="pcre.html#genericchartypes">
724  .\" </a>  .\" </a>
725  generic character types  generic character types
# Line 673  of UTF-8 characters instead of single-by Line 745  of UTF-8 characters instead of single-by
745  available only when PCRE is built to include UTF-8 support. If not, the use  available only when PCRE is built to include UTF-8 support. If not, the use
746  of this option provokes an error. Details of how this option changes the  of this option provokes an error. Details of how this option changes the
747  behaviour of PCRE are given in the  behaviour of PCRE are given in the
 .\" HTML <a href="pcre.html#utf8support">  
 .\" </a>  
 section on UTF-8 support  
 .\"  
 in the main  
748  .\" HREF  .\" HREF
749  \fBpcre\fP  \fBpcreunicode\fP
750  .\"  .\"
751  page.  page.
752  .sp  .sp
# Line 749  out of use. To avoid confusion, they hav Line 816  out of use. To avoid confusion, they hav
816    34  character value in \ex{...} sequence is too large    34  character value in \ex{...} sequence is too large
817    35  invalid condition (?(0)    35  invalid condition (?(0)
818    36  \eC not allowed in lookbehind assertion    36  \eC not allowed in lookbehind assertion
819    37  PCRE does not support \eL, \el, \eN, \eU, or \eu    37  PCRE does not support \eL, \el, \eN{name}, \eU, or \eu
820    38  number after (?C is > 255    38  number after (?C is > 255
821    39  closing ) for (?C expected    39  closing ) for (?C expected
822    40  recursive call could loop indefinitely    40  recursive call could loop indefinitely
# Line 783  out of use. To avoid confusion, they hav Line 850  out of use. To avoid confusion, they hav
850          not allowed          not allowed
851    66  (*MARK) must have an argument    66  (*MARK) must have an argument
852    67  this version of PCRE is not compiled with PCRE_UCP support    67  this version of PCRE is not compiled with PCRE_UCP support
853      68  \ec must be followed by an ASCII character
854      69  \ek is not followed by a braced, angle-bracketed, or quoted name
855  .sp  .sp
856  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
857  be used if the limits were changed when PCRE was built.  be used if the limits were changed when PCRE was built.
858  .  .
859  .  .
860    .\" HTML <a name="studyingapattern"></a>
861  .SH "STUDYING A PATTERN"  .SH "STUDYING A PATTERN"
862  .rs  .rs
863  .sp  .sp
# Line 818  If studying the pattern does not produce Line 888  If studying the pattern does not produce
888  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
889  \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.
890  .P  .P
891  The second argument of \fBpcre_study()\fP contains option bits. At present, no  The second argument of \fBpcre_study()\fP contains option bits. There is only
892  options are defined, and this argument should always be zero.  one option: PCRE_STUDY_JIT_COMPILE. If this is set, and the just-in-time
893    compiler is available, the pattern is further compiled into machine code that
894    executes much faster than the \fBpcre_exec()\fP matching function. If
895    the just-in-time compiler is not available, this option is ignored. All other
896    bits in the \fIoptions\fP argument must be zero.
897    .P
898    JIT compilation is a heavyweight optimization. It can take some time for
899    patterns to be analyzed, and for one-off matches and simple patterns the
900    benefit of faster execution might be offset by a much slower study time.
901    Not all patterns can be optimized by the JIT compiler. For those that cannot be
902    handled, matching automatically falls back to the \fBpcre_exec()\fP
903    interpreter. For more details, see the
904    .\" HREF
905    \fBpcrejit\fP
906    .\"
907    documentation.
908  .P  .P
909  The third argument for \fBpcre_study()\fP is a pointer for an error message. If  The third argument for \fBpcre_study()\fP is a pointer for an error message. If
910  studying succeeds (even if no data is returned), the variable it points to is  studying succeeds (even if no data is returned), the variable it points to is
# Line 828  static string that is part of the librar Line 913  static string that is part of the librar
913  should test the error pointer for NULL after calling \fBpcre_study()\fP, to be  should test the error pointer for NULL after calling \fBpcre_study()\fP, to be
914  sure that it has run successfully.  sure that it has run successfully.
915  .P  .P
916  This is a typical call to \fBpcre_study\fP():  When you are finished with a pattern, you can free the memory used for the
917    study data by calling \fBpcre_free_study()\fP. This function was added to the
918    API for release 8.20. For earlier versions, the memory could be freed with
919    \fBpcre_free()\fP, just like the pattern itself. This will still work in cases
920    where PCRE_STUDY_JIT_COMPILE is not used, but it is advisable to change to the
921    new function when convenient.
922    .P
923    This is a typical way in which \fBpcre_study\fP() is used (except that in a
924    real application there should be tests for errors):
925  .sp  .sp
926    pcre_extra *pe;    int rc;
927    pe = pcre_study(    pcre *re;
928      pcre_extra *sd;
929      re = pcre_compile("pattern", 0, &error, &erroroffset, NULL);
930      sd = pcre_study(
931      re,             /* result of pcre_compile() */      re,             /* result of pcre_compile() */
932      0,              /* no options exist */      0,              /* no options */
933      &error);        /* set to NULL or points to a message */      &error);        /* set to NULL or points to a message */
934      rc = pcre_exec(   /* see below for details of pcre_exec() options */
935        re, sd, "subject", 7, 0, 0, ovector, 30);
936      ...
937      pcre_free_study(sd);
938      pcre_free(re);
939  .sp  .sp
940  Studying a pattern does two things: first, a lower bound for the length of  Studying a pattern does two things: first, a lower bound for the length of
941  subject string that is needed to match the pattern is computed. This does not  subject string that is needed to match the pattern is computed. This does not
# Line 849  single fixed starting character. A bitma Line 950  single fixed starting character. A bitma
950  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
951  matching.  matching.
952  .P  .P
953  The two optimizations just described can be disabled by setting the  These two optimizations apply to both \fBpcre_exec()\fP and
954  PCRE_NO_START_OPTIMIZE option when calling \fBpcre_exec()\fP or  \fBpcre_dfa_exec()\fP. However, they are not used by \fBpcre_exec()\fP if
955    \fBpcre_study()\fP is called with the PCRE_STUDY_JIT_COMPILE option, and
956    just-in-time compiling is successful. The optimizations can be disabled by
957    setting the PCRE_NO_START_OPTIMIZE option when calling \fBpcre_exec()\fP or
958  \fBpcre_dfa_exec()\fP. You might want to do this if your pattern contains  \fBpcre_dfa_exec()\fP. You might want to do this if your pattern contains
959  callouts, or make use of (*MARK), and you make use of these in cases where  callouts or (*MARK) (which cannot be handled by the JIT compiler), and you want
960  matching fails. See the discussion of PCRE_NO_START_OPTIMIZE  to make use of these facilities in cases where matching fails. See the
961    discussion of PCRE_NO_START_OPTIMIZE
962  .\" HTML <a href="#execoptions">  .\" HTML <a href="#execoptions">
963  .\" </a>  .\" </a>
964  below.  below.
# Line 918  one in which it was compiled. Passing ta Line 1023  one in which it was compiled. Passing ta
1023  below in the section on matching a pattern.  below in the section on matching a pattern.
1024  .  .
1025  .  .
1026    .\" HTML <a name="infoaboutpattern"></a>
1027  .SH "INFORMATION ABOUT A PATTERN"  .SH "INFORMATION ABOUT A PATTERN"
1028  .rs  .rs
1029  .sp  .sp
# Line 949  check against passing an arbitrary memor Line 1055  check against passing an arbitrary memor
1055    size_t length;    size_t length;
1056    rc = pcre_fullinfo(    rc = pcre_fullinfo(
1057      re,               /* result of pcre_compile() */      re,               /* result of pcre_compile() */
1058      pe,               /* result of pcre_study(), or NULL */      sd,               /* result of pcre_study(), or NULL */
1059      PCRE_INFO_SIZE,   /* what is required */      PCRE_INFO_SIZE,   /* what is required */
1060      &length);         /* where to put the data */      &length);         /* where to put the data */
1061  .sp  .sp
# Line 1014  Return 1 if the (?J) or (?-J) option set Line 1120  Return 1 if the (?J) or (?-J) option set
1120  0. The fourth argument should point to an \fBint\fP variable. (?J) and  0. The fourth argument should point to an \fBint\fP variable. (?J) and
1121  (?-J) set and unset the local PCRE_DUPNAMES option, respectively.  (?-J) set and unset the local PCRE_DUPNAMES option, respectively.
1122  .sp  .sp
1123      PCRE_INFO_JIT
1124    .sp
1125    Return 1 if the pattern was studied with the PCRE_STUDY_JIT_COMPILE option, and
1126    just-in-time compiling was successful. The fourth argument should point to an
1127    \fBint\fP variable. A return value of 0 means that JIT support is not available
1128    in this version of PCRE, or that the pattern was not studied with the
1129    PCRE_STUDY_JIT_COMPILE option, or that the JIT compiler could not handle this
1130    particular pattern. See the
1131    .\" HREF
1132    \fBpcrejit\fP
1133    .\"
1134    documentation for details of what can and cannot be handled.
1135    .sp
1136    PCRE_INFO_LASTLITERAL    PCRE_INFO_LASTLITERAL
1137  .sp  .sp
1138  Return the value of the rightmost literal byte that must exist in any matched  Return the value of the rightmost literal byte that must exist in any matched
# Line 1136  variable. Line 1255  variable.
1255  .sp  .sp
1256    PCRE_INFO_STUDYSIZE    PCRE_INFO_STUDYSIZE
1257  .sp  .sp
1258  Return the size of the data block pointed to by the \fIstudy_data\fP field in  Return the size of the data block pointed to by the \fIstudy_data\fP field in a
1259  a \fBpcre_extra\fP block. That is, it is the value that was passed to  \fBpcre_extra\fP block. If \fBpcre_extra\fP is NULL, or there is no study data,
1260  \fBpcre_malloc()\fP when PCRE was getting memory into which to place the data  zero is returned. The fourth argument should point to a \fBsize_t\fP variable.
1261  created by \fBpcre_study()\fP. If \fBpcre_extra\fP is NULL, or there is no  The \fIstudy_data\fP field is set by \fBpcre_study()\fP to record information
1262  study data, zero is returned. The fourth argument should point to a  that will speed up matching (see the section entitled
1263  \fBsize_t\fP variable.  .\" HTML <a href="#studyingapattern">
1264    .\" </a>
1265    "Studying a pattern"
1266    .\"
1267    above). The format of the \fIstudy_data\fP block is private, but its length
1268    is made available via this option so that it can be saved and restored (see the
1269    .\" HREF
1270    \fBpcreprecompile\fP
1271    .\"
1272    documentation for details).
1273  .  .
1274  .  .
1275  .SH "OBSOLETE INFO FUNCTION"  .SH "OBSOLETE INFO FUNCTION"
# Line 1203  is different. (This seems a highly unlik Line 1331  is different. (This seems a highly unlik
1331  The function \fBpcre_exec()\fP is called to match a subject string against a  The function \fBpcre_exec()\fP is called to match a subject string against a
1332  compiled pattern, which is passed in the \fIcode\fP argument. If the  compiled pattern, which is passed in the \fIcode\fP argument. If the
1333  pattern was studied, the result of the study should be passed in the  pattern was studied, the result of the study should be passed in the
1334  \fIextra\fP argument. This function is the main matching facility of the  \fIextra\fP argument. You can call \fBpcre_exec()\fP with the same \fIcode\fP
1335  library, and it operates in a Perl-like manner. For specialist use there is  and \fIextra\fP arguments as many times as you like, in order to match
1336  also an alternative matching function, which is described  different subject strings with the same pattern.
1337    .P
1338    This function is the main matching facility of the library, and it operates in
1339    a Perl-like manner. For specialist use there is also an alternative matching
1340    function, which is described
1341  .\" HTML <a href="#dfamatch">  .\" HTML <a href="#dfamatch">
1342  .\" </a>  .\" </a>
1343  below  below
# Line 1236  Here is an example of a simple call to \ Line 1368  Here is an example of a simple call to \
1368      ovector,        /* vector of integers for substring information */      ovector,        /* vector of integers for substring information */
1369      30);            /* number of elements (NOT size in bytes) */      30);            /* number of elements (NOT size in bytes) */
1370  .  .
1371    .
1372  .\" HTML <a name="extradata"></a>  .\" HTML <a name="extradata"></a>
1373  .SS "Extra data for \fBpcre_exec()\fR"  .SS "Extra data for \fBpcre_exec()\fR"
1374  .rs  .rs
# Line 1248  fields (not necessarily in this order): Line 1381  fields (not necessarily in this order):
1381  .sp  .sp
1382    unsigned long int \fIflags\fP;    unsigned long int \fIflags\fP;
1383    void *\fIstudy_data\fP;    void *\fIstudy_data\fP;
1384      void *\fIexecutable_jit\fP;
1385    unsigned long int \fImatch_limit\fP;    unsigned long int \fImatch_limit\fP;
1386    unsigned long int \fImatch_limit_recursion\fP;    unsigned long int \fImatch_limit_recursion\fP;
1387    void *\fIcallout_data\fP;    void *\fIcallout_data\fP;
# Line 1258  The \fIflags\fP field is a bitmap that s Line 1392  The \fIflags\fP field is a bitmap that s
1392  are set. The flag bits are:  are set. The flag bits are:
1393  .sp  .sp
1394    PCRE_EXTRA_STUDY_DATA    PCRE_EXTRA_STUDY_DATA
1395      PCRE_EXTRA_EXECUTABLE_JIT
1396    PCRE_EXTRA_MATCH_LIMIT    PCRE_EXTRA_MATCH_LIMIT
1397    PCRE_EXTRA_MATCH_LIMIT_RECURSION    PCRE_EXTRA_MATCH_LIMIT_RECURSION
1398    PCRE_EXTRA_CALLOUT_DATA    PCRE_EXTRA_CALLOUT_DATA
1399    PCRE_EXTRA_TABLES    PCRE_EXTRA_TABLES
1400    PCRE_EXTRA_MARK    PCRE_EXTRA_MARK
1401  .sp  .sp
1402  Other flag bits should be set to zero. The \fIstudy_data\fP field is set in the  Other flag bits should be set to zero. The \fIstudy_data\fP field and sometimes
1403  \fBpcre_extra\fP block that is returned by \fBpcre_study()\fP, together with  the \fIexecutable_jit\fP field are set in the \fBpcre_extra\fP block that is
1404  the appropriate flag bit. You should not set this yourself, but you may add to  returned by \fBpcre_study()\fP, together with the appropriate flag bits. You
1405  the block by setting the other fields and their corresponding flag bits.  should not set these yourself, but you may add to the block by setting the
1406    other fields and their corresponding flag bits.
1407  .P  .P
1408  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
1409  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,
1410  but which have a very large number of possibilities in their search trees. The  but which have a very large number of possibilities in their search trees. The
1411  classic example is a pattern that uses nested unlimited repeats.  classic example is a pattern that uses nested unlimited repeats.
1412  .P  .P
1413  Internally, PCRE uses a function called \fBmatch()\fP which it calls repeatedly  Internally, \fBpcre_exec()\fP uses a function called \fBmatch()\fP, which it
1414  (sometimes recursively). The limit set by \fImatch_limit\fP is imposed on the  calls repeatedly (sometimes recursively). The limit set by \fImatch_limit\fP is
1415  number of times this function is called during a match, which has the effect of  imposed on the number of times this function is called during a match, which
1416  limiting the amount of backtracking that can take place. For patterns that are  has the effect of limiting the amount of backtracking that can take place. For
1417  not anchored, the count restarts from zero for each position in the subject  patterns that are not anchored, the count restarts from zero for each position
1418  string.  in the subject string.
1419    .P
1420    When \fBpcre_exec()\fP is called with a pattern that was successfully studied
1421    with the PCRE_STUDY_JIT_COMPILE option, the way that the matching is executed
1422    is entirely different. However, there is still the possibility of runaway
1423    matching that goes on for a very long time, and so the \fImatch_limit\fP value
1424    is also used in this case (but in a different way) to limit how long the
1425    matching can continue.
1426  .P  .P
1427  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
1428  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 1294  limits the depth of recursion. The recur Line 1437  limits the depth of recursion. The recur
1437  total number of calls, because not all calls to \fBmatch()\fP are recursive.  total number of calls, because not all calls to \fBmatch()\fP are recursive.
1438  This limit is of use only if it is set smaller than \fImatch_limit\fP.  This limit is of use only if it is set smaller than \fImatch_limit\fP.
1439  .P  .P
1440  Limiting the recursion depth limits the amount of stack that can be used, or,  Limiting the recursion depth limits the amount of machine stack that can be
1441  when PCRE has been compiled to use memory on the heap instead of the stack, the  used, or, when PCRE has been compiled to use memory on the heap instead of the
1442  amount of heap memory that can be used.  stack, the amount of heap memory that can be used. This limit is not relevant,
1443    and is ignored, if the pattern was successfully studied with
1444    PCRE_STUDY_JIT_COMPILE.
1445  .P  .P
1446  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
1447  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 1355  zero. The only bits that may be set are Line 1500  zero. The only bits that may be set are
1500  PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NOTEMPTY_ATSTART,  PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NOTEMPTY_ATSTART,
1501  PCRE_NO_START_OPTIMIZE, PCRE_NO_UTF8_CHECK, PCRE_PARTIAL_SOFT, and  PCRE_NO_START_OPTIMIZE, PCRE_NO_UTF8_CHECK, PCRE_PARTIAL_SOFT, and
1502  PCRE_PARTIAL_HARD.  PCRE_PARTIAL_HARD.
1503    .P
1504    If the pattern was successfully studied with the PCRE_STUDY_JIT_COMPILE option,
1505    the only supported options for JIT execution are PCRE_NO_UTF8_CHECK,
1506    PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, and PCRE_NOTEMPTY_ATSTART. Note in
1507    particular that partial matching is not supported. If an unsupported option is
1508    used, JIT execution is disabled and the normal interpretive code in
1509    \fBpcre_exec()\fP is run.
1510  .sp  .sp
1511    PCRE_ANCHORED    PCRE_ANCHORED
1512  .sp  .sp
# Line 1450  the Line 1602  the
1602  .\" HREF  .\" HREF
1603  \fBpcredemo\fP  \fBpcredemo\fP
1604  .\"  .\"
1605  sample program. In the most general case, you have to check to see if the  sample program. In the most general case, you have to check to see if the
1606  newline convention recognizes CRLF as a newline, and if so, and the current  newline convention recognizes CRLF as a newline, and if so, and the current
1607  character is CR followed by LF, advance the starting offset by two characters  character is CR followed by LF, advance the starting offset by two characters
1608  instead of one.  instead of one.
1609  .sp  .sp
# Line 1471  a pre-scan of the subject that takes pla Line 1623  a pre-scan of the subject that takes pla
1623  The PCRE_NO_START_OPTIMIZE option disables the start-up optimizations, possibly  The PCRE_NO_START_OPTIMIZE option disables the start-up optimizations, possibly
1624  causing performance to suffer, but ensuring that in cases where the result is  causing performance to suffer, but ensuring that in cases where the result is
1625  "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)
1626  are considered at every possible starting position in the subject string.  are considered at every possible starting position in the subject string. If
1627    PCRE_NO_START_OPTIMIZE is set at compile time, it cannot be unset at matching
1628    time.
1629    .P
1630  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.
1631  Consider the pattern  Consider the pattern
1632  .sp  .sp
# Line 1515  in the main Line 1670  in the main
1670  \fBpcre\fP  \fBpcre\fP
1671  .\"  .\"
1672  page. If an invalid UTF-8 sequence of bytes is found, \fBpcre_exec()\fP returns  page. If an invalid UTF-8 sequence of bytes is found, \fBpcre_exec()\fP returns
1673  the error PCRE_ERROR_BADUTF8. If \fIstartoffset\fP contains a value that does  the error PCRE_ERROR_BADUTF8 or, if PCRE_PARTIAL_HARD is set and the problem is
1674  not point to the start of a UTF-8 character (or to the end of the subject),  a truncated UTF-8 character at the end of the subject, PCRE_ERROR_SHORTUTF8. In
1675  PCRE_ERROR_BADUTF8_OFFSET is returned.  both cases, information about the precise nature of the error may also be
1676    returned (see the descriptions of these errors in the section entitled \fIError
1677    return values from\fP \fBpcre_exec()\fP
1678    .\" HTML <a href="#errorlist">
1679    .\" </a>
1680    below).
1681    .\"
1682    If \fIstartoffset\fP contains a value that does not point to the start of a
1683    UTF-8 character (or to the end of the subject), PCRE_ERROR_BADUTF8_OFFSET is
1684    returned.
1685  .P  .P
1686  If you already know that your subject is valid, and you want to skip these  If you already know that your subject is valid, and you want to skip these
1687  checks for performance reasons, you can set the PCRE_NO_UTF8_CHECK option when  checks for performance reasons, you can set the PCRE_NO_UTF8_CHECK option when
# Line 1545  but only if no complete match can be fou Line 1709  but only if no complete match can be fou
1709  If PCRE_PARTIAL_HARD is set, it overrides PCRE_PARTIAL_SOFT. In this case, if a  If PCRE_PARTIAL_HARD is set, it overrides PCRE_PARTIAL_SOFT. In this case, if a
1710  partial match is found, \fBpcre_exec()\fP immediately returns  partial match is found, \fBpcre_exec()\fP immediately returns
1711  PCRE_ERROR_PARTIAL, without considering any other alternatives. In other words,  PCRE_ERROR_PARTIAL, without considering any other alternatives. In other words,
1712  when PCRE_PARTIAL_HARD is set, a partial match is considered to be more  when PCRE_PARTIAL_HARD is set, a partial match is considered to be more
1713  important that an alternative complete match.  important that an alternative complete match.
1714  .P  .P
1715  In both cases, the portion of the string that was inspected when the partial  In both cases, the portion of the string that was inspected when the partial
# Line 1562  documentation. Line 1726  documentation.
1726  .sp  .sp
1727  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
1728  \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
1729  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
1730  subject, \fBpcre_exec()\fP returns PCRE_ERROR_BADOFFSET.  subject, \fBpcre_exec()\fP returns PCRE_ERROR_BADOFFSET. When the starting
1731  .P  offset is zero, the search for a match starts at the beginning of the subject,
1732  In UTF-8 mode, the byte offset must point to the start of a UTF-8 character (or  and this is by far the most common case. In UTF-8 mode, the byte offset must
1733  the end of the subject). Unlike the pattern string, the subject may contain  point to the start of a UTF-8 character (or the end of the subject). Unlike the
1734  binary zero bytes. When the starting offset is zero, the search for a match  pattern string, the subject may contain binary zero bytes.
 starts at the beginning of the subject, and this is by far the most common  
 case.  
1735  .P  .P
1736  A non-zero starting offset is useful when searching for another match in the  A non-zero starting offset is useful when searching for another match in the
1737  same subject by calling \fBpcre_exec()\fP again after a previous success.  same subject by calling \fBpcre_exec()\fP again after a previous success.
# Line 1598  do this in the Line 1760  do this in the
1760  .\" HREF  .\" HREF
1761  \fBpcredemo\fP  \fBpcredemo\fP
1762  .\"  .\"
1763  sample program. In the most general case, you have to check to see if the  sample program. In the most general case, you have to check to see if the
1764  newline convention recognizes CRLF as a newline, and if so, and the current  newline convention recognizes CRLF as a newline, and if so, and the current
1765  character is CR followed by LF, advance the starting offset by two characters  character is CR followed by LF, advance the starting offset by two characters
1766  instead of one.  instead of one.
1767  .P  .P
# Line 1651  string that it matched that is returned. Line 1813  string that it matched that is returned.
1813  .P  .P
1814  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
1815  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
1816  returns a value of zero. If the substring offsets are not of interest,  returns a value of zero. If neither the actual string matched not any captured
1817  \fBpcre_exec()\fP may be called with \fIovector\fP passed as NULL and  substrings are of interest, \fBpcre_exec()\fP may be called with \fIovector\fP
1818  \fIovecsize\fP as zero. However, if the pattern contains back references and  passed as NULL and \fIovecsize\fP as zero. However, if the pattern contains
1819  the \fIovector\fP is not big enough to remember the related substrings, PCRE  back references and the \fIovector\fP is not big enough to remember the related
1820  has to get additional memory for use during matching. Thus it is usually  substrings, PCRE has to get additional memory for use during matching. Thus it
1821  advisable to supply an \fIovector\fP.  is usually advisable to supply an \fIovector\fP of reasonable size.
1822    .P
1823    There are some cases where zero is returned (indicating vector overflow) when
1824    in fact the vector is exactly the right size for the final match. For example,
1825    consider the pattern
1826    .sp
1827      (a)(?:(b)c|bd)
1828    .sp
1829    If a vector of 6 elements (allowing for only 1 captured substring) is given
1830    with subject string "abd", \fBpcre_exec()\fP will try to set the second
1831    captured string, thereby recording a vector overflow, before failing to match
1832    "c" and backing up to try the second alternative. The zero return, however,
1833    does correctly indicate that the maximum number of slots (namely 2) have been
1834    filled. In similar cases where there is temporary overflow, but the final
1835    number of used slots is actually less than the maximum, a non-zero value is
1836    returned.
1837  .P  .P
1838  The \fBpcre_fullinfo()\fP function can be used to find out how many capturing  The \fBpcre_fullinfo()\fP function can be used to find out how many capturing
1839  subpatterns there are in a compiled pattern. The smallest size for  subpatterns there are in a compiled pattern. The smallest size for
# Line 1674  Offset values that correspond to unused Line 1851  Offset values that correspond to unused
1851  expression are also set to -1. For example, if the string "abc" is matched  expression are also set to -1. For example, if the string "abc" is matched
1852  against the pattern (abc)(x(yz)?)? subpatterns 2 and 3 are not matched. The  against the pattern (abc)(x(yz)?)? subpatterns 2 and 3 are not matched. The
1853  return from the function is 2, because the highest used capturing subpattern  return from the function is 2, because the highest used capturing subpattern
1854  number is 1. However, you can refer to the offsets for the second and third  number is 1, and the offsets for for the second and third capturing subpatterns
1855  capturing subpatterns if you wish (assuming the vector is large enough, of  (assuming the vector is large enough, of course) are set to -1.
1856  course).  .P
1857    \fBNote\fP: Elements in the first two-thirds of \fIovector\fP that do not
1858    correspond to capturing parentheses in the pattern are never changed. That is,
1859    if a pattern contains \fIn\fP capturing parentheses, no more than
1860    \fIovector[0]\fP to \fIovector[2n+1]\fP are set by \fBpcre_exec()\fP. The other
1861    elements (in the first two-thirds) retain whatever values they previously had.
1862  .P  .P
1863  Some convenience functions are provided for extracting the captured substrings  Some convenience functions are provided for extracting the captured substrings
1864  as separate strings. These are described below.  as separate strings. These are described below.
1865  .  .
1866    .
1867  .\" HTML <a name="errorlist"></a>  .\" HTML <a name="errorlist"></a>
1868  .SS "Error return values from \fBpcre_exec()\fP"  .SS "Error return values from \fBpcre_exec()\fP"
1869  .rs  .rs
# Line 1750  documentation for details. Line 1933  documentation for details.
1933  .sp  .sp
1934    PCRE_ERROR_BADUTF8        (-10)    PCRE_ERROR_BADUTF8        (-10)
1935  .sp  .sp
1936  A string that contains an invalid UTF-8 byte sequence was passed as a subject.  A string that contains an invalid UTF-8 byte sequence was passed as a subject,
1937    and the PCRE_NO_UTF8_CHECK option was not set. If the size of the output vector
1938    (\fIovecsize\fP) is at least 2, the byte offset to the start of the the invalid
1939    UTF-8 character is placed in the first element, and a reason code is placed in
1940    the second element. The reason codes are listed in the
1941    .\" HTML <a href="#badutf8reasons">
1942    .\" </a>
1943    following section.
1944    .\"
1945    For backward compatibility, if PCRE_PARTIAL_HARD is set and the problem is a
1946    truncated UTF-8 character at the end of the subject (reason codes 1 to 5),
1947    PCRE_ERROR_SHORTUTF8 is returned instead of PCRE_ERROR_BADUTF8.
1948  .sp  .sp
1949    PCRE_ERROR_BADUTF8_OFFSET (-11)    PCRE_ERROR_BADUTF8_OFFSET (-11)
1950  .sp  .sp
1951  The UTF-8 byte sequence that was passed as a subject was valid, but the value  The UTF-8 byte sequence that was passed as a subject was checked and found to
1952  of \fIstartoffset\fP did not point to the beginning of a UTF-8 character.  be valid (the PCRE_NO_UTF8_CHECK option was not set), but the value of
1953    \fIstartoffset\fP did not point to the beginning of a UTF-8 character or the
1954    end of the subject.
1955  .sp  .sp
1956    PCRE_ERROR_PARTIAL        (-12)    PCRE_ERROR_PARTIAL        (-12)
1957  .sp  .sp
# Line 1793  An invalid combination of PCRE_NEWLINE_\ Line 1989  An invalid combination of PCRE_NEWLINE_\
1989  .sp  .sp
1990    PCRE_ERROR_BADOFFSET      (-24)    PCRE_ERROR_BADOFFSET      (-24)
1991  .sp  .sp
1992  The value of \fIstartoffset\fP was negative or greater than the length of the  The value of \fIstartoffset\fP was negative or greater than the length of the
1993  subject, that is, the value in \fIlength\fP.  subject, that is, the value in \fIlength\fP.
1994    .sp
1995      PCRE_ERROR_SHORTUTF8      (-25)
1996    .sp
1997    This error is returned instead of PCRE_ERROR_BADUTF8 when the subject string
1998    ends with a truncated UTF-8 character and the PCRE_PARTIAL_HARD option is set.
1999    Information about the failure is returned as for PCRE_ERROR_BADUTF8. It is in
2000    fact sufficient to detect this case, but this special error code for
2001    PCRE_PARTIAL_HARD precedes the implementation of returned information; it is
2002    retained for backwards compatibility.
2003    .sp
2004      PCRE_ERROR_RECURSELOOP    (-26)
2005    .sp
2006    This error is returned when \fBpcre_exec()\fP detects a recursion loop within
2007    the pattern. Specifically, it means that either the whole pattern or a
2008    subpattern has been called recursively for the second time at the same position
2009    in the subject string. Some simple patterns that might do this are detected and
2010    faulted at compile time, but more complicated cases, in particular mutual
2011    recursions between two different subpatterns, cannot be detected until run
2012    time.
2013    .sp
2014      PCRE_ERROR_JIT_STACKLIMIT (-27)
2015    .sp
2016    This error is returned when a pattern that was successfully studied using the
2017    PCRE_STUDY_JIT_COMPILE option is being matched, but the memory available for
2018    the just-in-time processing stack is not large enough. See the
2019    .\" HREF
2020    \fBpcrejit\fP
2021    .\"
2022    documentation for more details.
2023  .P  .P
2024  Error numbers -16 to -20 and -22 are not used by \fBpcre_exec()\fP.  Error numbers -16 to -20 and -22 are not used by \fBpcre_exec()\fP.
2025  .  .
2026  .  .
2027    .\" HTML <a name="badutf8reasons"></a>
2028    .SS "Reason codes for invalid UTF-8 strings"
2029    .rs
2030    .sp
2031    When \fBpcre_exec()\fP returns either PCRE_ERROR_BADUTF8 or
2032    PCRE_ERROR_SHORTUTF8, and the size of the output vector (\fIovecsize\fP) is at
2033    least 2, the offset of the start of the invalid UTF-8 character is placed in
2034    the first output vector element (\fIovector[0]\fP) and a reason code is placed
2035    in the second element (\fIovector[1]\fP). The reason codes are given names in
2036    the \fBpcre.h\fP header file:
2037    .sp
2038      PCRE_UTF8_ERR1
2039      PCRE_UTF8_ERR2
2040      PCRE_UTF8_ERR3
2041      PCRE_UTF8_ERR4
2042      PCRE_UTF8_ERR5
2043    .sp
2044    The string ends with a truncated UTF-8 character; the code specifies how many
2045    bytes are missing (1 to 5). Although RFC 3629 restricts UTF-8 characters to be
2046    no longer than 4 bytes, the encoding scheme (originally defined by RFC 2279)
2047    allows for up to 6 bytes, and this is checked first; hence the possibility of
2048    4 or 5 missing bytes.
2049    .sp
2050      PCRE_UTF8_ERR6
2051      PCRE_UTF8_ERR7
2052      PCRE_UTF8_ERR8
2053      PCRE_UTF8_ERR9
2054      PCRE_UTF8_ERR10
2055    .sp
2056    The two most significant bits of the 2nd, 3rd, 4th, 5th, or 6th byte of the
2057    character do not have the binary value 0b10 (that is, either the most
2058    significant bit is 0, or the next bit is 1).
2059    .sp
2060      PCRE_UTF8_ERR11
2061      PCRE_UTF8_ERR12
2062    .sp
2063    A character that is valid by the RFC 2279 rules is either 5 or 6 bytes long;
2064    these code points are excluded by RFC 3629.
2065    .sp
2066      PCRE_UTF8_ERR13
2067    .sp
2068    A 4-byte character has a value greater than 0x10fff; these code points are
2069    excluded by RFC 3629.
2070    .sp
2071      PCRE_UTF8_ERR14
2072    .sp
2073    A 3-byte character has a value in the range 0xd800 to 0xdfff; this range of
2074    code points are reserved by RFC 3629 for use with UTF-16, and so are excluded
2075    from UTF-8.
2076    .sp
2077      PCRE_UTF8_ERR15
2078      PCRE_UTF8_ERR16
2079      PCRE_UTF8_ERR17
2080      PCRE_UTF8_ERR18
2081      PCRE_UTF8_ERR19
2082    .sp
2083    A 2-, 3-, 4-, 5-, or 6-byte character is "overlong", that is, it codes for a
2084    value that can be represented by fewer bytes, which is invalid. For example,
2085    the two bytes 0xc0, 0xae give the value 0x2e, whose correct coding uses just
2086    one byte.
2087    .sp
2088      PCRE_UTF8_ERR20
2089    .sp
2090    The two most significant bits of the first byte of a character have the binary
2091    value 0b10 (that is, the most significant bit is 1 and the second is 0). Such a
2092    byte can only validly occur as the second or subsequent byte of a multi-byte
2093    character.
2094    .sp
2095      PCRE_UTF8_ERR21
2096    .sp
2097    The first byte of a character has the value 0xfe or 0xff. These values can
2098    never occur in a valid UTF-8 string.
2099    .
2100    .
2101  .SH "EXTRACTING CAPTURED SUBSTRINGS BY NUMBER"  .SH "EXTRACTING CAPTURED SUBSTRINGS BY NUMBER"
2102  .rs  .rs
2103  .sp  .sp
# Line 1961  names are not included in the compiled c Line 2260  names are not included in the compiled c
2260  numbers. For this reason, the use of different names for subpatterns of the  numbers. For this reason, the use of different names for subpatterns of the
2261  same number causes an error at compile time.  same number causes an error at compile time.
2262  .  .
2263    .
2264  .SH "DUPLICATE SUBPATTERN NAMES"  .SH "DUPLICATE SUBPATTERN NAMES"
2265  .rs  .rs
2266  .sp  .sp
# Line 1994  fourth are pointers to variables which a Line 2294  fourth are pointers to variables which a
2294  has run, they point to the first and last entries in the name-to-number table  has run, they point to the first and last entries in the name-to-number table
2295  for the given name. The function itself returns the length of each entry, or  for the given name. The function itself returns the length of each entry, or
2296  PCRE_ERROR_NOSUBSTRING (-7) if there are none. The format of the table is  PCRE_ERROR_NOSUBSTRING (-7) if there are none. The format of the table is
2297  described above in the section entitled \fIInformation about a pattern\fP.  described above in the section entitled \fIInformation about a pattern\fP
2298    .\" HTML <a href="#infoaboutpattern">
2299    .\" </a>
2300    above.
2301    .\"
2302  Given all the relevant entries for the name, you can extract each of their  Given all the relevant entries for the name, you can extract each of their
2303  numbers, and hence the captured data, if any.  numbers, and hence the captured data, if any.
2304  .  .
# Line 2124  match. There is more discussion of this Line 2428  match. There is more discussion of this
2428  .\"  .\"
2429  documentation.  documentation.
2430  .  .
2431    .
2432  .SS "Successful returns from \fBpcre_dfa_exec()\fP"  .SS "Successful returns from \fBpcre_dfa_exec()\fP"
2433  .rs  .rs
2434  .sp  .sp
# Line 2155  returns data, even though the meaning of Line 2460  returns data, even though the meaning of
2460  The strings are returned in reverse order of length; that is, the longest  The strings are returned in reverse order of length; that is, the longest
2461  matching string is given first. If there were too many matches to fit into  matching string is given first. If there were too many matches to fit into
2462  \fIovector\fP, the yield of the function is zero, and the vector is filled with  \fIovector\fP, the yield of the function is zero, and the vector is filled with
2463  the longest matches.  the longest matches. Unlike \fBpcre_exec()\fP, \fBpcre_dfa_exec()\fP can use
2464    the entire \fIovector\fP for returning matched strings.
2465    .
2466  .  .
2467  .SS "Error returns from \fBpcre_dfa_exec()\fP"  .SS "Error returns from \fBpcre_dfa_exec()\fP"
2468  .rs  .rs
# Line 2184  group. These are not supported. Line 2491  group. These are not supported.
2491    PCRE_ERROR_DFA_UMLIMIT    (-18)    PCRE_ERROR_DFA_UMLIMIT    (-18)
2492  .sp  .sp
2493  This return is given if \fBpcre_dfa_exec()\fP is called with an \fIextra\fP  This return is given if \fBpcre_dfa_exec()\fP is called with an \fIextra\fP
2494  block that contains a setting of the \fImatch_limit\fP field. This is not  block that contains a setting of the \fImatch_limit\fP or
2495  supported (it is meaningless).  \fImatch_limit_recursion\fP fields. This is not supported (these fields are
2496    meaningless for DFA matching).
2497  .sp  .sp
2498    PCRE_ERROR_DFA_WSSIZE     (-19)    PCRE_ERROR_DFA_WSSIZE     (-19)
2499  .sp  .sp
# Line 2222  Cambridge CB2 3QH, England. Line 2530  Cambridge CB2 3QH, England.
2530  .rs  .rs
2531  .sp  .sp
2532  .nf  .nf
2533  Last updated: 06 November 2010  Last updated: 23 September 2011
2534  Copyright (c) 1997-2010 University of Cambridge.  Copyright (c) 1997-2011 University of Cambridge.
2535  .fi  .fi

Legend:
Removed from v.567  
changed lines
  Added in v.707

  ViewVC Help
Powered by ViewVC 1.1.5