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

Diff of /code/trunk/ChangeLog

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

revision 202 by ph10, Fri Aug 3 09:44:26 2007 UTC revision 236 by ph10, Tue Sep 11 12:57:06 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    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    8.  Changed all #include <config.h> to #include "config.h". There were also
39        some further <pcre.h> cases that I changed to "pcre.h".
40    
41    
42    Version 7.3 28-Aug-07
43  ---------------------  ---------------------
44    
45   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 65  Version 7.3 05-Jul-07 Line 103  Version 7.3 05-Jul-07
103      length has been removed - we now have only the limit on the total length of      length has been removed - we now have only the limit on the total length of
104      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
105    
106    10. Fixed a bug in the documentation for get/copy named substring when
107        duplicate names are permitted. If none of the named substrings are set, the
108        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
109        empty string.
110    
111    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
112        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
113        because the ] is interpreted as the first data character and the
114        terminating ] is not found. PCRE has been made compatible with Perl in this
115        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
116        cause memory overwriting.
117    
118    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
119        string has been matched (to stop an infinite loop). It was not recognizing
120        a conditional subpattern that could match an empty string if that
121        subpattern was within another subpattern. For example, it looped when
122        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
123        condition was not nested. This bug has been fixed.
124    
125    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
126        past the start of the subject in the presence of bytes with the top bit
127        set, for example "\x8aBCD".
128    
129    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
130        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
131    
132    14. Optimized (?!) to (*FAIL).
133    
134    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
135        This restricts code points to be within the range 0 to 0x10FFFF, excluding
136        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
137        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
138        does: it's just the validity check that is more restrictive.
139    
140    16. Inserted checks for integer overflows during escape sequence (backslash)
141        processing, and also fixed erroneous offset values for syntax errors during
142        backslash processing.
143    
144    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
145        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
146    
147    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
148        caused an overrun.
149    
150    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
151        something other than just ASCII characters) inside a group that had an
152        unlimited repeat caused a loop at compile time (while checking to see
153        whether the group could match an empty string).
154    
155    20. Debugging a pattern containing \p or \P could cause a crash. For example,
156        [\P{Any}] did so. (Error in the code for printing property names.)
157    
158    21. An orphan \E inside a character class could cause a crash.
159    
160    22. A repeated capturing bracket such as (A)? could cause a wild memory
161        reference during compilation.
162    
163    23. There are several functions in pcre_compile() that scan along a compiled
164        expression for various reasons (e.g. to see if it's fixed length for look
165        behind). There were bugs in these functions when a repeated \p or \P was
166        present in the pattern. These operators have additional parameters compared
167        with \d, etc, and these were not being taken into account when moving along
168        the compiled data. Specifically:
169    
170        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
171            length.
172    
173        (b) An item such as \pL+ within a repeated group could cause crashes or
174            loops.
175    
176        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
177            "reference to non-existent subpattern" error.
178    
179        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
180    
181    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
182        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
183    
184    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
185    
186    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
187        character were causing crashes (broken optimization).
188    
189    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
190        \p or \P) caused a compile-time loop.
191    
192    28. More problems have arisen in unanchored patterns when CRLF is a valid line
193        break. For example, the unstudied pattern [\r\n]A does not match the string
194        "\r\nA" because change 7.0/46 below moves the current point on by two
195        characters after failing to match at the start. However, the pattern \nA
196        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
197        the same is true. There doesn't seem any very clean way out of this, but
198        what I have chosen to do makes the common cases work: PCRE now takes note
199        of whether there can be an explicit match for \r or \n anywhere in the
200        pattern, and if so, 7.0/46 no longer applies. As part of this change,
201        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
202        pattern has explicit CR or LF references.
203    
204    29. Added (*CR) etc for changing newline setting at start of pattern.
205    
206    
207  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
208  ---------------------  ---------------------
Legend:
Removed from v.202  
changed lines
  Added in v.236
  ViewVC Help
Powered by ViewVC 1.1.5