--- embedaddon/pcre/doc/html/pcrecompat.html 2012/02/21 23:05:52 1.1 +++ embedaddon/pcre/doc/html/pcrecompat.html 2012/10/09 09:19:18 1.1.1.3 @@ -21,8 +21,8 @@ regular expressions. The differences described here ar versions 5.10 and above.

-1. PCRE has only a subset of Perl's UTF-8 and Unicode support. Details of what -it does have are given in the +1. PCRE has only a subset of Perl's Unicode support. Details of what it does +have are given in the pcreunicode page.

@@ -107,8 +107,16 @@ in the page.

-11. If (*THEN) is present in a group that is called as a subroutine, its action -is limited to that group, even if the group does not contain any | characters. +11. If any of the backtracking control verbs are used in an assertion or in a +subpattern that is called as a subroutine (whether or not recursively), their +effect is confined to that subpattern; it does not extend to the surrounding +pattern. This is not always the case in Perl. In particular, if (*THEN) is +present in a group that is called as a subroutine, its action is limited to +that group, even if the group does not contain any | characters. There is one +exception to this: the name from a *(MARK), (*PRUNE), or (*THEN) that is +encountered in a successful positive assertion is passed back when a +match succeeds (compare capturing parentheses in assertions). Note that such +subpatterns are processed as anchored at the point where they are tested.

12. There are some differences that are concerned with the settings of captured @@ -129,7 +137,7 @@ an error is given at compile time.

14. Perl recognizes comments in some places that PCRE does not, for example, between the ( and ? at the start of a subpattern. If the /x modifier is set, -Perl allows whitespace between ( and ? but PCRE never does, even if the +Perl allows white space between ( and ? but PCRE never does, even if the PCRE_EXTENDED option is set.

@@ -181,8 +189,8 @@ different hosts that have the other endianness. Howeve optimized data created by the just-in-time compiler.

-(k) The alternative matching function (pcre_dfa_exec()) matches in a -different way and is not Perl-compatible. +(k) The alternative matching functions (pcre_dfa_exec() and +pcre16_dfa_exec()) match in a different way and are not Perl-compatible.

(l) PCRE recognizes some special sequences such as (*CR) at the start of @@ -203,9 +211,9 @@ Cambridge CB2 3QH, England. REVISION

-Last updated: 14 November 2011 +Last updated: 01 June 2012
-Copyright © 1997-2011 University of Cambridge. +Copyright © 1997-2012 University of Cambridge.

Return to the PCRE index page.