ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 600 by ph10, Mon May 9 08:54:11 2011 UTC revision 1035 by ph10, Mon Sep 10 16:23:12 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 30-Apr-2011  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.
79    Version 8.31 06-July-2012
80    -------------------------
82    1.  Fixing a wrong JIT test case and some compiler warnings.
84    2.  Removed a bashism from the RunTest script.
86    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
87        to unsigned type, result still unsigned" that was given by an MS compiler
88        on encountering the code "-sizeof(xxx)".
90    4.  Partial matching support is added to the JIT compiler.
92    5.  Fixed several bugs concerned with partial matching of items that consist
93        of more than one character:
95        (a) /^(..)\1/ did not partially match "aba" because checking references was
96            done on an "all or nothing" basis. This also applied to repeated
97            references.
99        (b) \R did not give a hard partial match if \r was found at the end of the
100            subject.
102        (c) \X did not give a hard partial match after matching one or more
103            characters at the end of the subject.
105        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
106            a partial match for the string "\r".
108        (e) When newline was set to CRLF, the metacharacter "." did not recognize
109            a partial match for a CR character at the end of the subject string.
111    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
112        running pcretest, the text "(JIT)" added to the output whenever JIT is
113        actually used to run the match.
115    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
116        or /S+[+] with a digit between 1 and 7.
118    8.  OP_NOT now supports any UTF character not just single-byte ones.
120    9.  (*MARK) control verb is now supported by the JIT compiler.
122    10. The command "./RunTest list" lists the available tests without actually
123        running any of them. (Because I keep forgetting what they all are.)
127    12. Applied a (slightly modified) user-supplied patch that improves performance
128        when the heap is used for recursion (compiled with --disable-stack-for-
129        recursion). Instead of malloc and free for each heap frame each time a
130        logical recursion happens, frames are retained on a chain and re-used where
131        possible. This sometimes gives as much as 30% improvement.
133    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
134        call.
136    14. As documented, (*COMMIT) is now confined to within a positive assertion.
138    15. It is now possible to link pcretest with libedit as an alternative to
139        libreadline.
141    16. (*COMMIT) control verb is now supported by the JIT compiler.
143    17. The Unicode data tables have been updated to Unicode 6.1.0.
145    18. Added --file-list option to pcregrep.
147    19. Added binary file support to pcregrep, including the -a, --binary-files,
148        -I, and --text options.
150    20. The madvise function is renamed for posix_madvise for QNX compatibility
151        reasons. Fixed by Giuseppe D'Angelo.
153    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
155    22. Changed the option for creating symbolic links for 16-bit man pages from
156        -s to -sf so that re-installing does not cause issues.
158    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
160    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
161        matches in certain environments (the workspace was not being correctly
162        retained). Also added to pcre_dfa_exec() a simple plausibility check on
163        some of the workspace data at the beginning of a restart.
165    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
166        was not doing so when it should - probably a typo introduced by SVN 528
167        (change 8.10/14).
169    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
170        \w+ when the character tables indicated that \x{c4} was a word character.
171        There were several related cases, all because the tests for doing a table
172        lookup were testing for characters less than 127 instead of 255.
174    27. If a pattern contains capturing parentheses that are not used in a match,
175        their slots in the ovector are set to -1. For those that are higher than
176        any matched groups, this happens at the end of processing. In the case when
177        there were back references that the ovector was too small to contain
178        (causing temporary malloc'd memory to be used during matching), and the
179        highest capturing number was not used, memory off the end of the ovector
180        was incorrectly being set to -1. (It was using the size of the temporary
181        memory instead of the true size.)
183    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
184        ovector size, it uses memory at the end of the block that it has got.
186    29. Check for an overlong MARK name and give an error at compile time. The
187        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
189    30. JIT compiler update.
191    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
192        Rill for the patch.
194    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
196    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
198    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
199        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
200        was enabled.
202    35. Improve JIT code generation for greedy plus quantifier.
204    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
205        1 to "aa" instead of to an empty string. The bug affected repeated groups
206        that could potentially match an empty string.
208    37. Optimizing single character iterators in JIT.
210    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
211        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
212        codepoints that are too big for the mode are faulted, and in a UTF mode,
213        disallowed codepoints are also faulted.
215    39. If PCRE was compiled with UTF support, in three places in the DFA
216        matcher there was code that should only have been obeyed in UTF mode, but
217        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
218        processing when bytes with values greater than 127 were present. In 16-bit
219        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
220        both cases the values are those that cannot be the first data item in a UTF
221        character. The three items that might have provoked this were recursions,
222        possessively repeated groups, and atomic groups.
224    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
225        and pcregrep, because some OS require shared objects to be explicitly
226        passed to ld, causing the link step to fail if they are not.
228    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
229        mode, patterns that started with \h* or \R* might be incorrectly matched.
232    Version 8.30 04-February-2012
233    -----------------------------
235    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
236        name is defined in ctype.h.
238    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
239        only in quite long subpatterns.
241    3.  Removed the function pcre_info(), which has been obsolete and deprecated
242        since it was replaced by pcre_fullinfo() in February 2000.
244    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
245        match a (*MARK), and the match failed at the start of the subject, a
246        reference to memory before the start of the subject could occur. This bug
247        was introduced by fix 17 of release 8.21.
249    5.  A reference to an unset group with zero minimum repetition was giving
250        totally wrong answers (in non-JavaScript-compatibility mode). For example,
251        /(another)?(\1?)test/ matched against "hello world test". This bug was
252        introduced in release 8.13.
254    6.  Add support for 16-bit character strings (a large amount of work involving
255        many changes and refactorings).
257    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
258        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
259        from a file.
261    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
262        rounding is not applied in this particular case).
264    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
265        if they appear, or are escaped, in patterns.
267    10. Get rid of a number of -Wunused-but-set-variable warnings.
269    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
270        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
271        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
272        also returns the mark "x". This bug applied to capturing parentheses,
273        non-capturing parentheses, and atomic parentheses. It also applied to some
274        assertions.
276    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
277        information out of configure.ac instead of relying on pcre.h.generic, which
278        is not stored in the repository.
280    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
281        -lreadline.
283    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
285    15. Applied Graycode's patch to put the top-level frame on the stack rather
286        than the heap when not using the stack for recursion. This gives a
287        performance improvement in many cases when recursion is not deep.
289    16. Experimental code added to "pcretest -C" to output the stack frame size.
292    Version 8.21 12-Dec-2011
293    ------------------------
295    1.  Updating the JIT compiler.
297    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
298        are added as well.
300    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
301        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
302        calling _pcre_jit_exec. Some extra comments are added.
304    4.  (*MARK) settings inside atomic groups that do not contain any capturing
305        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
306        was introduced by change 18 for 8.20.
308    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
309        ECMA-262 standard.
311    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
312        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
313        This bug was probably introduced by change 9 of 8.13.
315    7.  While fixing 6 above, I noticed that a number of other items were being
316        incorrectly rejected as "not fixed length". This arose partly because newer
317        opcodes had not been added to the fixed-length checking code. I have (a)
318        corrected the bug and added tests for these items, and (b) arranged for an
319        error to occur if an unknown opcode is encountered while checking for fixed
320        length instead of just assuming "not fixed length". The items that were
321        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
322        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
323        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
325    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
326        being incorrectly compiled and would have given unpredicatble results.
328    9.  A possessively repeated subpattern with minimum repeat count greater than
329        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
330        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
331        the first (A) could occur when it should not.
333    10. Add a cast and remove a redundant test from the code.
335    11. JIT should use pcre_malloc/pcre_free for allocation.
337    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
338        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
339        is anything other than /usr, -L is still shown).
341    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
343    14. Perl does not support \N without a following name in a [] class; PCRE now
344        also gives an error.
346    15. If a forward reference was repeated with an upper limit of around 2000,
347        it caused the error "internal error: overran compiling workspace". The
348        maximum number of forward references (including repeats) was limited by the
349        internal workspace, and dependent on the LINK_SIZE. The code has been
350        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
351        the default depends on LINK_SIZE. There is a new upper limit (for safety)
352        of around 200,000 forward references. While doing this, I also speeded up
353        the filling in of repeated forward references.
355    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
356        incorrectly expecting the subject to contain another "a" after the start.
358    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
359        in the match, the SKIP should be ignored. This was not happening; instead
360        the SKIP was being treated as NOMATCH. For patterns such as
361        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
362        tested.
364    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
365        now much more compatible with Perl, in particular in cases where the result
366        is a non-match for a non-anchored pattern. For example, if
367        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
368        "m", where previously it did not return a name. A side effect of this
369        change is that for partial matches, the last encountered mark name is
370        returned, as for non matches. A number of tests that were previously not
371        Perl-compatible have been moved into the Perl-compatible test files. The
372        refactoring has had the pleasing side effect of removing one argument from
373        the match() function, thus reducing its stack requirements.
375    19. If the /S+ option was used in pcretest to study a pattern using JIT,
376        subsequent uses of /S (without +) incorrectly behaved like /S+.
378    21. Retrieve executable code size support for the JIT compiler and fixing
379        some warnings.
381    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
382        not work when the shorter character appeared right at the end of the
383        subject string.
385    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
386        systems.
388    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
389        output it when the /M option is used in pcretest.
391    25. The CheckMan script was not being included in the distribution. Also, added
392        an explicit "perl" to run Perl scripts from the PrepareRelease script
393        because this is reportedly needed in Windows.
395    26. If study data was being save in a file and studying had not found a set of
396        "starts with" bytes for the pattern, the data written to the file (though
397        never used) was taken from uninitialized memory and so caused valgrind to
398        complain.
400    27. Updated RunTest.bat as provided by Sheri Pierce.
402    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
404    29. Computation of memory usage for the table of capturing group names was
405        giving an unnecessarily large value.
408    Version 8.20 21-Oct-2011
409    ------------------------
411    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
412        a POSIX class. After further experiments with Perl, which convinced me that
413        Perl has bugs and confusions, a closing square bracket is no longer allowed
414        in a POSIX name. This bug also affected patterns with classes that started
415        with full stops.
417    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
418        captured substring, but while checking the failing first alternative,
419        substring 1 is temporarily captured. If the output vector supplied to
420        pcre_exec() was not big enough for this capture, the yield of the function
421        was still zero ("insufficient space for captured substrings"). This cannot
422        be totally fixed without adding another stack variable, which seems a lot
423        of expense for a edge case. However, I have improved the situation in cases
424        such as /(a)(b)x|abc/ matched against "abc", where the return code
425        indicates that fewer than the maximum number of slots in the ovector have
426        been set.
428    3.  Related to (2) above: when there are more back references in a pattern than
429        slots in the output vector, pcre_exec() uses temporary memory during
430        matching, and copies in the captures as far as possible afterwards. It was
431        using the entire output vector, but this conflicts with the specification
432        that only 2/3 is used for passing back captured substrings. Now it uses
433        only the first 2/3, for compatibility. This is, of course, another edge
434        case.
436    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
437        main code base, and can be used by building with --enable-jit. When this is
438        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
439        runtime --no-jit option is given.
441    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
442        ovector, the return from the function was zero, implying that there were
443        other matches that did not fit. The correct "exactly full" value is now
444        returned.
446    6.  If a subpattern that was called recursively or as a subroutine contained
447        (*PRUNE) or any other control that caused it to give a non-standard return,
448        invalid errors such as "Error -26 (nested recursion at the same subject
449        position)" or even infinite loops could occur.
451    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
452        computing the minimum length on reaching *ACCEPT, and so ended up with the
453        wrong value of 1 rather than 0. Further investigation indicates that
454        computing a minimum subject length in the presence of *ACCEPT is difficult
455        (think back references, subroutine calls), and so I have changed the code
456        so that no minimum is registered for a pattern that contains *ACCEPT.
458    8.  If (*THEN) was present in the first (true) branch of a conditional group,
459        it was not handled as intended. [But see 16 below.]
461    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
462        Sheri Pierce.
464    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
465        the first byte in a match must be "a".
467    11. Change 17 for 8.13 increased the recursion depth for patterns like
468        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
469        pattern contains any instances of (*THEN). If it does not, the old
470        optimizations are restored. It would be nice to do this on a per-group
471        basis, but at the moment that is not feasible.
473    12. In some environments, the output of pcretest -C is CRLF terminated. This
474        broke RunTest's code that checks for the link size. A single white space
475        character after the value is now allowed for.
477    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
478        For "fr", it uses the Windows-specific input and output files.
480    14. If (*THEN) appeared in a group that was called recursively or as a
481        subroutine, it did not work as intended. [But see next item.]
483    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
484        pattern fragments (but not containing any | characters). If A and B are
485        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
486        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
487        D. In other words, Perl considers parentheses that do not contain any |
488        characters to be part of a surrounding alternative, whereas PCRE was
489        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
490        differently. PCRE now behaves in the same way as Perl, except in the case
491        of subroutine/recursion calls such as (?1) which have in any case always
492        been different (but PCRE had them first :-).
494    16. Related to 15 above: Perl does not treat the | in a conditional group as
495        creating alternatives. Such a group is treated in the same way as an
496        ordinary group without any | characters when processing (*THEN). PCRE has
497        been changed to match Perl's behaviour.
499    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
500        RunGrepTest script failed.
502    18. Change 22 for version 13 caused atomic groups to use more stack. This is
503        inevitable for groups that contain captures, but it can lead to a lot of
504        stack use in large patterns. The old behaviour has been restored for atomic
505        groups that do not contain any capturing parentheses.
507    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
508        suppress the check for a minimum subject length at run time. (If it was
509        given to pcre_exec() or pcre_dfa_exec() it did work.)
511    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
512        fail to work when decoding hex characters in data strings in EBCDIC
513        environments.
515    21. It appears that in at least one Mac OS environment, the isxdigit() function
516        is implemented as a macro that evaluates to its argument more than once,
517        contravening the C 90 Standard (I haven't checked a later standard). There
518        was an instance in pcretest which caused it to go wrong when processing
519        \x{...} escapes in subject strings. The has been rewritten to avoid using
520        things like p++ in the argument of isxdigit().
523    Version 8.13 16-Aug-2011
524  ------------------------  ------------------------
526  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 20  Version 8.13 30-Apr-2011 Line 539  Version 8.13 30-Apr-2011
539      code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a      code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
540      2-byte code at the end of the subject (it thought there wasn't enough data      2-byte code at the end of the subject (it thought there wasn't enough data
541      left).      left).
543  5.  Comprehensive information about what went wrong is now returned by  5.  Comprehensive information about what went wrong is now returned by
544      pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long      pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
545      as the output vector has at least 2 elements. The offset of the start of      as the output vector has at least 2 elements. The offset of the start of
546      the failing character and a reason code are placed in the vector.      the failing character and a reason code are placed in the vector.
548  6.  When the UTF-8 string check fails for pcre_compile(), the offset that is  6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
549      now returned is for the first byte of the failing character, instead of the      now returned is for the first byte of the failing character, instead of the
550      last byte inspected. This is an incompatible change, but I hope it is small      last byte inspected. This is an incompatible change, but I hope it is small
551      enough not to be a problem. It makes the returned offset consistent with      enough not to be a problem. It makes the returned offset consistent with
552      pcre_exec() and pcre_dfa_exec().      pcre_exec() and pcre_dfa_exec().
554  7.  pcretest now gives a text phrase as well as the error number when  7.  pcretest now gives a text phrase as well as the error number when
555      pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check      pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
556      failure, the offset and reason code are output.      failure, the offset and reason code are output.
558  8.  When \R was used with a maximizing quantifier it failed to skip backwards  8.  When \R was used with a maximizing quantifier it failed to skip backwards
559      over a \r\n pair if the subsequent match failed. Instead, it just skipped      over a \r\n pair if the subsequent match failed. Instead, it just skipped
560      back over a single character (\n). This seems wrong (because it treated the      back over a single character (\n). This seems wrong (because it treated the
561      two characters as a single entity when going forwards), conflicts with the      two characters as a single entity when going forwards), conflicts with the
562      documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the      documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
563      behaviour of \R* different to (\R)*, which also seems wrong. The behaviour      behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
564      has been changed.      has been changed.
566    9.  Some internal refactoring has changed the processing so that the handling
567        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
568        time (the PCRE_DOTALL option was changed this way some time ago: version
569        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
570        which was always a bit of a fudge. It also means that there is one less
571        argument for the match() function, which reduces its stack requirements
572        slightly. This change also fixes an incompatibility with Perl: the pattern
573        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
575    10. More internal refactoring has drastically reduced the number of recursive
576        calls to match() for possessively repeated groups such as (abc)++ when
577        using pcre_exec().
579    11. While implementing 10, a number of bugs in the handling of groups were
580        discovered and fixed:
582        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
583        (a|)*(?1) gave a compile-time internal error.
584        ((a|)+)+  did not notice that the outer group could match an empty string.
585        (^a|^)+   was not marked as anchored.
586        (.*a|.*)+ was not marked as matching at start or after a newline.
588    12. Yet more internal refactoring has removed another argument from the match()
589        function. Special calls to this function are now indicated by setting a
590        value in a variable in the "match data" data block.
592    13. Be more explicit in pcre_study() instead of relying on "default" for
593        opcodes that mean there is no starting character; this means that when new
594        ones are added and accidentally left out of pcre_study(), testing should
595        pick them up.
597    14. The -s option of pcretest has been documented for ages as being an old
598        synonym of -m (show memory usage). I have changed it to mean "force study
599        for every regex", that is, assume /S for every regex. This is similar to -i
600        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
601        using it. It makes it easier to run collections of tests with and without
602        study enabled, and thereby test pcre_study() more easily. All the standard
603        tests are now run with and without -s (but some patterns can be marked as
604        "never study" - see 20 below).
606    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
607        restoration of the capturing data to the outer values was not happening
608        correctly.
610    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
611        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
612        pattern had matched an empty string, and so incorrectly returned a no
613        match.
615    17. There was optimizing code for the last branch of non-capturing parentheses,
616        and also for the obeyed branch of a conditional subexpression, which used
617        tail recursion to cut down on stack usage. Unfortunately, now that there is
618        the possibility of (*THEN) occurring in these branches, tail recursion is
619        no longer possible because the return has to be checked for (*THEN). These
620        two optimizations have therefore been removed. [But see 8.20/11 above.]
622    18. If a pattern containing \R was studied, it was assumed that \R always
623        matched two bytes, thus causing the minimum subject length to be
624        incorrectly computed because \R can also match just one byte.
626    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
627        was incorrectly computed.
629    20. If /S is present twice on a test pattern in pcretest input, it now
630        *disables* studying, thereby overriding the use of -s on the command line
631        (see 14 above). This is necessary for one or two tests to keep the output
632        identical in both cases.
634    21. When (*ACCEPT) was used in an assertion that matched an empty string and
635        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
637    22. When an atomic group that contained a capturing parenthesis was
638        successfully matched, but the branch in which it appeared failed, the
639        capturing was not being forgotten if a higher numbered group was later
640        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
641        group 1 to "a", when in fact it should be unset. This applied to multi-
642        branched capturing and non-capturing groups, repeated or not, and also to
643        positive assertions (capturing in negative assertions does not happen
644        in PCRE) and also to nested atomic groups.
646    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
647        subject after a captured substring, to make it easier to tell which of a
648        number of identical substrings has been captured.
650    24. The way atomic groups are processed by pcre_exec() has been changed so that
651        if they are repeated, backtracking one repetition now resets captured
652        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
653        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
654        "aaa". Previously, it would have been "a". As part of this code
655        refactoring, the way recursive calls are handled has also been changed.
657    25. If an assertion condition captured any substrings, they were not passed
658        back unless some other capturing happened later. For example, if
659        (?(?=(a))a) was matched against "a", no capturing was returned.
661    26. When studying a pattern that contained subroutine calls or assertions,
662        the code for finding the minimum length of a possible match was handling
663        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
664        group 1 called group 2 while simultaneously a separate group 2 called group
665        1). A stack overflow occurred in this case. I have fixed this by limiting
666        the recursion depth to 10.
668    27. Updated RunTest.bat in the distribution to the version supplied by Tom
669        Fortmann. This supports explicit test numbers on the command line, and has
670        argument validation and error reporting.
672    28. An instance of \X with an unlimited repeat could fail if at any point the
673        first character it looked at was a mark character.
675    29. Some minor code refactoring concerning Unicode properties and scripts
676        should reduce the stack requirement of match() slightly.
678    30. Added the '=' option to pcretest to check the setting of unused capturing
679        slots at the end of the pattern, which are documented as being -1, but are
680        not included in the return count.
682    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
683        compiled something random. Now it gives a compile-time error (as does
684        Perl).
686    32. A *MARK encountered during the processing of a positive assertion is now
687        recorded and passed back (compatible with Perl).
689    33. If --only-matching or --colour was set on a pcregrep call whose pattern
690        had alternative anchored branches, the search for a second match in a line
691        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
692        matched the line "0102" twice. The same bug affected patterns that started
693        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
694        twice.
696    34. Previously, PCRE did not allow quantification of assertions. However, Perl
697        does, and because of capturing effects, quantifying parenthesized
698        assertions may at times be useful. Quantifiers are now allowed for
699        parenthesized assertions.
701    35. A minor code tidy in pcre_compile() when checking options for \R usage.
703    36. \g was being checked for fancy things in a character class, when it should
704        just be a literal "g".
706    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
707        appearance of a nested POSIX class supersedes an apparent external class.
708        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
709        unescaped square brackets may also appear as part of class names. For
710        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
711        more like Perl. (But see 8.20/1 above.)
713    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
714        was because it thought it was \N{name}, which is not supported).
716    39. Add minix to OS list not supporting the -S option in pcretest.
718    40. PCRE tries to detect cases of infinite recursion at compile time, but it
719        cannot analyze patterns in sufficient detail to catch mutual recursions
720        such as ((?1))((?2)). There is now a runtime test that gives an error if a
721        subgroup is called recursively as a subpattern for a second time at the
722        same position in the subject string. In previous releases this might have
723        been caught by the recursion limit, or it might have run out of stack.
725    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
726        happen only once. PCRE was, however incorrectly giving a compile time error
727        "recursive call could loop indefinitely" because it cannot analyze the
728        pattern in sufficient detail. The compile time test no longer happens when
729        PCRE is compiling a conditional subpattern, but actual runaway loops are
730        now caught at runtime (see 40 above).
732    42. It seems that Perl allows any characters other than a closing parenthesis
733        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
734        has been changed to be the same.
736    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
737        as not to get warnings when autogen.sh is called. Also changed
738        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
740    44. To help people who use pcregrep to scan files containing exceedingly long
741        lines, the following changes have been made:
743        (a) The default value of the buffer size parameter has been increased from
744            8K to 20K. (The actual buffer used is three times this size.)
746        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
747            PCRE is built.
749        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
750            to be set at run time.
752        (d) Numerical values in pcregrep options can be followed by K or M, for
753            example --buffer-size=50K.
755        (e) If a line being scanned overflows pcregrep's buffer, an error is now
756            given and the return code is set to 2.
758    45. Add a pointer to the latest mark to the callout data block.
760    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
761        partial match of an empty string instead of no match. This was specific to
762        the use of ".".
764    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
765        complete match instead of a partial match. This bug was dependent on both
766        the PCRE_UTF8 and PCRE_DOTALL options being set.
768    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
769        starting byte set, because \b was not being ignored.
772  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
773  ------------------------  ------------------------

Removed from v.600  
changed lines
  Added in v.1035

  ViewVC Help
Powered by ViewVC 1.1.5