| 39 |
/t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial |
/t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial |
| 40 |
match rather than a full match, which was wrong by the old rules, but is |
match rather than a full match, which was wrong by the old rules, but is |
| 41 |
now correct.] |
now correct.] |
| 42 |
|
|
| 43 |
|
6. There was a bug in the handling of #-introduced comments, recognized when |
| 44 |
|
PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set. |
| 45 |
|
If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose |
| 46 |
|
UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when |
| 47 |
|
scanning for the end of the comment. (*Character* 0x85 is an "any" newline, |
| 48 |
|
but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several |
| 49 |
|
places in pcre_compile(). |
| 50 |
|
|
| 51 |
|
7. Related to (6) above, when pcre_compile() was skipping #-introduced |
| 52 |
|
comments when looking ahead for named forward references to subpatterns, |
| 53 |
|
the only newline sequence it recognized was NL. It now handles newlines |
| 54 |
|
according to the set newline convention. |
| 55 |
|
|
| 56 |
|
8. SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the |
| 57 |
|
former, but used strtoul(), whereas pcretest avoided strtoul() but did not |
| 58 |
|
cater for a lack of strerror(). These oversights have been fixed. |
| 59 |
|
|
| 60 |
|
9. Added --match-limit and --recursion-limit to pcregrep. |
| 61 |
|
|
| 62 |
|
10. Added two casts needed to build with Visual Studio when NO_RECURSE is set. |
| 63 |
|
|
| 64 |
|
|
| 65 |
Version 8.10 25-Jun-2010 |
Version 8.10 25-Jun-2010 |
Parent Directory
| 
Revision Log
| 
Patch