ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.261  
changed lines
  Added in v.303

  ViewVC Help
Powered by ViewVC 1.1.5