/[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 371 by ph10, Mon Aug 25 18:28:05 2008 UTC revision 391 by ph10, Tue Mar 17 21:16:01 2009 UTC
# Line 317  properties is available; otherwise it is Line 317  properties is available; otherwise it is
317  .sp  .sp
318  The output is an integer whose value specifies the default character sequence  The output is an integer whose value specifies the default character sequence
319  that is recognized as meaning "newline". The four values that are supported  that is recognized as meaning "newline". The four values that are supported
320  are: 10 for LF, 13 for CR, 3338 for CRLF, -2 for ANYCRLF, and -1 for ANY. The  are: 10 for LF, 13 for CR, 3338 for CRLF, -2 for ANYCRLF, and -1 for ANY.
321  default should normally be the standard sequence for your operating system.  Though they are derived from ASCII, the same values are returned in EBCDIC
322    environments. The default should normally correspond to the standard sequence
323    for your operating system.
324  .sp  .sp
325    PCRE_CONFIG_BSR    PCRE_CONFIG_BSR
326  .sp  .sp
# Line 347  documentation. Line 349  documentation.
349  .sp  .sp
350    PCRE_CONFIG_MATCH_LIMIT    PCRE_CONFIG_MATCH_LIMIT
351  .sp  .sp
352  The output is an integer that gives the default limit for the number of  The output is a long integer that gives the default limit for the number of
353  internal matching function calls in a \fBpcre_exec()\fP execution. Further  internal matching function calls in a \fBpcre_exec()\fP execution. Further
354  details are given with \fBpcre_exec()\fP below.  details are given with \fBpcre_exec()\fP below.
355  .sp  .sp
356    PCRE_CONFIG_MATCH_LIMIT_RECURSION    PCRE_CONFIG_MATCH_LIMIT_RECURSION
357  .sp  .sp
358  The output is an integer that gives the default limit for the depth of  The output is a long integer that gives the default limit for the depth of
359  recursion when calling the internal matching function in a \fBpcre_exec()\fP  recursion when calling the internal matching function in a \fBpcre_exec()\fP
360  execution. Further details are given with \fBpcre_exec()\fP below.  execution. Further details are given with \fBpcre_exec()\fP below.
361  .sp  .sp
# Line 1237  documentation for a discussion of saving Line 1239  documentation for a discussion of saving
1239  .sp  .sp
1240  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
1241  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,
1242  PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NO_UTF8_CHECK and PCRE_PARTIAL.  PCRE_NOTBOL, PCRE_NOTEOL, PCRE_NOTEMPTY, PCRE_NO_START_OPTIMIZE,
1243    PCRE_NO_UTF8_CHECK and PCRE_PARTIAL.
1244  .sp  .sp
1245    PCRE_ANCHORED    PCRE_ANCHORED
1246  .sp  .sp
# Line 1324  PCRE_NOTEMPTY and PCRE_ANCHORED, and the Line 1327  PCRE_NOTEMPTY and PCRE_ANCHORED, and the
1327  starting offset (see below) and trying an ordinary match again. There is some  starting offset (see below) and trying an ordinary match again. There is some
1328  code that demonstrates how to do this in the \fIpcredemo.c\fP sample program.  code that demonstrates how to do this in the \fIpcredemo.c\fP sample program.
1329  .sp  .sp
1330      PCRE_NO_START_OPTIMIZE
1331    .sp
1332    There are a number of optimizations that \fBpcre_exec()\fP uses at the start of
1333    a match, in order to speed up the process. For example, if it is known that a
1334    match must start with a specific character, it searches the subject for that
1335    character, and fails immediately if it cannot find it, without actually running
1336    the main matching function. When callouts are in use, these optimizations can
1337    cause them to be skipped. This option disables the "start-up" optimizations,
1338    causing performance to suffer, but ensuring that the callouts do occur.
1339    .sp
1340    PCRE_NO_UTF8_CHECK    PCRE_NO_UTF8_CHECK
1341  .sp  .sp
1342  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
# Line 1729  These functions call \fBpcre_get_stringn Line 1742  These functions call \fBpcre_get_stringn
1742  then call \fBpcre_copy_substring()\fP or \fBpcre_get_substring()\fP, as  then call \fBpcre_copy_substring()\fP or \fBpcre_get_substring()\fP, as
1743  appropriate. \fBNOTE:\fP If PCRE_DUPNAMES is set and there are duplicate names,  appropriate. \fBNOTE:\fP If PCRE_DUPNAMES is set and there are duplicate names,
1744  the behaviour may not be what you want (see the next section).  the behaviour may not be what you want (see the next section).
1745  .  .P
1746    \fBWarning:\fP If the pattern uses the "(?|" feature to set up multiple
1747    subpatterns with the same number, you cannot use names to distinguish them,
1748    because names are not included in the compiled code. The matching process uses
1749    only numbers.
1750  .  .
1751  .SH "DUPLICATE SUBPATTERN NAMES"  .SH "DUPLICATE SUBPATTERN NAMES"
1752  .rs  .rs
# Line 1978  Cambridge CB2 3QH, England. Line 1995  Cambridge CB2 3QH, England.
1995  .rs  .rs
1996  .sp  .sp
1997  .nf  .nf
1998  Last updated: 24 August 2008  Last updated: 17 March 2009
1999  Copyright (c) 1997-2008 University of Cambridge.  Copyright (c) 1997-2009 University of Cambridge.
2000  .fi  .fi

Legend:
Removed from v.371  
changed lines
  Added in v.391

  ViewVC Help
Powered by ViewVC 1.1.5