/[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 344 by ph10, Tue Apr 22 09:16:15 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. (See also #8 below.)
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    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
41        caused by fix #2  above. (Subsequently also a second patch to fix the
42        first patch. And a third patch - this was a messy problem.)
43    
44    9.  Applied Craig's patch to remove the use of push_back().
45    
46    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
47        matching function regexec().
48    
49    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
50        which, however, unlike Perl's \g{...}, are subroutine calls, not back
51        references. PCRE supports relative numbers with this syntax (I don't think
52        Oniguruma does).
53    
54    12. Previously, a group with a zero repeat such as (...){0} was completely
55        omitted from the compiled regex. However, this means that if the group
56        was called as a subroutine from elsewhere in the pattern, things went wrong
57        (an internal error was given). Such groups are now left in the compiled
58        pattern, with a new opcode that causes them to be skipped at execution
59        time.
60    
61    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
62        to the way PCRE behaves:
63    
64        (a) A lone ] character is dis-allowed (Perl treats it as data).
65    
66        (b) A back reference to an unmatched subpattern matches an empty string
67            (Perl fails the current match path).
68    
69        (c) A data ] in a character class must be notated as \] because if the
70            first data character in a class is ], it defines an empty class. (In
71            Perl it is not possible to have an empty class.) The empty class []
72            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
73            The negative empty class [^] matches any one character, independently
74            of the DOTALL setting.
75    
76    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
77        non-existent subpattern following a character class starting with ']' and
78        containing () gave an internal compiling error instead of "reference to
79        non-existent subpattern". Fortunately, when the pattern did exist, the
80        compiled code was correct. (When scanning forwards to check for the
81        existencd of the subpattern, it was treating the data ']' as terminating
82        the class, so got the count wrong. When actually compiling, the reference
83        was subsequently set up correctly.)
84    
85    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
86        it was being rejected as not supported by pcre_dfa_exec(), even though
87        other assertions are supported. I have made pcre_dfa_exec() support
88        (*FAIL).
89    
90    16. The implementation of 13c above involved the invention of a new opcode,
91        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
92        cannot be changed at match time, I realized I could make a small
93        improvement to matching performance by compiling OP_ALLANY instead of
94        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
95        on the OP_ANY path.
96    
97    17. Compiling pcretest on Windows with readline support failed without the
98        following two fixes: (1) Make the unistd.h include conditional on
99        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
100    
101    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
102        ncurses library to be included for pcretest when ReadLine support is
103        requested, but also to allow for it to be overridden. This patch came from
104        Daniel Bergström.
105    
106    
107    Version 7.6 28-Jan-08
108    ---------------------
109    
110    1.  A character class containing a very large number of characters with
111        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
112        overflow.
113    
114    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
115        HAVE_LONG_LONG is not defined.
116    
117    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
118        bring them up to date and include new features. This patch includes:
119    
120        - Fixed PH's badly added libz and libbz2 support.
121        - Fixed a problem with static linking.
122        - Added pcredemo. [But later removed - see 7 below.]
123        - Fixed dftables problem and added an option.
124        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
125            HAVE_LONG_LONG.
126        - Added readline support for pcretest.
127        - Added an listing of the option settings after cmake has run.
128    
129    4.  A user submitted a patch to Makefile that makes it easy to create
130        "pcre.dll" under mingw when using Configure/Make. I added stuff to
131        Makefile.am that cause it to include this special target, without
132        affecting anything else. Note that the same mingw target plus all
133        the other distribution libraries and programs are now supported
134        when configuring with CMake (see 6 below) instead of with
135        Configure/Make.
136    
137    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
138        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
139        exported in the Windows port". It has not yet been confirmed that the patch
140        solves the problem, but it does no harm.
141    
142    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
143        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
144        with CMake, and also correct the comment about stack recursion.
145    
146    7.  Remove the automatic building of pcredemo from the ./configure system and
147        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
148        of a program that users should build themselves after PCRE is installed, so
149        building it automatically is not really right. What is more, it gave
150        trouble in some build environments.
151    
152    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
153    
154    
155    Version 7.5 10-Jan-08
156  ---------------------  ---------------------
157    
158  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 250  Version 7.5 31-Dec-07
250    
251  20. In pcrecpp.cc, the variable 'count' was incremented twice in  20. In pcrecpp.cc, the variable 'count' was incremented twice in
252      RE::GlobalReplace(). As a result, the number of replacements returned was      RE::GlobalReplace(). As a result, the number of replacements returned was
253      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
254        later patch that removed the other one (the right fix) and added unit tests
255        that check the return values (which was not done before).
256    
257  21. Several CMake things:  21. Several CMake things:
258    
# Line 110  Version 7.5 31-Dec-07 Line 263  Version 7.5 31-Dec-07
263          linked with the newly-built libraries, not previously installed ones.          linked with the newly-built libraries, not previously installed ones.
264    
265      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
266    
267  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.*
268      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
269      UTF-8 newline character). The key issue is that the pattern starts .*;      UTF-8 newline character). The key issue is that the pattern starts .*;
270      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
271      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
272      checking that the new position followed a newline. It was not taking      checking that the new position followed a newline. It was not taking
273      account of UTF-8 characters correctly.      account of UTF-8 characters correctly.
274    
275  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
276      character classes. PCRE was not treating the sequence [:...:] as a      character classes. PCRE was not treating the sequence [:...:] as a
277      character class unless the ... were all letters. Perl, however, seems to      character class unless the ... were all letters. Perl, however, seems to
278      allow any characters between [: and :], though of course it rejects as      allow any characters between [: and :], though of course it rejects as
279      unknown any "names" that contain non-letters, because all the known class      unknown any "names" that contain non-letters, because all the known class
280      names consist only of letters. Thus, Perl gives an error for [[:1234:]],      names consist only of letters. Thus, Perl gives an error for [[:1234:]],
281      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
282      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
283      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
284      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
285      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
286      Perl does, and where it didn't before.      Perl does, and where it didn't before.
287    
288    24. Rewrite so as to remove the single use of %n from pcregrep because in some
289        Windows environments %n is disabled by default.
290    
291    
292  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12