| 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 |
|
3. The pcregrep --count option prints the count for each file even when it is |
| 17 |
|
zero, as does GNU grep. However, pcregrep was also printing all files when |
| 18 |
|
--files-with-matches was added. Now, when both options are given, it prints |
| 19 |
|
counts only for those files that have at least one match. (GNU grep just |
| 20 |
|
prints the file name in this circumstance, but including the count seems |
| 21 |
|
more useful - otherwise, why use --count?) Also ensured that the |
| 22 |
|
combination -clh just lists non-zero counts, with no names. |
| 23 |
|
|
| 24 |
|
4. The long form of the pcregrep -F option was incorrectly implemented as |
| 25 |
|
--fixed_strings instead of --fixed-strings. This is an incompatible change, |
| 26 |
|
but it seems right to fix it, and I didn't think it was worth preserving |
| 27 |
|
the old behaviour. |
| 28 |
|
|
| 29 |
|
5. The command line items --regex=pattern and --regexp=pattern were not |
| 30 |
|
recognized by pcregrep, which required --regex pattern or --regexp pattern |
| 31 |
|
(with a space rather than an '='). The man page documented the '=' forms, |
| 32 |
|
which are compatible with GNU grep; these now work. |
| 33 |
|
|
| 34 |
|
6. No libpcreposix.pc file was created for pkg-config; there was just |
| 35 |
|
libpcre.pc and libpcrecpp.pc. The omission has been rectified. |
| 36 |
|
|
| 37 |
|
7. Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size |
| 38 |
|
when UCP support is not needed, by modifying the Python script that |
| 39 |
|
generates it from Unicode data files. This should not matter if the module |
| 40 |
|
is correctly used as a library, but I received one complaint about 50K of |
| 41 |
|
unwanted data. My guess is that the person linked everything into his |
| 42 |
|
program rather than using a library. Anyway, it does no harm. |
| 43 |
|
|
| 44 |
|
8. A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger |
| 45 |
|
was a minimum greater than 1 for a wide character in a possessive |
| 46 |
|
repetition. Chaos could result. |
| 47 |
|
|
| 48 |
|
9. The restrictions on what a pattern can contain when partial matching is |
| 49 |
|
requested for pcre_exec() have been removed. All patterns can now be |
| 50 |
|
partially matched by this function. In addition, if there are at least two |
| 51 |
|
slots in the offset vector, the offsets of the first-encountered partial |
| 52 |
|
match are set in them when PCRE_ERROR_PARTIAL is returned. |
| 53 |
|
|
| 54 |
|
|
| 55 |
|
Version 7.9 11-Apr-09 |
| 56 |
--------------------- |
--------------------- |
| 57 |
|
|
| 58 |
1. When building with support for bzlib/zlib (pcregrep) and/or readline |
1. When building with support for bzlib/zlib (pcregrep) and/or readline |
| 68 |
but BOOL is not. |
but BOOL is not. |
| 69 |
|
|
| 70 |
3. The pcre_config() function was treating the PCRE_MATCH_LIMIT and |
3. The pcre_config() function was treating the PCRE_MATCH_LIMIT and |
| 71 |
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. |
| 72 |
|
|
| 73 |
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 |
| 74 |
hyphens) following file names and line numbers when outputting matching |
hyphens) following file names and line numbers when outputting matching |
| 146 |
CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is |
CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is |
| 147 |
included within another project. |
included within another project. |
| 148 |
|
|
| 149 |
|
24. Steven Van Ingelgem's patches to add more options to the CMake support, |
| 150 |
|
slightly modified by me: |
| 151 |
|
|
| 152 |
|
(a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including |
| 153 |
|
not building pcregrep. |
| 154 |
|
|
| 155 |
|
(b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only |
| 156 |
|
if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep. |
| 157 |
|
|
| 158 |
|
25. Forward references, both numeric and by name, in patterns that made use of |
| 159 |
|
duplicate group numbers, could behave incorrectly or give incorrect errors, |
| 160 |
|
because when scanning forward to find the reference group, PCRE was not |
| 161 |
|
taking into account the duplicate group numbers. A pattern such as |
| 162 |
|
^X(?3)(a)(?|(b)|(q))(Y) is an example. |
| 163 |
|
|
| 164 |
|
26. Changed a few more instances of "const unsigned char *" to USPTR, making |
| 165 |
|
the feature of a custom pointer more persuasive (as requested by a user). |
| 166 |
|
|
| 167 |
|
27. Wrapped the definitions of fileno and isatty for Windows, which appear in |
| 168 |
|
pcretest.c, inside #ifndefs, because it seems they are sometimes already |
| 169 |
|
pre-defined. |
| 170 |
|
|
| 171 |
|
28. Added support for (*UTF8) at the start of a pattern. |
| 172 |
|
|
| 173 |
|
29. Arrange for flags added by the "release type" setting in CMake to be shown |
| 174 |
|
in the configuration summary. |
| 175 |
|
|
| 176 |
|
|
| 177 |
Version 7.8 05-Sep-08 |
Version 7.8 05-Sep-08 |
Parent Directory
| 
Revision Log
| 
Patch