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

Diff of /code/trunk/ChangeLog

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

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