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

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

  ViewVC Help
Powered by ViewVC 1.1.5