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 563 by ph10, Sun Oct 31 14:15:04 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.02 01-Mar-2010  Version 8.11 10-Oct-2010
5    ------------------------
7    1.  (*THEN) was not working properly if there were untried alternatives prior
8        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
9        backtracked to try for "b" instead of moving to the next alternative branch
10        at the same level (in this case, to look for "c"). The Perl documentation
11        is clear that when (*THEN) is backtracked onto, it goes to the "next
12        alternative in the innermost enclosing group".
14    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
15        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
16        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
17        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
18        (*THEN).
20    3.  If \s appeared in a character class, it removed the VT character from
21        the class, even if it had been included by some previous item, for example
22        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
23        of \s, but is part of the POSIX "space" class.)
25    4.  A partial match never returns an empty string (because you can always
26        match an empty string at the end of the subject); however the checking for
27        an empty string was starting at the "start of match" point. This has been
28        changed to the "earliest inspected character" point, because the returned
29        data for a partial match starts at this character. This means that, for
30        example, /(?<=abc)def/ gives a partial match for the subject "abc"
31        (previously it gave "no match").
33    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
34        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
35        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
36        has an implication that the given string is incomplete (because a partial
37        match is preferred over a full match). For this reason, these items now
38        give a partial match in this situation. [Aside: previously, the one case
39        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
40        match rather than a full match, which was wrong by the old rules, but is
41        now correct.]
43    6.  There was a bug in the handling of #-introduced comments, recognized when
44        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
45        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
46        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
47        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
48        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
49        places in pcre_compile().
51    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
52        comments when looking ahead for named forward references to subpatterns,
53        the only newline sequence it recognized was NL. It now handles newlines
54        according to the set newline convention.
56    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
57        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
58        cater for a lack of strerror(). These oversights have been fixed.
60    9.  Added --match-limit and --recursion-limit to pcregrep.
62    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
65    Version 8.10 25-Jun-2010
66    ------------------------
68    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
69        THEN.
71    2.  (*ACCEPT) was not working when inside an atomic group.
73    3.  Inside a character class, \B is treated as a literal by default, but
74        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
75        causes the error). The code is unchanged, but I tidied the documentation.
77    4.  Inside a character class, PCRE always treated \R and \X as literals,
78        whereas Perl faults them if its -w option is set. I have changed PCRE so
79        that it faults them when PCRE_EXTRA is set.
81    5.  Added support for \N, which always matches any character other than
82        newline. (It is the same as "." when PCRE_DOTALL is not set.)
84    6.  When compiling pcregrep with newer versions of gcc which may have
85        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
86        declared with attribute warn_unused_result" were given. Just casting the
87        result to (void) does not stop the warnings; a more elaborate fudge is
88        needed. I've used a macro to implement this.
90    7.  Minor change to pcretest.c to avoid a compiler warning.
92    8.  Added four artifical Unicode properties to help with an option to make
93        \s etc use properties (see next item). The new properties are: Xan
94        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
96    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
97        use Unicode properties. (*UCP) at the start of a pattern can be used to set
98        this option. Modified pcretest to add /W to test this facility. Added
99        REG_UCP to make it available via the POSIX interface.
101    10. Added --line-buffered to pcregrep.
103    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
104        studied, and the match started with a letter with a code point greater than
105        127 whose first byte was different to the first byte of the other case of
106        the letter, the other case of this starting letter was not recognized
107        (#976).
109    12. If a pattern that was studied started with a repeated Unicode property
110        test, for example, \p{Nd}+, there was the theoretical possibility of
111        setting up an incorrect bitmap of starting bytes, but fortunately it could
112        not have actually happened in practice until change 8 above was made (it
113        added property types that matched character-matching opcodes).
115    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
116        possible starting bytes for non-anchored patterns.
118    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
119        \R, and also a number of cases that involve Unicode properties, both
120        explicit and implicit when PCRE_UCP is set.
122    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
123        input, it could crash or give wrong results if characters with values
124        greater than 0xc0 were present in the subject string. (Detail: it assumed
125        UTF-8 input when processing these items.)
127    16. Added a lot of (int) casts to avoid compiler warnings in systems where
128        size_t is 64-bit (#991).
130    17. Added a check for running out of memory when PCRE is compiled with
131        --disable-stack-for-recursion (#990).
133    18. If the last data line in a file for pcretest does not have a newline on
134        the end, a newline was missing in the output.
136    19. The default pcre_chartables.c file recognizes only ASCII characters (values
137        less than 128) in its various bitmaps. However, there is a facility for
138        generating tables according to the current locale when PCRE is compiled. It
139        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
140        characters, are recognized by isspace() and therefore were getting set in
141        these tables, and indeed these tables seem to approximate to ISO 8859. This
142        caused a problem in UTF-8 mode when pcre_study() was used to create a list
143        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
144        which of course cannot start UTF-8 characters. I have changed the code so
145        that only real ASCII characters (less than 128) and the correct starting
146        bytes for UTF-8 encodings are set for characters greater than 127 when in
147        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
148        altogether.)
150    20. Added the /T option to pcretest so as to be able to run tests with non-
151        standard character tables, thus making it possible to include the tests
152        used for 19 above in the standard set of tests.
154    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
155        reference to a subpattern the other side of a comment that contains an
156        opening parenthesis caused either an internal compiling error, or a
157        reference to the wrong subpattern.
160    Version 8.02 19-Mar-2010
161  ------------------------  ------------------------
163  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.
165    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
166        configured.
168    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
169        original author of that file, following a query about its status.
171    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
172        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
174    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
175        quantifier applied to a forward-referencing subroutine call, could compile
176        incorrect code or give the error "internal error: previously-checked
177        referenced subpattern not found".
179    6.  Both MS Visual Studio and Symbian OS have problems with initializing
180        variables to point to external functions. For these systems, therefore,
181        pcre_malloc etc. are now initialized to local functions that call the
182        relevant global functions.
184    7.  There were two entries missing in the vectors called coptable and poptable
185        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
186        I've fixed the data, and added a kludgy way of testing at compile time that
187        the lengths are correct (equal to the number of opcodes).
189    8.  Following on from 7, I added a similar kludge to check the length of the
190        eint vector in pcreposix.c.
192    9.  Error texts for pcre_compile() are held as one long string to avoid too
193        much relocation at load time. To find a text, the string is searched,
194        counting zeros. There was no check for running off the end of the string,
195        which could happen if a new error number was added without updating the
196        string.
198    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
200    11. \K was not working if it appeared in an atomic group or in a group that
201        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
202        \K is "not well defined" if used in an assertion. PCRE now accepts it if
203        the assertion is positive, but not if it is negative.
205    12. Change 11 fortuitously reduced the size of the stack frame used in the
206        "match()" function of pcre_exec.c by one pointer. Forthcoming
207        implementation of support for (*MARK) will need an extra pointer on the
208        stack; I have reserved it now, so that the stack frame size does not
209        decrease.
211    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
212        item in branch that calls a recursion is a subroutine call - as in the
213        second branch in the above example - was incorrectly given the compile-
214        time error "recursive call could loop indefinitely" because pcre_compile()
215        was not correctly checking the subroutine for matching a non-empty string.
217    14. The checks for overrunning compiling workspace could trigger after an
218        overrun had occurred. This is a "should never occur" error, but it can be
219        triggered by pathological patterns such as hundreds of nested parentheses.
220        The checks now trigger 100 bytes before the end of the workspace.
222    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
225  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
226  ------------------------  ------------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5