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

Diff of /code/trunk/ChangeLog

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

revision 535 by ph10, Thu Jun 3 19:18:24 2010 UTC revision 585 by ph10, Wed Jan 12 17:21:11 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.10 03-Jun-2010  Version 8.12 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 crash. (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    
21    Version 8.11 10-Dec-2010
22    ------------------------
23    
24    1.  (*THEN) was not working properly if there were untried alternatives prior
25        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
26        backtracked to try for "b" instead of moving to the next alternative branch
27        at the same level (in this case, to look for "c"). The Perl documentation
28        is clear that when (*THEN) is backtracked onto, it goes to the "next
29        alternative in the innermost enclosing group".
30    
31    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
32        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
33        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
34        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
35        (*THEN).
36    
37    3.  If \s appeared in a character class, it removed the VT character from
38        the class, even if it had been included by some previous item, for example
39        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
40        of \s, but is part of the POSIX "space" class.)
41    
42    4.  A partial match never returns an empty string (because you can always
43        match an empty string at the end of the subject); however the checking for
44        an empty string was starting at the "start of match" point. This has been
45        changed to the "earliest inspected character" point, because the returned
46        data for a partial match starts at this character. This means that, for
47        example, /(?<=abc)def/ gives a partial match for the subject "abc"
48        (previously it gave "no match").
49    
50    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
51        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
52        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
53        has an implication that the given string is incomplete (because a partial
54        match is preferred over a full match). For this reason, these items now
55        give a partial match in this situation. [Aside: previously, the one case
56        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
57        match rather than a full match, which was wrong by the old rules, but is
58        now correct.]
59    
60    6.  There was a bug in the handling of #-introduced comments, recognized when
61        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
62        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
63        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
64        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
65        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
66        places in pcre_compile().
67    
68    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
69        comments when looking ahead for named forward references to subpatterns,
70        the only newline sequence it recognized was NL. It now handles newlines
71        according to the set newline convention.
72    
73    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
74        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
75        cater for a lack of strerror(). These oversights have been fixed.
76    
77    9.  Added --match-limit and --recursion-limit to pcregrep.
78    
79    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
80    
81    11. When the -o option was used, pcregrep was setting a return code of 1, even
82        when matches were found, and --line-buffered was not being honoured.
83    
84    12. Added an optional parentheses number to the -o and --only-matching options
85        of pcregrep.
86    
87    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
88        can match an empty string. The code to do it in pcretest and pcredemo
89        needed fixing:
90    
91        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
92            only one byte after an empty string match just before CRLF (this case
93            just got forgotten; "any" and "anycrlf" were OK).
94    
95        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
96            mode when an empty string match preceded an ASCII character followed by
97            a non-ASCII character. (The code for advancing by one character rather
98            than one byte was nonsense.)
99    
100        (c) The pcredemo.c sample program did not have any code at all to handle
101            the cases when CRLF is a valid newline sequence.
102    
103    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
104        as a starting offset was within the subject string. There is now a new
105        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
106        negative or greater than the length of the string. In order to test this,
107        pcretest is extended to allow the setting of negative starting offsets.
108    
109    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
110        starting offset points to the beginning of a UTF-8 character was
111        unnecessarily clumsy. I tidied it up.
112    
113    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
114        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
115    
116    17. Nobody had reported that the --include_dir option, which was added in
117        release 7.7 should have been called --include-dir (hyphen, not underscore)
118        for compatibility with GNU grep. I have changed it to --include-dir, but
119        left --include_dir as an undocumented synonym, and the same for
120        --exclude-dir, though that is not available in GNU grep, at least as of
121        release 2.5.4.
122    
123    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
124        characters from a string of bytes) have been redefined so as not to use
125        loops, in order to improve performance in some environments. At the same
126        time, I abstracted some of the common code into auxiliary macros to save
127        repetition (this should not affect the compiled code).
128    
129    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
130        compile-time error is now given if \c is not followed by an ASCII
131        character, that is, a byte less than 128. (In EBCDIC mode, the code is
132        different, and any byte value is allowed.)
133    
134    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
135        START_OPTIMIZE option, which is now allowed at compile time - but just
136        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
137        to pcregrep and other applications that have no direct access to PCRE
138        options. The new /Y option in pcretest sets this option when calling
139        pcre_compile().
140    
141    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
142        back references. Groups containing recursive back references were forced to
143        be atomic by that change, but in the case of named groups, the amount of
144        memory required was incorrectly computed, leading to "Failed: internal
145        error: code overflow". This has been fixed.
146    
147    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
148        pcretest.c, to avoid build problems in some Borland environments.
149    
150    
151    Version 8.10 25-Jun-2010
152  ------------------------  ------------------------
153    
154  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 42  Version 8.10 03-Jun-2010 Line 189  Version 8.10 03-Jun-2010
189  11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was  11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
190      studied, and the match started with a letter with a code point greater than      studied, and the match started with a letter with a code point greater than
191      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
192      the letter, the other case of this starting letter was not recognized.      the letter, the other case of this starting letter was not recognized
193        (#976).
194    
195  12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a  12. If a pattern that was studied started with a repeated Unicode property
     conflict in the definition of PCRE_EXP_DECL. I have removed the include of  
     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  
196      test, for example, \p{Nd}+, there was the theoretical possibility of      test, for example, \p{Nd}+, there was the theoretical possibility of
197      setting up an incorrect bitmap of starting bytes, but fortunately it could      setting up an incorrect bitmap of starting bytes, but fortunately it could
198      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
199      added property types that matched character-matching opcodes).      added property types that matched character-matching opcodes).
200    
201  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
202      possible starting bytes for non-anchored patterns.      possible starting bytes for non-anchored patterns.
203    
204  15. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes  14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
205      \R, and also a number of cases that involve Unicode properties, both      \R, and also a number of cases that involve Unicode properties, both
206      explicit and implicit when PCRE_UCP is set.      explicit and implicit when PCRE_UCP is set.
207    
208  16. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8  15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
209      input, it could crash or give wrong results if characters with values      input, it could crash or give wrong results if characters with values
210      greater than 0xc0 were present in the subject string. (Detail: it assumed      greater than 0xc0 were present in the subject string. (Detail: it assumed
211      UTF-8 input when processing these items.)      UTF-8 input when processing these items.)
212    
213  17. Added a lot of (int) casts to avoid compiler warnings in systems where  16. Added a lot of (int) casts to avoid compiler warnings in systems where
214      size_t is 64-bit.      size_t is 64-bit (#991).
215    
216    17. Added a check for running out of memory when PCRE is compiled with
217        --disable-stack-for-recursion (#990).
218    
219    18. If the last data line in a file for pcretest does not have a newline on
220        the end, a newline was missing in the output.
221    
222  18. Added a check for running out of memory when PCRE is compiled with  19. The default pcre_chartables.c file recognizes only ASCII characters (values
223      --disable-stack-for-recursion.      less than 128) in its various bitmaps. However, there is a facility for
224        generating tables according to the current locale when PCRE is compiled. It
225        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
226        characters, are recognized by isspace() and therefore were getting set in
227        these tables, and indeed these tables seem to approximate to ISO 8859. This
228        caused a problem in UTF-8 mode when pcre_study() was used to create a list
229        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
230        which of course cannot start UTF-8 characters. I have changed the code so
231        that only real ASCII characters (less than 128) and the correct starting
232        bytes for UTF-8 encodings are set for characters greater than 127 when in
233        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
234        altogether.)
235    
236    20. Added the /T option to pcretest so as to be able to run tests with non-
237        standard character tables, thus making it possible to include the tests
238        used for 19 above in the standard set of tests.
239    
240    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
241        reference to a subpattern the other side of a comment that contains an
242        opening parenthesis caused either an internal compiling error, or a
243        reference to the wrong subpattern.
244    
245    
246  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Legend:
Removed from v.535  
changed lines
  Added in v.585

  ViewVC Help
Powered by ViewVC 1.1.5