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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.267  
changed lines
  Added in v.304

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12