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

Diff of /code/trunk/ChangeLog

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

revision 264 by ph10, Tue Nov 13 11:07:16 2007 UTC revision 300 by ph10, Mon Jan 14 19:43:19 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 12-Nov-07  Version 7.6 14-Jan-08
5    ---------------------
6    
7    1.  A class with a very large number of characters with codepoints greater
8        than 255 (in UTF-8 mode, of course), caused a buffer overflow.
9    
10    
11    Version 7.5 10-Jan-08
12  ---------------------  ---------------------
13    
14  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
15      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
16    
17  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
18      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
19      included.      included.
20    
21    3.  The same bug as (2) above applied to negated POSIX classes such as
22        [:^space:].
23    
24    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
25        defined or documented. It seems to have been a typo for PCRE_STATIC, so
26        I have changed it.
27    
28    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
29        first named subpattern) and a construct such as (?&a) would reference the
30        first named subpattern whose name started with "a" (in other words, the
31        length check was missing). Both these problems are fixed. "Subpattern name
32        expected" is now given for (?&) (a zero-length name), and this patch also
33        makes it give the same error for \k'' (previously it complained that that
34        was a reference to a non-existent subpattern).
35    
36    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
37        this is right because (?- can be followed by option settings as well as by
38        digits. I have, however, made the messages clearer.
39    
40    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
41        than the number used in the conditional) now cause a compile-time error.
42        This is actually not compatible with Perl, which accepts such patterns, but
43        treats the conditional as always being FALSE (as PCRE used to), but it
44        seems to me that giving a diagnostic is better.
45    
46    8.  Change "alphameric" to the more common word "alphanumeric" in comments
47        and messages.
48    
49    9.  Fix two occurrences of "backslash" in comments that should have been
50        "backspace".
51    
52    10. Remove two redundant lines of code that can never be obeyed (their function
53        was moved elsewhere).
54    
55    11. The program that makes PCRE's Unicode character property table had a bug
56        which caused it to generate incorrect table entries for sequences of
57        characters that have the same character type, but are in different scripts.
58        It amalgamated them into a single range, with the script of the first of
59        them. In other words, some characters were in the wrong script. There were
60        thirteen such cases, affecting characters in the following ranges:
61    
62          U+002b0 - U+002c1
63          U+0060c - U+0060d
64          U+0061e - U+00612
65          U+0064b - U+0065e
66          U+0074d - U+0076d
67          U+01800 - U+01805
68          U+01d00 - U+01d77
69          U+01d9b - U+01dbf
70          U+0200b - U+0200f
71          U+030fc - U+030fe
72          U+03260 - U+0327f
73          U+0fb46 - U+0fbb1
74          U+10450 - U+1049d
75    
76    12. The -o option (show only the matching part of a line) for pcregrep was not
77        compatible with GNU grep in that, if there was more than one match in a
78        line, it showed only the first of them. It now behaves in the same way as
79        GNU grep.
80    
81    13. If the -o and -v options were combined for pcregrep, it printed a blank
82        line for every non-matching line. GNU grep prints nothing, and pcregrep now
83        does the same. The return code can be used to tell if there were any
84        non-matching lines.
85    
86    14. Added --file-offsets and --line-offsets to pcregrep.
87    
88    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
89        infinitely looping recursion. The bug was that positive lookaheads were not
90        being skipped when checking for a possible empty match (negative lookaheads
91        and both kinds of lookbehind were skipped).
92    
93    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
94        inclusion of <windows.h> to before rather than after the definition of
95        INVALID_FILE_ATTRIBUTES (patch from David Byron).
96    
97    17. Specifying a possessive quantifier with a specific limit for a Unicode
98        character property caused pcre_compile() to compile bad code, which led at
99        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
100        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
101        caused the error; without that there was no problem.
102    
103    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
104    
105    19. Added --enable-pcretest-libreadline.
106    
107    20. In pcrecpp.cc, the variable 'count' was incremented twice in
108        RE::GlobalReplace(). As a result, the number of replacements returned was
109        double what it should be. I removed one of the increments, but Craig sent a
110        later patch that removed the other one (the right fix) and added unit tests
111        that check the return values (which was not done before).
112    
113    21. Several CMake things:
114    
115        (1) Arranged that, when cmake is used on Unix, the libraries end up with
116            the names libpcre and libpcreposix, not just pcre and pcreposix.
117    
118        (2) The above change means that pcretest and pcregrep are now correctly
119            linked with the newly-built libraries, not previously installed ones.
120    
121        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
122    
123    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
124        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
125        UTF-8 newline character). The key issue is that the pattern starts .*;
126        this means that the match must be either at the beginning, or after a
127        newline. The bug was in the code for advancing after a failed match and
128        checking that the new position followed a newline. It was not taking
129        account of UTF-8 characters correctly.
130    
131    23. PCRE was behaving differently from Perl in the way it recognized POSIX
132        character classes. PCRE was not treating the sequence [:...:] as a
133        character class unless the ... were all letters. Perl, however, seems to
134        allow any characters between [: and :], though of course it rejects as
135        unknown any "names" that contain non-letters, because all the known class
136        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
137        for example, whereas PCRE did not - it did not recognize a POSIX character
138        class. This seemed a bit dangerous, so the code has been changed to be
139        closer to Perl. The behaviour is not identical to Perl, because PCRE will
140        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
141        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
142        Perl does, and where it didn't before.
143    
144    24. Rewrite so as to remove the single use of %n from pcregrep because in some
145        Windows environments %n is disabled by default.
146    
147    
148  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07
149  ---------------------  ---------------------

Legend:
Removed from v.264  
changed lines
  Added in v.300

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12