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

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

  ViewVC Help
Powered by ViewVC 1.1.5