ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 203 by ph10, Fri Aug 3 10:09:57 2007 UTC revision 276 by ph10, Wed Nov 21 15:39:20 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-07  Version 7.5 12-Nov-07
5    ---------------------
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."
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.
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
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.
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).
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.
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.
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
42    9.  Fix two occurrences of "backslash" in comments that should have been
43        "backspace".
45    10. Remove two redundant lines of code that can never be obeyed (their function
46        was moved elsewhere).
49    Version 7.4 21-Sep-07
50    ---------------------
52    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
53        means that a class such as [\s] counted as "explicit reference to CR or
54        LF". That isn't really right - the whole point of the change was to try to
55        help when there was an actual mention of one of the two characters. So now
56        the change happens only if \r or \n (or a literal CR or LF) character is
57        encountered.
59    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
60        of both had grown to the point where there were only 3 bits left.
61        Fortunately, there was spare space in the data structure, and so I have
62        moved the internal flags into a new 16-bit field to free up more option
63        bits.
65    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
66        but did not set the internal JCHANGED flag - either of these is enough to
67        control the way the "get" function works - but the PCRE_INFO_JCHANGED
68        facility is supposed to tell if (?J) was ever used, so now (?J) at the
69        start sets both bits.
71    4.  Added options (at build time, compile time, exec time) to change \R from
72        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
74    5.  doc/pcresyntax.html was missing from the distribution.
76    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
77        compatibility, even though it is no longer used.
79    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
80        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
81        windows.h file is present (where different names are used). [This was
82        reversed later after testing - see 16 below.]
84    8.  Changed all #include <config.h> to #include "config.h". There were also
85        some further <pcre.h> cases that I changed to "pcre.h".
87    9.  When pcregrep was used with the --colour option, it missed the line ending
88        sequence off the lines that it output.
90    10. It was pointed out to me that arrays of string pointers cause lots of
91        relocations when a shared library is dynamically loaded. A technique of
92        using a single long string with a table of offsets can drastically reduce
93        these. I have refactored PCRE in four places to do this. The result is
94        dramatic:
96          Originally:                          290
97          After changing UCP table:            187
98          After changing error message table:   43
99          After changing table of "verbs"       36
100          After changing table of Posix names   22
102        Thanks to the folks working on Gregex for glib for this insight.
104    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
105        unicode-properties was also set.
107    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
109    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
110        checked only for CRLF.
112    14. Added casts to pcretest.c to avoid compiler warnings.
114    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
116    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
117        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
118        entirely. This removes changes made in 7 above.
120    17. The CMake files have been updated, and there is now more information about
121        building with CMake in the NON-UNIX-USE document.
124    Version 7.3 28-Aug-07
125  ---------------------  ---------------------
127   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 184  Version 7.3 05-Jul-07
184      dynamic way, which I have now done. The artificial limitation on group      dynamic way, which I have now done. The artificial limitation on group
185      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
186      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
188  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
189      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
190      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
191      empty string.      empty string.
193    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
194        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
195        because the ] is interpreted as the first data character and the
196        terminating ] is not found. PCRE has been made compatible with Perl in this
197        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
198        cause memory overwriting.
200    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
201        string has been matched (to stop an infinite loop). It was not recognizing
202        a conditional subpattern that could match an empty string if that
203        subpattern was within another subpattern. For example, it looped when
204        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
205        condition was not nested. This bug has been fixed.
207    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
208        past the start of the subject in the presence of bytes with the top bit
209        set, for example "\x8aBCD".
211    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
212        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
214    14. Optimized (?!) to (*FAIL).
216    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
217        This restricts code points to be within the range 0 to 0x10FFFF, excluding
218        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
219        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
220        does: it's just the validity check that is more restrictive.
222    16. Inserted checks for integer overflows during escape sequence (backslash)
223        processing, and also fixed erroneous offset values for syntax errors during
224        backslash processing.
226    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
227        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
229    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
230        caused an overrun.
232    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
233        something other than just ASCII characters) inside a group that had an
234        unlimited repeat caused a loop at compile time (while checking to see
235        whether the group could match an empty string).
237    20. Debugging a pattern containing \p or \P could cause a crash. For example,
238        [\P{Any}] did so. (Error in the code for printing property names.)
240    21. An orphan \E inside a character class could cause a crash.
242    22. A repeated capturing bracket such as (A)? could cause a wild memory
243        reference during compilation.
245    23. There are several functions in pcre_compile() that scan along a compiled
246        expression for various reasons (e.g. to see if it's fixed length for look
247        behind). There were bugs in these functions when a repeated \p or \P was
248        present in the pattern. These operators have additional parameters compared
249        with \d, etc, and these were not being taken into account when moving along
250        the compiled data. Specifically:
252        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
253            length.
255        (b) An item such as \pL+ within a repeated group could cause crashes or
256            loops.
258        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
259            "reference to non-existent subpattern" error.
261        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
263    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
264        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
266    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
268    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
269        character were causing crashes (broken optimization).
271    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
272        \p or \P) caused a compile-time loop.
274    28. More problems have arisen in unanchored patterns when CRLF is a valid line
275        break. For example, the unstudied pattern [\r\n]A does not match the string
276        "\r\nA" because change 7.0/46 below moves the current point on by two
277        characters after failing to match at the start. However, the pattern \nA
278        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
279        the same is true. There doesn't seem any very clean way out of this, but
280        what I have chosen to do makes the common cases work: PCRE now takes note
281        of whether there can be an explicit match for \r or \n anywhere in the
282        pattern, and if so, 7.0/46 no longer applies. As part of this change,
283        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
284        pattern has explicit CR or LF references.
286    29. Added (*CR) etc for changing newline setting at start of pattern.
289  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Removed from v.203  
changed lines
  Added in v.276

  ViewVC Help
Powered by ViewVC 1.1.5