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

Diff of /code/trunk/ChangeLog

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

revision 297 by ph10, Fri Jan 4 19:44:00 2008 UTC revision 355 by ph10, Mon Jul 7 17:45:23 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 04-Jan-08  Version 8.0 02 Jul-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    
31    Version 7.7 07-May-08
32    ---------------------
33    
34    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
35        a string to a long long, pretend we don't even have a long long." This is
36        done by checking for the strtoq, strtoll, and _strtoi64 functions.
37    
38    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
39        pre-7.6 versions, which defined a global no_arg variable instead of putting
40        it in the RE class. (See also #8 below.)
41    
42    3.  Remove a line of dead code, identified by coverity and reported by Nuno
43        Lopes.
44    
45    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
46    
47        (1) The include/exclude patterns were being applied to the whole pathnames
48            of files, instead of just to the final components.
49    
50        (2) If there was more than one level of directory, the subdirectories were
51            skipped unless they satisfied the include/exclude conditions. This is
52            inconsistent with GNU grep (and could even be seen as contrary to the
53            pcregrep specification - which I improved to make it absolutely clear).
54            The action now is always to scan all levels of directory, and just
55            apply the include/exclude patterns to regular files.
56    
57    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
58        --exclude_dir in the tests to avoid scanning .svn directories.
59    
60    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
61        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
62        doesn't support NULs in patterns.
63    
64    7.  Added some missing "const"s to declarations of static tables in
65        pcre_compile.c and pcre_dfa_exec.c.
66    
67    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
68        caused by fix #2  above. (Subsequently also a second patch to fix the
69        first patch. And a third patch - this was a messy problem.)
70    
71    9.  Applied Craig's patch to remove the use of push_back().
72    
73    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
74        matching function regexec().
75    
76    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
77        which, however, unlike Perl's \g{...}, are subroutine calls, not back
78        references. PCRE supports relative numbers with this syntax (I don't think
79        Oniguruma does).
80    
81    12. Previously, a group with a zero repeat such as (...){0} was completely
82        omitted from the compiled regex. However, this means that if the group
83        was called as a subroutine from elsewhere in the pattern, things went wrong
84        (an internal error was given). Such groups are now left in the compiled
85        pattern, with a new opcode that causes them to be skipped at execution
86        time.
87    
88    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
89        to the way PCRE behaves:
90    
91        (a) A lone ] character is dis-allowed (Perl treats it as data).
92    
93        (b) A back reference to an unmatched subpattern matches an empty string
94            (Perl fails the current match path).
95    
96        (c) A data ] in a character class must be notated as \] because if the
97            first data character in a class is ], it defines an empty class. (In
98            Perl it is not possible to have an empty class.) The empty class []
99            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
100            The negative empty class [^] matches any one character, independently
101            of the DOTALL setting.
102    
103    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
104        non-existent subpattern following a character class starting with ']' and
105        containing () gave an internal compiling error instead of "reference to
106        non-existent subpattern". Fortunately, when the pattern did exist, the
107        compiled code was correct. (When scanning forwards to check for the
108        existencd of the subpattern, it was treating the data ']' as terminating
109        the class, so got the count wrong. When actually compiling, the reference
110        was subsequently set up correctly.)
111    
112    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
113        it was being rejected as not supported by pcre_dfa_exec(), even though
114        other assertions are supported. I have made pcre_dfa_exec() support
115        (*FAIL).
116    
117    16. The implementation of 13c above involved the invention of a new opcode,
118        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
119        cannot be changed at match time, I realized I could make a small
120        improvement to matching performance by compiling OP_ALLANY instead of
121        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
122        on the OP_ANY path.
123    
124    17. Compiling pcretest on Windows with readline support failed without the
125        following two fixes: (1) Make the unistd.h include conditional on
126        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
127    
128    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
129        ncurses library to be included for pcretest when ReadLine support is
130        requested, but also to allow for it to be overridden. This patch came from
131        Daniel Bergström.
132    
133    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
134        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
135        any errors with the current Unicode tables. Thanks to Peter Kankowski for
136        spotting this.
137    
138    
139    Version 7.6 28-Jan-08
140    ---------------------
141    
142    1.  A character class containing a very large number of characters with
143        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
144        overflow.
145    
146    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
147        HAVE_LONG_LONG is not defined.
148    
149    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
150        bring them up to date and include new features. This patch includes:
151    
152        - Fixed PH's badly added libz and libbz2 support.
153        - Fixed a problem with static linking.
154        - Added pcredemo. [But later removed - see 7 below.]
155        - Fixed dftables problem and added an option.
156        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
157            HAVE_LONG_LONG.
158        - Added readline support for pcretest.
159        - Added an listing of the option settings after cmake has run.
160    
161    4.  A user submitted a patch to Makefile that makes it easy to create
162        "pcre.dll" under mingw when using Configure/Make. I added stuff to
163        Makefile.am that cause it to include this special target, without
164        affecting anything else. Note that the same mingw target plus all
165        the other distribution libraries and programs are now supported
166        when configuring with CMake (see 6 below) instead of with
167        Configure/Make.
168    
169    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
170        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
171        exported in the Windows port". It has not yet been confirmed that the patch
172        solves the problem, but it does no harm.
173    
174    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
175        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
176        with CMake, and also correct the comment about stack recursion.
177    
178    7.  Remove the automatic building of pcredemo from the ./configure system and
179        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
180        of a program that users should build themselves after PCRE is installed, so
181        building it automatically is not really right. What is more, it gave
182        trouble in some build environments.
183    
184    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
185    
186    
187    Version 7.5 10-Jan-08
188  ---------------------  ---------------------
189    
190  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 04-Jan-08 Line 282  Version 7.5 04-Jan-08
282    
283  20. In pcrecpp.cc, the variable 'count' was incremented twice in  20. In pcrecpp.cc, the variable 'count' was incremented twice in
284      RE::GlobalReplace(). As a result, the number of replacements returned was      RE::GlobalReplace(). As a result, the number of replacements returned was
285      double what it should be. I removed one of the increments, but Craig sent a      double what it should be. I removed one of the increments, but Craig sent a
286      later patch that removed the other one (the right fix) and added unit tests      later patch that removed the other one (the right fix) and added unit tests
287      that check the return values (which was not done before).      that check the return values (which was not done before).
288    
289  21. Several CMake things:  21. Several CMake things:
290    
# Line 112  Version 7.5 04-Jan-08 Line 295  Version 7.5 04-Jan-08
295          linked with the newly-built libraries, not previously installed ones.          linked with the newly-built libraries, not previously installed ones.
296    
297      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
298    
299  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.*
300      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
301      UTF-8 newline character). The key issue is that the pattern starts .*;      UTF-8 newline character). The key issue is that the pattern starts .*;
302      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
303      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
304      checking that the new position followed a newline. It was not taking      checking that the new position followed a newline. It was not taking
305      account of UTF-8 characters correctly.      account of UTF-8 characters correctly.
306    
307  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
308      character classes. PCRE was not treating the sequence [:...:] as a      character classes. PCRE was not treating the sequence [:...:] as a
309      character class unless the ... were all letters. Perl, however, seems to      character class unless the ... were all letters. Perl, however, seems to
310      allow any characters between [: and :], though of course it rejects as      allow any characters between [: and :], though of course it rejects as
311      unknown any "names" that contain non-letters, because all the known class      unknown any "names" that contain non-letters, because all the known class
312      names consist only of letters. Thus, Perl gives an error for [[:1234:]],      names consist only of letters. Thus, Perl gives an error for [[:1234:]],
313      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
314      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
315      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
316      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
317      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
318      Perl does, and where it didn't before.      Perl does, and where it didn't before.
319    
320  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
321      Windows environments %n is disabled by default.      Windows environments %n is disabled by default.
322    

Legend:
Removed from v.297  
changed lines
  Added in v.355

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12