ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.265  
changed lines
  Added in v.302

  ViewVC Help
Powered by ViewVC 1.1.5