/[pcre]/code/trunk/ChangeLog
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 274 by ph10, Tue Nov 20 10:05:23 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-07  Version 7.5 12-Nov-07
5    ---------------------
6    
7    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
8        values in parens when parsing an RE using the C++ wrapper."
9    
10    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
11        Characters greater than 255 were excluded from the class instead of being
12        included.
13    
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
16    
17    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
18        defined or documented. It seems to have been a typo for PCRE_STATIC, so
19        I have changed it.
20    
21    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
22        first named subpattern) and a construct such as (?&a) would reference the
23        first named subpattern whose name started with "a" (in other words, the
24        length check was missing). Both these problems are fixed. "Subpattern name
25        expected" is now given for (?&) (a zero-length name), and this patch also
26        makes it give the same error for \k'' (previously it complained that that
27        was a reference to a non-existent subpattern).
28    
29    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
30        this is right because (?- can be followed by option settings as well as by
31        digits. I have, however, made the messages clearer.
32    
33    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
34        than the number used in the conditional) now cause a compile-time error.
35        This is actually not compatible with Perl, which accepts such patterns, but
36        treats the conditional as always being FALSE (as PCRE used to), but it
37        seems to me that giving a diagnostic is better.
38    
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
41    
42    
43    Version 7.4 21-Sep-07
44    ---------------------
45    
46    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
47        means that a class such as [\s] counted as "explicit reference to CR or
48        LF". That isn't really right - the whole point of the change was to try to
49        help when there was an actual mention of one of the two characters. So now
50        the change happens only if \r or \n (or a literal CR or LF) character is
51        encountered.
52    
53    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
54        of both had grown to the point where there were only 3 bits left.
55        Fortunately, there was spare space in the data structure, and so I have
56        moved the internal flags into a new 16-bit field to free up more option
57        bits.
58    
59    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
60        but did not set the internal JCHANGED flag - either of these is enough to
61        control the way the "get" function works - but the PCRE_INFO_JCHANGED
62        facility is supposed to tell if (?J) was ever used, so now (?J) at the
63        start sets both bits.
64    
65    4.  Added options (at build time, compile time, exec time) to change \R from
66        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
67    
68    5.  doc/pcresyntax.html was missing from the distribution.
69    
70    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
71        compatibility, even though it is no longer used.
72    
73    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
74        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
75        windows.h file is present (where different names are used). [This was
76        reversed later after testing - see 16 below.]
77    
78    8.  Changed all #include <config.h> to #include "config.h". There were also
79        some further <pcre.h> cases that I changed to "pcre.h".
80    
81    9.  When pcregrep was used with the --colour option, it missed the line ending
82        sequence off the lines that it output.
83    
84    10. It was pointed out to me that arrays of string pointers cause lots of
85        relocations when a shared library is dynamically loaded. A technique of
86        using a single long string with a table of offsets can drastically reduce
87        these. I have refactored PCRE in four places to do this. The result is
88        dramatic:
89    
90          Originally:                          290
91          After changing UCP table:            187
92          After changing error message table:   43
93          After changing table of "verbs"       36
94          After changing table of Posix names   22
95    
96        Thanks to the folks working on Gregex for glib for this insight.
97    
98    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
99        unicode-properties was also set.
100    
101    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
102    
103    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
104        checked only for CRLF.
105    
106    14. Added casts to pcretest.c to avoid compiler warnings.
107    
108    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
109    
110    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
111        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
112        entirely. This removes changes made in 7 above.
113    
114    17. The CMake files have been updated, and there is now more information about
115        building with CMake in the NON-UNIX-USE document.
116    
117    
118    Version 7.3 28-Aug-07
119  ---------------------  ---------------------
120    
121   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 201  Version 7.3 05-Jul-07
201  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
202      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
203      set, for example "\x8aBCD".      set, for example "\x8aBCD".
204    
205  13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),  13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
206      (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).      (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
207    
208  14. Optimized (?!) to (*FAIL).  14. Optimized (?!) to (*FAIL).
209    
210    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
211        This restricts code points to be within the range 0 to 0x10FFFF, excluding
212        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
213        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
214        does: it's just the validity check that is more restrictive.
215    
216    16. Inserted checks for integer overflows during escape sequence (backslash)
217        processing, and also fixed erroneous offset values for syntax errors during
218        backslash processing.
219    
220    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
221        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
222    
223    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
224        caused an overrun.
225    
226    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
227        something other than just ASCII characters) inside a group that had an
228        unlimited repeat caused a loop at compile time (while checking to see
229        whether the group could match an empty string).
230    
231    20. Debugging a pattern containing \p or \P could cause a crash. For example,
232        [\P{Any}] did so. (Error in the code for printing property names.)
233    
234    21. An orphan \E inside a character class could cause a crash.
235    
236    22. A repeated capturing bracket such as (A)? could cause a wild memory
237        reference during compilation.
238    
239    23. There are several functions in pcre_compile() that scan along a compiled
240        expression for various reasons (e.g. to see if it's fixed length for look
241        behind). There were bugs in these functions when a repeated \p or \P was
242        present in the pattern. These operators have additional parameters compared
243        with \d, etc, and these were not being taken into account when moving along
244        the compiled data. Specifically:
245    
246        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
247            length.
248    
249        (b) An item such as \pL+ within a repeated group could cause crashes or
250            loops.
251    
252        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
253            "reference to non-existent subpattern" error.
254    
255        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
256    
257    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
258        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
259    
260    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
261    
262    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
263        character were causing crashes (broken optimization).
264    
265    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
266        \p or \P) caused a compile-time loop.
267    
268    28. More problems have arisen in unanchored patterns when CRLF is a valid line
269        break. For example, the unstudied pattern [\r\n]A does not match the string
270        "\r\nA" because change 7.0/46 below moves the current point on by two
271        characters after failing to match at the start. However, the pattern \nA
272        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
273        the same is true. There doesn't seem any very clean way out of this, but
274        what I have chosen to do makes the common cases work: PCRE now takes note
275        of whether there can be an explicit match for \r or \n anywhere in the
276        pattern, and if so, 7.0/46 no longer applies. As part of this change,
277        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
278        pattern has explicit CR or LF references.
279    
280    29. Added (*CR) etc for changing newline setting at start of pattern.
281    
282    
283  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Legend:
Removed from v.210  
changed lines
  Added in v.274

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12