/[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 196 by ph10, Mon Jul 30 13:44:50 2007 UTC revision 202 by ph10, Fri Aug 3 09:44:26 2007 UTC
# Line 669  out of use. To avoid confusion, they hav Line 669  out of use. To avoid confusion, they hav
669    47  unknown property name after \eP or \ep    47  unknown property name after \eP or \ep
670    48  subpattern name is too long (maximum 32 characters)    48  subpattern name is too long (maximum 32 characters)
671    49  too many named subpatterns (maximum 10,000)    49  too many named subpatterns (maximum 10,000)
672    50  repeated subpattern is too long    50  [this code is not in use]
673    51  octal value is greater than \e377 (not in UTF-8 mode)    51  octal value is greater than \e377 (not in UTF-8 mode)
674    52  internal error: overran compiling workspace    52  internal error: overran compiling workspace
675    53  internal error: previously-checked referenced subpattern not found    53  internal error: previously-checked referenced subpattern not found
# Line 1466  The internal recursion limit, as specifi Line 1466  The internal recursion limit, as specifi
1466  field in a \fBpcre_extra\fP structure (or defaulted) was reached. See the  field in a \fBpcre_extra\fP structure (or defaulted) was reached. See the
1467  description above.  description above.
1468  .sp  .sp
   PCRE_ERROR_NULLWSLIMIT    (-22)  
 .sp  
 When a parenthesized subpattern that can match an empty substring is repeated  
 with an unbounded upper limit, the subject position at the start of the group  
 must be remembered, so that a test for an empty string can be made when the end  
 of the group is reached. The repetition loop is automatically terminated when  
 an empty string is matched.  
 .P  
 Some workspace is required for remembering the starting position. For most  
 capturing subpatterns, an internal recursive call of the match() function is  
 used, and in this case, the workspace is taken from the runtime stack. However,  
 for non-capturing subpatterns, this is not available. Instead, some fixed  
 workspace (taken from the top-level stack) is used. If it runs out, the  
 PCRE_ERROR_NULLWSLIMIT error is given. The size of the fixed workspace allows  
 for up to 1000 repetitions of a non-capturing subpattern that might match an  
 empty string. If this limit is a problem for you, you can sometimes get round  
 it by changing a non-capturing subpattern into a capturing one, but that will  
 increase the amount of runtime stack that is used.  
 .sp  
1469    PCRE_ERROR_BADNEWLINE     (-23)    PCRE_ERROR_BADNEWLINE     (-23)
1470  .sp  .sp
1471  An invalid combination of PCRE_NEWLINE_\fIxxx\fP options was given.  An invalid combination of PCRE_NEWLINE_\fIxxx\fP options was given.
1472  .P  .P
1473  Error numbers -16 to -20 are not used by \fBpcre_exec()\fP.  Error numbers -16 to -20 and -22 are not used by \fBpcre_exec()\fP.
1474  .  .
1475  .  .
1476  .SH "EXTRACTING CAPTURED SUBSTRINGS BY NUMBER"  .SH "EXTRACTING CAPTURED SUBSTRINGS BY NUMBER"
Legend:
Removed from v.196  
changed lines
  Added in v.202
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12