1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
2 |
------------------ |
------------------ |
3 |
|
|
4 |
Version 7.9 xx-xxx-09 |
Version 8.00 ??-???-?? |
5 |
|
---------------------- |
6 |
|
|
7 |
|
1. The table for translating pcre_compile() error codes into POSIX error codes |
8 |
|
was out-of-date, and there was no check on the pcre_compile() error code |
9 |
|
being within the table. This could lead to an OK return being given in |
10 |
|
error. |
11 |
|
|
12 |
|
2. Changed the call to open a subject file in pcregrep from fopen(pathname, |
13 |
|
"r") to fopen(pathname, "rb"), which fixed a problem with some of the tests |
14 |
|
in a Windows environment. |
15 |
|
|
16 |
|
|
17 |
|
Version 7.9 11-Apr-09 |
18 |
--------------------- |
--------------------- |
19 |
|
|
20 |
1. When building with support for bzlib/zlib (pcregrep) and/or readline |
1. When building with support for bzlib/zlib (pcregrep) and/or readline |
21 |
(pcretest), all targets were linked against these libraries. This included |
(pcretest), all targets were linked against these libraries. This included |
22 |
libpcre, libpcreposix, and libpcrecpp, even though they do not use these |
libpcre, libpcreposix, and libpcrecpp, even though they do not use these |
23 |
libraries. This caused unwanted dependencies to be created. This problem |
libraries. This caused unwanted dependencies to be created. This problem |
24 |
has been fixed, and now only pcregrep is linked with bzlib/zlib and only |
has been fixed, and now only pcregrep is linked with bzlib/zlib and only |
25 |
pcretest is linked with readline. |
pcretest is linked with readline. |
26 |
|
|
27 |
2. The "typedef int BOOL" in pcre_internal.h that was included inside the |
2. The "typedef int BOOL" in pcre_internal.h that was included inside the |
28 |
"#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been |
"#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been |
29 |
moved outside it again, because FALSE and TRUE are already defined in AIX, |
moved outside it again, because FALSE and TRUE are already defined in AIX, |
30 |
but BOOL is not. |
but BOOL is not. |
31 |
|
|
32 |
3. The pcre_config() function was treating the PCRE_MATCH_LIMIT and |
3. The pcre_config() function was treating the PCRE_MATCH_LIMIT and |
33 |
PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints. |
PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints. |
34 |
|
|
35 |
4. The pcregrep documentation said spaces were inserted as well as colons (or |
4. The pcregrep documentation said spaces were inserted as well as colons (or |
36 |
hyphens) following file names and line numbers when outputting matching |
hyphens) following file names and line numbers when outputting matching |
37 |
lines. This is not true; no spaces are inserted. I have also clarified the |
lines. This is not true; no spaces are inserted. I have also clarified the |
38 |
wording for the --colour (or --color) option. |
wording for the --colour (or --color) option. |
39 |
|
|
40 |
5. In pcregrep, when --colour was used with -o, the list of matching strings |
5. In pcregrep, when --colour was used with -o, the list of matching strings |
41 |
was not coloured; this is different to GNU grep, so I have changed it to be |
was not coloured; this is different to GNU grep, so I have changed it to be |
42 |
the same. |
the same. |
43 |
|
|
44 |
6. When --colo(u)r was used in pcregrep, only the first matching substring in |
6. When --colo(u)r was used in pcregrep, only the first matching substring in |
45 |
each matching line was coloured. Now it goes on to look for further matches |
each matching line was coloured. Now it goes on to look for further matches |
46 |
of any of the test patterns, which is the same behaviour as GNU grep. |
of any of the test patterns, which is the same behaviour as GNU grep. |
47 |
|
|
48 |
7. A pattern that could match an empty string could cause pcregrep to loop; it |
7. A pattern that could match an empty string could cause pcregrep to loop; it |
49 |
doesn't make sense to accept an empty string match in pcregrep, so I have |
doesn't make sense to accept an empty string match in pcregrep, so I have |
50 |
locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this |
locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this |
51 |
seems to be how GNU grep behaves. |
seems to be how GNU grep behaves. |
52 |
|
|
53 |
8. The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at |
8. The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at |
54 |
start or after a newline", because the conditional assertion was not being |
start or after a newline", because the conditional assertion was not being |
55 |
correctly handled. The rule now is that both the assertion and what follows |
correctly handled. The rule now is that both the assertion and what follows |
56 |
in the first alternative must satisfy the test. |
in the first alternative must satisfy the test. |
57 |
|
|
58 |
9. If auto-callout was enabled in a pattern with a conditional group, PCRE |
9. If auto-callout was enabled in a pattern with a conditional group whose |
59 |
could crash during matching. |
condition was an assertion, PCRE could crash during matching, both with |
60 |
|
pcre_exec() and pcre_dfa_exec(). |
61 |
10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was |
|
62 |
used for matching. |
10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was |
63 |
|
used for matching. |
64 |
11. Unicode property support in character classes was not working for |
|
65 |
|
11. Unicode property support in character classes was not working for |
66 |
characters (bytes) greater than 127 when not in UTF-8 mode. |
characters (bytes) greater than 127 when not in UTF-8 mode. |
67 |
|
|
68 |
12. Added the -M command line option to pcretest. |
12. Added the -M command line option to pcretest. |
69 |
|
|
70 |
14. Added the non-standard REG_NOTEMPTY option to the POSIX interface. |
14. Added the non-standard REG_NOTEMPTY option to the POSIX interface. |
71 |
|
|
72 |
15. Added the PCRE_NO_START_OPTIMIZE match-time option. |
15. Added the PCRE_NO_START_OPTIMIZE match-time option. |
73 |
|
|
74 |
16. Added comments and documentation about mis-use of no_arg in the C++ |
16. Added comments and documentation about mis-use of no_arg in the C++ |
75 |
wrapper. |
wrapper. |
76 |
|
|
77 |
|
17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch |
78 |
|
from Martin Jerabek that uses macro names for all relevant character and |
79 |
|
string constants. |
80 |
|
|
81 |
|
18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and |
82 |
|
SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without |
83 |
|
SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of |
84 |
|
these, but not everybody uses configure. |
85 |
|
|
86 |
|
19. A conditional group that had only one branch was not being correctly |
87 |
|
recognized as an item that could match an empty string. This meant that an |
88 |
|
enclosing group might also not be so recognized, causing infinite looping |
89 |
|
(and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$ |
90 |
|
with the subject "ab", where knowledge that the repeated group can match |
91 |
|
nothing is needed in order to break the loop. |
92 |
|
|
93 |
|
20. If a pattern that was compiled with callouts was matched using pcre_dfa_ |
94 |
|
exec(), but without supplying a callout function, matching went wrong. |
95 |
|
|
96 |
|
21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory |
97 |
|
leak if the size of the offset vector was greater than 30. When the vector |
98 |
|
is smaller, the saved offsets during recursion go onto a local stack |
99 |
|
vector, but for larger vectors malloc() is used. It was failing to free |
100 |
|
when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal" |
101 |
|
error, in fact). |
102 |
|
|
103 |
|
22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the |
104 |
|
heapframe that is used only when UTF-8 support is enabled. This caused no |
105 |
|
problem, but was untidy. |
106 |
|
|
107 |
|
23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name |
108 |
|
CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is |
109 |
|
included within another project. |
110 |
|
|
111 |
|
24. Steven Van Ingelgem's patches to add more options to the CMake support, |
112 |
|
slightly modified by me: |
113 |
|
|
114 |
|
(a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including |
115 |
|
not building pcregrep. |
116 |
|
|
117 |
|
(b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only |
118 |
|
if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep. |
119 |
|
|
120 |
|
25. Forward references, both numeric and by name, in patterns that made use of |
121 |
|
duplicate group numbers, could behave incorrectly or give incorrect errors, |
122 |
|
because when scanning forward to find the reference group, PCRE was not |
123 |
|
taking into account the duplicate group numbers. A pattern such as |
124 |
|
^X(?3)(a)(?|(b)|(q))(Y) is an example. |
125 |
|
|
126 |
|
26. Changed a few more instances of "const unsigned char *" to USPTR, making |
127 |
|
the feature of a custom pointer more persuasive (as requested by a user). |
128 |
|
|
129 |
|
27. Wrapped the definitions of fileno and isatty for Windows, which appear in |
130 |
|
pcretest.c, inside #ifndefs, because it seems they are sometimes already |
131 |
|
pre-defined. |
132 |
|
|
133 |
|
28. Added support for (*UTF8) at the start of a pattern. |
134 |
|
|
135 |
|
29. Arrange for flags added by the "release type" setting in CMake to be shown |
136 |
|
in the configuration summary. |
137 |
|
|
138 |
|
|
139 |
Version 7.8 05-Sep-08 |
Version 7.8 05-Sep-08 |
140 |
--------------------- |
--------------------- |