ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 1244 by zherczeg, Tue Feb 5 12:03:43 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 02-Aug-2011  Version 8.33 xx-xxxx-201x
5    -------------------------
7    1.  Added 'U' to some constants that are compared to unsigned integers, to
8        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
9        variables that are added to signed variables, to ensure the result is
10        signed and can be negated.
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
15    3.  Revise the creation of config.h.generic so that all boolean macros are
16        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
17        overriding via -D on the command line possible.
19    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
20        to unsigned int is reported to make a quite noticeable speed difference in
21        a specific Windows environment. Testing on Linux did also appear to show
22        some benefit (and it is clearly not harmful). Also fixed the definition of
23        Xop which should be unsigned.
25    5.  Related to (4), changing the definition of the intermediate variable cc
26        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
27        improvements.
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
37    9.  Optimizing fast_forward_start_bits in JIT.
40    Version 8.32 30-November-2012
41    -----------------------------
43    1.  Improved JIT compiler optimizations for first character search and single
44        character iterators.
46    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
47        Patch by Daniel Richard G.
49    3.  Single character iterator optimizations in the JIT compiler.
51    4.  Improved JIT compiler optimizations for character ranges.
53    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
54        Reported by Giuseppe D'Angelo.
56    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
57        of a line, was being set incorrectly in cases where .* appeared inside
58        atomic brackets at the start of a pattern, or where there was a subsequent
59        *PRUNE or *SKIP.
61    7.  Improved instruction cache flush for POWER/PowerPC.
62        Patch by Daniel Richard G.
64    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
65        grep:
67        (a) There is now no limit to the number of patterns to be matched.
69        (b) An error is given if a pattern is too long.
71        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
72            are now supported.
74        (d) --exclude-from and --include-from (multiple use) have been added.
76        (e) Exclusions and inclusions now apply to all files and directories, not
77            just to those obtained from scanning a directory recursively.
79        (f) Multiple uses of -f and --file-list are now supported.
81        (g) In a Windows environment, the default for -d has been changed from
82            "read" (the GNU grep default) to "skip", because otherwise the presence
83            of a directory in the file list provokes an error.
85        (h) The documentation has been revised and clarified in places.
87    9.  Improve the matching speed of capturing brackets.
89    10. Changed the meaning of \X so that it now matches a Unicode extended
90        grapheme cluster.
92    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
93        out POSIX threads when JIT support is configured.
95    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
97    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
98        structure could go wrong in environments where size_t is not the same size
99        as int.
101    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
102        set.
104    15. The EBCDIC support had decayed; later updates to the code had included
105        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
106        general tidy up of EBCDIC-related issues, and the documentation was also
107        not quite right. There is now a test that can be run on ASCII systems to
108        check some of the EBCDIC-related things (but is it not a full test).
110    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
111        in a small tidy to the code.
113    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
115    18. If the --only-matching (-o) option in pcregrep is specified multiple
116        times, each one causes appropriate output. For example, -o1 -o2 outputs the
117        substrings matched by the 1st and 2nd capturing parentheses. A separating
118        string can be specified by --om-separator (default empty).
120    19. Improving the first n character searches.
122    20. Turn case lists for horizontal and vertical white space into macros so that
123        they are defined only once.
125    21. This set of changes together give more compatible Unicode case-folding
126        behaviour for characters that have more than one other case when UCP
127        support is available.
129        (a) The Unicode property table now has offsets into a new table of sets of
130            three or more characters that are case-equivalent. The MultiStage2.py
131            script that generates these tables (the pcre_ucd.c file) now scans
132            CaseFolding.txt instead of UnicodeData.txt for character case
133            information.
135        (b) The code for adding characters or ranges of characters to a character
136            class has been abstracted into a generalized function that also handles
137            case-independence. In UTF-mode with UCP support, this uses the new data
138            to handle characters with more than one other case.
140        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
141            whose other case is greater than 256 are now correctly matched
142            caselessly. Previously, the high codepoint matched the low one, but not
143            vice versa.
145        (d) The processing of \h, \H, \v, and \ in character classes now makes use
146            of the new class addition function, using character lists defined as
147            macros alongside the case definitions of 20 above.
149        (e) Caseless back references now work with characters that have more than
150            one other case.
152        (f) General caseless matching of characters with more than one other case
153            is supported.
155    22. Unicode character properties were updated from Unicode 6.2.0
157    23. Improved CMake support under Windows. Patch by Daniel Richard G.
159    24. Add support for 32-bit character strings, and UTF-32
161    25. Major JIT compiler update (code refactoring and bugfixing).
162        Experimental Sparc 32 support is added.
164    26. Applied a modified version of Daniel Richard G's patch to create
165        pcre.h.generic and config.h.generic by "make" instead of in the
166        PrepareRelease script.
168    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
169        pcre_compile.c when checking for a zero character.
171    28. Introducing a native interface for JIT. Through this interface, the compiled
172        machine code can be directly executed. The purpose of this interface is to
173        provide fast pattern matching, so several sanity checks are not performed.
174        However, feature tests are still performed. The new interface provides
175        1.4x speedup compared to the old one.
177    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
178        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
179        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
181    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
182        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
183        the "old" RFC 2279). Instead, it ended up passing a negative length to
184        pcre_exec().
186    31. Add support for GCC's visibility feature to hide internal functions.
188    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
189        "unknown -C option" after outputting 0 or 1.
191    33. There is now support for generating a code coverage report for the test
192        suite in environments where gcc is the compiler and lcov is installed. This
193        is mainly for the benefit of the developers.
195    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
196        unaddressable using valgrind annotations, allowing valgrind to detect
197        invalid memory accesses. This is mainly for the benefit of the developers.
199    25. (*UTF) can now be used to start a pattern in any of the three libraries.
201    26. Give configure error if --enable-cpp but no C++ compiler found.
204    Version 8.31 06-July-2012
205    -------------------------
207    1.  Fixing a wrong JIT test case and some compiler warnings.
209    2.  Removed a bashism from the RunTest script.
211    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
212        to unsigned type, result still unsigned" that was given by an MS compiler
213        on encountering the code "-sizeof(xxx)".
215    4.  Partial matching support is added to the JIT compiler.
217    5.  Fixed several bugs concerned with partial matching of items that consist
218        of more than one character:
220        (a) /^(..)\1/ did not partially match "aba" because checking references was
221            done on an "all or nothing" basis. This also applied to repeated
222            references.
224        (b) \R did not give a hard partial match if \r was found at the end of the
225            subject.
227        (c) \X did not give a hard partial match after matching one or more
228            characters at the end of the subject.
230        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
231            a partial match for the string "\r".
233        (e) When newline was set to CRLF, the metacharacter "." did not recognize
234            a partial match for a CR character at the end of the subject string.
236    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
237        running pcretest, the text "(JIT)" added to the output whenever JIT is
238        actually used to run the match.
240    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
241        or /S+[+] with a digit between 1 and 7.
243    8.  OP_NOT now supports any UTF character not just single-byte ones.
245    9.  (*MARK) control verb is now supported by the JIT compiler.
247    10. The command "./RunTest list" lists the available tests without actually
248        running any of them. (Because I keep forgetting what they all are.)
252    12. Applied a (slightly modified) user-supplied patch that improves performance
253        when the heap is used for recursion (compiled with --disable-stack-for-
254        recursion). Instead of malloc and free for each heap frame each time a
255        logical recursion happens, frames are retained on a chain and re-used where
256        possible. This sometimes gives as much as 30% improvement.
258    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
259        call.
261    14. As documented, (*COMMIT) is now confined to within a positive assertion.
263    15. It is now possible to link pcretest with libedit as an alternative to
264        libreadline.
266    16. (*COMMIT) control verb is now supported by the JIT compiler.
268    17. The Unicode data tables have been updated to Unicode 6.1.0.
270    18. Added --file-list option to pcregrep.
272    19. Added binary file support to pcregrep, including the -a, --binary-files,
273        -I, and --text options.
275    20. The madvise function is renamed for posix_madvise for QNX compatibility
276        reasons. Fixed by Giuseppe D'Angelo.
278    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
280    22. Changed the option for creating symbolic links for 16-bit man pages from
281        -s to -sf so that re-installing does not cause issues.
283    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
285    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
286        matches in certain environments (the workspace was not being correctly
287        retained). Also added to pcre_dfa_exec() a simple plausibility check on
288        some of the workspace data at the beginning of a restart.
290    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
291        was not doing so when it should - probably a typo introduced by SVN 528
292        (change 8.10/14).
294    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
295        \w+ when the character tables indicated that \x{c4} was a word character.
296        There were several related cases, all because the tests for doing a table
297        lookup were testing for characters less than 127 instead of 255.
299    27. If a pattern contains capturing parentheses that are not used in a match,
300        their slots in the ovector are set to -1. For those that are higher than
301        any matched groups, this happens at the end of processing. In the case when
302        there were back references that the ovector was too small to contain
303        (causing temporary malloc'd memory to be used during matching), and the
304        highest capturing number was not used, memory off the end of the ovector
305        was incorrectly being set to -1. (It was using the size of the temporary
306        memory instead of the true size.)
308    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
309        ovector size, it uses memory at the end of the block that it has got.
311    29. Check for an overlong MARK name and give an error at compile time. The
312        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
314    30. JIT compiler update.
316    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
317        Rill for the patch.
319    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
321    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
323    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
324        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
325        was enabled.
327    35. Improve JIT code generation for greedy plus quantifier.
329    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
330        1 to "aa" instead of to an empty string. The bug affected repeated groups
331        that could potentially match an empty string.
333    37. Optimizing single character iterators in JIT.
335    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
336        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
337        codepoints that are too big for the mode are faulted, and in a UTF mode,
338        disallowed codepoints are also faulted.
340    39. If PCRE was compiled with UTF support, in three places in the DFA
341        matcher there was code that should only have been obeyed in UTF mode, but
342        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
343        processing when bytes with values greater than 127 were present. In 16-bit
344        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
345        both cases the values are those that cannot be the first data item in a UTF
346        character. The three items that might have provoked this were recursions,
347        possessively repeated groups, and atomic groups.
349    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
350        and pcregrep, because some OS require shared objects to be explicitly
351        passed to ld, causing the link step to fail if they are not.
353    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
354        mode, patterns that started with \h* or \R* might be incorrectly matched.
357    Version 8.30 04-February-2012
358    -----------------------------
360    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
361        name is defined in ctype.h.
363    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
364        only in quite long subpatterns.
366    3.  Removed the function pcre_info(), which has been obsolete and deprecated
367        since it was replaced by pcre_fullinfo() in February 2000.
369    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
370        match a (*MARK), and the match failed at the start of the subject, a
371        reference to memory before the start of the subject could occur. This bug
372        was introduced by fix 17 of release 8.21.
374    5.  A reference to an unset group with zero minimum repetition was giving
375        totally wrong answers (in non-JavaScript-compatibility mode). For example,
376        /(another)?(\1?)test/ matched against "hello world test". This bug was
377        introduced in release 8.13.
379    6.  Add support for 16-bit character strings (a large amount of work involving
380        many changes and refactorings).
382    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
383        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
384        from a file.
386    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
387        rounding is not applied in this particular case).
389    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
390        if they appear, or are escaped, in patterns.
392    10. Get rid of a number of -Wunused-but-set-variable warnings.
394    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
395        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
396        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
397        also returns the mark "x". This bug applied to capturing parentheses,
398        non-capturing parentheses, and atomic parentheses. It also applied to some
399        assertions.
401    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
402        information out of configure.ac instead of relying on pcre.h.generic, which
403        is not stored in the repository.
405    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
406        -lreadline.
408    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
410    15. Applied Graycode's patch to put the top-level frame on the stack rather
411        than the heap when not using the stack for recursion. This gives a
412        performance improvement in many cases when recursion is not deep.
414    16. Experimental code added to "pcretest -C" to output the stack frame size.
417    Version 8.21 12-Dec-2011
418    ------------------------
420    1.  Updating the JIT compiler.
422    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
423        are added as well.
425    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
426        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
427        calling _pcre_jit_exec. Some extra comments are added.
429    4.  (*MARK) settings inside atomic groups that do not contain any capturing
430        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
431        was introduced by change 18 for 8.20.
433    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
434        ECMA-262 standard.
436    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
437        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
438        This bug was probably introduced by change 9 of 8.13.
440    7.  While fixing 6 above, I noticed that a number of other items were being
441        incorrectly rejected as "not fixed length". This arose partly because newer
442        opcodes had not been added to the fixed-length checking code. I have (a)
443        corrected the bug and added tests for these items, and (b) arranged for an
444        error to occur if an unknown opcode is encountered while checking for fixed
445        length instead of just assuming "not fixed length". The items that were
446        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
447        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
448        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
450    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
451        being incorrectly compiled and would have given unpredicatble results.
453    9.  A possessively repeated subpattern with minimum repeat count greater than
454        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
455        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
456        the first (A) could occur when it should not.
458    10. Add a cast and remove a redundant test from the code.
460    11. JIT should use pcre_malloc/pcre_free for allocation.
462    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
463        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
464        is anything other than /usr, -L is still shown).
466    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
468    14. Perl does not support \N without a following name in a [] class; PCRE now
469        also gives an error.
471    15. If a forward reference was repeated with an upper limit of around 2000,
472        it caused the error "internal error: overran compiling workspace". The
473        maximum number of forward references (including repeats) was limited by the
474        internal workspace, and dependent on the LINK_SIZE. The code has been
475        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
476        the default depends on LINK_SIZE. There is a new upper limit (for safety)
477        of around 200,000 forward references. While doing this, I also speeded up
478        the filling in of repeated forward references.
480    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
481        incorrectly expecting the subject to contain another "a" after the start.
483    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
484        in the match, the SKIP should be ignored. This was not happening; instead
485        the SKIP was being treated as NOMATCH. For patterns such as
486        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
487        tested.
489    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
490        now much more compatible with Perl, in particular in cases where the result
491        is a non-match for a non-anchored pattern. For example, if
492        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
493        "m", where previously it did not return a name. A side effect of this
494        change is that for partial matches, the last encountered mark name is
495        returned, as for non matches. A number of tests that were previously not
496        Perl-compatible have been moved into the Perl-compatible test files. The
497        refactoring has had the pleasing side effect of removing one argument from
498        the match() function, thus reducing its stack requirements.
500    19. If the /S+ option was used in pcretest to study a pattern using JIT,
501        subsequent uses of /S (without +) incorrectly behaved like /S+.
503    21. Retrieve executable code size support for the JIT compiler and fixing
504        some warnings.
506    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
507        not work when the shorter character appeared right at the end of the
508        subject string.
510    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
511        systems.
513    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
514        output it when the /M option is used in pcretest.
516    25. The CheckMan script was not being included in the distribution. Also, added
517        an explicit "perl" to run Perl scripts from the PrepareRelease script
518        because this is reportedly needed in Windows.
520    26. If study data was being save in a file and studying had not found a set of
521        "starts with" bytes for the pattern, the data written to the file (though
522        never used) was taken from uninitialized memory and so caused valgrind to
523        complain.
525    27. Updated RunTest.bat as provided by Sheri Pierce.
527    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
529    29. Computation of memory usage for the table of capturing group names was
530        giving an unnecessarily large value.
533    Version 8.20 21-Oct-2011
534    ------------------------
536    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
537        a POSIX class. After further experiments with Perl, which convinced me that
538        Perl has bugs and confusions, a closing square bracket is no longer allowed
539        in a POSIX name. This bug also affected patterns with classes that started
540        with full stops.
542    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
543        captured substring, but while checking the failing first alternative,
544        substring 1 is temporarily captured. If the output vector supplied to
545        pcre_exec() was not big enough for this capture, the yield of the function
546        was still zero ("insufficient space for captured substrings"). This cannot
547        be totally fixed without adding another stack variable, which seems a lot
548        of expense for a edge case. However, I have improved the situation in cases
549        such as /(a)(b)x|abc/ matched against "abc", where the return code
550        indicates that fewer than the maximum number of slots in the ovector have
551        been set.
553    3.  Related to (2) above: when there are more back references in a pattern than
554        slots in the output vector, pcre_exec() uses temporary memory during
555        matching, and copies in the captures as far as possible afterwards. It was
556        using the entire output vector, but this conflicts with the specification
557        that only 2/3 is used for passing back captured substrings. Now it uses
558        only the first 2/3, for compatibility. This is, of course, another edge
559        case.
561    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
562        main code base, and can be used by building with --enable-jit. When this is
563        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
564        runtime --no-jit option is given.
566    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
567        ovector, the return from the function was zero, implying that there were
568        other matches that did not fit. The correct "exactly full" value is now
569        returned.
571    6.  If a subpattern that was called recursively or as a subroutine contained
572        (*PRUNE) or any other control that caused it to give a non-standard return,
573        invalid errors such as "Error -26 (nested recursion at the same subject
574        position)" or even infinite loops could occur.
576    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
577        computing the minimum length on reaching *ACCEPT, and so ended up with the
578        wrong value of 1 rather than 0. Further investigation indicates that
579        computing a minimum subject length in the presence of *ACCEPT is difficult
580        (think back references, subroutine calls), and so I have changed the code
581        so that no minimum is registered for a pattern that contains *ACCEPT.
583    8.  If (*THEN) was present in the first (true) branch of a conditional group,
584        it was not handled as intended. [But see 16 below.]
586    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
587        Sheri Pierce.
589    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
590        the first byte in a match must be "a".
592    11. Change 17 for 8.13 increased the recursion depth for patterns like
593        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
594        pattern contains any instances of (*THEN). If it does not, the old
595        optimizations are restored. It would be nice to do this on a per-group
596        basis, but at the moment that is not feasible.
598    12. In some environments, the output of pcretest -C is CRLF terminated. This
599        broke RunTest's code that checks for the link size. A single white space
600        character after the value is now allowed for.
602    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
603        For "fr", it uses the Windows-specific input and output files.
605    14. If (*THEN) appeared in a group that was called recursively or as a
606        subroutine, it did not work as intended. [But see next item.]
608    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
609        pattern fragments (but not containing any | characters). If A and B are
610        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
611        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
612        D. In other words, Perl considers parentheses that do not contain any |
613        characters to be part of a surrounding alternative, whereas PCRE was
614        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
615        differently. PCRE now behaves in the same way as Perl, except in the case
616        of subroutine/recursion calls such as (?1) which have in any case always
617        been different (but PCRE had them first :-).
619    16. Related to 15 above: Perl does not treat the | in a conditional group as
620        creating alternatives. Such a group is treated in the same way as an
621        ordinary group without any | characters when processing (*THEN). PCRE has
622        been changed to match Perl's behaviour.
624    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
625        RunGrepTest script failed.
627    18. Change 22 for version 13 caused atomic groups to use more stack. This is
628        inevitable for groups that contain captures, but it can lead to a lot of
629        stack use in large patterns. The old behaviour has been restored for atomic
630        groups that do not contain any capturing parentheses.
632    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
633        suppress the check for a minimum subject length at run time. (If it was
634        given to pcre_exec() or pcre_dfa_exec() it did work.)
636    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
637        fail to work when decoding hex characters in data strings in EBCDIC
638        environments.
640    21. It appears that in at least one Mac OS environment, the isxdigit() function
641        is implemented as a macro that evaluates to its argument more than once,
642        contravening the C 90 Standard (I haven't checked a later standard). There
643        was an instance in pcretest which caused it to go wrong when processing
644        \x{...} escapes in subject strings. The has been rewritten to avoid using
645        things like p++ in the argument of isxdigit().
648    Version 8.13 16-Aug-2011
649  ------------------------  ------------------------
651  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 98  Version 8.13 02-Aug-2011 Line 742  Version 8.13 02-Aug-2011
742      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
743      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
744      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
745      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
747  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
748      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 833  Version 8.13 02-Aug-2011
833      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
834      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
835      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
836      more like Perl.      more like Perl. (But see 8.20/1 above.)
838  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
839      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 868  Version 8.13 02-Aug-2011
868      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
869          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
871      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
872          PCRE is built.          PCRE is built.
874      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 245  Version 8.13 02-Aug-2011 Line 889  Version 8.13 02-Aug-2011
889  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
890      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
891      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
893  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
894      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
897  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011

Removed from v.657  
changed lines
  Added in v.1244

  ViewVC Help
Powered by ViewVC 1.1.5