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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.214  
changed lines
  Added in v.307

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12