ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 486 by ph10, Tue Jan 5 17:44:57 2010 UTC revision 594 by ph10, Sun May 1 08:22:12 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.01 06-Jan-10  Version 8.13 30-Apr-2011
5  ----------------------  ------------------------
7    1.  The Unicode data tables have been updated to Unicode 6.0.0.
9    2.  Two minor typos in pcre_internal.h have been fixed.
11    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
12        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
13        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
16    Version 8.12 15-Jan-2011
17    ------------------------
19    1.  Fixed some typos in the markup of the man pages, and wrote a script that
20        checks for such things as part of the documentation building process.
22    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
23        --match-limit and --recursion-limit options (added for 8.11). In
24        particular, this made one of the standard tests fail. (The integer value
25        went into the wrong half of a long int.)
27    3.  If the --colour option was given to pcregrep with -v (invert match), it
28        did strange things, either producing crazy output, or crashing. It should,
29        of course, ignore a request for colour when reporting lines that do not
30        match.
32    4.  Another pcregrep bug caused similar problems if --colour was specified with
33        -M (multiline) and the pattern match finished with a line ending.
35    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
36        matched in multiline mode, the following line was shown as part of the
37        match. This seems wrong, so I have changed it.
39    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
40        the check for further matches in the same line (so they could be coloured)
41        to overrun the end of the current line. If another match was found, it was
42        incorrectly shown (and then shown again when found in the next line).
44    7.  If pcregrep was compiled under Windows, there was a reference to the
45        function pcregrep_exit() before it was defined. I am assuming this was
46        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
47        reported by a user. I've moved the definition above the reference.
50    Version 8.11 10-Dec-2010
51    ------------------------
53    1.  (*THEN) was not working properly if there were untried alternatives prior
54        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
55        backtracked to try for "b" instead of moving to the next alternative branch
56        at the same level (in this case, to look for "c"). The Perl documentation
57        is clear that when (*THEN) is backtracked onto, it goes to the "next
58        alternative in the innermost enclosing group".
60    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
61        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
62        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
63        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
64        (*THEN).
66    3.  If \s appeared in a character class, it removed the VT character from
67        the class, even if it had been included by some previous item, for example
68        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
69        of \s, but is part of the POSIX "space" class.)
71    4.  A partial match never returns an empty string (because you can always
72        match an empty string at the end of the subject); however the checking for
73        an empty string was starting at the "start of match" point. This has been
74        changed to the "earliest inspected character" point, because the returned
75        data for a partial match starts at this character. This means that, for
76        example, /(?<=abc)def/ gives a partial match for the subject "abc"
77        (previously it gave "no match").
79    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
80        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
81        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
82        has an implication that the given string is incomplete (because a partial
83        match is preferred over a full match). For this reason, these items now
84        give a partial match in this situation. [Aside: previously, the one case
85        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
86        match rather than a full match, which was wrong by the old rules, but is
87        now correct.]
89    6.  There was a bug in the handling of #-introduced comments, recognized when
90        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
91        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
92        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
93        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
94        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
95        places in pcre_compile().
97    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
98        comments when looking ahead for named forward references to subpatterns,
99        the only newline sequence it recognized was NL. It now handles newlines
100        according to the set newline convention.
102    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
103        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
104        cater for a lack of strerror(). These oversights have been fixed.
106    9.  Added --match-limit and --recursion-limit to pcregrep.
108    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
110    11. When the -o option was used, pcregrep was setting a return code of 1, even
111        when matches were found, and --line-buffered was not being honoured.
113    12. Added an optional parentheses number to the -o and --only-matching options
114        of pcregrep.
116    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
117        can match an empty string. The code to do it in pcretest and pcredemo
118        needed fixing:
120        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
121            only one byte after an empty string match just before CRLF (this case
122            just got forgotten; "any" and "anycrlf" were OK).
124        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
125            mode when an empty string match preceded an ASCII character followed by
126            a non-ASCII character. (The code for advancing by one character rather
127            than one byte was nonsense.)
129        (c) The pcredemo.c sample program did not have any code at all to handle
130            the cases when CRLF is a valid newline sequence.
132    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
133        as a starting offset was within the subject string. There is now a new
134        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
135        negative or greater than the length of the string. In order to test this,
136        pcretest is extended to allow the setting of negative starting offsets.
138    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
139        starting offset points to the beginning of a UTF-8 character was
140        unnecessarily clumsy. I tidied it up.
142    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
143        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
145    17. Nobody had reported that the --include_dir option, which was added in
146        release 7.7 should have been called --include-dir (hyphen, not underscore)
147        for compatibility with GNU grep. I have changed it to --include-dir, but
148        left --include_dir as an undocumented synonym, and the same for
149        --exclude-dir, though that is not available in GNU grep, at least as of
150        release 2.5.4.
152    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
153        characters from a string of bytes) have been redefined so as not to use
154        loops, in order to improve performance in some environments. At the same
155        time, I abstracted some of the common code into auxiliary macros to save
156        repetition (this should not affect the compiled code).
158    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
159        compile-time error is now given if \c is not followed by an ASCII
160        character, that is, a byte less than 128. (In EBCDIC mode, the code is
161        different, and any byte value is allowed.)
163    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
164        START_OPTIMIZE option, which is now allowed at compile time - but just
165        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
166        to pcregrep and other applications that have no direct access to PCRE
167        options. The new /Y option in pcretest sets this option when calling
168        pcre_compile().
170    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
171        back references. Groups containing recursive back references were forced to
172        be atomic by that change, but in the case of named groups, the amount of
173        memory required was incorrectly computed, leading to "Failed: internal
174        error: code overflow". This has been fixed.
176    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
177        pcretest.c, to avoid build problems in some Borland environments.
180    Version 8.10 25-Jun-2010
181    ------------------------
183    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
184        THEN.
186    2.  (*ACCEPT) was not working when inside an atomic group.
188    3.  Inside a character class, \B is treated as a literal by default, but
189        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
190        causes the error). The code is unchanged, but I tidied the documentation.
192    4.  Inside a character class, PCRE always treated \R and \X as literals,
193        whereas Perl faults them if its -w option is set. I have changed PCRE so
194        that it faults them when PCRE_EXTRA is set.
196    5.  Added support for \N, which always matches any character other than
197        newline. (It is the same as "." when PCRE_DOTALL is not set.)
199    6.  When compiling pcregrep with newer versions of gcc which may have
200        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
201        declared with attribute warn_unused_result" were given. Just casting the
202        result to (void) does not stop the warnings; a more elaborate fudge is
203        needed. I've used a macro to implement this.
205    7.  Minor change to pcretest.c to avoid a compiler warning.
207    8.  Added four artifical Unicode properties to help with an option to make
208        \s etc use properties (see next item). The new properties are: Xan
209        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
211    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
212        use Unicode properties. (*UCP) at the start of a pattern can be used to set
213        this option. Modified pcretest to add /W to test this facility. Added
214        REG_UCP to make it available via the POSIX interface.
216    10. Added --line-buffered to pcregrep.
218    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
219        studied, and the match started with a letter with a code point greater than
220        127 whose first byte was different to the first byte of the other case of
221        the letter, the other case of this starting letter was not recognized
222        (#976).
224    12. If a pattern that was studied started with a repeated Unicode property
225        test, for example, \p{Nd}+, there was the theoretical possibility of
226        setting up an incorrect bitmap of starting bytes, but fortunately it could
227        not have actually happened in practice until change 8 above was made (it
228        added property types that matched character-matching opcodes).
230    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
231        possible starting bytes for non-anchored patterns.
233    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
234        \R, and also a number of cases that involve Unicode properties, both
235        explicit and implicit when PCRE_UCP is set.
237    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
238        input, it could crash or give wrong results if characters with values
239        greater than 0xc0 were present in the subject string. (Detail: it assumed
240        UTF-8 input when processing these items.)
242    16. Added a lot of (int) casts to avoid compiler warnings in systems where
243        size_t is 64-bit (#991).
245    17. Added a check for running out of memory when PCRE is compiled with
246        --disable-stack-for-recursion (#990).
248    18. If the last data line in a file for pcretest does not have a newline on
249        the end, a newline was missing in the output.
251    19. The default pcre_chartables.c file recognizes only ASCII characters (values
252        less than 128) in its various bitmaps. However, there is a facility for
253        generating tables according to the current locale when PCRE is compiled. It
254        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
255        characters, are recognized by isspace() and therefore were getting set in
256        these tables, and indeed these tables seem to approximate to ISO 8859. This
257        caused a problem in UTF-8 mode when pcre_study() was used to create a list
258        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
259        which of course cannot start UTF-8 characters. I have changed the code so
260        that only real ASCII characters (less than 128) and the correct starting
261        bytes for UTF-8 encodings are set for characters greater than 127 when in
262        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
263        altogether.)
265    20. Added the /T option to pcretest so as to be able to run tests with non-
266        standard character tables, thus making it possible to include the tests
267        used for 19 above in the standard set of tests.
269    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
270        reference to a subpattern the other side of a comment that contains an
271        opening parenthesis caused either an internal compiling error, or a
272        reference to the wrong subpattern.
275    Version 8.02 19-Mar-2010
276    ------------------------
278    1.  The Unicode data tables have been updated to Unicode 5.2.0.
280    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
281        configured.
283    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
284        original author of that file, following a query about its status.
286    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
287        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
289    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
290        quantifier applied to a forward-referencing subroutine call, could compile
291        incorrect code or give the error "internal error: previously-checked
292        referenced subpattern not found".
294    6.  Both MS Visual Studio and Symbian OS have problems with initializing
295        variables to point to external functions. For these systems, therefore,
296        pcre_malloc etc. are now initialized to local functions that call the
297        relevant global functions.
299    7.  There were two entries missing in the vectors called coptable and poptable
300        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
301        I've fixed the data, and added a kludgy way of testing at compile time that
302        the lengths are correct (equal to the number of opcodes).
304    8.  Following on from 7, I added a similar kludge to check the length of the
305        eint vector in pcreposix.c.
307    9.  Error texts for pcre_compile() are held as one long string to avoid too
308        much relocation at load time. To find a text, the string is searched,
309        counting zeros. There was no check for running off the end of the string,
310        which could happen if a new error number was added without updating the
311        string.
313    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
315    11. \K was not working if it appeared in an atomic group or in a group that
316        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
317        \K is "not well defined" if used in an assertion. PCRE now accepts it if
318        the assertion is positive, but not if it is negative.
320    12. Change 11 fortuitously reduced the size of the stack frame used in the
321        "match()" function of pcre_exec.c by one pointer. Forthcoming
322        implementation of support for (*MARK) will need an extra pointer on the
323        stack; I have reserved it now, so that the stack frame size does not
324        decrease.
326    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
327        item in branch that calls a recursion is a subroutine call - as in the
328        second branch in the above example - was incorrectly given the compile-
329        time error "recursive call could loop indefinitely" because pcre_compile()
330        was not correctly checking the subroutine for matching a non-empty string.
332    14. The checks for overrunning compiling workspace could trigger after an
333        overrun had occurred. This is a "should never occur" error, but it can be
334        triggered by pathological patterns such as hundreds of nested parentheses.
335        The checks now trigger 100 bytes before the end of the workspace.
337    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
340    Version 8.01 19-Jan-2010
341    ------------------------
343  1.  If a pattern contained a conditional subpattern with only one branch (in  1.  If a pattern contained a conditional subpattern with only one branch (in
344      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
345      computed the wrong minimum data length (which is of course zero for such      computed the wrong minimum data length (which is of course zero for such
346      subpatterns).      subpatterns). This could cause incorrect "no match" results.
348  2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of  2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
349      the pattern is reset in the first branch, pcre_compile() failed with      the pattern is reset in the first branch, pcre_compile() failed with
# Line 61  Version 8.01 06-Jan-10 Line 397  Version 8.01 06-Jan-10
397      custom one, because of the following reported problem in Windows:      custom one, because of the following reported problem in Windows:
399        - libbz2 uses the Pascal calling convention (WINAPI) for the functions        - libbz2 uses the Pascal calling convention (WINAPI) for the functions
400          under Win32.            under Win32.
401        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
402          therefore missing the function definition.            therefore missing the function definition.
403        - The compiler thus generates a "C" signature for the test function.        - The compiler thus generates a "C" signature for the test function.
404        - The linker fails to find the "C" function.        - The linker fails to find the "C" function.
405        - PCRE fails to configure if asked to do so against libbz2.        - PCRE fails to configure if asked to do so against libbz2.
# Line 113  Version 8.01 06-Jan-10 Line 449  Version 8.01 06-Jan-10
449      equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for      equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
450      instance, but it only takes 2 args instead of 3!"      instance, but it only takes 2 args instead of 3!"
452    18. A subtle bug concerned with back references has been fixed by a change of
453        specification, with a corresponding code fix. A pattern such as
454        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
455        refers, was giving matches when it shouldn't. For example, xa=xaaa would
456        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
457        same bug. Such groups have to be quantified to be useful, or contained
458        inside another quantified group. (If there's no repetition, the reference
459        can never match.) The problem arises because, having left the group and
460        moved on to the rest of the pattern, a later failure that backtracks into
461        the group uses the captured value from the final iteration of the group
462        rather than the correct earlier one. I have fixed this in PCRE by forcing
463        any group that contains a reference to itself to be an atomic group; that
464        is, there cannot be any backtracking into it once it has completed. This is
465        similar to recursive and subroutine calls.
468  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09
469  ----------------------  ----------------------

Removed from v.486  
changed lines
  Added in v.594

  ViewVC Help
Powered by ViewVC 1.1.5