/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 518 by ph10, Tue May 18 15:47:01 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  ------------------  ------------------
3    
4  Version 8.10 03 May-2010  Version 8.11 10-Oct-2010
5    ------------------------
6    
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".
13    
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).
19    
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.)
24    
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").
32    
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.]
42    
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().
50    
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.
55    
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.
59    
60    9.  Added --match-limit and --recursion-limit to pcregrep.
61    
62    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
63    
64    
65    Version 8.10 25-Jun-2010
66  ------------------------  ------------------------
67    
68  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
# Line 9  Version 8.10 03 May-2010 Line 70  Version 8.10 03 May-2010
70    
71  2.  (*ACCEPT) was not working when inside an atomic group.  2.  (*ACCEPT) was not working when inside an atomic group.
72    
73  3.  Inside a character class, \B is treated as a literal by default, but  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      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.      causes the error). The code is unchanged, but I tidied the documentation.
76    
77  4.  Inside a character class, PCRE always treated \R and \X as literals,  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      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.      that it faults them when PCRE_EXTRA is set.
80    
81  5.  Added support for \N, which always matches any character other than  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.)      newline. (It is the same as "." when PCRE_DOTALL is not set.)
83    
84  6.  When compiling pcregrep with newer versions of gcc which may have  6.  When compiling pcregrep with newer versions of gcc which may have
85      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
86      declared with attribute warn_unused_result" were given. Just casting the      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      result to (void) does not stop the warnings; a more elaborate fudge is
88      needed. I've used a macro to implement this.      needed. I've used a macro to implement this.
89    
90  7.  Minor change to pcretest.c to avoid a compiler warning.  7.  Minor change to pcretest.c to avoid a compiler warning.
91    
92  8.  Added four artifical Unicode properties to help with an option to make  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      \s etc use properties (see next item). The new properties are: Xan
94      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
95    
96  9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes  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      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      this option. Modified pcretest to add /W to test this facility. Added
99      REG_UCP to make it available via the POSIX interface.      REG_UCP to make it available via the POSIX interface.
100    
101    10. Added --line-buffered to pcregrep.
102    
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).
108    
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).
114    
115    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
116        possible starting bytes for non-anchored patterns.
117    
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.
121    
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.)
126    
127    16. Added a lot of (int) casts to avoid compiler warnings in systems where
128        size_t is 64-bit (#991).
129    
130    17. Added a check for running out of memory when PCRE is compiled with
131        --disable-stack-for-recursion (#990).
132    
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.
135    
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.)
149    
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.
153    
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.
158    
159    
160  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010
161  ------------------------  ------------------------

Legend:
Removed from v.518  
changed lines
  Added in v.563

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12