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

Diff of /code/trunk/ChangeLog

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

revision 561 by ph10, Sat Oct 30 18:37:47 2010 UTC revision 592 by ph10, Sat Apr 30 17:37:37 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    
10    Version 8.12 15-Jan-2011
11    ------------------------
12    
13    1.  Fixed some typos in the markup of the man pages, and wrote a script that
14        checks for such things as part of the documentation building process.
15    
16    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
17        --match-limit and --recursion-limit options (added for 8.11). In
18        particular, this made one of the standard tests fail. (The integer value
19        went into the wrong half of a long int.)
20    
21    3.  If the --colour option was given to pcregrep with -v (invert match), it
22        did strange things, either producing crazy output, or crashing. It should,
23        of course, ignore a request for colour when reporting lines that do not
24        match.
25    
26    4.  Another pcregrep bug caused similar problems if --colour was specified with
27        -M (multiline) and the pattern match finished with a line ending.
28    
29    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
30        matched in multiline mode, the following line was shown as part of the
31        match. This seems wrong, so I have changed it.
32    
33    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
34        the check for further matches in the same line (so they could be coloured)
35        to overrun the end of the current line. If another match was found, it was
36        incorrectly shown (and then shown again when found in the next line).
37    
38    7.  If pcregrep was compiled under Windows, there was a reference to the
39        function pcregrep_exit() before it was defined. I am assuming this was
40        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
41        reported by a user. I've moved the definition above the reference.
42    
43    
44    Version 8.11 10-Dec-2010
45  ------------------------  ------------------------
46    
47  1.  (*THEN) was not working properly if there were untried alternatives prior  1.  (*THEN) was not working properly if there were untried alternatives prior
48      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
49      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
50      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
51      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
52      alternative in the innermost enclosing group".      alternative in the innermost enclosing group".
53    
54  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
55      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
56      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
57      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
58      (*THEN).      (*THEN).
59    
60  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
61      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
62      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
63      of \s, but is part of the POSIX "space" class.)      of \s, but is part of the POSIX "space" class.)
64    
65  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
66      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
67      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 71  Version 8.11 10-Oct-2010
71      (previously it gave "no match").      (previously it gave "no match").
72    
73  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
74      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,
75      previously a full match would be given. However, setting PCRE_PARTIAL_HARD      previously a full match would be given. However, setting PCRE_PARTIAL_HARD
76      has an implication that the given string is incomplete (because a partial      has an implication that the given string is incomplete (because a partial
77      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
78      give a partial match in this situation. [Aside: previously, the one case      give a partial match in this situation. [Aside: previously, the one case
79      /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
80      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
81      now correct.]      now correct.]
82    
83  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
84      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.
85      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
86      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
87      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,
88      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
89      places in pcre_compile().      places in pcre_compile().
90    
91  7.  Related to (6) above, when pcre_compile() was skipping #-introduced  7.  Related to (6) above, when pcre_compile() was skipping #-introduced
92      comments when looking ahead for named forward references to subpatterns,      comments when looking ahead for named forward references to subpatterns,
93      the only newline sequence it recognized was NL. It now handles newlines      the only newline sequence it recognized was NL. It now handles newlines
94      according to the set newline convention.      according to the set newline convention.
95    
96  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the  8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
97      former, but used strtoul(), whereas pcretest avoided strtoul() but did not      former, but used strtoul(), whereas pcretest avoided strtoul() but did not
98      cater for a lack of strerror(). These oversights have been fixed.      cater for a lack of strerror(). These oversights have been fixed.
99    
100  9.  Added --match-limit and --recursion-limit to pcregrep.  9.  Added --match-limit and --recursion-limit to pcregrep.
101    
102    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
103    
104    11. When the -o option was used, pcregrep was setting a return code of 1, even
105        when matches were found, and --line-buffered was not being honoured.
106    
107    12. Added an optional parentheses number to the -o and --only-matching options
108        of pcregrep.
109    
110    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
111        can match an empty string. The code to do it in pcretest and pcredemo
112        needed fixing:
113    
114        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
115            only one byte after an empty string match just before CRLF (this case
116            just got forgotten; "any" and "anycrlf" were OK).
117    
118        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
119            mode when an empty string match preceded an ASCII character followed by
120            a non-ASCII character. (The code for advancing by one character rather
121            than one byte was nonsense.)
122    
123        (c) The pcredemo.c sample program did not have any code at all to handle
124            the cases when CRLF is a valid newline sequence.
125    
126    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
127        as a starting offset was within the subject string. There is now a new
128        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
129        negative or greater than the length of the string. In order to test this,
130        pcretest is extended to allow the setting of negative starting offsets.
131    
132    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
133        starting offset points to the beginning of a UTF-8 character was
134        unnecessarily clumsy. I tidied it up.
135    
136    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
137        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
138    
139    17. Nobody had reported that the --include_dir option, which was added in
140        release 7.7 should have been called --include-dir (hyphen, not underscore)
141        for compatibility with GNU grep. I have changed it to --include-dir, but
142        left --include_dir as an undocumented synonym, and the same for
143        --exclude-dir, though that is not available in GNU grep, at least as of
144        release 2.5.4.
145    
146    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
147        characters from a string of bytes) have been redefined so as not to use
148        loops, in order to improve performance in some environments. At the same
149        time, I abstracted some of the common code into auxiliary macros to save
150        repetition (this should not affect the compiled code).
151    
152    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
153        compile-time error is now given if \c is not followed by an ASCII
154        character, that is, a byte less than 128. (In EBCDIC mode, the code is
155        different, and any byte value is allowed.)
156    
157    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
158        START_OPTIMIZE option, which is now allowed at compile time - but just
159        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
160        to pcregrep and other applications that have no direct access to PCRE
161        options. The new /Y option in pcretest sets this option when calling
162        pcre_compile().
163    
164    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
165        back references. Groups containing recursive back references were forced to
166        be atomic by that change, but in the case of named groups, the amount of
167        memory required was incorrectly computed, leading to "Failed: internal
168        error: code overflow". This has been fixed.
169    
170    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
171        pcretest.c, to avoid build problems in some Borland environments.
172    
173    
174  Version 8.10 25-Jun-2010  Version 8.10 25-Jun-2010

Legend:
Removed from v.561  
changed lines
  Added in v.592

  ViewVC Help
Powered by ViewVC 1.1.5