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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.264  
changed lines
  Added in v.327

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12