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

Diff of /code/trunk/ChangeLog

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

revision 558 by ph10, Tue Oct 26 15:26:45 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  ------------------  ------------------
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    
16    Version 8.12 15-Jan-2011
17    ------------------------
18    
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.
21    
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.)
26    
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.
31    
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.
34    
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.
38    
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).
43    
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.
48    
49    
50    Version 8.11 10-Dec-2010
51  ------------------------  ------------------------
52    
53  1.  (*THEN) was not working properly if there were untried alternatives prior  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      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      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      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      is clear that when (*THEN) is backtracked onto, it goes to the "next
58      alternative in the innermost enclosing group".      alternative in the innermost enclosing group".
59    
60  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
61      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
62      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
63      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
64      (*THEN).      (*THEN).
65    
66  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
67      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
68      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
69      of \s, but is part of the POSIX "space" class.)      of \s, but is part of the POSIX "space" class.)
70    
71  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
72      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
73      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 77  Version 8.11 10-Oct-2010
77      (previously it gave "no match").      (previously it gave "no match").
78    
79  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
80      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,
81      previously a full match would be given. However, setting PCRE_PARTIAL_HARD      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      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      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      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      /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      match rather than a full match, which was wrong by the old rules, but is
87      now correct.]      now correct.]
88    
89  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
90      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.
91      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
92      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
93      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,
94      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
95      places in pcre_compile().      places in pcre_compile().
96    
97  7.  Related to (6) above, when pcre_compile() was skipping #-introduced  7.  Related to (6) above, when pcre_compile() was skipping #-introduced
98      comments when looking ahead for named forward references to subpatterns,      comments when looking ahead for named forward references to subpatterns,
99      the only newline sequence it recognized was NL. It now handles newlines      the only newline sequence it recognized was NL. It now handles newlines
100      according to the set newline convention.      according to the set newline convention.
101    
102  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
103      former, but used strtoul(), whereas pcretest avoided strtoul() but did not      former, but used strtoul(), whereas pcretest avoided strtoul() but did not
104      cater for a lack of strerror(). These oversights have been fixed.      cater for a lack of strerror(). These oversights have been fixed.
105    
106    9.  Added --match-limit and --recursion-limit to pcregrep.
107    
108    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
109    
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.
112    
113    12. Added an optional parentheses number to the -o and --only-matching options
114        of pcregrep.
115    
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:
119    
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).
123    
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.)
128    
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.
131    
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.
137    
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.
141    
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.
144    
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.
151    
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).
157    
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.)
162    
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().
169    
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.
175    
176    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
177        pcretest.c, to avoid build problems in some Borland environments.
178    
179    
180  Version 8.10 25-Jun-2010  Version 8.10 25-Jun-2010
181  ------------------------  ------------------------

Legend:
Removed from v.558  
changed lines
  Added in v.594

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12