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

Diff of /code/trunk/ChangeLog

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

revision 215 by ph10, Wed Aug 15 14:20:05 2007 UTC revision 264 by ph10, Tue Nov 13 11:07:16 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 09-Aug-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    
15    Version 7.4 21-Sep-07
16    ---------------------
17    
18    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
19        means that a class such as [\s] counted as "explicit reference to CR or
20        LF". That isn't really right - the whole point of the change was to try to
21        help when there was an actual mention of one of the two characters. So now
22        the change happens only if \r or \n (or a literal CR or LF) character is
23        encountered.
24    
25    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
26        of both had grown to the point where there were only 3 bits left.
27        Fortunately, there was spare space in the data structure, and so I have
28        moved the internal flags into a new 16-bit field to free up more option
29        bits.
30    
31    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
32        but did not set the internal JCHANGED flag - either of these is enough to
33        control the way the "get" function works - but the PCRE_INFO_JCHANGED
34        facility is supposed to tell if (?J) was ever used, so now (?J) at the
35        start sets both bits.
36    
37    4.  Added options (at build time, compile time, exec time) to change \R from
38        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
39    
40    5.  doc/pcresyntax.html was missing from the distribution.
41    
42    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
43        compatibility, even though it is no longer used.
44    
45    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
46        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
47        windows.h file is present (where different names are used). [This was
48        reversed later after testing - see 16 below.]
49    
50    8.  Changed all #include <config.h> to #include "config.h". There were also
51        some further <pcre.h> cases that I changed to "pcre.h".
52    
53    9.  When pcregrep was used with the --colour option, it missed the line ending
54        sequence off the lines that it output.
55    
56    10. It was pointed out to me that arrays of string pointers cause lots of
57        relocations when a shared library is dynamically loaded. A technique of
58        using a single long string with a table of offsets can drastically reduce
59        these. I have refactored PCRE in four places to do this. The result is
60        dramatic:
61    
62          Originally:                          290
63          After changing UCP table:            187
64          After changing error message table:   43
65          After changing table of "verbs"       36
66          After changing table of Posix names   22
67    
68        Thanks to the folks working on Gregex for glib for this insight.
69    
70    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
71        unicode-properties was also set.
72    
73    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
74    
75    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
76        checked only for CRLF.
77    
78    14. Added casts to pcretest.c to avoid compiler warnings.
79    
80    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
81    
82    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
83        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
84        entirely. This removes changes made in 7 above.
85    
86    17. The CMake files have been updated, and there is now more information about
87        building with CMake in the NON-UNIX-USE document.
88    
89    
90    Version 7.3 28-Aug-07
91  ---------------------  ---------------------
92    
93   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 184  Version 7.3 09-Aug-07
184      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
185      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
186      does: it's just the validity check that is more restrictive.      does: it's just the validity check that is more restrictive.
187    
188  16. Inserted checks for integer overflows during escape sequence (backslash)  16. Inserted checks for integer overflows during escape sequence (backslash)
189      processing, and also fixed erroneous offset values for syntax errors during      processing, and also fixed erroneous offset values for syntax errors during
190      backslash processing.      backslash processing.
191    
192  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)
193      for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".      for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
194    
195  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"
196      caused an overrun.      caused an overrun.
197    
198    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
199        something other than just ASCII characters) inside a group that had an
200        unlimited repeat caused a loop at compile time (while checking to see
201        whether the group could match an empty string).
202    
203    20. Debugging a pattern containing \p or \P could cause a crash. For example,
204        [\P{Any}] did so. (Error in the code for printing property names.)
205    
206    21. An orphan \E inside a character class could cause a crash.
207    
208    22. A repeated capturing bracket such as (A)? could cause a wild memory
209        reference during compilation.
210    
211    23. There are several functions in pcre_compile() that scan along a compiled
212        expression for various reasons (e.g. to see if it's fixed length for look
213        behind). There were bugs in these functions when a repeated \p or \P was
214        present in the pattern. These operators have additional parameters compared
215        with \d, etc, and these were not being taken into account when moving along
216        the compiled data. Specifically:
217    
218        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
219            length.
220    
221        (b) An item such as \pL+ within a repeated group could cause crashes or
222            loops.
223    
224        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
225            "reference to non-existent subpattern" error.
226    
227        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
228    
229    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
230        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
231    
232    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
233    
234    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
235        character were causing crashes (broken optimization).
236    
237    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
238        \p or \P) caused a compile-time loop.
239    
240    28. More problems have arisen in unanchored patterns when CRLF is a valid line
241        break. For example, the unstudied pattern [\r\n]A does not match the string
242        "\r\nA" because change 7.0/46 below moves the current point on by two
243        characters after failing to match at the start. However, the pattern \nA
244        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
245        the same is true. There doesn't seem any very clean way out of this, but
246        what I have chosen to do makes the common cases work: PCRE now takes note
247        of whether there can be an explicit match for \r or \n anywhere in the
248        pattern, and if so, 7.0/46 no longer applies. As part of this change,
249        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
250        pattern has explicit CR or LF references.
251    
252    29. Added (*CR) etc for changing newline setting at start of pattern.
253    
254    
255  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
256  ---------------------  ---------------------

Legend:
Removed from v.215  
changed lines
  Added in v.264

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12