ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 491 by ph10, Mon Mar 1 17:45:08 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  ------------------  ------------------
4  Version 8.02 01-Mar-2010  Version 8.13 30-Apr-2011
5    ------------------------
7    1.  The Unicode data tables have been updated to Unicode 6.0.0.
9    2.  Two minor typos in pcre_internal.h have been fixed.
12    Version 8.12 15-Jan-2011
13    ------------------------
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.
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.)
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.
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.
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.
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).
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.
46    Version 8.11 10-Dec-2010
47    ------------------------
49    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
51        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
53        is clear that when (*THEN) is backtracked onto, it goes to the "next
54        alternative in the innermost enclosing group".
56    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
58        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
59        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
60        (*THEN).
62    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
64        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.)
67    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
69        an empty string was starting at the "start of match" point. This has been
70        changed to the "earliest inspected character" point, because the returned
71        data for a partial match starts at this character. This means that, for
72        example, /(?<=abc)def/ gives a partial match for the subject "abc"
73        (previously it gave "no match").
75    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,
77        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
79        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
81        /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
83        now correct.]
85    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.
87        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
89        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
91        places in pcre_compile().
93    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
94        comments when looking ahead for named forward references to subpatterns,
95        the only newline sequence it recognized was NL. It now handles newlines
96        according to the set newline convention.
98    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
99        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
100        cater for a lack of strerror(). These oversights have been fixed.
102    9.  Added --match-limit and --recursion-limit to pcregrep.
104    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
106    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.
109    12. Added an optional parentheses number to the -o and --only-matching options
110        of pcregrep.
112    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
114        needed fixing:
116        (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
118            just got forgotten; "any" and "anycrlf" were OK).
120        (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
122            a non-ASCII character. (The code for advancing by one character rather
123            than one byte was nonsense.)
125        (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.
128    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
130        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,
132        pcretest is extended to allow the setting of negative starting offsets.
134    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
136        unnecessarily clumsy. I tidied it up.
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.
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.
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).
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.)
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().
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.
172    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
173        pcretest.c, to avoid build problems in some Borland environments.
176    Version 8.10 25-Jun-2010
177    ------------------------
179    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
180        THEN.
182    2.  (*ACCEPT) was not working when inside an atomic group.
184    3.  Inside a character class, \B is treated as a literal by default, but
185        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
186        causes the error). The code is unchanged, but I tidied the documentation.
188    4.  Inside a character class, PCRE always treated \R and \X as literals,
189        whereas Perl faults them if its -w option is set. I have changed PCRE so
190        that it faults them when PCRE_EXTRA is set.
192    5.  Added support for \N, which always matches any character other than
193        newline. (It is the same as "." when PCRE_DOTALL is not set.)
195    6.  When compiling pcregrep with newer versions of gcc which may have
196        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
197        declared with attribute warn_unused_result" were given. Just casting the
198        result to (void) does not stop the warnings; a more elaborate fudge is
199        needed. I've used a macro to implement this.
201    7.  Minor change to pcretest.c to avoid a compiler warning.
203    8.  Added four artifical Unicode properties to help with an option to make
204        \s etc use properties (see next item). The new properties are: Xan
205        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
207    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
208        use Unicode properties. (*UCP) at the start of a pattern can be used to set
209        this option. Modified pcretest to add /W to test this facility. Added
210        REG_UCP to make it available via the POSIX interface.
212    10. Added --line-buffered to pcregrep.
214    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
215        studied, and the match started with a letter with a code point greater than
216        127 whose first byte was different to the first byte of the other case of
217        the letter, the other case of this starting letter was not recognized
218        (#976).
220    12. If a pattern that was studied started with a repeated Unicode property
221        test, for example, \p{Nd}+, there was the theoretical possibility of
222        setting up an incorrect bitmap of starting bytes, but fortunately it could
223        not have actually happened in practice until change 8 above was made (it
224        added property types that matched character-matching opcodes).
226    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
227        possible starting bytes for non-anchored patterns.
229    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
230        \R, and also a number of cases that involve Unicode properties, both
231        explicit and implicit when PCRE_UCP is set.
233    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
234        input, it could crash or give wrong results if characters with values
235        greater than 0xc0 were present in the subject string. (Detail: it assumed
236        UTF-8 input when processing these items.)
238    16. Added a lot of (int) casts to avoid compiler warnings in systems where
239        size_t is 64-bit (#991).
241    17. Added a check for running out of memory when PCRE is compiled with
242        --disable-stack-for-recursion (#990).
244    18. If the last data line in a file for pcretest does not have a newline on
245        the end, a newline was missing in the output.
247    19. The default pcre_chartables.c file recognizes only ASCII characters (values
248        less than 128) in its various bitmaps. However, there is a facility for
249        generating tables according to the current locale when PCRE is compiled. It
250        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
251        characters, are recognized by isspace() and therefore were getting set in
252        these tables, and indeed these tables seem to approximate to ISO 8859. This
253        caused a problem in UTF-8 mode when pcre_study() was used to create a list
254        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
255        which of course cannot start UTF-8 characters. I have changed the code so
256        that only real ASCII characters (less than 128) and the correct starting
257        bytes for UTF-8 encodings are set for characters greater than 127 when in
258        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
259        altogether.)
261    20. Added the /T option to pcretest so as to be able to run tests with non-
262        standard character tables, thus making it possible to include the tests
263        used for 19 above in the standard set of tests.
265    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
266        reference to a subpattern the other side of a comment that contains an
267        opening parenthesis caused either an internal compiling error, or a
268        reference to the wrong subpattern.
271    Version 8.02 19-Mar-2010
272  ------------------------  ------------------------
274  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.
276    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
277        configured.
279    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
280        original author of that file, following a query about its status.
282    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
283        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
285    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
286        quantifier applied to a forward-referencing subroutine call, could compile
287        incorrect code or give the error "internal error: previously-checked
288        referenced subpattern not found".
290    6.  Both MS Visual Studio and Symbian OS have problems with initializing
291        variables to point to external functions. For these systems, therefore,
292        pcre_malloc etc. are now initialized to local functions that call the
293        relevant global functions.
295    7.  There were two entries missing in the vectors called coptable and poptable
296        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
297        I've fixed the data, and added a kludgy way of testing at compile time that
298        the lengths are correct (equal to the number of opcodes).
300    8.  Following on from 7, I added a similar kludge to check the length of the
301        eint vector in pcreposix.c.
303    9.  Error texts for pcre_compile() are held as one long string to avoid too
304        much relocation at load time. To find a text, the string is searched,
305        counting zeros. There was no check for running off the end of the string,
306        which could happen if a new error number was added without updating the
307        string.
309    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
311    11. \K was not working if it appeared in an atomic group or in a group that
312        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
313        \K is "not well defined" if used in an assertion. PCRE now accepts it if
314        the assertion is positive, but not if it is negative.
316    12. Change 11 fortuitously reduced the size of the stack frame used in the
317        "match()" function of pcre_exec.c by one pointer. Forthcoming
318        implementation of support for (*MARK) will need an extra pointer on the
319        stack; I have reserved it now, so that the stack frame size does not
320        decrease.
322    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
323        item in branch that calls a recursion is a subroutine call - as in the
324        second branch in the above example - was incorrectly given the compile-
325        time error "recursive call could loop indefinitely" because pcre_compile()
326        was not correctly checking the subroutine for matching a non-empty string.
328    14. The checks for overrunning compiling workspace could trigger after an
329        overrun had occurred. This is a "should never occur" error, but it can be
330        triggered by pathological patterns such as hundreds of nested parentheses.
331        The checks now trigger 100 bytes before the end of the workspace.
333    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
336  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
337  ------------------------  ------------------------

Removed from v.491  
changed lines
  Added in v.593

  ViewVC Help
Powered by ViewVC 1.1.5