ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 210 by ph10, Wed Aug 8 14:24:50 2007 UTC revision 319 by ph10, Mon Jan 28 15:27:45 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-07  Version 7.6 28-Jan-08
5    ---------------------
7    1.  A character class containing a very large number of characters with
8        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
9        overflow.
11    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
12        HAVE_LONG_LONG is not defined.
14    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
15        bring them up to date and include new features. This patch includes:
17        - Fixed PH's badly added libz and libbz2 support.
18        - Fixed a problem with static linking.
19        - Added pcredemo. [But later removed - see 7 below.]
20        - Fixed dftables problem and added an option.
21        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
22            HAVE_LONG_LONG.
23        - Added readline support for pcretest.
24        - Added an listing of the option settings after cmake has run.
26    4.  A user submitted a patch to Makefile that makes it easy to create
27        "pcre.dll" under mingw when using Configure/Make. I added stuff to
28        Makefile.am that cause it to include this special target, without
29        affecting anything else. Note that the same mingw target plus all
30        the other distribution libraries and programs are now supported
31        when configuring with CMake (see 6 below) instead of with
32        Configure/Make.
34    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
35        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
36        exported in the Windows port". It has not yet been confirmed that the patch
37        solves the problem, but it does no harm.
39    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
40        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
41        with CMake, and also correct the comment about stack recursion.
43    7.  Remove the automatic building of pcredemo from the ./configure system and
44        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
45        of a program that users should build themselves after PCRE is installed, so
46        building it automatically is not really right. What is more, it gave
47        trouble in some build environments.
49    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
52    Version 7.5 10-Jan-08
53    ---------------------
55    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
56        values in parens when parsing an RE using the C++ wrapper."
58    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
59        Characters greater than 255 were excluded from the class instead of being
60        included.
62    3.  The same bug as (2) above applied to negated POSIX classes such as
63        [:^space:].
65    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
66        defined or documented. It seems to have been a typo for PCRE_STATIC, so
67        I have changed it.
69    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
70        first named subpattern) and a construct such as (?&a) would reference the
71        first named subpattern whose name started with "a" (in other words, the
72        length check was missing). Both these problems are fixed. "Subpattern name
73        expected" is now given for (?&) (a zero-length name), and this patch also
74        makes it give the same error for \k'' (previously it complained that that
75        was a reference to a non-existent subpattern).
77    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
78        this is right because (?- can be followed by option settings as well as by
79        digits. I have, however, made the messages clearer.
81    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
82        than the number used in the conditional) now cause a compile-time error.
83        This is actually not compatible with Perl, which accepts such patterns, but
84        treats the conditional as always being FALSE (as PCRE used to), but it
85        seems to me that giving a diagnostic is better.
87    8.  Change "alphameric" to the more common word "alphanumeric" in comments
88        and messages.
90    9.  Fix two occurrences of "backslash" in comments that should have been
91        "backspace".
93    10. Remove two redundant lines of code that can never be obeyed (their function
94        was moved elsewhere).
96    11. The program that makes PCRE's Unicode character property table had a bug
97        which caused it to generate incorrect table entries for sequences of
98        characters that have the same character type, but are in different scripts.
99        It amalgamated them into a single range, with the script of the first of
100        them. In other words, some characters were in the wrong script. There were
101        thirteen such cases, affecting characters in the following ranges:
103          U+002b0 - U+002c1
104          U+0060c - U+0060d
105          U+0061e - U+00612
106          U+0064b - U+0065e
107          U+0074d - U+0076d
108          U+01800 - U+01805
109          U+01d00 - U+01d77
110          U+01d9b - U+01dbf
111          U+0200b - U+0200f
112          U+030fc - U+030fe
113          U+03260 - U+0327f
114          U+0fb46 - U+0fbb1
115          U+10450 - U+1049d
117    12. The -o option (show only the matching part of a line) for pcregrep was not
118        compatible with GNU grep in that, if there was more than one match in a
119        line, it showed only the first of them. It now behaves in the same way as
120        GNU grep.
122    13. If the -o and -v options were combined for pcregrep, it printed a blank
123        line for every non-matching line. GNU grep prints nothing, and pcregrep now
124        does the same. The return code can be used to tell if there were any
125        non-matching lines.
127    14. Added --file-offsets and --line-offsets to pcregrep.
129    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
130        infinitely looping recursion. The bug was that positive lookaheads were not
131        being skipped when checking for a possible empty match (negative lookaheads
132        and both kinds of lookbehind were skipped).
134    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
135        inclusion of <windows.h> to before rather than after the definition of
136        INVALID_FILE_ATTRIBUTES (patch from David Byron).
138    17. Specifying a possessive quantifier with a specific limit for a Unicode
139        character property caused pcre_compile() to compile bad code, which led at
140        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
141        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
142        caused the error; without that there was no problem.
144    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
146    19. Added --enable-pcretest-libreadline.
148    20. In pcrecpp.cc, the variable 'count' was incremented twice in
149        RE::GlobalReplace(). As a result, the number of replacements returned was
150        double what it should be. I removed one of the increments, but Craig sent a
151        later patch that removed the other one (the right fix) and added unit tests
152        that check the return values (which was not done before).
154    21. Several CMake things:
156        (1) Arranged that, when cmake is used on Unix, the libraries end up with
157            the names libpcre and libpcreposix, not just pcre and pcreposix.
159        (2) The above change means that pcretest and pcregrep are now correctly
160            linked with the newly-built libraries, not previously installed ones.
164    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
165        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
166        UTF-8 newline character). The key issue is that the pattern starts .*;
167        this means that the match must be either at the beginning, or after a
168        newline. The bug was in the code for advancing after a failed match and
169        checking that the new position followed a newline. It was not taking
170        account of UTF-8 characters correctly.
172    23. PCRE was behaving differently from Perl in the way it recognized POSIX
173        character classes. PCRE was not treating the sequence [:...:] as a
174        character class unless the ... were all letters. Perl, however, seems to
175        allow any characters between [: and :], though of course it rejects as
176        unknown any "names" that contain non-letters, because all the known class
177        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
178        for example, whereas PCRE did not - it did not recognize a POSIX character
179        class. This seemed a bit dangerous, so the code has been changed to be
180        closer to Perl. The behaviour is not identical to Perl, because PCRE will
181        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
182        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
183        Perl does, and where it didn't before.
185    24. Rewrite so as to remove the single use of %n from pcregrep because in some
186        Windows environments %n is disabled by default.
189    Version 7.4 21-Sep-07
190    ---------------------
192    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
193        means that a class such as [\s] counted as "explicit reference to CR or
194        LF". That isn't really right - the whole point of the change was to try to
195        help when there was an actual mention of one of the two characters. So now
196        the change happens only if \r or \n (or a literal CR or LF) character is
197        encountered.
199    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
200        of both had grown to the point where there were only 3 bits left.
201        Fortunately, there was spare space in the data structure, and so I have
202        moved the internal flags into a new 16-bit field to free up more option
203        bits.
205    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
206        but did not set the internal JCHANGED flag - either of these is enough to
207        control the way the "get" function works - but the PCRE_INFO_JCHANGED
208        facility is supposed to tell if (?J) was ever used, so now (?J) at the
209        start sets both bits.
211    4.  Added options (at build time, compile time, exec time) to change \R from
212        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
214    5.  doc/pcresyntax.html was missing from the distribution.
216    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
217        compatibility, even though it is no longer used.
219    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
220        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
221        windows.h file is present (where different names are used). [This was
222        reversed later after testing - see 16 below.]
224    8.  Changed all #include <config.h> to #include "config.h". There were also
225        some further <pcre.h> cases that I changed to "pcre.h".
227    9.  When pcregrep was used with the --colour option, it missed the line ending
228        sequence off the lines that it output.
230    10. It was pointed out to me that arrays of string pointers cause lots of
231        relocations when a shared library is dynamically loaded. A technique of
232        using a single long string with a table of offsets can drastically reduce
233        these. I have refactored PCRE in four places to do this. The result is
234        dramatic:
236          Originally:                          290
237          After changing UCP table:            187
238          After changing error message table:   43
239          After changing table of "verbs"       36
240          After changing table of Posix names   22
242        Thanks to the folks working on Gregex for glib for this insight.
244    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
245        unicode-properties was also set.
247    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
249    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
250        checked only for CRLF.
252    14. Added casts to pcretest.c to avoid compiler warnings.
254    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
256    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
257        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
258        entirely. This removes changes made in 7 above.
260    17. The CMake files have been updated, and there is now more information about
261        building with CMake in the NON-UNIX-USE document.
264    Version 7.3 28-Aug-07
265  ---------------------  ---------------------
267   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 87  Version 7.3 05-Jul-07 Line 347  Version 7.3 05-Jul-07
347  12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack  12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
348      past the start of the subject in the presence of bytes with the top bit      past the start of the subject in the presence of bytes with the top bit
349      set, for example "\x8aBCD".      set, for example "\x8aBCD".
351  13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),  13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
352      (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).      (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
354  14. Optimized (?!) to (*FAIL).  14. Optimized (?!) to (*FAIL).
356    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
357        This restricts code points to be within the range 0 to 0x10FFFF, excluding
358        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
359        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
360        does: it's just the validity check that is more restrictive.
362    16. Inserted checks for integer overflows during escape sequence (backslash)
363        processing, and also fixed erroneous offset values for syntax errors during
364        backslash processing.
366    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
367        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
369    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
370        caused an overrun.
372    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
373        something other than just ASCII characters) inside a group that had an
374        unlimited repeat caused a loop at compile time (while checking to see
375        whether the group could match an empty string).
377    20. Debugging a pattern containing \p or \P could cause a crash. For example,
378        [\P{Any}] did so. (Error in the code for printing property names.)
380    21. An orphan \E inside a character class could cause a crash.
382    22. A repeated capturing bracket such as (A)? could cause a wild memory
383        reference during compilation.
385    23. There are several functions in pcre_compile() that scan along a compiled
386        expression for various reasons (e.g. to see if it's fixed length for look
387        behind). There were bugs in these functions when a repeated \p or \P was
388        present in the pattern. These operators have additional parameters compared
389        with \d, etc, and these were not being taken into account when moving along
390        the compiled data. Specifically:
392        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
393            length.
395        (b) An item such as \pL+ within a repeated group could cause crashes or
396            loops.
398        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
399            "reference to non-existent subpattern" error.
401        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
403    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
404        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
406    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
408    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
409        character were causing crashes (broken optimization).
411    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
412        \p or \P) caused a compile-time loop.
414    28. More problems have arisen in unanchored patterns when CRLF is a valid line
415        break. For example, the unstudied pattern [\r\n]A does not match the string
416        "\r\nA" because change 7.0/46 below moves the current point on by two
417        characters after failing to match at the start. However, the pattern \nA
418        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
419        the same is true. There doesn't seem any very clean way out of this, but
420        what I have chosen to do makes the common cases work: PCRE now takes note
421        of whether there can be an explicit match for \r or \n anywhere in the
422        pattern, and if so, 7.0/46 no longer applies. As part of this change,
423        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
424        pattern has explicit CR or LF references.
426    29. Added (*CR) etc for changing newline setting at start of pattern.
429  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Removed from v.210  
changed lines
  Added in v.319

  ViewVC Help
Powered by ViewVC 1.1.5