ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 203 by ph10, Fri Aug 3 10:09:57 2007 UTC revision 353 by ph10, Mon Jul 7 15:44:24 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-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.
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.
22    Version 7.7 07-May-08
23    ---------------------
25    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
26        a string to a long long, pretend we don't even have a long long." This is
27        done by checking for the strtoq, strtoll, and _strtoi64 functions.
29    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
30        pre-7.6 versions, which defined a global no_arg variable instead of putting
31        it in the RE class. (See also #8 below.)
33    3.  Remove a line of dead code, identified by coverity and reported by Nuno
34        Lopes.
36    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
38        (1) The include/exclude patterns were being applied to the whole pathnames
39            of files, instead of just to the final components.
41        (2) If there was more than one level of directory, the subdirectories were
42            skipped unless they satisfied the include/exclude conditions. This is
43            inconsistent with GNU grep (and could even be seen as contrary to the
44            pcregrep specification - which I improved to make it absolutely clear).
45            The action now is always to scan all levels of directory, and just
46            apply the include/exclude patterns to regular files.
48    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
49        --exclude_dir in the tests to avoid scanning .svn directories.
51    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
52        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
53        doesn't support NULs in patterns.
55    7.  Added some missing "const"s to declarations of static tables in
56        pcre_compile.c and pcre_dfa_exec.c.
58    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
59        caused by fix #2  above. (Subsequently also a second patch to fix the
60        first patch. And a third patch - this was a messy problem.)
62    9.  Applied Craig's patch to remove the use of push_back().
64    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
65        matching function regexec().
67    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
68        which, however, unlike Perl's \g{...}, are subroutine calls, not back
69        references. PCRE supports relative numbers with this syntax (I don't think
70        Oniguruma does).
72    12. Previously, a group with a zero repeat such as (...){0} was completely
73        omitted from the compiled regex. However, this means that if the group
74        was called as a subroutine from elsewhere in the pattern, things went wrong
75        (an internal error was given). Such groups are now left in the compiled
76        pattern, with a new opcode that causes them to be skipped at execution
77        time.
79    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
80        to the way PCRE behaves:
82        (a) A lone ] character is dis-allowed (Perl treats it as data).
84        (b) A back reference to an unmatched subpattern matches an empty string
85            (Perl fails the current match path).
87        (c) A data ] in a character class must be notated as \] because if the
88            first data character in a class is ], it defines an empty class. (In
89            Perl it is not possible to have an empty class.) The empty class []
90            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
91            The negative empty class [^] matches any one character, independently
92            of the DOTALL setting.
94    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
95        non-existent subpattern following a character class starting with ']' and
96        containing () gave an internal compiling error instead of "reference to
97        non-existent subpattern". Fortunately, when the pattern did exist, the
98        compiled code was correct. (When scanning forwards to check for the
99        existencd of the subpattern, it was treating the data ']' as terminating
100        the class, so got the count wrong. When actually compiling, the reference
101        was subsequently set up correctly.)
103    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
104        it was being rejected as not supported by pcre_dfa_exec(), even though
105        other assertions are supported. I have made pcre_dfa_exec() support
106        (*FAIL).
108    16. The implementation of 13c above involved the invention of a new opcode,
109        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
110        cannot be changed at match time, I realized I could make a small
111        improvement to matching performance by compiling OP_ALLANY instead of
112        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
113        on the OP_ANY path.
115    17. Compiling pcretest on Windows with readline support failed without the
116        following two fixes: (1) Make the unistd.h include conditional on
117        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
119    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
120        ncurses library to be included for pcretest when ReadLine support is
121        requested, but also to allow for it to be overridden. This patch came from
122        Daniel Bergström.
124    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
125        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
126        any errors with the current Unicode tables. Thanks to Peter Kankowski for
127        spotting this.
130    Version 7.6 28-Jan-08
131    ---------------------
133    1.  A character class containing a very large number of characters with
134        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
135        overflow.
137    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
138        HAVE_LONG_LONG is not defined.
140    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
141        bring them up to date and include new features. This patch includes:
143        - Fixed PH's badly added libz and libbz2 support.
144        - Fixed a problem with static linking.
145        - Added pcredemo. [But later removed - see 7 below.]
146        - Fixed dftables problem and added an option.
147        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
148            HAVE_LONG_LONG.
149        - Added readline support for pcretest.
150        - Added an listing of the option settings after cmake has run.
152    4.  A user submitted a patch to Makefile that makes it easy to create
153        "pcre.dll" under mingw when using Configure/Make. I added stuff to
154        Makefile.am that cause it to include this special target, without
155        affecting anything else. Note that the same mingw target plus all
156        the other distribution libraries and programs are now supported
157        when configuring with CMake (see 6 below) instead of with
158        Configure/Make.
160    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
161        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
162        exported in the Windows port". It has not yet been confirmed that the patch
163        solves the problem, but it does no harm.
165    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
166        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
167        with CMake, and also correct the comment about stack recursion.
169    7.  Remove the automatic building of pcredemo from the ./configure system and
170        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
171        of a program that users should build themselves after PCRE is installed, so
172        building it automatically is not really right. What is more, it gave
173        trouble in some build environments.
175    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
178    Version 7.5 10-Jan-08
179    ---------------------
181    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
182        values in parens when parsing an RE using the C++ wrapper."
184    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
185        Characters greater than 255 were excluded from the class instead of being
186        included.
188    3.  The same bug as (2) above applied to negated POSIX classes such as
189        [:^space:].
191    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
192        defined or documented. It seems to have been a typo for PCRE_STATIC, so
193        I have changed it.
195    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
196        first named subpattern) and a construct such as (?&a) would reference the
197        first named subpattern whose name started with "a" (in other words, the
198        length check was missing). Both these problems are fixed. "Subpattern name
199        expected" is now given for (?&) (a zero-length name), and this patch also
200        makes it give the same error for \k'' (previously it complained that that
201        was a reference to a non-existent subpattern).
203    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
204        this is right because (?- can be followed by option settings as well as by
205        digits. I have, however, made the messages clearer.
207    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
208        than the number used in the conditional) now cause a compile-time error.
209        This is actually not compatible with Perl, which accepts such patterns, but
210        treats the conditional as always being FALSE (as PCRE used to), but it
211        seems to me that giving a diagnostic is better.
213    8.  Change "alphameric" to the more common word "alphanumeric" in comments
214        and messages.
216    9.  Fix two occurrences of "backslash" in comments that should have been
217        "backspace".
219    10. Remove two redundant lines of code that can never be obeyed (their function
220        was moved elsewhere).
222    11. The program that makes PCRE's Unicode character property table had a bug
223        which caused it to generate incorrect table entries for sequences of
224        characters that have the same character type, but are in different scripts.
225        It amalgamated them into a single range, with the script of the first of
226        them. In other words, some characters were in the wrong script. There were
227        thirteen such cases, affecting characters in the following ranges:
229          U+002b0 - U+002c1
230          U+0060c - U+0060d
231          U+0061e - U+00612
232          U+0064b - U+0065e
233          U+0074d - U+0076d
234          U+01800 - U+01805
235          U+01d00 - U+01d77
236          U+01d9b - U+01dbf
237          U+0200b - U+0200f
238          U+030fc - U+030fe
239          U+03260 - U+0327f
240          U+0fb46 - U+0fbb1
241          U+10450 - U+1049d
243    12. The -o option (show only the matching part of a line) for pcregrep was not
244        compatible with GNU grep in that, if there was more than one match in a
245        line, it showed only the first of them. It now behaves in the same way as
246        GNU grep.
248    13. If the -o and -v options were combined for pcregrep, it printed a blank
249        line for every non-matching line. GNU grep prints nothing, and pcregrep now
250        does the same. The return code can be used to tell if there were any
251        non-matching lines.
253    14. Added --file-offsets and --line-offsets to pcregrep.
255    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
256        infinitely looping recursion. The bug was that positive lookaheads were not
257        being skipped when checking for a possible empty match (negative lookaheads
258        and both kinds of lookbehind were skipped).
260    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
261        inclusion of <windows.h> to before rather than after the definition of
262        INVALID_FILE_ATTRIBUTES (patch from David Byron).
264    17. Specifying a possessive quantifier with a specific limit for a Unicode
265        character property caused pcre_compile() to compile bad code, which led at
266        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
267        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
268        caused the error; without that there was no problem.
270    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
272    19. Added --enable-pcretest-libreadline.
274    20. In pcrecpp.cc, the variable 'count' was incremented twice in
275        RE::GlobalReplace(). As a result, the number of replacements returned was
276        double what it should be. I removed one of the increments, but Craig sent a
277        later patch that removed the other one (the right fix) and added unit tests
278        that check the return values (which was not done before).
280    21. Several CMake things:
282        (1) Arranged that, when cmake is used on Unix, the libraries end up with
283            the names libpcre and libpcreposix, not just pcre and pcreposix.
285        (2) The above change means that pcretest and pcregrep are now correctly
286            linked with the newly-built libraries, not previously installed ones.
290    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
291        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
292        UTF-8 newline character). The key issue is that the pattern starts .*;
293        this means that the match must be either at the beginning, or after a
294        newline. The bug was in the code for advancing after a failed match and
295        checking that the new position followed a newline. It was not taking
296        account of UTF-8 characters correctly.
298    23. PCRE was behaving differently from Perl in the way it recognized POSIX
299        character classes. PCRE was not treating the sequence [:...:] as a
300        character class unless the ... were all letters. Perl, however, seems to
301        allow any characters between [: and :], though of course it rejects as
302        unknown any "names" that contain non-letters, because all the known class
303        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
304        for example, whereas PCRE did not - it did not recognize a POSIX character
305        class. This seemed a bit dangerous, so the code has been changed to be
306        closer to Perl. The behaviour is not identical to Perl, because PCRE will
307        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
308        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
309        Perl does, and where it didn't before.
311    24. Rewrite so as to remove the single use of %n from pcregrep because in some
312        Windows environments %n is disabled by default.
315    Version 7.4 21-Sep-07
316    ---------------------
318    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
319        means that a class such as [\s] counted as "explicit reference to CR or
320        LF". That isn't really right - the whole point of the change was to try to
321        help when there was an actual mention of one of the two characters. So now
322        the change happens only if \r or \n (or a literal CR or LF) character is
323        encountered.
325    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
326        of both had grown to the point where there were only 3 bits left.
327        Fortunately, there was spare space in the data structure, and so I have
328        moved the internal flags into a new 16-bit field to free up more option
329        bits.
331    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
332        but did not set the internal JCHANGED flag - either of these is enough to
333        control the way the "get" function works - but the PCRE_INFO_JCHANGED
334        facility is supposed to tell if (?J) was ever used, so now (?J) at the
335        start sets both bits.
337    4.  Added options (at build time, compile time, exec time) to change \R from
338        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
340    5.  doc/pcresyntax.html was missing from the distribution.
342    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
343        compatibility, even though it is no longer used.
345    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
346        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
347        windows.h file is present (where different names are used). [This was
348        reversed later after testing - see 16 below.]
350    8.  Changed all #include <config.h> to #include "config.h". There were also
351        some further <pcre.h> cases that I changed to "pcre.h".
353    9.  When pcregrep was used with the --colour option, it missed the line ending
354        sequence off the lines that it output.
356    10. It was pointed out to me that arrays of string pointers cause lots of
357        relocations when a shared library is dynamically loaded. A technique of
358        using a single long string with a table of offsets can drastically reduce
359        these. I have refactored PCRE in four places to do this. The result is
360        dramatic:
362          Originally:                          290
363          After changing UCP table:            187
364          After changing error message table:   43
365          After changing table of "verbs"       36
366          After changing table of Posix names   22
368        Thanks to the folks working on Gregex for glib for this insight.
370    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
371        unicode-properties was also set.
373    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
375    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
376        checked only for CRLF.
378    14. Added casts to pcretest.c to avoid compiler warnings.
380    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
382    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
383        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
384        entirely. This removes changes made in 7 above.
386    17. The CMake files have been updated, and there is now more information about
387        building with CMake in the NON-UNIX-USE document.
390    Version 7.3 28-Aug-07
391  ---------------------  ---------------------
393   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 64  Version 7.3 05-Jul-07 Line 450  Version 7.3 05-Jul-07
450      dynamic way, which I have now done. The artificial limitation on group      dynamic way, which I have now done. The artificial limitation on group
451      length has been removed - we now have only the limit on the total length of      length has been removed - we now have only the limit on the total length of
452      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
454  10. Fixed a bug in the documentation for get/copy named substring when  10. Fixed a bug in the documentation for get/copy named substring when
455      duplicate names are permitted. If none of the named substrings are set, the      duplicate names are permitted. If none of the named substrings are set, the
456      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
457      empty string.      empty string.
459    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
460        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
461        because the ] is interpreted as the first data character and the
462        terminating ] is not found. PCRE has been made compatible with Perl in this
463        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
464        cause memory overwriting.
466    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
467        string has been matched (to stop an infinite loop). It was not recognizing
468        a conditional subpattern that could match an empty string if that
469        subpattern was within another subpattern. For example, it looped when
470        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
471        condition was not nested. This bug has been fixed.
473    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
474        past the start of the subject in the presence of bytes with the top bit
475        set, for example "\x8aBCD".
477    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
478        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
480    14. Optimized (?!) to (*FAIL).
482    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
483        This restricts code points to be within the range 0 to 0x10FFFF, excluding
484        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
485        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
486        does: it's just the validity check that is more restrictive.
488    16. Inserted checks for integer overflows during escape sequence (backslash)
489        processing, and also fixed erroneous offset values for syntax errors during
490        backslash processing.
492    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
493        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
495    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
496        caused an overrun.
498    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
499        something other than just ASCII characters) inside a group that had an
500        unlimited repeat caused a loop at compile time (while checking to see
501        whether the group could match an empty string).
503    20. Debugging a pattern containing \p or \P could cause a crash. For example,
504        [\P{Any}] did so. (Error in the code for printing property names.)
506    21. An orphan \E inside a character class could cause a crash.
508    22. A repeated capturing bracket such as (A)? could cause a wild memory
509        reference during compilation.
511    23. There are several functions in pcre_compile() that scan along a compiled
512        expression for various reasons (e.g. to see if it's fixed length for look
513        behind). There were bugs in these functions when a repeated \p or \P was
514        present in the pattern. These operators have additional parameters compared
515        with \d, etc, and these were not being taken into account when moving along
516        the compiled data. Specifically:
518        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
519            length.
521        (b) An item such as \pL+ within a repeated group could cause crashes or
522            loops.
524        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
525            "reference to non-existent subpattern" error.
527        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
529    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
530        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
532    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
534    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
535        character were causing crashes (broken optimization).
537    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
538        \p or \P) caused a compile-time loop.
540    28. More problems have arisen in unanchored patterns when CRLF is a valid line
541        break. For example, the unstudied pattern [\r\n]A does not match the string
542        "\r\nA" because change 7.0/46 below moves the current point on by two
543        characters after failing to match at the start. However, the pattern \nA
544        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
545        the same is true. There doesn't seem any very clean way out of this, but
546        what I have chosen to do makes the common cases work: PCRE now takes note
547        of whether there can be an explicit match for \r or \n anywhere in the
548        pattern, and if so, 7.0/46 no longer applies. As part of this change,
549        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
550        pattern has explicit CR or LF references.
552    29. Added (*CR) etc for changing newline setting at start of pattern.
555  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Removed from v.203  
changed lines
  Added in v.353

  ViewVC Help
Powered by ViewVC 1.1.5