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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.528  
changed lines
  Added in v.592

  ViewVC Help
Powered by ViewVC 1.1.5