/[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 234 by ph10, Tue Sep 11 11:36:27 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 (where
36        different names are used).
37    
38    
39    Version 7.3 28-Aug-07
40  ---------------------  ---------------------
41    
42   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 133  Version 7.3 09-Aug-07
133      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
134      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
135      does: it's just the validity check that is more restrictive.      does: it's just the validity check that is more restrictive.
136    
137  16. Inserted checks for integer overflows during escape sequence (backslash)  16. Inserted checks for integer overflows during escape sequence (backslash)
138      processing, and also fixed erroneous offset values for syntax errors during      processing, and also fixed erroneous offset values for syntax errors during
139      backslash processing.      backslash processing.
140    
141    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
142        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
143    
144    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
145        caused an overrun.
146    
147    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
148        something other than just ASCII characters) inside a group that had an
149        unlimited repeat caused a loop at compile time (while checking to see
150        whether the group could match an empty string).
151    
152    20. Debugging a pattern containing \p or \P could cause a crash. For example,
153        [\P{Any}] did so. (Error in the code for printing property names.)
154    
155    21. An orphan \E inside a character class could cause a crash.
156    
157    22. A repeated capturing bracket such as (A)? could cause a wild memory
158        reference during compilation.
159    
160    23. There are several functions in pcre_compile() that scan along a compiled
161        expression for various reasons (e.g. to see if it's fixed length for look
162        behind). There were bugs in these functions when a repeated \p or \P was
163        present in the pattern. These operators have additional parameters compared
164        with \d, etc, and these were not being taken into account when moving along
165        the compiled data. Specifically:
166    
167        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
168            length.
169    
170        (b) An item such as \pL+ within a repeated group could cause crashes or
171            loops.
172    
173        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
174            "reference to non-existent subpattern" error.
175    
176        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
177    
178    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
179        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
180    
181    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
182    
183    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
184        character were causing crashes (broken optimization).
185    
186    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
187        \p or \P) caused a compile-time loop.
188    
189    28. More problems have arisen in unanchored patterns when CRLF is a valid line
190        break. For example, the unstudied pattern [\r\n]A does not match the string
191        "\r\nA" because change 7.0/46 below moves the current point on by two
192        characters after failing to match at the start. However, the pattern \nA
193        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
194        the same is true. There doesn't seem any very clean way out of this, but
195        what I have chosen to do makes the common cases work: PCRE now takes note
196        of whether there can be an explicit match for \r or \n anywhere in the
197        pattern, and if so, 7.0/46 no longer applies. As part of this change,
198        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
199        pattern has explicit CR or LF references.
200    
201    29. Added (*CR) etc for changing newline setting at start of pattern.
202    
203    
204  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12