| 69 |
duplicate names are permitted. If none of the named substrings are set, the |
duplicate names are permitted. If none of the named substrings are set, the |
| 70 |
functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an |
functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an |
| 71 |
empty string. |
empty string. |
| 72 |
|
|
| 73 |
|
11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E |
| 74 |
|
instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error, |
| 75 |
|
because the ] is interpreted as the first data character and the |
| 76 |
|
terminating ] is not found. PCRE has been made compatible with Perl in this |
| 77 |
|
regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could |
| 78 |
|
cause memory overwriting. |
| 79 |
|
|
| 80 |
|
10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty |
| 81 |
|
string has been matched (to stop an infinite loop). It was not recognizing |
| 82 |
|
a conditional subpattern that could match an empty string if that |
| 83 |
|
subpattern was within another subpattern. For example, it looped when |
| 84 |
|
trying to match (((?(1)X|))*) but it was OK with ((?(1)X|)*) where the |
| 85 |
|
condition was not nested. This bug has been fixed. |
| 86 |
|
|
| 87 |
|
|
| 88 |
Version 7.2 19-Jun-07 |
Version 7.2 19-Jun-07 |
Parent Directory
| 
Revision Log
| 
Patch