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

Diff of /code/trunk/ChangeLog

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

revision 206 by ph10, Fri Aug 3 14:53:04 2007 UTC revision 255 by ph10, Wed Sep 19 08:50:04 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 when the
36        windows.h file is present (where 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    9.  When pcregrep was used with the --colour option, it missed the line ending
42        sequence off the lines that it output.
43    
44    10. It was pointed out to me that arrays of string pointers cause lots of
45        relocations when a shared library is dynamically loaded. A technique of
46        using a single long string with a table of offsets can drastically reduce
47        these. I have refactored PCRE in four places to do this. The result is
48        dramatic:
49    
50          Originally:                          290
51          After changing UCP table:            187
52          After changing error message table:   43
53          After changing table of "verbs"       36
54          After changing table of Posix names   22
55    
56        Thanks to the folks working on Gregex for glib for this insight.
57    
58    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
59        unicode-properties was also set.
60    
61    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
62    
63    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
64        checked only for CRLF.
65    
66    14. Added casts to pcretest.c to avoid compiler warnings.
67    
68    
69    Version 7.3 28-Aug-07
70  ---------------------  ---------------------
71    
72   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 64  Version 7.3 05-Jul-07 Line 129  Version 7.3 05-Jul-07
129      dynamic way, which I have now done. The artificial limitation on group      dynamic way, which I have now done. The artificial limitation on group
130      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
131      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
132    
133  10. Fixed a bug in the documentation for get/copy named substring when  10. Fixed a bug in the documentation for get/copy named substring when
134      duplicate names are permitted. If none of the named substrings are set, the      duplicate names are permitted. If none of the named substrings are set, the
135      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
136      empty string.      empty string.
137    
138  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
139      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
140      because the ] is interpreted as the first data character and the      because the ] is interpreted as the first data character and the
141      terminating ] is not found. PCRE has been made compatible with Perl in this      terminating ] is not found. PCRE has been made compatible with Perl in this
142      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
143      cause memory overwriting.      cause memory overwriting.
144    
145  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
146      string has been matched (to stop an infinite loop). It was not recognizing      string has been matched (to stop an infinite loop). It was not recognizing
147      a conditional subpattern that could match an empty string if that      a conditional subpattern that could match an empty string if that
148      subpattern was within another subpattern. For example, it looped when      subpattern was within another subpattern. For example, it looped when
149      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
150      condition was not nested. This bug has been fixed.      condition was not nested. This bug has been fixed.
151    
152    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
153        past the start of the subject in the presence of bytes with the top bit
154        set, for example "\x8aBCD".
155    
156    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
157        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
158    
159    14. Optimized (?!) to (*FAIL).
160    
161    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
162        This restricts code points to be within the range 0 to 0x10FFFF, excluding
163        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
164        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
165        does: it's just the validity check that is more restrictive.
166    
167    16. Inserted checks for integer overflows during escape sequence (backslash)
168        processing, and also fixed erroneous offset values for syntax errors during
169        backslash processing.
170    
171    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
172        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
173    
174    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
175        caused an overrun.
176    
177    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
178        something other than just ASCII characters) inside a group that had an
179        unlimited repeat caused a loop at compile time (while checking to see
180        whether the group could match an empty string).
181    
182    20. Debugging a pattern containing \p or \P could cause a crash. For example,
183        [\P{Any}] did so. (Error in the code for printing property names.)
184    
185    21. An orphan \E inside a character class could cause a crash.
186    
187    22. A repeated capturing bracket such as (A)? could cause a wild memory
188        reference during compilation.
189    
190    23. There are several functions in pcre_compile() that scan along a compiled
191        expression for various reasons (e.g. to see if it's fixed length for look
192        behind). There were bugs in these functions when a repeated \p or \P was
193        present in the pattern. These operators have additional parameters compared
194        with \d, etc, and these were not being taken into account when moving along
195        the compiled data. Specifically:
196    
197        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
198            length.
199    
200        (b) An item such as \pL+ within a repeated group could cause crashes or
201            loops.
202    
203        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
204            "reference to non-existent subpattern" error.
205    
206        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
207    
208    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
209        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
210    
211    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
212    
213    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
214        character were causing crashes (broken optimization).
215    
216    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
217        \p or \P) caused a compile-time loop.
218    
219    28. More problems have arisen in unanchored patterns when CRLF is a valid line
220        break. For example, the unstudied pattern [\r\n]A does not match the string
221        "\r\nA" because change 7.0/46 below moves the current point on by two
222        characters after failing to match at the start. However, the pattern \nA
223        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
224        the same is true. There doesn't seem any very clean way out of this, but
225        what I have chosen to do makes the common cases work: PCRE now takes note
226        of whether there can be an explicit match for \r or \n anywhere in the
227        pattern, and if so, 7.0/46 no longer applies. As part of this change,
228        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
229        pattern has explicit CR or LF references.
230    
231    29. Added (*CR) etc for changing newline setting at start of pattern.
232    
233    
234  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
235  ---------------------  ---------------------

Legend:
Removed from v.206  
changed lines
  Added in v.255

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12