1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
2 |
------------------ |
------------------ |
3 |
|
|
4 |
Version 7.5 29-Dec-07 |
Version 7.5 31-Dec-07 |
5 |
--------------------- |
--------------------- |
6 |
|
|
7 |
1. Applied a patch from Craig: "This patch makes it possible to 'ignore' |
1. Applied a patch from Craig: "This patch makes it possible to 'ignore' |
118 |
newline. The bug was in the code for advancing after a failed match and |
newline. The bug was in the code for advancing after a failed match and |
119 |
checking that the new position followed a newline. It was not taking |
checking that the new position followed a newline. It was not taking |
120 |
account of UTF-8 characters correctly. |
account of UTF-8 characters correctly. |
121 |
|
|
122 |
|
23. PCRE was behaving differently from Perl in the way it recognized POSIX |
123 |
|
character classes. PCRE was not treating the sequence [:...:] as a |
124 |
|
character class unless the ... were all letters. Perl, however, seems to |
125 |
|
allow any characters between [: and :], though of course it rejects as |
126 |
|
unknown any "names" that contain non-letters, because all the known class |
127 |
|
names consist only of letters. Thus, Perl gives an error for [[:1234:]], |
128 |
|
for example, whereas PCRE did not - it did not recognize a POSIX character |
129 |
|
class. This seemed a bit dangerous, so the code has been changed to be |
130 |
|
closer to Perl. The behaviour is not identical to Perl, because PCRE will |
131 |
|
diagnose an unknown class for, for example, [[:l\ower:]] where Perl will |
132 |
|
treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where |
133 |
|
Perl does, and where it didn't before. |
134 |
|
|
135 |
|
|
136 |
Version 7.4 21-Sep-07 |
Version 7.4 21-Sep-07 |