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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.515  
changed lines
  Added in v.598

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12