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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.213  
changed lines
  Added in v.259

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12