ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 345 by ph10, Mon Apr 28 15:10:02 2008 UTC revision 429 by ph10, Tue Sep 1 16:10:16 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.7 28-Apr-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.
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.
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.
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.
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.
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.
54    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
55        synonymous with PCRE_PARTIAL, for backwards compatibility, and
56        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
57        and may be more useful for multi-segment matching, especially with
58        pcre_exec().
60    11. Partial matching with pcre_exec() is now more intuitive. A partial match
61        used to be given if ever the end of the subject was reached; now it is
62        given only if matching could not proceed because another character was
63        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
64        string "Z", which now yields "no match" instead of "partial match". In the
65        case of pcre_dfa_exec(), "no match" is given if every matching path for the
66        final character ended with (*FAIL).
68    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
69        if the pattern had a "must contain" character that was already found in the
70        earlier partial match, unless partial matching was again requested. For
71        example, with the pattern /dog.(body)?/, the "must contain" character is
72        "g". If the first part-match was for the string "dog", restarting with
73        "sbody" failed.
75    13. Added a pcredemo man page, created automatically from the pcredemo.c file,
76        so that the demonstration program is easily available in environments where
77        PCRE has not been installed from source.
80    Version 7.9 11-Apr-09
81    ---------------------
83    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
84        (pcretest), all targets were linked against these libraries. This included
85        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
86        libraries. This caused unwanted dependencies to be created. This problem
87        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
88        pcretest is linked with readline.
90    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
91        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
92        moved outside it again, because FALSE and TRUE are already defined in AIX,
93        but BOOL is not.
95    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
96        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
98    4.  The pcregrep documentation said spaces were inserted as well as colons (or
99        hyphens) following file names and line numbers when outputting matching
100        lines. This is not true; no spaces are inserted. I have also clarified the
101        wording for the --colour (or --color) option.
103    5.  In pcregrep, when --colour was used with -o, the list of matching strings
104        was not coloured; this is different to GNU grep, so I have changed it to be
105        the same.
107    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
108        each matching line was coloured. Now it goes on to look for further matches
109        of any of the test patterns, which is the same behaviour as GNU grep.
111    7.  A pattern that could match an empty string could cause pcregrep to loop; it
112        doesn't make sense to accept an empty string match in pcregrep, so I have
113        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
114        seems to be how GNU grep behaves.
116    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
117        start or after a newline", because the conditional assertion was not being
118        correctly handled. The rule now is that both the assertion and what follows
119        in the first alternative must satisfy the test.
121    9.  If auto-callout was enabled in a pattern with a conditional group whose
122        condition was an assertion, PCRE could crash during matching, both with
123        pcre_exec() and pcre_dfa_exec().
125    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
126        used for matching.
128    11. Unicode property support in character classes was not working for
129        characters (bytes) greater than 127 when not in UTF-8 mode.
131    12. Added the -M command line option to pcretest.
133    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
135    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
137    16. Added comments and documentation about mis-use of no_arg in the C++
138        wrapper.
140    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
141        from Martin Jerabek that uses macro names for all relevant character and
142        string constants.
144    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
145        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
146        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
147        these, but not everybody uses configure.
149    19. A conditional group that had only one branch was not being correctly
150        recognized as an item that could match an empty string. This meant that an
151        enclosing group might also not be so recognized, causing infinite looping
152        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
153        with the subject "ab", where knowledge that the repeated group can match
154        nothing is needed in order to break the loop.
156    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
157        exec(), but without supplying a callout function, matching went wrong.
159    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
160        leak if the size of the offset vector was greater than 30. When the vector
161        is smaller, the saved offsets during recursion go onto a local stack
162        vector, but for larger vectors malloc() is used. It was failing to free
163        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
164        error, in fact).
166    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
167        heapframe that is used only when UTF-8 support is enabled. This caused no
168        problem, but was untidy.
170    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
171        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
172        included within another project.
174    24. Steven Van Ingelgem's patches to add more options to the CMake support,
175        slightly modified by me:
177          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
178              not building pcregrep.
180          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
181              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
183    25. Forward references, both numeric and by name, in patterns that made use of
184        duplicate group numbers, could behave incorrectly or give incorrect errors,
185        because when scanning forward to find the reference group, PCRE was not
186        taking into account the duplicate group numbers. A pattern such as
187        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
189    26. Changed a few more instances of "const unsigned char *" to USPTR, making
190        the feature of a custom pointer more persuasive (as requested by a user).
192    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
193        pcretest.c, inside #ifndefs, because it seems they are sometimes already
194        pre-defined.
196    28. Added support for (*UTF8) at the start of a pattern.
198    29. Arrange for flags added by the "release type" setting in CMake to be shown
199        in the configuration summary.
202    Version 7.8 05-Sep-08
203    ---------------------
205    1.  Replaced UCP searching code with optimized version as implemented for Ad
206        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
207        stage table and inline lookup instead of a function, giving speed ups of 2
208        to 5 times on some simple patterns that I tested. Permission was given to
209        distribute the MultiStage2.py script that generates the tables (it's not in
210        the tarball, but is in the Subversion repository).
212    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
213        scripts.
215    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
216        a group with a zero qualifier. The result of the study could be incorrect,
217        or the function might crash, depending on the pattern.
219    4.  Caseless matching was not working for non-ASCII characters in back
220        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
221        It now works when Unicode Property Support is available.
223    5.  In pcretest, an escape such as \x{de} in the data was always generating
224        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
225        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
226        truncation.
228    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
230    7.  Added two (int) casts to pcregrep when printing the difference of two
231        pointers, in case they are 64-bit values.
233    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
234        test 2 if it fails.
236    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
237        and a #define of that name to empty if it is not externally set. This is to
238        allow users of MSVC to set it if necessary.
240    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
241        the convenience functions in the pcre_get.c source file.
243    11. An option change at the start of a pattern that had top-level alternatives
244        could cause overwriting and/or a crash. This command provoked a crash in
245        some environments:
247          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
249        This potential security problem was recorded as CVE-2008-2371.
251    12. For a pattern where the match had to start at the beginning or immediately
252        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
253        pcre_dfa_exec() could read past the end of the passed subject if there was
254        no match. To help with detecting such bugs (e.g. with valgrind), I modified
255        pcretest so that it places the subject at the end of its malloc-ed buffer.
257    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
258        exec() might read past the end of the data buffer in UTF-8 mode.
260    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
261        the data contained the byte 0x85 as part of a UTF-8 character within its
262        first line. This applied both to normal and DFA matching.
264    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
265        /^[^d]*?$/8 failed to match "abc".
267    16. Added a missing copyright notice to pcrecpp_internal.h.
269    17. Make it more clear in the documentation that values returned from
270        pcre_exec() in ovector are byte offsets, not character counts.
272    18. Tidied a few places to stop certain compilers from issuing warnings.
274    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
275        supplied by Stefan Weber. I made a further small update for 7.8 because
276        there is a change of source arrangements: the pcre_searchfuncs.c module is
277        replaced by pcre_ucd.c.
280    Version 7.7 07-May-08
281  ---------------------  ---------------------
283  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
# Line 103  Version 7.7 28-Apr-08 Line 379  Version 7.7 28-Apr-08
379      requested, but also to allow for it to be overridden. This patch came from      requested, but also to allow for it to be overridden. This patch came from
380      Daniel Bergström.      Daniel Bergström.
382    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
383        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
384        any errors with the current Unicode tables. Thanks to Peter Kankowski for
385        spotting this.
388  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
389  ---------------------  ---------------------

Removed from v.345  
changed lines
  Added in v.429

  ViewVC Help
Powered by ViewVC 1.1.5