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

Diff of /code/trunk/ChangeLog

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

revision 210 by ph10, Wed Aug 8 14:24:50 2007 UTC revision 298 by ph10, Thu Jan 10 17:09:12 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-07  Version 7.5 10-Jan-08
5    ---------------------
6    
7    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
8        values in parens when parsing an RE using the C++ wrapper."
9    
10    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
11        Characters greater than 255 were excluded from the class instead of being
12        included.
13    
14    3.  The same bug as (2) above applied to negated POSIX classes such as
15        [:^space:].
16    
17    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
18        defined or documented. It seems to have been a typo for PCRE_STATIC, so
19        I have changed it.
20    
21    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
22        first named subpattern) and a construct such as (?&a) would reference the
23        first named subpattern whose name started with "a" (in other words, the
24        length check was missing). Both these problems are fixed. "Subpattern name
25        expected" is now given for (?&) (a zero-length name), and this patch also
26        makes it give the same error for \k'' (previously it complained that that
27        was a reference to a non-existent subpattern).
28    
29    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
30        this is right because (?- can be followed by option settings as well as by
31        digits. I have, however, made the messages clearer.
32    
33    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
34        than the number used in the conditional) now cause a compile-time error.
35        This is actually not compatible with Perl, which accepts such patterns, but
36        treats the conditional as always being FALSE (as PCRE used to), but it
37        seems to me that giving a diagnostic is better.
38    
39    8.  Change "alphameric" to the more common word "alphanumeric" in comments
40        and messages.
41    
42    9.  Fix two occurrences of "backslash" in comments that should have been
43        "backspace".
44    
45    10. Remove two redundant lines of code that can never be obeyed (their function
46        was moved elsewhere).
47    
48    11. The program that makes PCRE's Unicode character property table had a bug
49        which caused it to generate incorrect table entries for sequences of
50        characters that have the same character type, but are in different scripts.
51        It amalgamated them into a single range, with the script of the first of
52        them. In other words, some characters were in the wrong script. There were
53        thirteen such cases, affecting characters in the following ranges:
54    
55          U+002b0 - U+002c1
56          U+0060c - U+0060d
57          U+0061e - U+00612
58          U+0064b - U+0065e
59          U+0074d - U+0076d
60          U+01800 - U+01805
61          U+01d00 - U+01d77
62          U+01d9b - U+01dbf
63          U+0200b - U+0200f
64          U+030fc - U+030fe
65          U+03260 - U+0327f
66          U+0fb46 - U+0fbb1
67          U+10450 - U+1049d
68    
69    12. The -o option (show only the matching part of a line) for pcregrep was not
70        compatible with GNU grep in that, if there was more than one match in a
71        line, it showed only the first of them. It now behaves in the same way as
72        GNU grep.
73    
74    13. If the -o and -v options were combined for pcregrep, it printed a blank
75        line for every non-matching line. GNU grep prints nothing, and pcregrep now
76        does the same. The return code can be used to tell if there were any
77        non-matching lines.
78    
79    14. Added --file-offsets and --line-offsets to pcregrep.
80    
81    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
82        infinitely looping recursion. The bug was that positive lookaheads were not
83        being skipped when checking for a possible empty match (negative lookaheads
84        and both kinds of lookbehind were skipped).
85    
86    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
87        inclusion of <windows.h> to before rather than after the definition of
88        INVALID_FILE_ATTRIBUTES (patch from David Byron).
89    
90    17. Specifying a possessive quantifier with a specific limit for a Unicode
91        character property caused pcre_compile() to compile bad code, which led at
92        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
93        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
94        caused the error; without that there was no problem.
95    
96    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
97    
98    19. Added --enable-pcretest-libreadline.
99    
100    20. In pcrecpp.cc, the variable 'count' was incremented twice in
101        RE::GlobalReplace(). As a result, the number of replacements returned was
102        double what it should be. I removed one of the increments, but Craig sent a
103        later patch that removed the other one (the right fix) and added unit tests
104        that check the return values (which was not done before).
105    
106    21. Several CMake things:
107    
108        (1) Arranged that, when cmake is used on Unix, the libraries end up with
109            the names libpcre and libpcreposix, not just pcre and pcreposix.
110    
111        (2) The above change means that pcretest and pcregrep are now correctly
112            linked with the newly-built libraries, not previously installed ones.
113    
114        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
115    
116    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
117        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
118        UTF-8 newline character). The key issue is that the pattern starts .*;
119        this means that the match must be either at the beginning, or after a
120        newline. The bug was in the code for advancing after a failed match and
121        checking that the new position followed a newline. It was not taking
122        account of UTF-8 characters correctly.
123    
124    23. PCRE was behaving differently from Perl in the way it recognized POSIX
125        character classes. PCRE was not treating the sequence [:...:] as a
126        character class unless the ... were all letters. Perl, however, seems to
127        allow any characters between [: and :], though of course it rejects as
128        unknown any "names" that contain non-letters, because all the known class
129        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
130        for example, whereas PCRE did not - it did not recognize a POSIX character
131        class. This seemed a bit dangerous, so the code has been changed to be
132        closer to Perl. The behaviour is not identical to Perl, because PCRE will
133        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
134        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
135        Perl does, and where it didn't before.
136    
137    24. Rewrite so as to remove the single use of %n from pcregrep because in some
138        Windows environments %n is disabled by default.
139    
140    
141    Version 7.4 21-Sep-07
142    ---------------------
143    
144    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
145        means that a class such as [\s] counted as "explicit reference to CR or
146        LF". That isn't really right - the whole point of the change was to try to
147        help when there was an actual mention of one of the two characters. So now
148        the change happens only if \r or \n (or a literal CR or LF) character is
149        encountered.
150    
151    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
152        of both had grown to the point where there were only 3 bits left.
153        Fortunately, there was spare space in the data structure, and so I have
154        moved the internal flags into a new 16-bit field to free up more option
155        bits.
156    
157    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
158        but did not set the internal JCHANGED flag - either of these is enough to
159        control the way the "get" function works - but the PCRE_INFO_JCHANGED
160        facility is supposed to tell if (?J) was ever used, so now (?J) at the
161        start sets both bits.
162    
163    4.  Added options (at build time, compile time, exec time) to change \R from
164        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
165    
166    5.  doc/pcresyntax.html was missing from the distribution.
167    
168    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
169        compatibility, even though it is no longer used.
170    
171    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
172        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
173        windows.h file is present (where different names are used). [This was
174        reversed later after testing - see 16 below.]
175    
176    8.  Changed all #include <config.h> to #include "config.h". There were also
177        some further <pcre.h> cases that I changed to "pcre.h".
178    
179    9.  When pcregrep was used with the --colour option, it missed the line ending
180        sequence off the lines that it output.
181    
182    10. It was pointed out to me that arrays of string pointers cause lots of
183        relocations when a shared library is dynamically loaded. A technique of
184        using a single long string with a table of offsets can drastically reduce
185        these. I have refactored PCRE in four places to do this. The result is
186        dramatic:
187    
188          Originally:                          290
189          After changing UCP table:            187
190          After changing error message table:   43
191          After changing table of "verbs"       36
192          After changing table of Posix names   22
193    
194        Thanks to the folks working on Gregex for glib for this insight.
195    
196    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
197        unicode-properties was also set.
198    
199    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
200    
201    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
202        checked only for CRLF.
203    
204    14. Added casts to pcretest.c to avoid compiler warnings.
205    
206    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
207    
208    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
209        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
210        entirely. This removes changes made in 7 above.
211    
212    17. The CMake files have been updated, and there is now more information about
213        building with CMake in the NON-UNIX-USE document.
214    
215    
216    Version 7.3 28-Aug-07
217  ---------------------  ---------------------
218    
219   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 87  Version 7.3 05-Jul-07 Line 299  Version 7.3 05-Jul-07
299  12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack  12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
300      past the start of the subject in the presence of bytes with the top bit      past the start of the subject in the presence of bytes with the top bit
301      set, for example "\x8aBCD".      set, for example "\x8aBCD".
302    
303  13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),  13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
304      (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).      (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
305    
306  14. Optimized (?!) to (*FAIL).  14. Optimized (?!) to (*FAIL).
307    
308    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
309        This restricts code points to be within the range 0 to 0x10FFFF, excluding
310        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
311        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
312        does: it's just the validity check that is more restrictive.
313    
314    16. Inserted checks for integer overflows during escape sequence (backslash)
315        processing, and also fixed erroneous offset values for syntax errors during
316        backslash processing.
317    
318    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
319        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
320    
321    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
322        caused an overrun.
323    
324    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
325        something other than just ASCII characters) inside a group that had an
326        unlimited repeat caused a loop at compile time (while checking to see
327        whether the group could match an empty string).
328    
329    20. Debugging a pattern containing \p or \P could cause a crash. For example,
330        [\P{Any}] did so. (Error in the code for printing property names.)
331    
332    21. An orphan \E inside a character class could cause a crash.
333    
334    22. A repeated capturing bracket such as (A)? could cause a wild memory
335        reference during compilation.
336    
337    23. There are several functions in pcre_compile() that scan along a compiled
338        expression for various reasons (e.g. to see if it's fixed length for look
339        behind). There were bugs in these functions when a repeated \p or \P was
340        present in the pattern. These operators have additional parameters compared
341        with \d, etc, and these were not being taken into account when moving along
342        the compiled data. Specifically:
343    
344        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
345            length.
346    
347        (b) An item such as \pL+ within a repeated group could cause crashes or
348            loops.
349    
350        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
351            "reference to non-existent subpattern" error.
352    
353        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
354    
355    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
356        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
357    
358    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
359    
360    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
361        character were causing crashes (broken optimization).
362    
363    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
364        \p or \P) caused a compile-time loop.
365    
366    28. More problems have arisen in unanchored patterns when CRLF is a valid line
367        break. For example, the unstudied pattern [\r\n]A does not match the string
368        "\r\nA" because change 7.0/46 below moves the current point on by two
369        characters after failing to match at the start. However, the pattern \nA
370        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
371        the same is true. There doesn't seem any very clean way out of this, but
372        what I have chosen to do makes the common cases work: PCRE now takes note
373        of whether there can be an explicit match for \r or \n anywhere in the
374        pattern, and if so, 7.0/46 no longer applies. As part of this change,
375        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
376        pattern has explicit CR or LF references.
377    
378    29. Added (*CR) etc for changing newline setting at start of pattern.
379    
380    
381  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Legend:
Removed from v.210  
changed lines
  Added in v.298

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12