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

Diff of /code/trunk/ChangeLog

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

revision 295 by ph10, Mon Dec 31 17:00:24 2007 UTC revision 369 by ph10, Sun Aug 24 16:53:47 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 31-Dec-07  Version 7.8 25-Aug-08
5    ---------------------
6    
7    1.  Replaced UCP searching code with optimized version as implemented for Ad
8        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
9        stage table and inline lookup instead of a function, giving speed ups of 2
10        to 5 times on some simple patterns that I tested. Permission was given to
11        distribute the MultiStage2.py script that generates the tables (it's not in
12        the tarball, but is in the Subversion repository).
13    
14    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
15        scripts.
16    
17    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
18        a group with a zero qualifier. The result of the study could be incorrect,
19        or the function might crash, depending on the pattern.
20    
21    4.  Caseless matching was not working for non-ASCII characters in back
22        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
23        It now works when Unicode Property Support is available.
24    
25    5.  In pcretest, an escape such as \x{de} in the data was always generating
26        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
27        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
28        truncation.
29    
30    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
31    
32    7.  Added two (int) casts to pcregrep when printing the difference of two
33        pointers, in case they are 64-bit values.
34    
35    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
36        test 2 if it fails.
37    
38    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
39        and a #define of that name to empty if it is not externally set. This is to
40        allow users of MSVC to set it if necessary.
41    
42    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
43        the convenience functions in the pcre_get.c source file.
44    
45    11. An option change at the start of a pattern that had top-level alternatives
46        could cause overwriting and/or a crash. This command provoked a crash in
47        some environments:
48    
49          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
50    
51        This potential security problem was recorded as CVE-2008-2371.
52    
53    12. For a pattern where the match had to start at the beginning or immediately
54        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
55        pcre_dfa_exec() could read past the end of the passed subject if there was
56        no match. To help with detecting such bugs (e.g. with valgrind), I modified
57        pcretest so that it places the subject at the end of its malloc-ed buffer.
58    
59    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
60        exec() might read past the end of the data buffer in UTF-8 mode.
61    
62    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
63        the data contained the byte 0x85 as part of a UTF-8 character within its
64        first line. This applied both to normal and DFA matching.
65    
66    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
67        /^[^d]*?$/8 failed to match "abc".
68    
69    16. Added a missing copyright notice to pcrecpp_internal.h.
70    
71    17. Make it more clear in the documentation that values returned from
72        pcre_exec() in ovector are byte offsets, not character counts.
73    
74    18. Tidied a few places to stop certain compilers from issuing warnings.
75    
76    
77    Version 7.7 07-May-08
78    ---------------------
79    
80    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
81        a string to a long long, pretend we don't even have a long long." This is
82        done by checking for the strtoq, strtoll, and _strtoi64 functions.
83    
84    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
85        pre-7.6 versions, which defined a global no_arg variable instead of putting
86        it in the RE class. (See also #8 below.)
87    
88    3.  Remove a line of dead code, identified by coverity and reported by Nuno
89        Lopes.
90    
91    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
92    
93        (1) The include/exclude patterns were being applied to the whole pathnames
94            of files, instead of just to the final components.
95    
96        (2) If there was more than one level of directory, the subdirectories were
97            skipped unless they satisfied the include/exclude conditions. This is
98            inconsistent with GNU grep (and could even be seen as contrary to the
99            pcregrep specification - which I improved to make it absolutely clear).
100            The action now is always to scan all levels of directory, and just
101            apply the include/exclude patterns to regular files.
102    
103    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
104        --exclude_dir in the tests to avoid scanning .svn directories.
105    
106    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
107        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
108        doesn't support NULs in patterns.
109    
110    7.  Added some missing "const"s to declarations of static tables in
111        pcre_compile.c and pcre_dfa_exec.c.
112    
113    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
114        caused by fix #2  above. (Subsequently also a second patch to fix the
115        first patch. And a third patch - this was a messy problem.)
116    
117    9.  Applied Craig's patch to remove the use of push_back().
118    
119    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
120        matching function regexec().
121    
122    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
123        which, however, unlike Perl's \g{...}, are subroutine calls, not back
124        references. PCRE supports relative numbers with this syntax (I don't think
125        Oniguruma does).
126    
127    12. Previously, a group with a zero repeat such as (...){0} was completely
128        omitted from the compiled regex. However, this means that if the group
129        was called as a subroutine from elsewhere in the pattern, things went wrong
130        (an internal error was given). Such groups are now left in the compiled
131        pattern, with a new opcode that causes them to be skipped at execution
132        time.
133    
134    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
135        to the way PCRE behaves:
136    
137        (a) A lone ] character is dis-allowed (Perl treats it as data).
138    
139        (b) A back reference to an unmatched subpattern matches an empty string
140            (Perl fails the current match path).
141    
142        (c) A data ] in a character class must be notated as \] because if the
143            first data character in a class is ], it defines an empty class. (In
144            Perl it is not possible to have an empty class.) The empty class []
145            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
146            The negative empty class [^] matches any one character, independently
147            of the DOTALL setting.
148    
149    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
150        non-existent subpattern following a character class starting with ']' and
151        containing () gave an internal compiling error instead of "reference to
152        non-existent subpattern". Fortunately, when the pattern did exist, the
153        compiled code was correct. (When scanning forwards to check for the
154        existencd of the subpattern, it was treating the data ']' as terminating
155        the class, so got the count wrong. When actually compiling, the reference
156        was subsequently set up correctly.)
157    
158    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
159        it was being rejected as not supported by pcre_dfa_exec(), even though
160        other assertions are supported. I have made pcre_dfa_exec() support
161        (*FAIL).
162    
163    16. The implementation of 13c above involved the invention of a new opcode,
164        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
165        cannot be changed at match time, I realized I could make a small
166        improvement to matching performance by compiling OP_ALLANY instead of
167        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
168        on the OP_ANY path.
169    
170    17. Compiling pcretest on Windows with readline support failed without the
171        following two fixes: (1) Make the unistd.h include conditional on
172        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
173    
174    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
175        ncurses library to be included for pcretest when ReadLine support is
176        requested, but also to allow for it to be overridden. This patch came from
177        Daniel Bergström.
178    
179    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
180        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
181        any errors with the current Unicode tables. Thanks to Peter Kankowski for
182        spotting this.
183    
184    
185    Version 7.6 28-Jan-08
186    ---------------------
187    
188    1.  A character class containing a very large number of characters with
189        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
190        overflow.
191    
192    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
193        HAVE_LONG_LONG is not defined.
194    
195    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
196        bring them up to date and include new features. This patch includes:
197    
198        - Fixed PH's badly added libz and libbz2 support.
199        - Fixed a problem with static linking.
200        - Added pcredemo. [But later removed - see 7 below.]
201        - Fixed dftables problem and added an option.
202        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
203            HAVE_LONG_LONG.
204        - Added readline support for pcretest.
205        - Added an listing of the option settings after cmake has run.
206    
207    4.  A user submitted a patch to Makefile that makes it easy to create
208        "pcre.dll" under mingw when using Configure/Make. I added stuff to
209        Makefile.am that cause it to include this special target, without
210        affecting anything else. Note that the same mingw target plus all
211        the other distribution libraries and programs are now supported
212        when configuring with CMake (see 6 below) instead of with
213        Configure/Make.
214    
215    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
216        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
217        exported in the Windows port". It has not yet been confirmed that the patch
218        solves the problem, but it does no harm.
219    
220    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
221        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
222        with CMake, and also correct the comment about stack recursion.
223    
224    7.  Remove the automatic building of pcredemo from the ./configure system and
225        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
226        of a program that users should build themselves after PCRE is installed, so
227        building it automatically is not really right. What is more, it gave
228        trouble in some build environments.
229    
230    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
231    
232    
233    Version 7.5 10-Jan-08
234  ---------------------  ---------------------
235    
236  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'
# Line 99  Version 7.5 31-Dec-07 Line 328  Version 7.5 31-Dec-07
328    
329  20. In pcrecpp.cc, the variable 'count' was incremented twice in  20. In pcrecpp.cc, the variable 'count' was incremented twice in
330      RE::GlobalReplace(). As a result, the number of replacements returned was      RE::GlobalReplace(). As a result, the number of replacements returned was
331      double what it should be. I have removed one of the increments.      double what it should be. I removed one of the increments, but Craig sent a
332        later patch that removed the other one (the right fix) and added unit tests
333        that check the return values (which was not done before).
334    
335  21. Several CMake things:  21. Several CMake things:
336    
# Line 110  Version 7.5 31-Dec-07 Line 341  Version 7.5 31-Dec-07
341          linked with the newly-built libraries, not previously installed ones.          linked with the newly-built libraries, not previously installed ones.
342    
343      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
344    
345  22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*  22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
346      crashed when matching a string such as a\x{2029}b (note that \x{2029} is a      crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
347      UTF-8 newline character). The key issue is that the pattern starts .*;      UTF-8 newline character). The key issue is that the pattern starts .*;
348      this means that the match must be either at the beginning, or after a      this means that the match must be either at the beginning, or after a
349      newline. The bug was in the code for advancing after a failed match and      newline. The bug was in the code for advancing after a failed match and
350      checking that the new position followed a newline. It was not taking      checking that the new position followed a newline. It was not taking
351      account of UTF-8 characters correctly.      account of UTF-8 characters correctly.
352    
353  23. PCRE was behaving differently from Perl in the way it recognized POSIX  23. PCRE was behaving differently from Perl in the way it recognized POSIX
354      character classes. PCRE was not treating the sequence [:...:] as a      character classes. PCRE was not treating the sequence [:...:] as a
355      character class unless the ... were all letters. Perl, however, seems to      character class unless the ... were all letters. Perl, however, seems to
356      allow any characters between [: and :], though of course it rejects as      allow any characters between [: and :], though of course it rejects as
357      unknown any "names" that contain non-letters, because all the known class      unknown any "names" that contain non-letters, because all the known class
358      names consist only of letters. Thus, Perl gives an error for [[:1234:]],      names consist only of letters. Thus, Perl gives an error for [[:1234:]],
359      for example, whereas PCRE did not - it did not recognize a POSIX character      for example, whereas PCRE did not - it did not recognize a POSIX character
360      class. This seemed a bit dangerous, so the code has been changed to be      class. This seemed a bit dangerous, so the code has been changed to be
361      closer to Perl. The behaviour is not identical to Perl, because PCRE will      closer to Perl. The behaviour is not identical to Perl, because PCRE will
362      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
363      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
364      Perl does, and where it didn't before.      Perl does, and where it didn't before.
365    
366    24. Rewrite so as to remove the single use of %n from pcregrep because in some
367        Windows environments %n is disabled by default.
368    
369    
370  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Legend:
Removed from v.295  
changed lines
  Added in v.369

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12