ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 314 by ph10, Fri Jan 25 17:09:21 2008 UTC revision 430 by ph10, Tue Sep 1 16:29:46 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.6 21-Jan-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.
79    14. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
80        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
81        library.
84    Version 7.9 11-Apr-09
85    ---------------------
87    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
88        (pcretest), all targets were linked against these libraries. This included
89        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
90        libraries. This caused unwanted dependencies to be created. This problem
91        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
92        pcretest is linked with readline.
94    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
95        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
96        moved outside it again, because FALSE and TRUE are already defined in AIX,
97        but BOOL is not.
99    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
100        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
102    4.  The pcregrep documentation said spaces were inserted as well as colons (or
103        hyphens) following file names and line numbers when outputting matching
104        lines. This is not true; no spaces are inserted. I have also clarified the
105        wording for the --colour (or --color) option.
107    5.  In pcregrep, when --colour was used with -o, the list of matching strings
108        was not coloured; this is different to GNU grep, so I have changed it to be
109        the same.
111    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
112        each matching line was coloured. Now it goes on to look for further matches
113        of any of the test patterns, which is the same behaviour as GNU grep.
115    7.  A pattern that could match an empty string could cause pcregrep to loop; it
116        doesn't make sense to accept an empty string match in pcregrep, so I have
117        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
118        seems to be how GNU grep behaves.
120    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
121        start or after a newline", because the conditional assertion was not being
122        correctly handled. The rule now is that both the assertion and what follows
123        in the first alternative must satisfy the test.
125    9.  If auto-callout was enabled in a pattern with a conditional group whose
126        condition was an assertion, PCRE could crash during matching, both with
127        pcre_exec() and pcre_dfa_exec().
129    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
130        used for matching.
132    11. Unicode property support in character classes was not working for
133        characters (bytes) greater than 127 when not in UTF-8 mode.
135    12. Added the -M command line option to pcretest.
137    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
139    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
141    16. Added comments and documentation about mis-use of no_arg in the C++
142        wrapper.
144    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
145        from Martin Jerabek that uses macro names for all relevant character and
146        string constants.
148    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
149        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
150        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
151        these, but not everybody uses configure.
153    19. A conditional group that had only one branch was not being correctly
154        recognized as an item that could match an empty string. This meant that an
155        enclosing group might also not be so recognized, causing infinite looping
156        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
157        with the subject "ab", where knowledge that the repeated group can match
158        nothing is needed in order to break the loop.
160    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
161        exec(), but without supplying a callout function, matching went wrong.
163    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
164        leak if the size of the offset vector was greater than 30. When the vector
165        is smaller, the saved offsets during recursion go onto a local stack
166        vector, but for larger vectors malloc() is used. It was failing to free
167        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
168        error, in fact).
170    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
171        heapframe that is used only when UTF-8 support is enabled. This caused no
172        problem, but was untidy.
174    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
175        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
176        included within another project.
178    24. Steven Van Ingelgem's patches to add more options to the CMake support,
179        slightly modified by me:
181          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
182              not building pcregrep.
184          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
185              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
187    25. Forward references, both numeric and by name, in patterns that made use of
188        duplicate group numbers, could behave incorrectly or give incorrect errors,
189        because when scanning forward to find the reference group, PCRE was not
190        taking into account the duplicate group numbers. A pattern such as
191        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
193    26. Changed a few more instances of "const unsigned char *" to USPTR, making
194        the feature of a custom pointer more persuasive (as requested by a user).
196    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
197        pcretest.c, inside #ifndefs, because it seems they are sometimes already
198        pre-defined.
200    28. Added support for (*UTF8) at the start of a pattern.
202    29. Arrange for flags added by the "release type" setting in CMake to be shown
203        in the configuration summary.
206    Version 7.8 05-Sep-08
207    ---------------------
209    1.  Replaced UCP searching code with optimized version as implemented for Ad
210        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
211        stage table and inline lookup instead of a function, giving speed ups of 2
212        to 5 times on some simple patterns that I tested. Permission was given to
213        distribute the MultiStage2.py script that generates the tables (it's not in
214        the tarball, but is in the Subversion repository).
216    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
217        scripts.
219    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
220        a group with a zero qualifier. The result of the study could be incorrect,
221        or the function might crash, depending on the pattern.
223    4.  Caseless matching was not working for non-ASCII characters in back
224        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
225        It now works when Unicode Property Support is available.
227    5.  In pcretest, an escape such as \x{de} in the data was always generating
228        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
229        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
230        truncation.
232    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
234    7.  Added two (int) casts to pcregrep when printing the difference of two
235        pointers, in case they are 64-bit values.
237    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
238        test 2 if it fails.
240    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
241        and a #define of that name to empty if it is not externally set. This is to
242        allow users of MSVC to set it if necessary.
244    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
245        the convenience functions in the pcre_get.c source file.
247    11. An option change at the start of a pattern that had top-level alternatives
248        could cause overwriting and/or a crash. This command provoked a crash in
249        some environments:
251          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
253        This potential security problem was recorded as CVE-2008-2371.
255    12. For a pattern where the match had to start at the beginning or immediately
256        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
257        pcre_dfa_exec() could read past the end of the passed subject if there was
258        no match. To help with detecting such bugs (e.g. with valgrind), I modified
259        pcretest so that it places the subject at the end of its malloc-ed buffer.
261    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
262        exec() might read past the end of the data buffer in UTF-8 mode.
264    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
265        the data contained the byte 0x85 as part of a UTF-8 character within its
266        first line. This applied both to normal and DFA matching.
268    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
269        /^[^d]*?$/8 failed to match "abc".
271    16. Added a missing copyright notice to pcrecpp_internal.h.
273    17. Make it more clear in the documentation that values returned from
274        pcre_exec() in ovector are byte offsets, not character counts.
276    18. Tidied a few places to stop certain compilers from issuing warnings.
278    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
279        supplied by Stefan Weber. I made a further small update for 7.8 because
280        there is a change of source arrangements: the pcre_searchfuncs.c module is
281        replaced by pcre_ucd.c.
284    Version 7.7 07-May-08
285    ---------------------
287    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
288        a string to a long long, pretend we don't even have a long long." This is
289        done by checking for the strtoq, strtoll, and _strtoi64 functions.
291    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
292        pre-7.6 versions, which defined a global no_arg variable instead of putting
293        it in the RE class. (See also #8 below.)
295    3.  Remove a line of dead code, identified by coverity and reported by Nuno
296        Lopes.
298    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
300        (1) The include/exclude patterns were being applied to the whole pathnames
301            of files, instead of just to the final components.
303        (2) If there was more than one level of directory, the subdirectories were
304            skipped unless they satisfied the include/exclude conditions. This is
305            inconsistent with GNU grep (and could even be seen as contrary to the
306            pcregrep specification - which I improved to make it absolutely clear).
307            The action now is always to scan all levels of directory, and just
308            apply the include/exclude patterns to regular files.
310    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
311        --exclude_dir in the tests to avoid scanning .svn directories.
313    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
314        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
315        doesn't support NULs in patterns.
317    7.  Added some missing "const"s to declarations of static tables in
318        pcre_compile.c and pcre_dfa_exec.c.
320    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
321        caused by fix #2  above. (Subsequently also a second patch to fix the
322        first patch. And a third patch - this was a messy problem.)
324    9.  Applied Craig's patch to remove the use of push_back().
326    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
327        matching function regexec().
329    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
330        which, however, unlike Perl's \g{...}, are subroutine calls, not back
331        references. PCRE supports relative numbers with this syntax (I don't think
332        Oniguruma does).
334    12. Previously, a group with a zero repeat such as (...){0} was completely
335        omitted from the compiled regex. However, this means that if the group
336        was called as a subroutine from elsewhere in the pattern, things went wrong
337        (an internal error was given). Such groups are now left in the compiled
338        pattern, with a new opcode that causes them to be skipped at execution
339        time.
341    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
342        to the way PCRE behaves:
344        (a) A lone ] character is dis-allowed (Perl treats it as data).
346        (b) A back reference to an unmatched subpattern matches an empty string
347            (Perl fails the current match path).
349        (c) A data ] in a character class must be notated as \] because if the
350            first data character in a class is ], it defines an empty class. (In
351            Perl it is not possible to have an empty class.) The empty class []
352            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
353            The negative empty class [^] matches any one character, independently
354            of the DOTALL setting.
356    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
357        non-existent subpattern following a character class starting with ']' and
358        containing () gave an internal compiling error instead of "reference to
359        non-existent subpattern". Fortunately, when the pattern did exist, the
360        compiled code was correct. (When scanning forwards to check for the
361        existencd of the subpattern, it was treating the data ']' as terminating
362        the class, so got the count wrong. When actually compiling, the reference
363        was subsequently set up correctly.)
365    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
366        it was being rejected as not supported by pcre_dfa_exec(), even though
367        other assertions are supported. I have made pcre_dfa_exec() support
368        (*FAIL).
370    16. The implementation of 13c above involved the invention of a new opcode,
371        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
372        cannot be changed at match time, I realized I could make a small
373        improvement to matching performance by compiling OP_ALLANY instead of
374        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
375        on the OP_ANY path.
377    17. Compiling pcretest on Windows with readline support failed without the
378        following two fixes: (1) Make the unistd.h include conditional on
379        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
381    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
382        ncurses library to be included for pcretest when ReadLine support is
383        requested, but also to allow for it to be overridden. This patch came from
384        Daniel Bergström.
386    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
387        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
388        any errors with the current Unicode tables. Thanks to Peter Kankowski for
389        spotting this.
392    Version 7.6 28-Jan-08
393  ---------------------  ---------------------
395  1.  A character class containing a very large number of characters with  1.  A character class containing a very large number of characters with
# Line 37  Version 7.6 21-Jan-08 Line 425  Version 7.6 21-Jan-08
425      solves the problem, but it does no harm.      solves the problem, but it does no harm.
427  6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and  6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
428      NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured      NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
429      with CMake, and also correct the comment about stack recursion.      with CMake, and also correct the comment about stack recursion.
431  7.  Remove the automatic building of pcredemo from the ./configure system and  7.  Remove the automatic building of pcredemo from the ./configure system and
# Line 46  Version 7.6 21-Jan-08 Line 434  Version 7.6 21-Jan-08
434      building it automatically is not really right. What is more, it gave      building it automatically is not really right. What is more, it gave
435      trouble in some build environments.      trouble in some build environments.
437    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
440  Version 7.5 10-Jan-08  Version 7.5 10-Jan-08
441  ---------------------  ---------------------

Removed from v.314  
changed lines
  Added in v.430

  ViewVC Help
Powered by ViewVC 1.1.5