ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 287 by ph10, Tue Dec 18 20:11:28 2007 UTC revision 377 by ph10, Sun Mar 1 12:07:19 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.5 12-Nov-07  Version 7.9 xx-xxx-09
5    ---------------------
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.
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.
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.
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.
27    5.  When --colour was used with -o, the list of matching strings was not
28        coloured; this is different to GNU grep, so I have changed it to be the
29        same.
32    Version 7.8 05-Sep-08
33    ---------------------
35    1.  Replaced UCP searching code with optimized version as implemented for Ad
36        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
37        stage table and inline lookup instead of a function, giving speed ups of 2
38        to 5 times on some simple patterns that I tested. Permission was given to
39        distribute the MultiStage2.py script that generates the tables (it's not in
40        the tarball, but is in the Subversion repository).
42    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
43        scripts.
45    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
46        a group with a zero qualifier. The result of the study could be incorrect,
47        or the function might crash, depending on the pattern.
49    4.  Caseless matching was not working for non-ASCII characters in back
50        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
51        It now works when Unicode Property Support is available.
53    5.  In pcretest, an escape such as \x{de} in the data was always generating
54        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
55        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
56        truncation.
58    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
60    7.  Added two (int) casts to pcregrep when printing the difference of two
61        pointers, in case they are 64-bit values.
63    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
64        test 2 if it fails.
66    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
67        and a #define of that name to empty if it is not externally set. This is to
68        allow users of MSVC to set it if necessary.
70    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
71        the convenience functions in the pcre_get.c source file.
73    11. An option change at the start of a pattern that had top-level alternatives
74        could cause overwriting and/or a crash. This command provoked a crash in
75        some environments:
77          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
79        This potential security problem was recorded as CVE-2008-2371.
81    12. For a pattern where the match had to start at the beginning or immediately
82        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
83        pcre_dfa_exec() could read past the end of the passed subject if there was
84        no match. To help with detecting such bugs (e.g. with valgrind), I modified
85        pcretest so that it places the subject at the end of its malloc-ed buffer.
87    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
88        exec() might read past the end of the data buffer in UTF-8 mode.
90    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
91        the data contained the byte 0x85 as part of a UTF-8 character within its
92        first line. This applied both to normal and DFA matching.
94    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
95        /^[^d]*?$/8 failed to match "abc".
97    16. Added a missing copyright notice to pcrecpp_internal.h.
99    17. Make it more clear in the documentation that values returned from
100        pcre_exec() in ovector are byte offsets, not character counts.
102    18. Tidied a few places to stop certain compilers from issuing warnings.
104    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
105        supplied by Stefan Weber. I made a further small update for 7.8 because
106        there is a change of source arrangements: the pcre_searchfuncs.c module is
107        replaced by pcre_ucd.c.
110    Version 7.7 07-May-08
111    ---------------------
113    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
114        a string to a long long, pretend we don't even have a long long." This is
115        done by checking for the strtoq, strtoll, and _strtoi64 functions.
117    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
118        pre-7.6 versions, which defined a global no_arg variable instead of putting
119        it in the RE class. (See also #8 below.)
121    3.  Remove a line of dead code, identified by coverity and reported by Nuno
122        Lopes.
124    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
126        (1) The include/exclude patterns were being applied to the whole pathnames
127            of files, instead of just to the final components.
129        (2) If there was more than one level of directory, the subdirectories were
130            skipped unless they satisfied the include/exclude conditions. This is
131            inconsistent with GNU grep (and could even be seen as contrary to the
132            pcregrep specification - which I improved to make it absolutely clear).
133            The action now is always to scan all levels of directory, and just
134            apply the include/exclude patterns to regular files.
136    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
137        --exclude_dir in the tests to avoid scanning .svn directories.
139    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
140        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
141        doesn't support NULs in patterns.
143    7.  Added some missing "const"s to declarations of static tables in
144        pcre_compile.c and pcre_dfa_exec.c.
146    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
147        caused by fix #2  above. (Subsequently also a second patch to fix the
148        first patch. And a third patch - this was a messy problem.)
150    9.  Applied Craig's patch to remove the use of push_back().
152    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
153        matching function regexec().
155    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
156        which, however, unlike Perl's \g{...}, are subroutine calls, not back
157        references. PCRE supports relative numbers with this syntax (I don't think
158        Oniguruma does).
160    12. Previously, a group with a zero repeat such as (...){0} was completely
161        omitted from the compiled regex. However, this means that if the group
162        was called as a subroutine from elsewhere in the pattern, things went wrong
163        (an internal error was given). Such groups are now left in the compiled
164        pattern, with a new opcode that causes them to be skipped at execution
165        time.
167    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
168        to the way PCRE behaves:
170        (a) A lone ] character is dis-allowed (Perl treats it as data).
172        (b) A back reference to an unmatched subpattern matches an empty string
173            (Perl fails the current match path).
175        (c) A data ] in a character class must be notated as \] because if the
176            first data character in a class is ], it defines an empty class. (In
177            Perl it is not possible to have an empty class.) The empty class []
178            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
179            The negative empty class [^] matches any one character, independently
180            of the DOTALL setting.
182    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
183        non-existent subpattern following a character class starting with ']' and
184        containing () gave an internal compiling error instead of "reference to
185        non-existent subpattern". Fortunately, when the pattern did exist, the
186        compiled code was correct. (When scanning forwards to check for the
187        existencd of the subpattern, it was treating the data ']' as terminating
188        the class, so got the count wrong. When actually compiling, the reference
189        was subsequently set up correctly.)
191    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
192        it was being rejected as not supported by pcre_dfa_exec(), even though
193        other assertions are supported. I have made pcre_dfa_exec() support
194        (*FAIL).
196    16. The implementation of 13c above involved the invention of a new opcode,
197        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
198        cannot be changed at match time, I realized I could make a small
199        improvement to matching performance by compiling OP_ALLANY instead of
200        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
201        on the OP_ANY path.
203    17. Compiling pcretest on Windows with readline support failed without the
204        following two fixes: (1) Make the unistd.h include conditional on
205        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
207    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
208        ncurses library to be included for pcretest when ReadLine support is
209        requested, but also to allow for it to be overridden. This patch came from
210        Daniel Bergström.
212    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
213        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
214        any errors with the current Unicode tables. Thanks to Peter Kankowski for
215        spotting this.
218    Version 7.6 28-Jan-08
219    ---------------------
221    1.  A character class containing a very large number of characters with
222        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
223        overflow.
225    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
226        HAVE_LONG_LONG is not defined.
228    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
229        bring them up to date and include new features. This patch includes:
231        - Fixed PH's badly added libz and libbz2 support.
232        - Fixed a problem with static linking.
233        - Added pcredemo. [But later removed - see 7 below.]
234        - Fixed dftables problem and added an option.
235        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
236            HAVE_LONG_LONG.
237        - Added readline support for pcretest.
238        - Added an listing of the option settings after cmake has run.
240    4.  A user submitted a patch to Makefile that makes it easy to create
241        "pcre.dll" under mingw when using Configure/Make. I added stuff to
242        Makefile.am that cause it to include this special target, without
243        affecting anything else. Note that the same mingw target plus all
244        the other distribution libraries and programs are now supported
245        when configuring with CMake (see 6 below) instead of with
246        Configure/Make.
248    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
249        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
250        exported in the Windows port". It has not yet been confirmed that the patch
251        solves the problem, but it does no harm.
253    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
254        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
255        with CMake, and also correct the comment about stack recursion.
257    7.  Remove the automatic building of pcredemo from the ./configure system and
258        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
259        of a program that users should build themselves after PCRE is installed, so
260        building it automatically is not really right. What is more, it gave
261        trouble in some build environments.
263    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
266    Version 7.5 10-Jan-08
267  ---------------------  ---------------------
269  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
# Line 76  Version 7.5 12-Nov-07 Line 338  Version 7.5 12-Nov-07
338      does the same. The return code can be used to tell if there were any      does the same. The return code can be used to tell if there were any
339      non-matching lines.      non-matching lines.
341  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
343    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
344      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
345      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
346      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
348  15. Fixed two typos in the Windows-only code in pcregrep.c, and moved the  16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
349      inclusion of <windows.h> to before rather than after the definition of      inclusion of <windows.h> to before rather than after the definition of
350      INVALID_FILE_ATTRIBUTES (patch from David Byron).      INVALID_FILE_ATTRIBUTES (patch from David Byron).
352  16. Specifying a possessive quantifier with a specific limit for a Unicode  17. Specifying a possessive quantifier with a specific limit for a Unicode
353      character property caused pcre_compile() to compile bad code, which led at      character property caused pcre_compile() to compile bad code, which led at
354      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
355      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
356      caused the error; without that there was no problem.      caused the error; without that there was no problem.
358  17. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.  18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
360    19. Added --enable-pcretest-libreadline.
362    20. In pcrecpp.cc, the variable 'count' was incremented twice in
363        RE::GlobalReplace(). As a result, the number of replacements returned was
364        double what it should be. I removed one of the increments, but Craig sent a
365        later patch that removed the other one (the right fix) and added unit tests
366        that check the return values (which was not done before).
368    21. Several CMake things:
370        (1) Arranged that, when cmake is used on Unix, the libraries end up with
371            the names libpcre and libpcreposix, not just pcre and pcreposix.
373        (2) The above change means that pcretest and pcregrep are now correctly
374            linked with the newly-built libraries, not previously installed ones.
378    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
379        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
380        UTF-8 newline character). The key issue is that the pattern starts .*;
381        this means that the match must be either at the beginning, or after a
382        newline. The bug was in the code for advancing after a failed match and
383        checking that the new position followed a newline. It was not taking
384        account of UTF-8 characters correctly.
386    23. PCRE was behaving differently from Perl in the way it recognized POSIX
387        character classes. PCRE was not treating the sequence [:...:] as a
388        character class unless the ... were all letters. Perl, however, seems to
389        allow any characters between [: and :], though of course it rejects as
390        unknown any "names" that contain non-letters, because all the known class
391        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
392        for example, whereas PCRE did not - it did not recognize a POSIX character
393        class. This seemed a bit dangerous, so the code has been changed to be
394        closer to Perl. The behaviour is not identical to Perl, because PCRE will
395        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
396        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
397        Perl does, and where it didn't before.
399  18. Added --enable-pcretest-libreadline.  24. Rewrite so as to remove the single use of %n from pcregrep because in some
400        Windows environments %n is disabled by default.
403  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Removed from v.287  
changed lines
  Added in v.377

  ViewVC Help
Powered by ViewVC 1.1.5