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

Diff of /code/trunk/ChangeLog

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

revision 528 by ph10, Sat May 29 16:40:22 2010 UTC revision 600 by ph10, Mon May 9 08:54:11 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.10 03 May-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    5.  Comprehensive information about what went wrong is now returned by
25        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
26        as the output vector has at least 2 elements. The offset of the start of
27        the failing character and a reason code are placed in the vector.
28    
29    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
30        now returned is for the first byte of the failing character, instead of the
31        last byte inspected. This is an incompatible change, but I hope it is small
32        enough not to be a problem. It makes the returned offset consistent with
33        pcre_exec() and pcre_dfa_exec().
34    
35    7.  pcretest now gives a text phrase as well as the error number when
36        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
37        failure, the offset and reason code are output.
38    
39    8.  When \R was used with a maximizing quantifier it failed to skip backwards
40        over a \r\n pair if the subsequent match failed. Instead, it just skipped
41        back over a single character (\n). This seems wrong (because it treated the
42        two characters as a single entity when going forwards), conflicts with the
43        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
44        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
45        has been changed.
46    
47    
48    Version 8.12 15-Jan-2011
49    ------------------------
50    
51    1.  Fixed some typos in the markup of the man pages, and wrote a script that
52        checks for such things as part of the documentation building process.
53    
54    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
55        --match-limit and --recursion-limit options (added for 8.11). In
56        particular, this made one of the standard tests fail. (The integer value
57        went into the wrong half of a long int.)
58    
59    3.  If the --colour option was given to pcregrep with -v (invert match), it
60        did strange things, either producing crazy output, or crashing. It should,
61        of course, ignore a request for colour when reporting lines that do not
62        match.
63    
64    4.  Another pcregrep bug caused similar problems if --colour was specified with
65        -M (multiline) and the pattern match finished with a line ending.
66    
67    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
68        matched in multiline mode, the following line was shown as part of the
69        match. This seems wrong, so I have changed it.
70    
71    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
72        the check for further matches in the same line (so they could be coloured)
73        to overrun the end of the current line. If another match was found, it was
74        incorrectly shown (and then shown again when found in the next line).
75    
76    7.  If pcregrep was compiled under Windows, there was a reference to the
77        function pcregrep_exit() before it was defined. I am assuming this was
78        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
79        reported by a user. I've moved the definition above the reference.
80    
81    
82    Version 8.11 10-Dec-2010
83    ------------------------
84    
85    1.  (*THEN) was not working properly if there were untried alternatives prior
86        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
87        backtracked to try for "b" instead of moving to the next alternative branch
88        at the same level (in this case, to look for "c"). The Perl documentation
89        is clear that when (*THEN) is backtracked onto, it goes to the "next
90        alternative in the innermost enclosing group".
91    
92    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
93        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
94        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
95        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
96        (*THEN).
97    
98    3.  If \s appeared in a character class, it removed the VT character from
99        the class, even if it had been included by some previous item, for example
100        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
101        of \s, but is part of the POSIX "space" class.)
102    
103    4.  A partial match never returns an empty string (because you can always
104        match an empty string at the end of the subject); however the checking for
105        an empty string was starting at the "start of match" point. This has been
106        changed to the "earliest inspected character" point, because the returned
107        data for a partial match starts at this character. This means that, for
108        example, /(?<=abc)def/ gives a partial match for the subject "abc"
109        (previously it gave "no match").
110    
111    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
112        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
113        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
114        has an implication that the given string is incomplete (because a partial
115        match is preferred over a full match). For this reason, these items now
116        give a partial match in this situation. [Aside: previously, the one case
117        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
118        match rather than a full match, which was wrong by the old rules, but is
119        now correct.]
120    
121    6.  There was a bug in the handling of #-introduced comments, recognized when
122        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
123        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
124        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
125        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
126        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
127        places in pcre_compile().
128    
129    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
130        comments when looking ahead for named forward references to subpatterns,
131        the only newline sequence it recognized was NL. It now handles newlines
132        according to the set newline convention.
133    
134    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
135        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
136        cater for a lack of strerror(). These oversights have been fixed.
137    
138    9.  Added --match-limit and --recursion-limit to pcregrep.
139    
140    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
141    
142    11. When the -o option was used, pcregrep was setting a return code of 1, even
143        when matches were found, and --line-buffered was not being honoured.
144    
145    12. Added an optional parentheses number to the -o and --only-matching options
146        of pcregrep.
147    
148    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
149        can match an empty string. The code to do it in pcretest and pcredemo
150        needed fixing:
151    
152        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
153            only one byte after an empty string match just before CRLF (this case
154            just got forgotten; "any" and "anycrlf" were OK).
155    
156        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
157            mode when an empty string match preceded an ASCII character followed by
158            a non-ASCII character. (The code for advancing by one character rather
159            than one byte was nonsense.)
160    
161        (c) The pcredemo.c sample program did not have any code at all to handle
162            the cases when CRLF is a valid newline sequence.
163    
164    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
165        as a starting offset was within the subject string. There is now a new
166        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
167        negative or greater than the length of the string. In order to test this,
168        pcretest is extended to allow the setting of negative starting offsets.
169    
170    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
171        starting offset points to the beginning of a UTF-8 character was
172        unnecessarily clumsy. I tidied it up.
173    
174    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
175        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
176    
177    17. Nobody had reported that the --include_dir option, which was added in
178        release 7.7 should have been called --include-dir (hyphen, not underscore)
179        for compatibility with GNU grep. I have changed it to --include-dir, but
180        left --include_dir as an undocumented synonym, and the same for
181        --exclude-dir, though that is not available in GNU grep, at least as of
182        release 2.5.4.
183    
184    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
185        characters from a string of bytes) have been redefined so as not to use
186        loops, in order to improve performance in some environments. At the same
187        time, I abstracted some of the common code into auxiliary macros to save
188        repetition (this should not affect the compiled code).
189    
190    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
191        compile-time error is now given if \c is not followed by an ASCII
192        character, that is, a byte less than 128. (In EBCDIC mode, the code is
193        different, and any byte value is allowed.)
194    
195    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
196        START_OPTIMIZE option, which is now allowed at compile time - but just
197        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
198        to pcregrep and other applications that have no direct access to PCRE
199        options. The new /Y option in pcretest sets this option when calling
200        pcre_compile().
201    
202    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
203        back references. Groups containing recursive back references were forced to
204        be atomic by that change, but in the case of named groups, the amount of
205        memory required was incorrectly computed, leading to "Failed: internal
206        error: code overflow". This has been fixed.
207    
208    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
209        pcretest.c, to avoid build problems in some Borland environments.
210    
211    
212    Version 8.10 25-Jun-2010
213  ------------------------  ------------------------
214    
215  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 217  Version 8.10 03 May-2010
217    
218  2.  (*ACCEPT) was not working when inside an atomic group.  2.  (*ACCEPT) was not working when inside an atomic group.
219    
220  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
221      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
222      causes the error). The code is unchanged, but I tidied the documentation.      causes the error). The code is unchanged, but I tidied the documentation.
223    
224  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,
225      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
226      that it faults them when PCRE_EXTRA is set.      that it faults them when PCRE_EXTRA is set.
227    
228  5.  Added support for \N, which always matches any character other than  5.  Added support for \N, which always matches any character other than
229      newline. (It is the same as "." when PCRE_DOTALL is not set.)      newline. (It is the same as "." when PCRE_DOTALL is not set.)
230    
231  6.  When compiling pcregrep with newer versions of gcc which may have  6.  When compiling pcregrep with newer versions of gcc which may have
232      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
233      declared with attribute warn_unused_result" were given. Just casting the      declared with attribute warn_unused_result" were given. Just casting the
234      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
235      needed. I've used a macro to implement this.      needed. I've used a macro to implement this.
236    
237  7.  Minor change to pcretest.c to avoid a compiler warning.  7.  Minor change to pcretest.c to avoid a compiler warning.
238    
239  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
240      \s etc use properties (see next item). The new properties are: Xan      \s etc use properties (see next item). The new properties are: Xan
241      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
242    
243  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
244      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
245      this option. Modified pcretest to add /W to test this facility. Added      this option. Modified pcretest to add /W to test this facility. Added
246      REG_UCP to make it available via the POSIX interface.      REG_UCP to make it available via the POSIX interface.
   
 10. Added --line-buffered to pcregrep.  
