| 1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
| 2 |
------------------ |
------------------ |
| 3 |
|
|
| 4 |
Version 7.5 23-Dec-07 |
Version 7.5 10-Jan-08 |
| 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' |
| 99 |
|
|
| 100 |
20. In pcrecpp.cc, the variable 'count' was incremented twice in |
20. In pcrecpp.cc, the variable 'count' was incremented twice in |
| 101 |
RE::GlobalReplace(). As a result, the number of replacements returned was |
RE::GlobalReplace(). As a result, the number of replacements returned was |
| 102 |
double what it should be. I have removed one of the increments. |
double what it should be. I removed one of the increments, but Craig sent a |
| 103 |
|
later patch that removed the other one (the right fix) and added unit tests |
| 104 |
|
that check the return values (which was not done before). |
| 105 |
|
|
| 106 |
21. Several CMake things: |
21. Several CMake things: |
| 107 |
|
|
| 108 |
(1) Arranged that, when cmake is used on Unix, the libraries end up with |
(1) Arranged that, when cmake is used on Unix, the libraries end up with |
| 109 |
the names libpcre and libpcreposix. |
the names libpcre and libpcreposix, not just pcre and pcreposix. |
| 110 |
|
|
| 111 |
(2) Arranged for pcretest and pcregrep to link with the newly-built |
(2) The above change means that pcretest and pcregrep are now correctly |
| 112 |
libraries, not previously installed ones. |
linked with the newly-built libraries, not previously installed ones. |
| 113 |
|
|
| 114 |
(3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2. |
(3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2. |
| 115 |
|
|
| 116 |
|
22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.* |
| 117 |
|
crashed when matching a string such as a\x{2029}b (note that \x{2029} is a |
| 118 |
|
UTF-8 newline character). The key issue is that the pattern starts .*; |
| 119 |
|
this means that the match must be either at the beginning, or after a |
| 120 |
|
newline. The bug was in the code for advancing after a failed match and |
| 121 |
|
checking that the new position followed a newline. It was not taking |
| 122 |
|
account of UTF-8 characters correctly. |
| 123 |
|
|
| 124 |
|
23. PCRE was behaving differently from Perl in the way it recognized POSIX |
| 125 |
|
character classes. PCRE was not treating the sequence [:...:] as a |
| 126 |
|
character class unless the ... were all letters. Perl, however, seems to |
| 127 |
|
allow any characters between [: and :], though of course it rejects as |
| 128 |
|
unknown any "names" that contain non-letters, because all the known class |
| 129 |
|
names consist only of letters. Thus, Perl gives an error for [[:1234:]], |
| 130 |
|
for example, whereas PCRE did not - it did not recognize a POSIX character |
| 131 |
|
class. This seemed a bit dangerous, so the code has been changed to be |
| 132 |
|
closer to Perl. The behaviour is not identical to Perl, because PCRE will |
| 133 |
|
diagnose an unknown class for, for example, [[:l\ower:]] where Perl will |
| 134 |
|
treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where |
| 135 |
|
Perl does, and where it didn't before. |
| 136 |
|
|
| 137 |
|
24. Rewrite so as to remove the single use of %n from pcregrep because in some |
| 138 |
|
Windows environments %n is disabled by default. |
| 139 |
|
|
| 140 |
|
|
| 141 |
Version 7.4 21-Sep-07 |
Version 7.4 21-Sep-07 |