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

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12