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