ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.491  
changed lines
  Added in v.595

  ViewVC Help
Powered by ViewVC 1.1.5