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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.269  
changed lines
  Added in v.313

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12