247    
248  11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was  10. Added --line-buffered to pcregrep.
249      studied, and the match started with a letter with a code point greater than  
250    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
251        studied, and the match started with a letter with a code point greater than
252      127 whose first byte was different to the first byte of the other case of      127 whose first byte was different to the first byte of the other case of
253      the letter, the other case of this starting letter was not recognized.      the letter, the other case of this starting letter was not recognized
254        (#976).
255  12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a  
256      conflict in the definition of PCRE_EXP_DECL. I have removed the include of  12. If a pattern that was studied started with a repeated Unicode property
     pcre.h as pcre_internal.h includes pcre.h itself. (This may be a bit of  
     historical tidying that never got done.)  
   
 13. If a pattern that was studied started with a repeated Unicode property  
257      test, for example, \p{Nd}+, there was the theoretical possibility of      test, for example, \p{Nd}+, there was the theoretical possibility of
258      setting up an incorrect bitmap of starting bytes, but fortunately it could      setting up an incorrect bitmap of starting bytes, but fortunately it could
259      not have actually happened in practice until change 8 above was made (it      not have actually happened in practice until change 8 above was made (it
260      added property types that matched character-matching opcodes).      added property types that matched character-matching opcodes).
261    
262  14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of  13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
263      possible starting bytes for non-anchored patterns.      possible starting bytes for non-anchored patterns.
264    
265  15. The "auto-possessify" feature of pcre_compile() now recognizes \R.  14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
266        \R, and also a number of cases that involve Unicode properties, both
267        explicit and implicit when PCRE_UCP is set.
268    
269    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
270        input, it could crash or give wrong results if characters with values
271        greater than 0xc0 were present in the subject string. (Detail: it assumed
272        UTF-8 input when processing these items.)
273    
274    16. Added a lot of (int) casts to avoid compiler warnings in systems where
275        size_t is 64-bit (#991).
276    
277    17. Added a check for running out of memory when PCRE is compiled with
278        --disable-stack-for-recursion (#990).
279    
280    18. If the last data line in a file for pcretest does not have a newline on
281        the end, a newline was missing in the output.
282    
283    19. The default pcre_chartables.c file recognizes only ASCII characters (values
284        less than 128) in its various bitmaps. However, there is a facility for
285        generating tables according to the current locale when PCRE is compiled. It
286        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
287        characters, are recognized by isspace() and therefore were getting set in
288        these tables, and indeed these tables seem to approximate to ISO 8859. This
289        caused a problem in UTF-8 mode when pcre_study() was used to create a list
290        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
291        which of course cannot start UTF-8 characters. I have changed the code so
292        that only real ASCII characters (less than 128) and the correct starting
293        bytes for UTF-8 encodings are set for characters greater than 127 when in
294        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
295        altogether.)
296    
297    20. Added the /T option to pcretest so as to be able to run tests with non-
298        standard character tables, thus making it possible to include the tests
299        used for 19 above in the standard set of tests.
300    
301    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
302        reference to a subpattern the other side of a comment that contains an
303        opening parenthesis caused either an internal compiling error, or a
304        reference to the wrong subpattern.
305    
306    
307  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Legend:
Removed from v.528  
changed lines
  Added in v.600

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12