| 1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
| 2 |
------------------ |
------------------ |
| 3 |
|
|
| 4 |
Version 7.1 12-Mar-07 |
Version 7.3 05-Jul-07 |
| 5 |
|
--------------------- |
| 6 |
|
|
| 7 |
|
1. In the rejigging of the build system that eventually resulted in 7.1, the |
| 8 |
|
line "#include <pcre.h>" was included in pcre_internal.h. The use of angle |
| 9 |
|
brackets there is not right, since it causes compilers to look for an |
| 10 |
|
installed pcre.h, not the version that is in the source that is being |
| 11 |
|
compiled (which of course may be different). I have changed it back to: |
| 12 |
|
|
| 13 |
|
#include "pcre.h" |
| 14 |
|
|
| 15 |
|
I have a vague recollection that the change was concerned with compiling in |
| 16 |
|
different directories, but in the new build system, that is taken care of |
| 17 |
|
by the VPATH setting the Makefile. |
| 18 |
|
|
| 19 |
|
2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed |
| 20 |
|
when the subject happened to end in the byte 0x85 (e.g. if the last |
| 21 |
|
character was \x{1ec5}). *Character* 0x85 is one of the "any" newline |
| 22 |
|
characters but of course it shouldn't be taken as a newline when it is part |
| 23 |
|
of another character. The bug was that, for an unlimited repeat of . in |
| 24 |
|
not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by |
| 25 |
|
characters when looking for a newline. |
| 26 |
|
|
| 27 |
|
3. A small performance improvement in the DOTALL UTF-8 mode .* case. |
| 28 |
|
|
| 29 |
|
4. Debugging: adjusted the names of opcodes for different kinds of parentheses |
| 30 |
|
in debug output. |
| 31 |
|
|
| 32 |
|
5. Arrange to use "%I64d" instead of "%lld" for long printing in the pcrecpp |
| 33 |
|
unittest when running under MinGW. |
| 34 |
|
|
| 35 |
|
6. ESC_K was left out of the EBCDIC table. |
| 36 |
|
|
| 37 |
|
|
| 38 |
|
|
| 39 |
|
Version 7.2 19-Jun-07 |
| 40 |
|
--------------------- |
| 41 |
|
|
| 42 |
|
1. If the fr_FR locale cannot be found for test 3, try the "french" locale, |
| 43 |
|
which is apparently normally available under Windows. |
| 44 |
|
|
| 45 |
|
2. Re-jig the pcregrep tests with different newline settings in an attempt |
| 46 |
|
to make them independent of the local environment's newline setting. |
| 47 |
|
|
| 48 |
|
3. Add code to configure.ac to remove -g from the CFLAGS default settings. |
| 49 |
|
|
| 50 |
|
4. Some of the "internals" tests were previously cut out when the link size |
| 51 |
|
was not 2, because the output contained actual offsets. The recent new |
| 52 |
|
"Z" feature of pcretest means that these can be cut out, making the tests |
| 53 |
|
usable with all link sizes. |
| 54 |
|
|
| 55 |
|
5. Implemented Stan Switzer's goto replacement for longjmp() when not using |
| 56 |
|
stack recursion. This gives a massive performance boost under BSD, but just |
| 57 |
|
a small improvement under Linux. However, it saves one field in the frame |
| 58 |
|
in all cases. |
| 59 |
|
|
| 60 |
|
6. Added more features from the forthcoming Perl 5.10: |
| 61 |
|
|
| 62 |
|
(a) (?-n) (where n is a string of digits) is a relative subroutine or |
| 63 |
|
recursion call. It refers to the nth most recently opened parentheses. |
| 64 |
|
|
| 65 |
|
(b) (?+n) is also a relative subroutine call; it refers to the nth next |
| 66 |
|
to be opened parentheses. |
| 67 |
|
|
| 68 |
|
(c) Conditions that refer to capturing parentheses can be specified |
| 69 |
|
relatively, for example, (?(-2)... or (?(+3)... |
| 70 |
|
|
| 71 |
|
(d) \K resets the start of the current match so that everything before |
| 72 |
|
is not part of it. |
| 73 |
|
|
| 74 |
|
(e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible). |
| 75 |
|
|
| 76 |
|
(f) \g{name} is another synonym - part of Perl 5.10's unification of |
| 77 |
|
reference syntax. |
| 78 |
|
|
| 79 |
|
(g) (?| introduces a group in which the numbering of parentheses in each |
| 80 |
|
alternative starts with the same number. |
| 81 |
|
|
| 82 |
|
(h) \h, \H, \v, and \V match horizontal and vertical whitespace. |
| 83 |
|
|
| 84 |
|
7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and |
| 85 |
|
PCRE_INFO_JCHANGED. |
| 86 |
|
|
| 87 |
|
8. A pattern such as (.*(.)?)* caused pcre_exec() to fail by either not |
| 88 |
|
terminating or by crashing. Diagnosed by Viktor Griph; it was in the code |
| 89 |
|
for detecting groups that can match an empty string. |
| 90 |
|
|
| 91 |
|
9. A pattern with a very large number of alternatives (more than several |
| 92 |
|
hundred) was running out of internal workspace during the pre-compile |
| 93 |
|
phase, where pcre_compile() figures out how much memory will be needed. A |
| 94 |
|
bit of new cunning has reduced the workspace needed for groups with |
| 95 |
|
alternatives. The 1000-alternative test pattern now uses 12 bytes of |
| 96 |
|
workspace instead of running out of the 4096 that are available. |
| 97 |
|
|
| 98 |
|
10. Inserted some missing (unsigned int) casts to get rid of compiler warnings. |
| 99 |
|
|
| 100 |
|
11. Applied patch from Google to remove an optimization that didn't quite work. |
| 101 |
|
The report of the bug said: |
| 102 |
|
|
| 103 |
|
pcrecpp::RE("a*").FullMatch("aaa") matches, while |
| 104 |
|
pcrecpp::RE("a*?").FullMatch("aaa") does not, and |
| 105 |
|
pcrecpp::RE("a*?\\z").FullMatch("aaa") does again. |
| 106 |
|
|
| 107 |
|
12. If \p or \P was used in non-UTF-8 mode on a character greater than 127 |
| 108 |
|
it matched the wrong number of bytes. |
| 109 |
|
|
| 110 |
|
|
| 111 |
|
Version 7.1 24-Apr-07 |
| 112 |
--------------------- |
--------------------- |
| 113 |
|
|
| 114 |
1. Applied Bob Rossi and Daniel G's patches to convert the build system to one |
1. Applied Bob Rossi and Daniel G's patches to convert the build system to one |
| 234 |
in an attempt to make files that differ only in their line terminators |
in an attempt to make files that differ only in their line terminators |
| 235 |
compare equal. This works on Linux. |
compare equal. This works on Linux. |
| 236 |
|
|
| 237 |
|
17. Under certain error circumstances pcregrep might try to free random memory |
| 238 |
|
as it exited. This is now fixed, thanks to valgrind. |
| 239 |
|
|
| 240 |
|
19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string |
| 241 |
|
"abc\r\n\r\n", it found an unwanted second match after the second \r. This |
| 242 |
|
was because its rules for how to advance for /g after matching an empty |
| 243 |
|
string at the end of a line did not allow for this case. They now check for |
| 244 |
|
it specially. |
| 245 |
|
|
| 246 |
|
20. pcretest is supposed to handle patterns and data of any length, by |
| 247 |
|
extending its buffers when necessary. It was getting this wrong when the |
| 248 |
|
buffer for a data line had to be extended. |
| 249 |
|
|
| 250 |
|
21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or |
| 251 |
|
CRLF as a newline sequence. |
| 252 |
|
|
| 253 |
|
22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut |
| 254 |
|
out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but |
| 255 |
|
I have nevertheless tidied it up. |
| 256 |
|
|
| 257 |
|
23. Added some casts to kill warnings from HP-UX ia64 compiler. |
| 258 |
|
|
| 259 |
|
24. Added a man page for pcre-config. |
| 260 |
|
|
| 261 |
|
|
| 262 |
Version 7.0 19-Dec-06 |
Version 7.0 19-Dec-06 |
| 263 |
--------------------- |
--------------------- |
Parent Directory
| 
Revision Log
| 
Patch