summaryrefslogtreecommitdiff
path: root/doc/pcreposix.3
diff options
context:
space:
mode:
authorph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2009-09-02 16:02:56 +0000
committerph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2009-09-02 16:02:56 +0000
commit5bda06fcd3562b292b125741fa74fc38a0c2a886 (patch)
treefdb5e283272ac1013ec8ffe6031459c9087df6e4 /doc/pcreposix.3
parenta89489db04146da6d48aace6317a74e6a2f240dd (diff)
downloadpcre-5bda06fcd3562b292b125741fa74fc38a0c2a886.tar.gz
Add REG_UNGREEDY (non-standard) to the POSIX interface.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@432 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'doc/pcreposix.3')
-rw-r--r--doc/pcreposix.314
1 files changed, 12 insertions, 2 deletions
diff --git a/doc/pcreposix.3 b/doc/pcreposix.3
index c5e5d7d..ad1bae1 100644
--- a/doc/pcreposix.3
+++ b/doc/pcreposix.3
@@ -45,6 +45,10 @@ the value zero. This has no effect, but since programs that are written to the
POSIX interface often use it, this makes it easier to slot in PCRE as a
replacement library. Other POSIX options are not even defined.
.P
+There are also some other options that are not defined by POSIX. These have
+been added at the request of users who want to make use of certain
+PCRE-specific features via the POSIX calling interface.
+.P
When PCRE is called via these functions, it is only the API that is POSIX-like
in style. The syntax and semantics of the regular expressions themselves are
still those of Perl, subject to the setting of various PCRE options, as
@@ -97,6 +101,12 @@ compiled with this flag is passed to \fBregexec()\fP for matching, the
\fInmatch\fP and \fIpmatch\fP arguments are ignored, and no captured strings
are returned.
.sp
+ REG_UNGREEDY
+.sp
+The PCRE_UNGREEDY option is set when the regular expression is passed for
+compilation to the native function. Note that REG_UNGREEDY is not part of the
+POSIX standard.
+.sp
REG_UTF8
.sp
The PCRE_UTF8 option is set when the regular expression is passed for
@@ -109,7 +119,7 @@ This means the the regex is compiled with PCRE default semantics. In
particular, the way it handles newline characters in the subject string is the
Perl way, not the POSIX way. Note that setting PCRE_MULTILINE has only
\fIsome\fP of the effects specified for REG_NEWLINE. It does not affect the way
-newlines are matched by . (they aren't) or by a negative class such as [^a]
+newlines are matched by . (they are not) or by a negative class such as [^a]
(they are).
.P
The yield of \fBregcomp()\fP is zero on success, and non-zero otherwise. The
@@ -243,6 +253,6 @@ Cambridge CB2 3QH, England.
.rs
.sp
.nf
-Last updated: 15 August 2009
+Last updated: 02 September 2009
Copyright (c) 1997-2009 University of Cambridge.
.fi