/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.219  
changed lines
  Added in v.304

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12