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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.567  
changed lines
  Added in v.593

  ViewVC Help
Powered by ViewVC 1.1.5