1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
2 |
------------------ |
------------------ |
3 |
|
|
4 |
Version 7.5 27-Dec-07 |
Version 7.7 05-Mar-08 |
5 |
|
--------------------- |
6 |
|
|
7 |
|
1. Applied Craig's patch to sort out a long long problem: "If we can't convert |
8 |
|
a string to a long long, pretend we don't even have a long long." This is |
9 |
|
done by checking for the strtoq, strtoll, and _strtoi64 functions. |
10 |
|
|
11 |
|
2. Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with |
12 |
|
pre-7.6 versions, which defined a global no_arg variable instead of putting |
13 |
|
it in the RE class. |
14 |
|
|
15 |
|
3. Remove a line of dead code, identified by coverity and reported by Nuno |
16 |
|
Lopes. |
17 |
|
|
18 |
|
4. Fixed two related pcregrep bugs involving -r with --include or --exclude: |
19 |
|
|
20 |
|
(1) The include/exclude patterns were being applied to the whole pathnames |
21 |
|
of files, instead of just to the final components. |
22 |
|
|
23 |
|
(2) If there was more than one level of directory, the subdirectories were |
24 |
|
skipped unless they satisfied the include/exclude conditions. This is |
25 |
|
inconsistent with GNU grep (and could even be seen as contrary to the |
26 |
|
pcregrep specification - which I improved to make it absolutely clear). |
27 |
|
The action now is always to scan all levels of directory, and just |
28 |
|
apply the include/exclude patterns to regular files. |
29 |
|
|
30 |
|
5. Added the --include_dir and --exclude_dir patterns to pcregrep, and used |
31 |
|
--exclude_dir in the tests to avoid scanning .svn directories. |
32 |
|
|
33 |
|
6. Applied Craig's patch to the QuoteMeta function so that it escapes the |
34 |
|
NUL character as backslash + 0 rather than backslash + NUL, because PCRE |
35 |
|
doesn't support NULs in patterns. |
36 |
|
|
37 |
|
|
38 |
|
Version 7.6 28-Jan-08 |
39 |
|
--------------------- |
40 |
|
|
41 |
|
1. A character class containing a very large number of characters with |
42 |
|
codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer |
43 |
|
overflow. |
44 |
|
|
45 |
|
2. Patch to cut out the "long long" test in pcrecpp_unittest when |
46 |
|
HAVE_LONG_LONG is not defined. |
47 |
|
|
48 |
|
3. Applied Christian Ehrlicher's patch to update the CMake build files to |
49 |
|
bring them up to date and include new features. This patch includes: |
50 |
|
|
51 |
|
- Fixed PH's badly added libz and libbz2 support. |
52 |
|
- Fixed a problem with static linking. |
53 |
|
- Added pcredemo. [But later removed - see 7 below.] |
54 |
|
- Fixed dftables problem and added an option. |
55 |
|
- Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and |
56 |
|
HAVE_LONG_LONG. |
57 |
|
- Added readline support for pcretest. |
58 |
|
- Added an listing of the option settings after cmake has run. |
59 |
|
|
60 |
|
4. A user submitted a patch to Makefile that makes it easy to create |
61 |
|
"pcre.dll" under mingw when using Configure/Make. I added stuff to |
62 |
|
Makefile.am that cause it to include this special target, without |
63 |
|
affecting anything else. Note that the same mingw target plus all |
64 |
|
the other distribution libraries and programs are now supported |
65 |
|
when configuring with CMake (see 6 below) instead of with |
66 |
|
Configure/Make. |
67 |
|
|
68 |
|
5. Applied Craig's patch that moves no_arg into the RE class in the C++ code. |
69 |
|
This is an attempt to solve the reported problem "pcrecpp::no_arg is not |
70 |
|
exported in the Windows port". It has not yet been confirmed that the patch |
71 |
|
solves the problem, but it does no harm. |
72 |
|
|
73 |
|
6. Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and |
74 |
|
NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured |
75 |
|
with CMake, and also correct the comment about stack recursion. |
76 |
|
|
77 |
|
7. Remove the automatic building of pcredemo from the ./configure system and |
78 |
|
from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example |
79 |
|
of a program that users should build themselves after PCRE is installed, so |
80 |
|
building it automatically is not really right. What is more, it gave |
81 |
|
trouble in some build environments. |
82 |
|
|
83 |
|
8. Further tidies to CMakeLists.txt from Sheri and Christian. |
84 |
|
|
85 |
|
|
86 |
|
Version 7.5 10-Jan-08 |
87 |
--------------------- |
--------------------- |
88 |
|
|
89 |
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' |
181 |
|
|
182 |
20. In pcrecpp.cc, the variable 'count' was incremented twice in |
20. In pcrecpp.cc, the variable 'count' was incremented twice in |
183 |
RE::GlobalReplace(). As a result, the number of replacements returned was |
RE::GlobalReplace(). As a result, the number of replacements returned was |
184 |
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 |
185 |
|
later patch that removed the other one (the right fix) and added unit tests |
186 |
|
that check the return values (which was not done before). |
187 |
|
|
188 |
21. Several CMake things: |
21. Several CMake things: |
189 |
|
|
195 |
|
|
196 |
(3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2. |
(3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2. |
197 |
|
|
198 |
|
22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.* |
199 |
|
crashed when matching a string such as a\x{2029}b (note that \x{2029} is a |
200 |
|
UTF-8 newline character). The key issue is that the pattern starts .*; |
201 |
|
this means that the match must be either at the beginning, or after a |
202 |
|
newline. The bug was in the code for advancing after a failed match and |
203 |
|
checking that the new position followed a newline. It was not taking |
204 |
|
account of UTF-8 characters correctly. |
205 |
|
|
206 |
|
23. PCRE was behaving differently from Perl in the way it recognized POSIX |
207 |
|
character classes. PCRE was not treating the sequence [:...:] as a |
208 |
|
character class unless the ... were all letters. Perl, however, seems to |
209 |
|
allow any characters between [: and :], though of course it rejects as |
210 |
|
unknown any "names" that contain non-letters, because all the known class |
211 |
|
names consist only of letters. Thus, Perl gives an error for [[:1234:]], |
212 |
|
for example, whereas PCRE did not - it did not recognize a POSIX character |
213 |
|
class. This seemed a bit dangerous, so the code has been changed to be |
214 |
|
closer to Perl. The behaviour is not identical to Perl, because PCRE will |
215 |
|
diagnose an unknown class for, for example, [[:l\ower:]] where Perl will |
216 |
|
treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where |
217 |
|
Perl does, and where it didn't before. |
218 |
|
|
219 |
|
24. Rewrite so as to remove the single use of %n from pcregrep because in some |
220 |
|
Windows environments %n is disabled by default. |
221 |
|
|
222 |
|
|
223 |
Version 7.4 21-Sep-07 |
Version 7.4 21-Sep-07 |
224 |
--------------------- |
--------------------- |