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

Diff of /code/trunk/ChangeLog

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

revision 296 by ph10, Tue Jan 1 20:09:30 2008 UTC revision 325 by ph10, Sat Mar 8 17:13:02 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 31-Dec-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    
34    Version 7.6 28-Jan-08
35    ---------------------
36    
37    1.  A character class containing a very large number of characters with
38        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
39        overflow.
40    
41    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
42        HAVE_LONG_LONG is not defined.
43    
44    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
45        bring them up to date and include new features. This patch includes:
46    
47        - Fixed PH's badly added libz and libbz2 support.
48        - Fixed a problem with static linking.
49        - Added pcredemo. [But later removed - see 7 below.]
50        - Fixed dftables problem and added an option.
51        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
52            HAVE_LONG_LONG.
53        - Added readline support for pcretest.
54        - Added an listing of the option settings after cmake has run.
55    
56    4.  A user submitted a patch to Makefile that makes it easy to create
57        "pcre.dll" under mingw when using Configure/Make. I added stuff to
58        Makefile.am that cause it to include this special target, without
59        affecting anything else. Note that the same mingw target plus all
60        the other distribution libraries and programs are now supported
61        when configuring with CMake (see 6 below) instead of with
62        Configure/Make.
63    
64    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
65        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
66        exported in the Windows port". It has not yet been confirmed that the patch
67        solves the problem, but it does no harm.
68    
69    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
70        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
71        with CMake, and also correct the comment about stack recursion.
72    
73    7.  Remove the automatic building of pcredemo from the ./configure system and
74        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
75        of a program that users should build themselves after PCRE is installed, so
76        building it automatically is not really right. What is more, it gave
77        trouble in some build environments.
78    
79    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
80    
81    
82    Version 7.5 10-Jan-08
83  ---------------------  ---------------------
84    
85  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 177  Version 7.5 31-Dec-07
177    
178  20. In pcrecpp.cc, the variable 'count' was incremented twice in  20. In pcrecpp.cc, the variable 'count' was incremented twice in
179      RE::GlobalReplace(). As a result, the number of replacements returned was      RE::GlobalReplace(). As a result, the number of replacements returned was
180      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
181        later patch that removed the other one (the right fix) and added unit tests
182        that check the return values (which was not done before).
183    
184  21. Several CMake things:  21. Several CMake things:
185    
# Line 110  Version 7.5 31-Dec-07 Line 190  Version 7.5 31-Dec-07
190          linked with the newly-built libraries, not previously installed ones.          linked with the newly-built libraries, not previously installed ones.
191    
192      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
193    
194  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.*
195      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
196      UTF-8 newline character). The key issue is that the pattern starts .*;      UTF-8 newline character). The key issue is that the pattern starts .*;
197      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
198      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
199      checking that the new position followed a newline. It was not taking      checking that the new position followed a newline. It was not taking
200      account of UTF-8 characters correctly.      account of UTF-8 characters correctly.
201    
202  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
203      character classes. PCRE was not treating the sequence [:...:] as a      character classes. PCRE was not treating the sequence [:...:] as a
204      character class unless the ... were all letters. Perl, however, seems to      character class unless the ... were all letters. Perl, however, seems to
205      allow any characters between [: and :], though of course it rejects as      allow any characters between [: and :], though of course it rejects as
206      unknown any "names" that contain non-letters, because all the known class      unknown any "names" that contain non-letters, because all the known class
207      names consist only of letters. Thus, Perl gives an error for [[:1234:]],      names consist only of letters. Thus, Perl gives an error for [[:1234:]],
208      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
209      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
210      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
211      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
212      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
213      Perl does, and where it didn't before.      Perl does, and where it didn't before.
214    
215  24. Rewrite so as to remove the single use of %n from pcregrep because in some  24. Rewrite so as to remove the single use of %n from pcregrep because in some
216      Windows environments %n is disabled by default.      Windows environments %n is disabled by default.
217    

Legend:
Removed from v.296  
changed lines
  Added in v.325

  ViewVC Help
Powered by ViewVC 1.1.5