--- code/trunk/doc/html/pcreposix.html 2009/09/01 16:10:16 429 +++ code/trunk/doc/html/pcreposix.html 2009/09/18 19:12:35 453 @@ -66,6 +66,11 @@ replacement library. Other POSIX options are not even defined.

+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. +

+

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 @@ -121,6 +126,12 @@ nmatch and pmatch arguments are ignored, and no captured strings are returned. 

+  REG_UNGREEDY
+
+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. +
   REG_UTF8
The PCRE_UTF8 option is set when the regular expression is passed for @@ -134,7 +145,7 @@ 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 some 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).

@@ -222,6 +233,10 @@ regexec() are ignored.

+If the value of nmatch is zero, or if the value pmatch is NULL, +no data about any matched strings is returned. +

+

Otherwise,the portion of the string that was matched, and also any captured substrings, are returned via the pmatch argument, which points to an array of nmatch structures of type regmatch_t, containing the @@ -262,7 +277,7 @@


REVISION

-Last updated: 15 August 2009 +Last updated: 02 September 2009
Copyright © 1997-2009 University of Cambridge.