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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.505  
changed lines
  Added in v.588

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12