ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 288 by ph10, Wed Dec 19 12:21:45 2007 UTC revision 361 by ph10, Thu Jul 10 16:03:28 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.5 12-Nov-07  Version 8.0 02 Jul-08
5    ---------------------
7    1.  Replaced UCP searching code with optimized version as implemented for Ad
8        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
9        stage table and inline lookup instead of a function, giving speed ups of 2
10        to 5 times on some simple patterns that I tested. Permission was given to
11        distribute the MultiStage2.py script that generates the tables (it's not in
12        the tarball, but is in the Subversion repository).
14    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
15        scripts.
17    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
18        a group with a zero qualifier. The result of the study could be incorrect,
19        or the function might crash, depending on the pattern.
21    4.  Caseless matching was not working for non-ASCII characters in back
22        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
23        It now works when Unicode Property Support is available.
25    5.  In pcretest, an escape such as \x{de} in the data was always generating
26        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
27        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
28        truncation.
30    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
32    7.  Added two (int) casts to pcregrep when printing the difference of two
33        pointers, in case they are 64-bit values.
35    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
36        test 2 if it fails.
38    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
39        and a #define of that name to empty if it is not externally set. This is to
40        allow users of MSVC to set it if necessary.
42    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
43        the convenience functions in the pcre_get.c source file.
45    11. An option change at the start of a pattern that had top-level alternatives
46        could cause overwriting and/or a crash. This command provoked a crash in
47        some environments:
49          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
51        This potential security problem was recorded as CVE-2008-2371.
53    12. For a pattern where the match had to start at the beginning or immediately
54        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
55        pcre_dfa_exec() could read past the end of the passed subject if there was
56        no match. To help with detecting such bugs (e.g. with valgrind), I modified
57        pcretest so that it places the subject at the end of its malloc-ed buffer.
60    Version 7.7 07-May-08
61    ---------------------
63    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
64        a string to a long long, pretend we don't even have a long long." This is
65        done by checking for the strtoq, strtoll, and _strtoi64 functions.
67    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
68        pre-7.6 versions, which defined a global no_arg variable instead of putting
69        it in the RE class. (See also #8 below.)
71    3.  Remove a line of dead code, identified by coverity and reported by Nuno
72        Lopes.
74    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
76        (1) The include/exclude patterns were being applied to the whole pathnames
77            of files, instead of just to the final components.
79        (2) If there was more than one level of directory, the subdirectories were
80            skipped unless they satisfied the include/exclude conditions. This is
81            inconsistent with GNU grep (and could even be seen as contrary to the
82            pcregrep specification - which I improved to make it absolutely clear).
83            The action now is always to scan all levels of directory, and just
84            apply the include/exclude patterns to regular files.
86    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
87        --exclude_dir in the tests to avoid scanning .svn directories.
89    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
90        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
91        doesn't support NULs in patterns.
93    7.  Added some missing "const"s to declarations of static tables in
94        pcre_compile.c and pcre_dfa_exec.c.
96    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
97        caused by fix #2  above. (Subsequently also a second patch to fix the
98        first patch. And a third patch - this was a messy problem.)
100    9.  Applied Craig's patch to remove the use of push_back().
102    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
103        matching function regexec().
105    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
106        which, however, unlike Perl's \g{...}, are subroutine calls, not back
107        references. PCRE supports relative numbers with this syntax (I don't think
108        Oniguruma does).
110    12. Previously, a group with a zero repeat such as (...){0} was completely
111        omitted from the compiled regex. However, this means that if the group
112        was called as a subroutine from elsewhere in the pattern, things went wrong
113        (an internal error was given). Such groups are now left in the compiled
114        pattern, with a new opcode that causes them to be skipped at execution
115        time.
117    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
118        to the way PCRE behaves:
120        (a) A lone ] character is dis-allowed (Perl treats it as data).
122        (b) A back reference to an unmatched subpattern matches an empty string
123            (Perl fails the current match path).
125        (c) A data ] in a character class must be notated as \] because if the
126            first data character in a class is ], it defines an empty class. (In
127            Perl it is not possible to have an empty class.) The empty class []
128            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
129            The negative empty class [^] matches any one character, independently
130            of the DOTALL setting.
132    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
133        non-existent subpattern following a character class starting with ']' and
134        containing () gave an internal compiling error instead of "reference to
135        non-existent subpattern". Fortunately, when the pattern did exist, the
136        compiled code was correct. (When scanning forwards to check for the
137        existencd of the subpattern, it was treating the data ']' as terminating
138        the class, so got the count wrong. When actually compiling, the reference
139        was subsequently set up correctly.)
141    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
142        it was being rejected as not supported by pcre_dfa_exec(), even though
143        other assertions are supported. I have made pcre_dfa_exec() support
144        (*FAIL).
146    16. The implementation of 13c above involved the invention of a new opcode,
147        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
148        cannot be changed at match time, I realized I could make a small
149        improvement to matching performance by compiling OP_ALLANY instead of
150        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
151        on the OP_ANY path.
153    17. Compiling pcretest on Windows with readline support failed without the
154        following two fixes: (1) Make the unistd.h include conditional on
155        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
157    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
158        ncurses library to be included for pcretest when ReadLine support is
159        requested, but also to allow for it to be overridden. This patch came from
160        Daniel Bergström.
162    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
163        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
164        any errors with the current Unicode tables. Thanks to Peter Kankowski for
165        spotting this.
168    Version 7.6 28-Jan-08
169    ---------------------
171    1.  A character class containing a very large number of characters with
172        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
173        overflow.
175    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
176        HAVE_LONG_LONG is not defined.
178    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
179        bring them up to date and include new features. This patch includes:
181        - Fixed PH's badly added libz and libbz2 support.
182        - Fixed a problem with static linking.
183        - Added pcredemo. [But later removed - see 7 below.]
184        - Fixed dftables problem and added an option.
185        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
186            HAVE_LONG_LONG.
187        - Added readline support for pcretest.
188        - Added an listing of the option settings after cmake has run.
190    4.  A user submitted a patch to Makefile that makes it easy to create
191        "pcre.dll" under mingw when using Configure/Make. I added stuff to
192        Makefile.am that cause it to include this special target, without
193        affecting anything else. Note that the same mingw target plus all
194        the other distribution libraries and programs are now supported
195        when configuring with CMake (see 6 below) instead of with
196        Configure/Make.
198    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
199        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
200        exported in the Windows port". It has not yet been confirmed that the patch
201        solves the problem, but it does no harm.
203    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
204        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
205        with CMake, and also correct the comment about stack recursion.
207    7.  Remove the automatic building of pcredemo from the ./configure system and
208        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
209        of a program that users should build themselves after PCRE is installed, so
210        building it automatically is not really right. What is more, it gave
211        trouble in some build environments.
213    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
216    Version 7.5 10-Jan-08
217  ---------------------  ---------------------
219  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 288  Version 7.5 12-Nov-07
288      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
289      non-matching lines.      non-matching lines.
291  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
293    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
294      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
295      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
296      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
298  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
299      inclusion of <windows.h> to before rather than after the definition of      inclusion of <windows.h> to before rather than after the definition of
300      INVALID_FILE_ATTRIBUTES (patch from David Byron).      INVALID_FILE_ATTRIBUTES (patch from David Byron).
302  16. Specifying a possessive quantifier with a specific limit for a Unicode  17. Specifying a possessive quantifier with a specific limit for a Unicode
303      character property caused pcre_compile() to compile bad code, which led at      character property caused pcre_compile() to compile bad code, which led at
304      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
305      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
306      caused the error; without that there was no problem.      caused the error; without that there was no problem.
308  17. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.  18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
310  18. Added --enable-pcretest-libreadline.  19. Added --enable-pcretest-libreadline.
312  19. In pcrecpp.cc, the variable 'count' was incremented twice in  20. In pcrecpp.cc, the variable 'count' was incremented twice in
313      RE::GlobalReplace(). As a result, the number of replacements returned was      RE::GlobalReplace(). As a result, the number of replacements returned was
314      double what it should be. I have removed one of the increments.      double what it should be. I removed one of the increments, but Craig sent a
315        later patch that removed the other one (the right fix) and added unit tests
316        that check the return values (which was not done before).
318    21. Several CMake things:
320        (1) Arranged that, when cmake is used on Unix, the libraries end up with
321            the names libpcre and libpcreposix, not just pcre and pcreposix.
323        (2) The above change means that pcretest and pcregrep are now correctly
324            linked with the newly-built libraries, not previously installed ones.
328    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
329        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
330        UTF-8 newline character). The key issue is that the pattern starts .*;
331        this means that the match must be either at the beginning, or after a
332        newline. The bug was in the code for advancing after a failed match and
333        checking that the new position followed a newline. It was not taking
334        account of UTF-8 characters correctly.
336    23. PCRE was behaving differently from Perl in the way it recognized POSIX
337        character classes. PCRE was not treating the sequence [:...:] as a
338        character class unless the ... were all letters. Perl, however, seems to
339        allow any characters between [: and :], though of course it rejects as
340        unknown any "names" that contain non-letters, because all the known class
341        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
342        for example, whereas PCRE did not - it did not recognize a POSIX character
343        class. This seemed a bit dangerous, so the code has been changed to be
344        closer to Perl. The behaviour is not identical to Perl, because PCRE will
345        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
346        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
347        Perl does, and where it didn't before.
349    24. Rewrite so as to remove the single use of %n from pcregrep because in some
350        Windows environments %n is disabled by default.
353  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Removed from v.288  
changed lines
  Added in v.361

  ViewVC Help
Powered by ViewVC 1.1.5