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

Diff of /code/trunk/ChangeLog

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

revision 564 by ph10, Sun Oct 31 16:07:24 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  ------------------  ------------------
3    
4  Version 8.11 10-Oct-2010  Version 8.13 30-Apr-2011
5    ------------------------
6    
7    1.  The Unicode data tables have been updated to Unicode 6.0.0.
8    
9    2.  Two minor typos in pcre_internal.h have been fixed.
10    
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).
14    
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).
23    
24    
25    Version 8.12 15-Jan-2011
26    ------------------------
27    
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.
30    
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.)
35    
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.
40    
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.
43    
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.
47    
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).
52    
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.
57    
58    
59    Version 8.11 10-Dec-2010
60  ------------------------  ------------------------
61    
62  1.  (*THEN) was not working properly if there were untried alternatives prior  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      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      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      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      is clear that when (*THEN) is backtracked onto, it goes to the "next
67      alternative in the innermost enclosing group".      alternative in the innermost enclosing group".
68    
69  2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern  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      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      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
72      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
73      (*THEN).      (*THEN).
74    
75  3.  If \s appeared in a character class, it removed the VT character from  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      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      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.)      of \s, but is part of the POSIX "space" class.)
79    
80  4.  A partial match never returns an empty string (because you can always  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      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      an empty string was starting at the "start of match" point. This has been
# Line 31  Version 8.11 10-Oct-2010 Line 86  Version 8.11 10-Oct-2010
86      (previously it gave "no match").      (previously it gave "no match").
87    
88  5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching  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,      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      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      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      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      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      /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      match rather than a full match, which was wrong by the old rules, but is
96      now correct.]      now correct.]
97    
98  6.  There was a bug in the handling of #-introduced comments, recognized when  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.      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      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      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,      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      but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
104      places in pcre_compile().      places in pcre_compile().
105    
106  7.  Related to (6) above, when pcre_compile() was skipping #-introduced  7.  Related to (6) above, when pcre_compile() was skipping #-introduced
107      comments when looking ahead for named forward references to subpatterns,      comments when looking ahead for named forward references to subpatterns,
108      the only newline sequence it recognized was NL. It now handles newlines      the only newline sequence it recognized was NL. It now handles newlines
109      according to the set newline convention.      according to the set newline convention.
110    
111  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
112      former, but used strtoul(), whereas pcretest avoided strtoul() but did not      former, but used strtoul(), whereas pcretest avoided strtoul() but did not
113      cater for a lack of strerror(). These oversights have been fixed.      cater for a lack of strerror(). These oversights have been fixed.
114    
115  9.  Added --match-limit and --recursion-limit to pcregrep.  9.  Added --match-limit and --recursion-limit to pcregrep.
116    
117  10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.  10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
118    
119  11. When the -o option was used, pcregrep was setting a return code of 1, even  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.      when matches were found, and --line-buffered was not being honoured.
121    
122    12. Added an optional parentheses number to the -o and --only-matching options
123        of pcregrep.
124    
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:
128    
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).
132    
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.)
137    
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.
140    
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.
146    
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.
150    
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.
153    
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.
160    
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).
166    
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.)
171    
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().
178    
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.
184    
185    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
186        pcretest.c, to avoid build problems in some Borland environments.
187    
188    
189  Version 8.10 25-Jun-2010  Version 8.10 25-Jun-2010
190  ------------------------  ------------------------

Legend:
Removed from v.564  
changed lines
  Added in v.595

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12