/[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 277 by ph10, Mon Nov 26 17:03:45 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    10. Remove two redundant lines of code that can never be obeyed (their function
46        was moved elsewhere).
47    
48    11. The program that makes PCRE's Unicode character property table had a bug
49        which caused it to generate incorrect table entries for sequences of
50        characters that have the same character type, but are in different scripts.
51        It amalgamated them into a single range, with the script of the first of
52        them. In other words, some characters were in the wrong script. There were
53        thirteen such cases, affecting characters in the following ranges:
54    
55          U+002b0 - U+002c1
56          U+0060c - U+0060d
57          U+0061e - U+00612
58          U+0064b - U+0065e
59          U+0074d - U+0076d
60          U+01800 - U+01805
61          U+01d00 - U+01d77
62          U+01d9b - U+01dbf
63          U+0200b - U+0200f
64          U+030fc - U+030fe
65          U+03260 - U+0327f
66          U+0fb46 - U+0fbb1
67          U+10450 - U+1049d
68    
69    
70    Version 7.4 21-Sep-07
71    ---------------------
72    
73    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
74        means that a class such as [\s] counted as "explicit reference to CR or
75        LF". That isn't really right - the whole point of the change was to try to
76        help when there was an actual mention of one of the two characters. So now
77        the change happens only if \r or \n (or a literal CR or LF) character is
78        encountered.
79    
80    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
81        of both had grown to the point where there were only 3 bits left.
82        Fortunately, there was spare space in the data structure, and so I have
83        moved the internal flags into a new 16-bit field to free up more option
84        bits.
85    
86    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
87        but did not set the internal JCHANGED flag - either of these is enough to
88        control the way the "get" function works - but the PCRE_INFO_JCHANGED
89        facility is supposed to tell if (?J) was ever used, so now (?J) at the
90        start sets both bits.
91    
92    4.  Added options (at build time, compile time, exec time) to change \R from
93        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
94    
95    5.  doc/pcresyntax.html was missing from the distribution.
96    
97    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
98        compatibility, even though it is no longer used.
99    
100    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
101        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
102        windows.h file is present (where different names are used). [This was
103        reversed later after testing - see 16 below.]
104    
105    8.  Changed all #include <config.h> to #include "config.h". There were also
106        some further <pcre.h> cases that I changed to "pcre.h".
107    
108    9.  When pcregrep was used with the --colour option, it missed the line ending
109        sequence off the lines that it output.
110    
111    10. It was pointed out to me that arrays of string pointers cause lots of
112        relocations when a shared library is dynamically loaded. A technique of
113        using a single long string with a table of offsets can drastically reduce
114        these. I have refactored PCRE in four places to do this. The result is
115        dramatic:
116    
117          Originally:                          290
118          After changing UCP table:            187
119          After changing error message table:   43
120          After changing table of "verbs"       36
121          After changing table of Posix names   22
122    
123        Thanks to the folks working on Gregex for glib for this insight.
124    
125    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
126        unicode-properties was also set.
127    
128    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
129    
130    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
131        checked only for CRLF.
132    
133    14. Added casts to pcretest.c to avoid compiler warnings.
134    
135    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
136    
137    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
138        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
139        entirely. This removes changes made in 7 above.
140    
141    17. The CMake files have been updated, and there is now more information about
142        building with CMake in the NON-UNIX-USE document.
143    
144    
145    Version 7.3 28-Aug-07
146  ---------------------  ---------------------
147    
148   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 205  Version 7.3 05-Jul-07
205      dynamic way, which I have now done. The artificial limitation on group      dynamic way, which I have now done. The artificial limitation on group
206      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
207      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
208    
209  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
210      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
211      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
212      empty string.      empty string.
213    
214  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
215      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,
216      because the ] is interpreted as the first data character and the      because the ] is interpreted as the first data character and the
217      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
218      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
219      cause memory overwriting.      cause memory overwriting.
220    
221  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
222      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
223      a conditional subpattern that could match an empty string if that      a conditional subpattern that could match an empty string if that
224      subpattern was within another subpattern. For example, it looped when      subpattern was within another subpattern. For example, it looped when
225      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
226      condition was not nested. This bug has been fixed.      condition was not nested. This bug has been fixed.
227    
228    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
229        past the start of the subject in the presence of bytes with the top bit
230        set, for example "\x8aBCD".
231    
232    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
233        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
234    
235    14. Optimized (?!) to (*FAIL).
236    
237    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
238        This restricts code points to be within the range 0 to 0x10FFFF, excluding
239        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
240        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
241        does: it's just the validity check that is more restrictive.
242    
243    16. Inserted checks for integer overflows during escape sequence (backslash)
244        processing, and also fixed erroneous offset values for syntax errors during
245        backslash processing.
246    
247    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
248        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
249    
250    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
251        caused an overrun.
252    
253    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
254        something other than just ASCII characters) inside a group that had an
255        unlimited repeat caused a loop at compile time (while checking to see
256        whether the group could match an empty string).
257    
258    20. Debugging a pattern containing \p or \P could cause a crash. For example,
259        [\P{Any}] did so. (Error in the code for printing property names.)
260    
261    21. An orphan \E inside a character class could cause a crash.
262    
263    22. A repeated capturing bracket such as (A)? could cause a wild memory
264        reference during compilation.
265    
266    23. There are several functions in pcre_compile() that scan along a compiled
267        expression for various reasons (e.g. to see if it's fixed length for look
268        behind). There were bugs in these functions when a repeated \p or \P was
269        present in the pattern. These operators have additional parameters compared
270        with \d, etc, and these were not being taken into account when moving along
271        the compiled data. Specifically:
272    
273        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
274            length.
275    
276        (b) An item such as \pL+ within a repeated group could cause crashes or
277            loops.
278    
279        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
280            "reference to non-existent subpattern" error.
281    
282        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
283    
284    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
285        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
286    
287    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
288    
289    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
290        character were causing crashes (broken optimization).
291    
292    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
293        \p or \P) caused a compile-time loop.
294    
295    28. More problems have arisen in unanchored patterns when CRLF is a valid line
296        break. For example, the unstudied pattern [\r\n]A does not match the string
297        "\r\nA" because change 7.0/46 below moves the current point on by two
298        characters after failing to match at the start. However, the pattern \nA
299        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
300        the same is true. There doesn't seem any very clean way out of this, but
301        what I have chosen to do makes the common cases work: PCRE now takes note
302        of whether there can be an explicit match for \r or \n anywhere in the
303        pattern, and if so, 7.0/46 no longer applies. As part of this change,
304        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
305        pattern has explicit CR or LF references.
306    
307    29. Added (*CR) etc for changing newline setting at start of pattern.
308    
309    
310  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
311  ---------------------  ---------------------

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12