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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.268  
changed lines
  Added in v.322

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12