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

Diff of /code/trunk/ChangeLog

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

revision 208 by ph10, Mon Aug 6 15:23:29 2007 UTC revision 230 by ph10, Mon Sep 10 13:23:56 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-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    
27    Version 7.3 28-Aug-07
28  ---------------------  ---------------------
29    
30   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 88  Version 7.3 05-Jul-07 Line 111  Version 7.3 05-Jul-07
111      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
112      set, for example "\x8aBCD".      set, for example "\x8aBCD".
113    
114    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
115        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
116    
117    14. Optimized (?!) to (*FAIL).
118    
119    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
120        This restricts code points to be within the range 0 to 0x10FFFF, excluding
121        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
122        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
123        does: it's just the validity check that is more restrictive.
124    
125    16. Inserted checks for integer overflows during escape sequence (backslash)
126        processing, and also fixed erroneous offset values for syntax errors during
127        backslash processing.
128    
129    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
130        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
131    
132    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
133        caused an overrun.
134    
135    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
136        something other than just ASCII characters) inside a group that had an
137        unlimited repeat caused a loop at compile time (while checking to see
138        whether the group could match an empty string).
139    
140    20. Debugging a pattern containing \p or \P could cause a crash. For example,
141        [\P{Any}] did so. (Error in the code for printing property names.)
142    
143    21. An orphan \E inside a character class could cause a crash.
144    
145    22. A repeated capturing bracket such as (A)? could cause a wild memory
146        reference during compilation.
147    
148    23. There are several functions in pcre_compile() that scan along a compiled
149        expression for various reasons (e.g. to see if it's fixed length for look
150        behind). There were bugs in these functions when a repeated \p or \P was
151        present in the pattern. These operators have additional parameters compared
152        with \d, etc, and these were not being taken into account when moving along
153        the compiled data. Specifically:
154    
155        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
156            length.
157    
158        (b) An item such as \pL+ within a repeated group could cause crashes or
159            loops.
160    
161        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
162            "reference to non-existent subpattern" error.
163    
164        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
165    
166    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
167        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
168    
169    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
170    
171    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
172        character were causing crashes (broken optimization).
173    
174    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
175        \p or \P) caused a compile-time loop.
176    
177    28. More problems have arisen in unanchored patterns when CRLF is a valid line
178        break. For example, the unstudied pattern [\r\n]A does not match the string
179        "\r\nA" because change 7.0/46 below moves the current point on by two
180        characters after failing to match at the start. However, the pattern \nA
181        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
182        the same is true. There doesn't seem any very clean way out of this, but
183        what I have chosen to do makes the common cases work: PCRE now takes note
184        of whether there can be an explicit match for \r or \n anywhere in the
185        pattern, and if so, 7.0/46 no longer applies. As part of this change,
186        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
187        pattern has explicit CR or LF references.
188    
189    29. Added (*CR) etc for changing newline setting at start of pattern.
190    
191    
192  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
193  ---------------------  ---------------------

Legend:
Removed from v.208  
changed lines
  Added in v.230

  ViewVC Help
Powered by ViewVC 1.1.5