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

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

  ViewVC Help
Powered by ViewVC 1.1.5