ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 247 by ph10, Mon Sep 17 09:38:32 2007 UTC revision 351 by ph10, Fri Jul 4 18:27:16 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.4 10-Sep-07  Version 8.0 02 Jul-08
5    ---------------------
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).
14    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
15        scripts.
18    Version 7.7 07-May-08
19    ---------------------
21    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
22        a string to a long long, pretend we don't even have a long long." This is
23        done by checking for the strtoq, strtoll, and _strtoi64 functions.
25    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
26        pre-7.6 versions, which defined a global no_arg variable instead of putting
27        it in the RE class. (See also #8 below.)
29    3.  Remove a line of dead code, identified by coverity and reported by Nuno
30        Lopes.
32    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
34        (1) The include/exclude patterns were being applied to the whole pathnames
35            of files, instead of just to the final components.
37        (2) If there was more than one level of directory, the subdirectories were
38            skipped unless they satisfied the include/exclude conditions. This is
39            inconsistent with GNU grep (and could even be seen as contrary to the
40            pcregrep specification - which I improved to make it absolutely clear).
41            The action now is always to scan all levels of directory, and just
42            apply the include/exclude patterns to regular files.
44    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
45        --exclude_dir in the tests to avoid scanning .svn directories.
47    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
48        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
49        doesn't support NULs in patterns.
51    7.  Added some missing "const"s to declarations of static tables in
52        pcre_compile.c and pcre_dfa_exec.c.
54    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
55        caused by fix #2  above. (Subsequently also a second patch to fix the
56        first patch. And a third patch - this was a messy problem.)
58    9.  Applied Craig's patch to remove the use of push_back().
60    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
61        matching function regexec().
63    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
64        which, however, unlike Perl's \g{...}, are subroutine calls, not back
65        references. PCRE supports relative numbers with this syntax (I don't think
66        Oniguruma does).
68    12. Previously, a group with a zero repeat such as (...){0} was completely
69        omitted from the compiled regex. However, this means that if the group
70        was called as a subroutine from elsewhere in the pattern, things went wrong
71        (an internal error was given). Such groups are now left in the compiled
72        pattern, with a new opcode that causes them to be skipped at execution
73        time.
75    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
76        to the way PCRE behaves:
78        (a) A lone ] character is dis-allowed (Perl treats it as data).
80        (b) A back reference to an unmatched subpattern matches an empty string
81            (Perl fails the current match path).
83        (c) A data ] in a character class must be notated as \] because if the
84            first data character in a class is ], it defines an empty class. (In
85            Perl it is not possible to have an empty class.) The empty class []
86            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
87            The negative empty class [^] matches any one character, independently
88            of the DOTALL setting.
90    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
91        non-existent subpattern following a character class starting with ']' and
92        containing () gave an internal compiling error instead of "reference to
93        non-existent subpattern". Fortunately, when the pattern did exist, the
94        compiled code was correct. (When scanning forwards to check for the
95        existencd of the subpattern, it was treating the data ']' as terminating
96        the class, so got the count wrong. When actually compiling, the reference
97        was subsequently set up correctly.)
99    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
100        it was being rejected as not supported by pcre_dfa_exec(), even though
101        other assertions are supported. I have made pcre_dfa_exec() support
102        (*FAIL).
104    16. The implementation of 13c above involved the invention of a new opcode,
105        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
106        cannot be changed at match time, I realized I could make a small
107        improvement to matching performance by compiling OP_ALLANY instead of
108        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
109        on the OP_ANY path.
111    17. Compiling pcretest on Windows with readline support failed without the
112        following two fixes: (1) Make the unistd.h include conditional on
113        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
115    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
116        ncurses library to be included for pcretest when ReadLine support is
117        requested, but also to allow for it to be overridden. This patch came from
118        Daniel Bergström.
120    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
121        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
122        any errors with the current Unicode tables. Thanks to Peter Kankowski for
123        spotting this.
126    Version 7.6 28-Jan-08
127    ---------------------
129    1.  A character class containing a very large number of characters with
130        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
131        overflow.
133    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
134        HAVE_LONG_LONG is not defined.
136    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
137        bring them up to date and include new features. This patch includes:
139        - Fixed PH's badly added libz and libbz2 support.
140        - Fixed a problem with static linking.
141        - Added pcredemo. [But later removed - see 7 below.]
142        - Fixed dftables problem and added an option.
143        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
144            HAVE_LONG_LONG.
145        - Added readline support for pcretest.
146        - Added an listing of the option settings after cmake has run.
148    4.  A user submitted a patch to Makefile that makes it easy to create
149        "pcre.dll" under mingw when using Configure/Make. I added stuff to
150        Makefile.am that cause it to include this special target, without
151        affecting anything else. Note that the same mingw target plus all
152        the other distribution libraries and programs are now supported
153        when configuring with CMake (see 6 below) instead of with
154        Configure/Make.
156    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
157        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
158        exported in the Windows port". It has not yet been confirmed that the patch
159        solves the problem, but it does no harm.
161    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
162        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
163        with CMake, and also correct the comment about stack recursion.
165    7.  Remove the automatic building of pcredemo from the ./configure system and
166        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
167        of a program that users should build themselves after PCRE is installed, so
168        building it automatically is not really right. What is more, it gave
169        trouble in some build environments.
171    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
174    Version 7.5 10-Jan-08
175    ---------------------
177    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
178        values in parens when parsing an RE using the C++ wrapper."
180    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
181        Characters greater than 255 were excluded from the class instead of being
182        included.
184    3.  The same bug as (2) above applied to negated POSIX classes such as
185        [:^space:].
187    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
188        defined or documented. It seems to have been a typo for PCRE_STATIC, so
189        I have changed it.
191    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
192        first named subpattern) and a construct such as (?&a) would reference the
193        first named subpattern whose name started with "a" (in other words, the
194        length check was missing). Both these problems are fixed. "Subpattern name
195        expected" is now given for (?&) (a zero-length name), and this patch also
196        makes it give the same error for \k'' (previously it complained that that
197        was a reference to a non-existent subpattern).
199    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
200        this is right because (?- can be followed by option settings as well as by
201        digits. I have, however, made the messages clearer.
203    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
204        than the number used in the conditional) now cause a compile-time error.
205        This is actually not compatible with Perl, which accepts such patterns, but
206        treats the conditional as always being FALSE (as PCRE used to), but it
207        seems to me that giving a diagnostic is better.
209    8.  Change "alphameric" to the more common word "alphanumeric" in comments
210        and messages.
212    9.  Fix two occurrences of "backslash" in comments that should have been
213        "backspace".
215    10. Remove two redundant lines of code that can never be obeyed (their function
216        was moved elsewhere).
218    11. The program that makes PCRE's Unicode character property table had a bug
219        which caused it to generate incorrect table entries for sequences of
220        characters that have the same character type, but are in different scripts.
221        It amalgamated them into a single range, with the script of the first of
222        them. In other words, some characters were in the wrong script. There were
223        thirteen such cases, affecting characters in the following ranges:
225          U+002b0 - U+002c1
226          U+0060c - U+0060d
227          U+0061e - U+00612
228          U+0064b - U+0065e
229          U+0074d - U+0076d
230          U+01800 - U+01805
231          U+01d00 - U+01d77
232          U+01d9b - U+01dbf
233          U+0200b - U+0200f
234          U+030fc - U+030fe
235          U+03260 - U+0327f
236          U+0fb46 - U+0fbb1
237          U+10450 - U+1049d
239    12. The -o option (show only the matching part of a line) for pcregrep was not
240        compatible with GNU grep in that, if there was more than one match in a
241        line, it showed only the first of them. It now behaves in the same way as
242        GNU grep.
244    13. If the -o and -v options were combined for pcregrep, it printed a blank
245        line for every non-matching line. GNU grep prints nothing, and pcregrep now
246        does the same. The return code can be used to tell if there were any
247        non-matching lines.
249    14. Added --file-offsets and --line-offsets to pcregrep.
251    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
252        infinitely looping recursion. The bug was that positive lookaheads were not
253        being skipped when checking for a possible empty match (negative lookaheads
254        and both kinds of lookbehind were skipped).
256    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
257        inclusion of <windows.h> to before rather than after the definition of
258        INVALID_FILE_ATTRIBUTES (patch from David Byron).
260    17. Specifying a possessive quantifier with a specific limit for a Unicode
261        character property caused pcre_compile() to compile bad code, which led at
262        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
263        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
264        caused the error; without that there was no problem.
266    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
268    19. Added --enable-pcretest-libreadline.
270    20. In pcrecpp.cc, the variable 'count' was incremented twice in
271        RE::GlobalReplace(). As a result, the number of replacements returned was
272        double what it should be. I removed one of the increments, but Craig sent a
273        later patch that removed the other one (the right fix) and added unit tests
274        that check the return values (which was not done before).
276    21. Several CMake things:
278        (1) Arranged that, when cmake is used on Unix, the libraries end up with
279            the names libpcre and libpcreposix, not just pcre and pcreposix.
281        (2) The above change means that pcretest and pcregrep are now correctly
282            linked with the newly-built libraries, not previously installed ones.
286    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
287        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
288        UTF-8 newline character). The key issue is that the pattern starts .*;
289        this means that the match must be either at the beginning, or after a
290        newline. The bug was in the code for advancing after a failed match and
291        checking that the new position followed a newline. It was not taking
292        account of UTF-8 characters correctly.
294    23. PCRE was behaving differently from Perl in the way it recognized POSIX
295        character classes. PCRE was not treating the sequence [:...:] as a
296        character class unless the ... were all letters. Perl, however, seems to
297        allow any characters between [: and :], though of course it rejects as
298        unknown any "names" that contain non-letters, because all the known class
299        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
300        for example, whereas PCRE did not - it did not recognize a POSIX character
301        class. This seemed a bit dangerous, so the code has been changed to be
302        closer to Perl. The behaviour is not identical to Perl, because PCRE will
303        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
304        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
305        Perl does, and where it didn't before.
307    24. Rewrite so as to remove the single use of %n from pcregrep because in some
308        Windows environments %n is disabled by default.
311    Version 7.4 21-Sep-07
312  ---------------------  ---------------------
314  1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This  1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
# Line 32  Version 7.4 10-Sep-07 Line 339  Version 7.4 10-Sep-07
339      compatibility, even though it is no longer used.      compatibility, even though it is no longer used.
341  7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and  7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
342      strtoull to pcrecpp.cc to select the available functions in WIN32 (where      strtoull to pcrecpp.cc to select the available functions in WIN32 when the
343      different names are used).      windows.h file is present (where different names are used). [This was
344        reversed later after testing - see 16 below.]
346  8.  Changed all #include <config.h> to #include "config.h". There were also  8.  Changed all #include <config.h> to #include "config.h". There were also
347      some further <pcre.h> cases that I changed to "pcre.h".      some further <pcre.h> cases that I changed to "pcre.h".
# Line 58  Version 7.4 10-Sep-07 Line 366  Version 7.4 10-Sep-07
366  11. --disable-stack-for-recursion caused compiling to fail unless -enable-  11. --disable-stack-for-recursion caused compiling to fail unless -enable-
367      unicode-properties was also set.      unicode-properties was also set.
369  12. Updated the RunTest script to miss out tests that don't work if \R is  12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
370      defaulted to ANYCRLF.  
371    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
372        checked only for CRLF.
374    14. Added casts to pcretest.c to avoid compiler warnings.
376    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
378    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
379        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
380        entirely. This removes changes made in 7 above.
382    17. The CMake files have been updated, and there is now more information about
383        building with CMake in the NON-UNIX-USE document.
386  Version 7.3 28-Aug-07  Version 7.3 28-Aug-07

Removed from v.247  
changed lines
  Added in v.351

  ViewVC Help
Powered by ViewVC 1.1.5