ViewVC logotype

Diff of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 351 by ph10, Fri Jul 4 18:27:16 2008 UTC revision 421 by ph10, Fri Aug 14 15:43:27 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.0 02 Jul-08  Version 8.00 ??-???-??
5    ----------------------
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.
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.
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.
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.
30    Version 7.9 11-Apr-09
31    ---------------------
33    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
34        (pcretest), all targets were linked against these libraries. This included
35        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
36        libraries. This caused unwanted dependencies to be created. This problem
37        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
38        pcretest is linked with readline.
40    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
41        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
42        moved outside it again, because FALSE and TRUE are already defined in AIX,
43        but BOOL is not.
45    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
46        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
48    4.  The pcregrep documentation said spaces were inserted as well as colons (or
49        hyphens) following file names and line numbers when outputting matching
50        lines. This is not true; no spaces are inserted. I have also clarified the
51        wording for the --colour (or --color) option.
53    5.  In pcregrep, when --colour was used with -o, the list of matching strings
54        was not coloured; this is different to GNU grep, so I have changed it to be
55        the same.
57    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
58        each matching line was coloured. Now it goes on to look for further matches
59        of any of the test patterns, which is the same behaviour as GNU grep.
61    7.  A pattern that could match an empty string could cause pcregrep to loop; it
62        doesn't make sense to accept an empty string match in pcregrep, so I have
63        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
64        seems to be how GNU grep behaves.
66    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
67        start or after a newline", because the conditional assertion was not being
68        correctly handled. The rule now is that both the assertion and what follows
69        in the first alternative must satisfy the test.
71    9.  If auto-callout was enabled in a pattern with a conditional group whose
72        condition was an assertion, PCRE could crash during matching, both with
73        pcre_exec() and pcre_dfa_exec().
75    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
76        used for matching.
78    11. Unicode property support in character classes was not working for
79        characters (bytes) greater than 127 when not in UTF-8 mode.
81    12. Added the -M command line option to pcretest.
83    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
85    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
87    16. Added comments and documentation about mis-use of no_arg in the C++
88        wrapper.
90    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
91        from Martin Jerabek that uses macro names for all relevant character and
92        string constants.
94    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
95        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
96        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
97        these, but not everybody uses configure.
99    19. A conditional group that had only one branch was not being correctly
100        recognized as an item that could match an empty string. This meant that an
101        enclosing group might also not be so recognized, causing infinite looping
102        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
103        with the subject "ab", where knowledge that the repeated group can match
104        nothing is needed in order to break the loop.
106    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
107        exec(), but without supplying a callout function, matching went wrong.
109    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
110        leak if the size of the offset vector was greater than 30. When the vector
111        is smaller, the saved offsets during recursion go onto a local stack
112        vector, but for larger vectors malloc() is used. It was failing to free
113        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
114        error, in fact).
116    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
117        heapframe that is used only when UTF-8 support is enabled. This caused no
118        problem, but was untidy.
120    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
121        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
122        included within another project.
124    24. Steven Van Ingelgem's patches to add more options to the CMake support,
125        slightly modified by me:
127          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
128              not building pcregrep.
130          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
131              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
133    25. Forward references, both numeric and by name, in patterns that made use of
134        duplicate group numbers, could behave incorrectly or give incorrect errors,
135        because when scanning forward to find the reference group, PCRE was not
136        taking into account the duplicate group numbers. A pattern such as
137        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
139    26. Changed a few more instances of "const unsigned char *" to USPTR, making
140        the feature of a custom pointer more persuasive (as requested by a user).
142    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
143        pcretest.c, inside #ifndefs, because it seems they are sometimes already
144        pre-defined.
146    28. Added support for (*UTF8) at the start of a pattern.
148    29. Arrange for flags added by the "release type" setting in CMake to be shown
149        in the configuration summary.
152    Version 7.8 05-Sep-08
153  ---------------------  ---------------------
155  1.  Replaced UCP searching code with optimized version as implemented for Ad  1.  Replaced UCP searching code with optimized version as implemented for Ad
# Line 14  Version 8.0 02 Jul-08 Line 162  Version 8.0 02 Jul-08
162  2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more  2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
163      scripts.      scripts.
165    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
166        a group with a zero qualifier. The result of the study could be incorrect,
167        or the function might crash, depending on the pattern.
169    4.  Caseless matching was not working for non-ASCII characters in back
170        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
171        It now works when Unicode Property Support is available.
173    5.  In pcretest, an escape such as \x{de} in the data was always generating
174        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
175        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
176        truncation.
178    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
180    7.  Added two (int) casts to pcregrep when printing the difference of two
181        pointers, in case they are 64-bit values.
183    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
184        test 2 if it fails.
186    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
187        and a #define of that name to empty if it is not externally set. This is to
188        allow users of MSVC to set it if necessary.
190    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
191        the convenience functions in the pcre_get.c source file.
193    11. An option change at the start of a pattern that had top-level alternatives
194        could cause overwriting and/or a crash. This command provoked a crash in
195        some environments:
197          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
199        This potential security problem was recorded as CVE-2008-2371.
201    12. For a pattern where the match had to start at the beginning or immediately
202        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
203        pcre_dfa_exec() could read past the end of the passed subject if there was
204        no match. To help with detecting such bugs (e.g. with valgrind), I modified
205        pcretest so that it places the subject at the end of its malloc-ed buffer.
207    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
208        exec() might read past the end of the data buffer in UTF-8 mode.
210    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
211        the data contained the byte 0x85 as part of a UTF-8 character within its
212        first line. This applied both to normal and DFA matching.
214    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
215        /^[^d]*?$/8 failed to match "abc".
217    16. Added a missing copyright notice to pcrecpp_internal.h.
219    17. Make it more clear in the documentation that values returned from
220        pcre_exec() in ovector are byte offsets, not character counts.
222    18. Tidied a few places to stop certain compilers from issuing warnings.
224    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
225        supplied by Stefan Weber. I made a further small update for 7.8 because
226        there is a change of source arrangements: the pcre_searchfuncs.c module is
227        replaced by pcre_ucd.c.
230  Version 7.7 07-May-08  Version 7.7 07-May-08
231  ---------------------  ---------------------

Removed from v.351  
changed lines
  Added in v.421

  ViewVC Help
Powered by ViewVC 1.1.5