/[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 275 by ph10, Wed Nov 21 15:35:09 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-07  Version 7.5 12-Nov-07
5    ---------------------
6    
7    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
8        values in parens when parsing an RE using the C++ wrapper."
9    
10    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
11        Characters greater than 255 were excluded from the class instead of being
12        included.
13    
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
16    
17    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
18        defined or documented. It seems to have been a typo for PCRE_STATIC, so
19        I have changed it.
20    
21    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
22        first named subpattern) and a construct such as (?&a) would reference the
23        first named subpattern whose name started with "a" (in other words, the
24        length check was missing). Both these problems are fixed. "Subpattern name
25        expected" is now given for (?&) (a zero-length name), and this patch also
26        makes it give the same error for \k'' (previously it complained that that
27        was a reference to a non-existent subpattern).
28    
29    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
30        this is right because (?- can be followed by option settings as well as by
31        digits. I have, however, made the messages clearer.
32    
33    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
34        than the number used in the conditional) now cause a compile-time error.
35        This is actually not compatible with Perl, which accepts such patterns, but
36        treats the conditional as always being FALSE (as PCRE used to), but it
37        seems to me that giving a diagnostic is better.
38    
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
41    
42    9.  Fix two occurrences of "backslash" in comments that should have been
43        "backspace".
44    
45    
46    Version 7.4 21-Sep-07
47    ---------------------
48    
49    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
50        means that a class such as [\s] counted as "explicit reference to CR or
51        LF". That isn't really right - the whole point of the change was to try to
52        help when there was an actual mention of one of the two characters. So now
53        the change happens only if \r or \n (or a literal CR or LF) character is
54        encountered.
55    
56    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
57        of both had grown to the point where there were only 3 bits left.
58        Fortunately, there was spare space in the data structure, and so I have
59        moved the internal flags into a new 16-bit field to free up more option
60        bits.
61    
62    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
63        but did not set the internal JCHANGED flag - either of these is enough to
64        control the way the "get" function works - but the PCRE_INFO_JCHANGED
65        facility is supposed to tell if (?J) was ever used, so now (?J) at the
66        start sets both bits.
67    
68    4.  Added options (at build time, compile time, exec time) to change \R from
69        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
70    
71    5.  doc/pcresyntax.html was missing from the distribution.
72    
73    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
74        compatibility, even though it is no longer used.
75    
76    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
77        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
78        windows.h file is present (where different names are used). [This was
79        reversed later after testing - see 16 below.]
80    
81    8.  Changed all #include <config.h> to #include "config.h". There were also
82        some further <pcre.h> cases that I changed to "pcre.h".
83    
84    9.  When pcregrep was used with the --colour option, it missed the line ending
85        sequence off the lines that it output.
86    
87    10. It was pointed out to me that arrays of string pointers cause lots of
88        relocations when a shared library is dynamically loaded. A technique of
89        using a single long string with a table of offsets can drastically reduce
90        these. I have refactored PCRE in four places to do this. The result is
91        dramatic:
92    
93          Originally:                          290
94          After changing UCP table:            187
95          After changing error message table:   43
96          After changing table of "verbs"       36
97          After changing table of Posix names   22
98    
99        Thanks to the folks working on Gregex for glib for this insight.
100    
101    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
102        unicode-properties was also set.
103    
104    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
105    
106    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
107        checked only for CRLF.
108    
109    14. Added casts to pcretest.c to avoid compiler warnings.
110    
111    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
112    
113    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
114        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
115        entirely. This removes changes made in 7 above.
116    
117    17. The CMake files have been updated, and there is now more information about
118        building with CMake in the NON-UNIX-USE document.
119    
120    
121    Version 7.3 28-Aug-07
122  ---------------------  ---------------------
123    
124   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 205  Version 7.3 05-Jul-07
205      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
206      set, for example "\x8aBCD".      set, for example "\x8aBCD".
207    
208    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
209        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
210    
211    14. Optimized (?!) to (*FAIL).
212    
213    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
214        This restricts code points to be within the range 0 to 0x10FFFF, excluding
215        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
216        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
217        does: it's just the validity check that is more restrictive.
218    
219    16. Inserted checks for integer overflows during escape sequence (backslash)
220        processing, and also fixed erroneous offset values for syntax errors during
221        backslash processing.
222    
223    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
224        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
225    
226    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
227        caused an overrun.
228    
229    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
230        something other than just ASCII characters) inside a group that had an
231        unlimited repeat caused a loop at compile time (while checking to see
232        whether the group could match an empty string).
233    
234    20. Debugging a pattern containing \p or \P could cause a crash. For example,
235        [\P{Any}] did so. (Error in the code for printing property names.)
236    
237    21. An orphan \E inside a character class could cause a crash.
238    
239    22. A repeated capturing bracket such as (A)? could cause a wild memory
240        reference during compilation.
241    
242    23. There are several functions in pcre_compile() that scan along a compiled
243        expression for various reasons (e.g. to see if it's fixed length for look
244        behind). There were bugs in these functions when a repeated \p or \P was
245        present in the pattern. These operators have additional parameters compared
246        with \d, etc, and these were not being taken into account when moving along
247        the compiled data. Specifically:
248    
249        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
250            length.
251    
252        (b) An item such as \pL+ within a repeated group could cause crashes or
253            loops.
254    
255        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
256            "reference to non-existent subpattern" error.
257    
258        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
259    
260    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
261        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
262    
263    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
264    
265    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
266        character were causing crashes (broken optimization).
267    
268    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
269        \p or \P) caused a compile-time loop.
270    
271    28. More problems have arisen in unanchored patterns when CRLF is a valid line
272        break. For example, the unstudied pattern [\r\n]A does not match the string
273        "\r\nA" because change 7.0/46 below moves the current point on by two
274        characters after failing to match at the start. However, the pattern \nA
275        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
276        the same is true. There doesn't seem any very clean way out of this, but
277        what I have chosen to do makes the common cases work: PCRE now takes note
278        of whether there can be an explicit match for \r or \n anywhere in the
279        pattern, and if so, 7.0/46 no longer applies. As part of this change,
280        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
281        pattern has explicit CR or LF references.
282    
283    29. Added (*CR) etc for changing newline setting at start of pattern.
284    
285    
286  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
287  ---------------------  ---------------------

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12