ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 507 by ph10, Wed Mar 10 16:08:01 2010 UTC revision 1041 by ph10, Sun Sep 16 10:16:27 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.02 10-Mar-2010  Version 8.32
5    ------------
7    1.  Improved JIT compiler optimizations for first character search and single
8        character iterators.
10    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
11        Patch by Daniel Richard G.
13    3.  Single character iterator optimizations in the JIT compiler.
15    4.  Improved JIT compiler optimizations for character ranges.
17    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
18        Reported by Giuseppe D'Angelo.
20    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
21        of a line, was being set incorrectly in cases where .* appeared inside
22        atomic brackets at the start of a pattern, or where there was a subsequent
23        *PRUNE or *SKIP.
25    7.  Improved instruction cache flush for POWER/PowerPC.
26        Patch by Daniel Richard G.
28    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
29        grep:
31        (a) There is now no limit to the number of patterns to be matched.
33        (b) An error is given if a pattern is too long.
35        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
36            are now supported.
38        (d) --exclude-from and --include-from (multiple use) have been added.
40        (e) Exclusions and inclusions now apply to all files and directories, not
41            just to those obtained from scanning a directory recursively.
43        (f) Multiple uses of -f and --file-list are now supported.
45        (g) In a Windows environment, the default for -d has been changed from
46            "read" (the GNU grep default) to "skip", because otherwise the presence
47            of a directory in the file list provokes an error.
49        (h) The documentation has been revised and clarified in places.
51    9.  Improve the matching speed of capturing brackets.
53    10. Changed the meaning of \X so that it now matches a Unicode extended
54        grapheme cluster.
56    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
57        out POSIX threads when JIT support is configured.
59    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
61    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
62        structure could go wrong in environments where size_t is not the same size
63        as int.
65    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
66        set.
68    15. The EBCDIC support had decayed; later updates to the code had included
69        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
70        general tidy up of EBCDIC-related issues, and the documentation was also
71        not quite right. There is now a test that can be run on ASCII systems to
72        check some of the EBCDIC-related things (but is it not a full test).
74    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
75        in a small tidy to the code.
77    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
79    18. If the --only-matching (-o) option in pcregrep is specified multiple
80        times, each one causes appropriate output. For example, -o1 -o2 outputs the
81        substrings matched by the 1st and 2nd capturing parentheses. A separating
82        string can be specified by --om-separator (default empty).
84    19. Improving the first n character searches.
86    20. Turn case lists for horizontal and vertical white space into macros so that
87        they are defined only once.
90    Version 8.31 06-July-2012
91    -------------------------
93    1.  Fixing a wrong JIT test case and some compiler warnings.
95    2.  Removed a bashism from the RunTest script.
97    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
98        to unsigned type, result still unsigned" that was given by an MS compiler
99        on encountering the code "-sizeof(xxx)".
101    4.  Partial matching support is added to the JIT compiler.
103    5.  Fixed several bugs concerned with partial matching of items that consist
104        of more than one character:
106        (a) /^(..)\1/ did not partially match "aba" because checking references was
107            done on an "all or nothing" basis. This also applied to repeated
108            references.
110        (b) \R did not give a hard partial match if \r was found at the end of the
111            subject.
113        (c) \X did not give a hard partial match after matching one or more
114            characters at the end of the subject.
116        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
117            a partial match for the string "\r".
119        (e) When newline was set to CRLF, the metacharacter "." did not recognize
120            a partial match for a CR character at the end of the subject string.
122    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
123        running pcretest, the text "(JIT)" added to the output whenever JIT is
124        actually used to run the match.
126    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
127        or /S+[+] with a digit between 1 and 7.
129    8.  OP_NOT now supports any UTF character not just single-byte ones.
131    9.  (*MARK) control verb is now supported by the JIT compiler.
133    10. The command "./RunTest list" lists the available tests without actually
134        running any of them. (Because I keep forgetting what they all are.)
138    12. Applied a (slightly modified) user-supplied patch that improves performance
139        when the heap is used for recursion (compiled with --disable-stack-for-
140        recursion). Instead of malloc and free for each heap frame each time a
141        logical recursion happens, frames are retained on a chain and re-used where
142        possible. This sometimes gives as much as 30% improvement.
144    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
145        call.
147    14. As documented, (*COMMIT) is now confined to within a positive assertion.
149    15. It is now possible to link pcretest with libedit as an alternative to
150        libreadline.
152    16. (*COMMIT) control verb is now supported by the JIT compiler.
154    17. The Unicode data tables have been updated to Unicode 6.1.0.
156    18. Added --file-list option to pcregrep.
158    19. Added binary file support to pcregrep, including the -a, --binary-files,
159        -I, and --text options.
161    20. The madvise function is renamed for posix_madvise for QNX compatibility
162        reasons. Fixed by Giuseppe D'Angelo.
164    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
166    22. Changed the option for creating symbolic links for 16-bit man pages from
167        -s to -sf so that re-installing does not cause issues.
169    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
171    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
172        matches in certain environments (the workspace was not being correctly
173        retained). Also added to pcre_dfa_exec() a simple plausibility check on
174        some of the workspace data at the beginning of a restart.
176    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
177        was not doing so when it should - probably a typo introduced by SVN 528
178        (change 8.10/14).
180    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
181        \w+ when the character tables indicated that \x{c4} was a word character.
182        There were several related cases, all because the tests for doing a table
183        lookup were testing for characters less than 127 instead of 255.
185    27. If a pattern contains capturing parentheses that are not used in a match,
186        their slots in the ovector are set to -1. For those that are higher than
187        any matched groups, this happens at the end of processing. In the case when
188        there were back references that the ovector was too small to contain
189        (causing temporary malloc'd memory to be used during matching), and the
190        highest capturing number was not used, memory off the end of the ovector
191        was incorrectly being set to -1. (It was using the size of the temporary
192        memory instead of the true size.)
194    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
195        ovector size, it uses memory at the end of the block that it has got.
197    29. Check for an overlong MARK name and give an error at compile time. The
198        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
200    30. JIT compiler update.
202    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
203        Rill for the patch.
205    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
207    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
209    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
210        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
211        was enabled.
213    35. Improve JIT code generation for greedy plus quantifier.
215    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
216        1 to "aa" instead of to an empty string. The bug affected repeated groups
217        that could potentially match an empty string.
219    37. Optimizing single character iterators in JIT.
221    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
222        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
223        codepoints that are too big for the mode are faulted, and in a UTF mode,
224        disallowed codepoints are also faulted.
226    39. If PCRE was compiled with UTF support, in three places in the DFA
227        matcher there was code that should only have been obeyed in UTF mode, but
228        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
229        processing when bytes with values greater than 127 were present. In 16-bit
230        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
231        both cases the values are those that cannot be the first data item in a UTF
232        character. The three items that might have provoked this were recursions,
233        possessively repeated groups, and atomic groups.
235    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
236        and pcregrep, because some OS require shared objects to be explicitly
237        passed to ld, causing the link step to fail if they are not.
239    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
240        mode, patterns that started with \h* or \R* might be incorrectly matched.
243    Version 8.30 04-February-2012
244    -----------------------------
246    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
247        name is defined in ctype.h.
249    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
250        only in quite long subpatterns.
252    3.  Removed the function pcre_info(), which has been obsolete and deprecated
253        since it was replaced by pcre_fullinfo() in February 2000.
255    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
256        match a (*MARK), and the match failed at the start of the subject, a
257        reference to memory before the start of the subject could occur. This bug
258        was introduced by fix 17 of release 8.21.
260    5.  A reference to an unset group with zero minimum repetition was giving
261        totally wrong answers (in non-JavaScript-compatibility mode). For example,
262        /(another)?(\1?)test/ matched against "hello world test". This bug was
263        introduced in release 8.13.
265    6.  Add support for 16-bit character strings (a large amount of work involving
266        many changes and refactorings).
268    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
269        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
270        from a file.
272    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
273        rounding is not applied in this particular case).
275    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
276        if they appear, or are escaped, in patterns.
278    10. Get rid of a number of -Wunused-but-set-variable warnings.
280    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
281        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
282        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
283        also returns the mark "x". This bug applied to capturing parentheses,
284        non-capturing parentheses, and atomic parentheses. It also applied to some
285        assertions.
287    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
288        information out of configure.ac instead of relying on pcre.h.generic, which
289        is not stored in the repository.
291    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
292        -lreadline.
294    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
296    15. Applied Graycode's patch to put the top-level frame on the stack rather
297        than the heap when not using the stack for recursion. This gives a
298        performance improvement in many cases when recursion is not deep.
300    16. Experimental code added to "pcretest -C" to output the stack frame size.
303    Version 8.21 12-Dec-2011
304    ------------------------
306    1.  Updating the JIT compiler.
308    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
309        are added as well.
311    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
312        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
313        calling _pcre_jit_exec. Some extra comments are added.
315    4.  (*MARK) settings inside atomic groups that do not contain any capturing
316        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
317        was introduced by change 18 for 8.20.
319    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
320        ECMA-262 standard.
322    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
323        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
324        This bug was probably introduced by change 9 of 8.13.
326    7.  While fixing 6 above, I noticed that a number of other items were being
327        incorrectly rejected as "not fixed length". This arose partly because newer
328        opcodes had not been added to the fixed-length checking code. I have (a)
329        corrected the bug and added tests for these items, and (b) arranged for an
330        error to occur if an unknown opcode is encountered while checking for fixed
331        length instead of just assuming "not fixed length". The items that were
332        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
333        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
334        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
336    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
337        being incorrectly compiled and would have given unpredicatble results.
339    9.  A possessively repeated subpattern with minimum repeat count greater than
340        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
341        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
342        the first (A) could occur when it should not.
344    10. Add a cast and remove a redundant test from the code.
346    11. JIT should use pcre_malloc/pcre_free for allocation.
348    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
349        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
350        is anything other than /usr, -L is still shown).
352    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
354    14. Perl does not support \N without a following name in a [] class; PCRE now
355        also gives an error.
357    15. If a forward reference was repeated with an upper limit of around 2000,
358        it caused the error "internal error: overran compiling workspace". The
359        maximum number of forward references (including repeats) was limited by the
360        internal workspace, and dependent on the LINK_SIZE. The code has been
361        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
362        the default depends on LINK_SIZE. There is a new upper limit (for safety)
363        of around 200,000 forward references. While doing this, I also speeded up
364        the filling in of repeated forward references.
366    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
367        incorrectly expecting the subject to contain another "a" after the start.
369    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
370        in the match, the SKIP should be ignored. This was not happening; instead
371        the SKIP was being treated as NOMATCH. For patterns such as
372        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
373        tested.
375    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
376        now much more compatible with Perl, in particular in cases where the result
377        is a non-match for a non-anchored pattern. For example, if
378        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
379        "m", where previously it did not return a name. A side effect of this
380        change is that for partial matches, the last encountered mark name is
381        returned, as for non matches. A number of tests that were previously not
382        Perl-compatible have been moved into the Perl-compatible test files. The
383        refactoring has had the pleasing side effect of removing one argument from
384        the match() function, thus reducing its stack requirements.
386    19. If the /S+ option was used in pcretest to study a pattern using JIT,
387        subsequent uses of /S (without +) incorrectly behaved like /S+.
389    21. Retrieve executable code size support for the JIT compiler and fixing
390        some warnings.
392    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
393        not work when the shorter character appeared right at the end of the
394        subject string.
396    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
397        systems.
399    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
400        output it when the /M option is used in pcretest.
402    25. The CheckMan script was not being included in the distribution. Also, added
403        an explicit "perl" to run Perl scripts from the PrepareRelease script
404        because this is reportedly needed in Windows.
406    26. If study data was being save in a file and studying had not found a set of
407        "starts with" bytes for the pattern, the data written to the file (though
408        never used) was taken from uninitialized memory and so caused valgrind to
409        complain.
411    27. Updated RunTest.bat as provided by Sheri Pierce.
413    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
415    29. Computation of memory usage for the table of capturing group names was
416        giving an unnecessarily large value.
419    Version 8.20 21-Oct-2011
420    ------------------------
422    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
423        a POSIX class. After further experiments with Perl, which convinced me that
424        Perl has bugs and confusions, a closing square bracket is no longer allowed
425        in a POSIX name. This bug also affected patterns with classes that started
426        with full stops.
428    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
429        captured substring, but while checking the failing first alternative,
430        substring 1 is temporarily captured. If the output vector supplied to
431        pcre_exec() was not big enough for this capture, the yield of the function
432        was still zero ("insufficient space for captured substrings"). This cannot
433        be totally fixed without adding another stack variable, which seems a lot
434        of expense for a edge case. However, I have improved the situation in cases
435        such as /(a)(b)x|abc/ matched against "abc", where the return code
436        indicates that fewer than the maximum number of slots in the ovector have
437        been set.
439    3.  Related to (2) above: when there are more back references in a pattern than
440        slots in the output vector, pcre_exec() uses temporary memory during
441        matching, and copies in the captures as far as possible afterwards. It was
442        using the entire output vector, but this conflicts with the specification
443        that only 2/3 is used for passing back captured substrings. Now it uses
444        only the first 2/3, for compatibility. This is, of course, another edge
445        case.
447    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
448        main code base, and can be used by building with --enable-jit. When this is
449        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
450        runtime --no-jit option is given.
452    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
453        ovector, the return from the function was zero, implying that there were
454        other matches that did not fit. The correct "exactly full" value is now
455        returned.
457    6.  If a subpattern that was called recursively or as a subroutine contained
458        (*PRUNE) or any other control that caused it to give a non-standard return,
459        invalid errors such as "Error -26 (nested recursion at the same subject
460        position)" or even infinite loops could occur.
462    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
463        computing the minimum length on reaching *ACCEPT, and so ended up with the
464        wrong value of 1 rather than 0. Further investigation indicates that
465        computing a minimum subject length in the presence of *ACCEPT is difficult
466        (think back references, subroutine calls), and so I have changed the code
467        so that no minimum is registered for a pattern that contains *ACCEPT.
469    8.  If (*THEN) was present in the first (true) branch of a conditional group,
470        it was not handled as intended. [But see 16 below.]
472    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
473        Sheri Pierce.
475    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
476        the first byte in a match must be "a".
478    11. Change 17 for 8.13 increased the recursion depth for patterns like
479        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
480        pattern contains any instances of (*THEN). If it does not, the old
481        optimizations are restored. It would be nice to do this on a per-group
482        basis, but at the moment that is not feasible.
484    12. In some environments, the output of pcretest -C is CRLF terminated. This
485        broke RunTest's code that checks for the link size. A single white space
486        character after the value is now allowed for.
488    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
489        For "fr", it uses the Windows-specific input and output files.
491    14. If (*THEN) appeared in a group that was called recursively or as a
492        subroutine, it did not work as intended. [But see next item.]
494    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
495        pattern fragments (but not containing any | characters). If A and B are
496        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
497        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
498        D. In other words, Perl considers parentheses that do not contain any |
499        characters to be part of a surrounding alternative, whereas PCRE was
500        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
501        differently. PCRE now behaves in the same way as Perl, except in the case
502        of subroutine/recursion calls such as (?1) which have in any case always
503        been different (but PCRE had them first :-).
505    16. Related to 15 above: Perl does not treat the | in a conditional group as
506        creating alternatives. Such a group is treated in the same way as an
507        ordinary group without any | characters when processing (*THEN). PCRE has
508        been changed to match Perl's behaviour.
510    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
511        RunGrepTest script failed.
513    18. Change 22 for version 13 caused atomic groups to use more stack. This is
514        inevitable for groups that contain captures, but it can lead to a lot of
515        stack use in large patterns. The old behaviour has been restored for atomic
516        groups that do not contain any capturing parentheses.
518    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
519        suppress the check for a minimum subject length at run time. (If it was
520        given to pcre_exec() or pcre_dfa_exec() it did work.)
522    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
523        fail to work when decoding hex characters in data strings in EBCDIC
524        environments.
526    21. It appears that in at least one Mac OS environment, the isxdigit() function
527        is implemented as a macro that evaluates to its argument more than once,
528        contravening the C 90 Standard (I haven't checked a later standard). There
529        was an instance in pcretest which caused it to go wrong when processing
530        \x{...} escapes in subject strings. The has been rewritten to avoid using
531        things like p++ in the argument of isxdigit().
534    Version 8.13 16-Aug-2011
535    ------------------------
537    1.  The Unicode data tables have been updated to Unicode 6.0.0.
539    2.  Two minor typos in pcre_internal.h have been fixed.
541    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
542        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
543        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
545    4.  There were a number of related bugs in the code for matching backrefences
546        caselessly in UTF-8 mode when codes for the characters concerned were
547        different numbers of bytes. For example, U+023A and U+2C65 are an upper
548        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
549        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
550        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
551        2-byte code at the end of the subject (it thought there wasn't enough data
552        left).
554    5.  Comprehensive information about what went wrong is now returned by
555        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
556        as the output vector has at least 2 elements. The offset of the start of
557        the failing character and a reason code are placed in the vector.
559    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
560        now returned is for the first byte of the failing character, instead of the
561        last byte inspected. This is an incompatible change, but I hope it is small
562        enough not to be a problem. It makes the returned offset consistent with
563        pcre_exec() and pcre_dfa_exec().
565    7.  pcretest now gives a text phrase as well as the error number when
566        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
567        failure, the offset and reason code are output.
569    8.  When \R was used with a maximizing quantifier it failed to skip backwards
570        over a \r\n pair if the subsequent match failed. Instead, it just skipped
571        back over a single character (\n). This seems wrong (because it treated the
572        two characters as a single entity when going forwards), conflicts with the
573        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
574        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
575        has been changed.
577    9.  Some internal refactoring has changed the processing so that the handling
578        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
579        time (the PCRE_DOTALL option was changed this way some time ago: version
580        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
581        which was always a bit of a fudge. It also means that there is one less
582        argument for the match() function, which reduces its stack requirements
583        slightly. This change also fixes an incompatibility with Perl: the pattern
584        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
586    10. More internal refactoring has drastically reduced the number of recursive
587        calls to match() for possessively repeated groups such as (abc)++ when
588        using pcre_exec().
590    11. While implementing 10, a number of bugs in the handling of groups were
591        discovered and fixed:
593        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
594        (a|)*(?1) gave a compile-time internal error.
595        ((a|)+)+  did not notice that the outer group could match an empty string.
596        (^a|^)+   was not marked as anchored.
597        (.*a|.*)+ was not marked as matching at start or after a newline.
599    12. Yet more internal refactoring has removed another argument from the match()
600        function. Special calls to this function are now indicated by setting a
601        value in a variable in the "match data" data block.
603    13. Be more explicit in pcre_study() instead of relying on "default" for
604        opcodes that mean there is no starting character; this means that when new
605        ones are added and accidentally left out of pcre_study(), testing should
606        pick them up.
608    14. The -s option of pcretest has been documented for ages as being an old
609        synonym of -m (show memory usage). I have changed it to mean "force study
610        for every regex", that is, assume /S for every regex. This is similar to -i
611        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
612        using it. It makes it easier to run collections of tests with and without
613        study enabled, and thereby test pcre_study() more easily. All the standard
614        tests are now run with and without -s (but some patterns can be marked as
615        "never study" - see 20 below).
617    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
618        restoration of the capturing data to the outer values was not happening
619        correctly.
621    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
622        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
623        pattern had matched an empty string, and so incorrectly returned a no
624        match.
626    17. There was optimizing code for the last branch of non-capturing parentheses,
627        and also for the obeyed branch of a conditional subexpression, which used
628        tail recursion to cut down on stack usage. Unfortunately, now that there is
629        the possibility of (*THEN) occurring in these branches, tail recursion is
630        no longer possible because the return has to be checked for (*THEN). These
631        two optimizations have therefore been removed. [But see 8.20/11 above.]
633    18. If a pattern containing \R was studied, it was assumed that \R always
634        matched two bytes, thus causing the minimum subject length to be
635        incorrectly computed because \R can also match just one byte.
637    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
638        was incorrectly computed.
640    20. If /S is present twice on a test pattern in pcretest input, it now
641        *disables* studying, thereby overriding the use of -s on the command line
642        (see 14 above). This is necessary for one or two tests to keep the output
643        identical in both cases.
645    21. When (*ACCEPT) was used in an assertion that matched an empty string and
646        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
648    22. When an atomic group that contained a capturing parenthesis was
649        successfully matched, but the branch in which it appeared failed, the
650        capturing was not being forgotten if a higher numbered group was later
651        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
652        group 1 to "a", when in fact it should be unset. This applied to multi-
653        branched capturing and non-capturing groups, repeated or not, and also to
654        positive assertions (capturing in negative assertions does not happen
655        in PCRE) and also to nested atomic groups.
657    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
658        subject after a captured substring, to make it easier to tell which of a
659        number of identical substrings has been captured.
661    24. The way atomic groups are processed by pcre_exec() has been changed so that
662        if they are repeated, backtracking one repetition now resets captured
663        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
664        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
665        "aaa". Previously, it would have been "a". As part of this code
666        refactoring, the way recursive calls are handled has also been changed.
668    25. If an assertion condition captured any substrings, they were not passed
669        back unless some other capturing happened later. For example, if
670        (?(?=(a))a) was matched against "a", no capturing was returned.
672    26. When studying a pattern that contained subroutine calls or assertions,
673        the code for finding the minimum length of a possible match was handling
674        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
675        group 1 called group 2 while simultaneously a separate group 2 called group
676        1). A stack overflow occurred in this case. I have fixed this by limiting
677        the recursion depth to 10.
679    27. Updated RunTest.bat in the distribution to the version supplied by Tom
680        Fortmann. This supports explicit test numbers on the command line, and has
681        argument validation and error reporting.
683    28. An instance of \X with an unlimited repeat could fail if at any point the
684        first character it looked at was a mark character.
686    29. Some minor code refactoring concerning Unicode properties and scripts
687        should reduce the stack requirement of match() slightly.
689    30. Added the '=' option to pcretest to check the setting of unused capturing
690        slots at the end of the pattern, which are documented as being -1, but are
691        not included in the return count.
693    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
694        compiled something random. Now it gives a compile-time error (as does
695        Perl).
697    32. A *MARK encountered during the processing of a positive assertion is now
698        recorded and passed back (compatible with Perl).
700    33. If --only-matching or --colour was set on a pcregrep call whose pattern
701        had alternative anchored branches, the search for a second match in a line
702        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
703        matched the line "0102" twice. The same bug affected patterns that started
704        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
705        twice.
707    34. Previously, PCRE did not allow quantification of assertions. However, Perl
708        does, and because of capturing effects, quantifying parenthesized
709        assertions may at times be useful. Quantifiers are now allowed for
710        parenthesized assertions.
712    35. A minor code tidy in pcre_compile() when checking options for \R usage.
714    36. \g was being checked for fancy things in a character class, when it should
715        just be a literal "g".
717    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
718        appearance of a nested POSIX class supersedes an apparent external class.
719        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
720        unescaped square brackets may also appear as part of class names. For
721        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
722        more like Perl. (But see 8.20/1 above.)
724    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
725        was because it thought it was \N{name}, which is not supported).
727    39. Add minix to OS list not supporting the -S option in pcretest.
729    40. PCRE tries to detect cases of infinite recursion at compile time, but it
730        cannot analyze patterns in sufficient detail to catch mutual recursions
731        such as ((?1))((?2)). There is now a runtime test that gives an error if a
732        subgroup is called recursively as a subpattern for a second time at the
733        same position in the subject string. In previous releases this might have
734        been caught by the recursion limit, or it might have run out of stack.
736    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
737        happen only once. PCRE was, however incorrectly giving a compile time error
738        "recursive call could loop indefinitely" because it cannot analyze the
739        pattern in sufficient detail. The compile time test no longer happens when
740        PCRE is compiling a conditional subpattern, but actual runaway loops are
741        now caught at runtime (see 40 above).
743    42. It seems that Perl allows any characters other than a closing parenthesis
744        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
745        has been changed to be the same.
747    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
748        as not to get warnings when autogen.sh is called. Also changed
749        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
751    44. To help people who use pcregrep to scan files containing exceedingly long
752        lines, the following changes have been made:
754        (a) The default value of the buffer size parameter has been increased from
755            8K to 20K. (The actual buffer used is three times this size.)
757        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
758            PCRE is built.
760        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
761            to be set at run time.
763        (d) Numerical values in pcregrep options can be followed by K or M, for
764            example --buffer-size=50K.
766        (e) If a line being scanned overflows pcregrep's buffer, an error is now
767            given and the return code is set to 2.
769    45. Add a pointer to the latest mark to the callout data block.
771    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
772        partial match of an empty string instead of no match. This was specific to
773        the use of ".".
775    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
776        complete match instead of a partial match. This bug was dependent on both
777        the PCRE_UTF8 and PCRE_DOTALL options being set.
779    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
780        starting byte set, because \b was not being ignored.
783    Version 8.12 15-Jan-2011
784    ------------------------
786    1.  Fixed some typos in the markup of the man pages, and wrote a script that
787        checks for such things as part of the documentation building process.
789    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
790        --match-limit and --recursion-limit options (added for 8.11). In
791        particular, this made one of the standard tests fail. (The integer value
792        went into the wrong half of a long int.)
794    3.  If the --colour option was given to pcregrep with -v (invert match), it
795        did strange things, either producing crazy output, or crashing. It should,
796        of course, ignore a request for colour when reporting lines that do not
797        match.
799    4.  Another pcregrep bug caused similar problems if --colour was specified with
800        -M (multiline) and the pattern match finished with a line ending.
802    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
803        matched in multiline mode, the following line was shown as part of the
804        match. This seems wrong, so I have changed it.
806    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
807        the check for further matches in the same line (so they could be coloured)
808        to overrun the end of the current line. If another match was found, it was
809        incorrectly shown (and then shown again when found in the next line).
811    7.  If pcregrep was compiled under Windows, there was a reference to the
812        function pcregrep_exit() before it was defined. I am assuming this was
813        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
814        reported by a user. I've moved the definition above the reference.
817    Version 8.11 10-Dec-2010
818    ------------------------
820    1.  (*THEN) was not working properly if there were untried alternatives prior
821        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
822        backtracked to try for "b" instead of moving to the next alternative branch
823        at the same level (in this case, to look for "c"). The Perl documentation
824        is clear that when (*THEN) is backtracked onto, it goes to the "next
825        alternative in the innermost enclosing group".
827    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
828        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
829        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
830        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
831        (*THEN).
833    3.  If \s appeared in a character class, it removed the VT character from
834        the class, even if it had been included by some previous item, for example
835        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
836        of \s, but is part of the POSIX "space" class.)
838    4.  A partial match never returns an empty string (because you can always
839        match an empty string at the end of the subject); however the checking for
840        an empty string was starting at the "start of match" point. This has been
841        changed to the "earliest inspected character" point, because the returned
842        data for a partial match starts at this character. This means that, for
843        example, /(?<=abc)def/ gives a partial match for the subject "abc"
844        (previously it gave "no match").
846    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
847        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
848        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
849        has an implication that the given string is incomplete (because a partial
850        match is preferred over a full match). For this reason, these items now
851        give a partial match in this situation. [Aside: previously, the one case
852        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
853        match rather than a full match, which was wrong by the old rules, but is
854        now correct.]
856    6.  There was a bug in the handling of #-introduced comments, recognized when
857        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
858        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
859        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
860        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
861        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
862        places in pcre_compile().
864    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
865        comments when looking ahead for named forward references to subpatterns,
866        the only newline sequence it recognized was NL. It now handles newlines
867        according to the set newline convention.
869    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
870        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
871        cater for a lack of strerror(). These oversights have been fixed.
873    9.  Added --match-limit and --recursion-limit to pcregrep.
875    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
877    11. When the -o option was used, pcregrep was setting a return code of 1, even
878        when matches were found, and --line-buffered was not being honoured.
880    12. Added an optional parentheses number to the -o and --only-matching options
881        of pcregrep.
883    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
884        can match an empty string. The code to do it in pcretest and pcredemo
885        needed fixing:
887        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
888            only one byte after an empty string match just before CRLF (this case
889            just got forgotten; "any" and "anycrlf" were OK).
891        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
892            mode when an empty string match preceded an ASCII character followed by
893            a non-ASCII character. (The code for advancing by one character rather
894            than one byte was nonsense.)
896        (c) The pcredemo.c sample program did not have any code at all to handle
897            the cases when CRLF is a valid newline sequence.
899    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
900        as a starting offset was within the subject string. There is now a new
901        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
902        negative or greater than the length of the string. In order to test this,
903        pcretest is extended to allow the setting of negative starting offsets.
905    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
906        starting offset points to the beginning of a UTF-8 character was
907        unnecessarily clumsy. I tidied it up.
909    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
910        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
912    17. Nobody had reported that the --include_dir option, which was added in
913        release 7.7 should have been called --include-dir (hyphen, not underscore)
914        for compatibility with GNU grep. I have changed it to --include-dir, but
915        left --include_dir as an undocumented synonym, and the same for
916        --exclude-dir, though that is not available in GNU grep, at least as of
917        release 2.5.4.
919    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
920        characters from a string of bytes) have been redefined so as not to use
921        loops, in order to improve performance in some environments. At the same
922        time, I abstracted some of the common code into auxiliary macros to save
923        repetition (this should not affect the compiled code).
925    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
926        compile-time error is now given if \c is not followed by an ASCII
927        character, that is, a byte less than 128. (In EBCDIC mode, the code is
928        different, and any byte value is allowed.)
930    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
931        START_OPTIMIZE option, which is now allowed at compile time - but just
932        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
933        to pcregrep and other applications that have no direct access to PCRE
934        options. The new /Y option in pcretest sets this option when calling
935        pcre_compile().
937    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
938        back references. Groups containing recursive back references were forced to
939        be atomic by that change, but in the case of named groups, the amount of
940        memory required was incorrectly computed, leading to "Failed: internal
941        error: code overflow". This has been fixed.
943    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
944        pcretest.c, to avoid build problems in some Borland environments.
947    Version 8.10 25-Jun-2010
948    ------------------------
950    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
951        THEN.
953    2.  (*ACCEPT) was not working when inside an atomic group.
955    3.  Inside a character class, \B is treated as a literal by default, but
956        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
957        causes the error). The code is unchanged, but I tidied the documentation.
959    4.  Inside a character class, PCRE always treated \R and \X as literals,
960        whereas Perl faults them if its -w option is set. I have changed PCRE so
961        that it faults them when PCRE_EXTRA is set.
963    5.  Added support for \N, which always matches any character other than
964        newline. (It is the same as "." when PCRE_DOTALL is not set.)
966    6.  When compiling pcregrep with newer versions of gcc which may have
967        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
968        declared with attribute warn_unused_result" were given. Just casting the
969        result to (void) does not stop the warnings; a more elaborate fudge is
970        needed. I've used a macro to implement this.
972    7.  Minor change to pcretest.c to avoid a compiler warning.
974    8.  Added four artifical Unicode properties to help with an option to make
975        \s etc use properties (see next item). The new properties are: Xan
976        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
978    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
979        use Unicode properties. (*UCP) at the start of a pattern can be used to set
980        this option. Modified pcretest to add /W to test this facility. Added
981        REG_UCP to make it available via the POSIX interface.
983    10. Added --line-buffered to pcregrep.
985    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
986        studied, and the match started with a letter with a code point greater than
987        127 whose first byte was different to the first byte of the other case of
988        the letter, the other case of this starting letter was not recognized
989        (#976).
991    12. If a pattern that was studied started with a repeated Unicode property
992        test, for example, \p{Nd}+, there was the theoretical possibility of
993        setting up an incorrect bitmap of starting bytes, but fortunately it could
994        not have actually happened in practice until change 8 above was made (it
995        added property types that matched character-matching opcodes).
997    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
998        possible starting bytes for non-anchored patterns.
1000    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1001        \R, and also a number of cases that involve Unicode properties, both
1002        explicit and implicit when PCRE_UCP is set.
1004    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1005        input, it could crash or give wrong results if characters with values
1006        greater than 0xc0 were present in the subject string. (Detail: it assumed
1007        UTF-8 input when processing these items.)
1009    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1010        size_t is 64-bit (#991).
1012    17. Added a check for running out of memory when PCRE is compiled with
1013        --disable-stack-for-recursion (#990).
1015    18. If the last data line in a file for pcretest does not have a newline on
1016        the end, a newline was missing in the output.
1018    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1019        less than 128) in its various bitmaps. However, there is a facility for
1020        generating tables according to the current locale when PCRE is compiled. It
1021        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1022        characters, are recognized by isspace() and therefore were getting set in
1023        these tables, and indeed these tables seem to approximate to ISO 8859. This
1024        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1025        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1026        which of course cannot start UTF-8 characters. I have changed the code so
1027        that only real ASCII characters (less than 128) and the correct starting
1028        bytes for UTF-8 encodings are set for characters greater than 127 when in
1029        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1030        altogether.)
1032    20. Added the /T option to pcretest so as to be able to run tests with non-
1033        standard character tables, thus making it possible to include the tests
1034        used for 19 above in the standard set of tests.
1036    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1037        reference to a subpattern the other side of a comment that contains an
1038        opening parenthesis caused either an internal compiling error, or a
1039        reference to the wrong subpattern.
1042    Version 8.02 19-Mar-2010
1043  ------------------------  ------------------------
1045  1.  The Unicode data tables have been updated to Unicode 5.2.0.  1.  The Unicode data tables have been updated to Unicode 5.2.0.

Removed from v.507  
changed lines
  Added in v.1041

  ViewVC Help
Powered by ViewVC 1.1.5