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

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

  ViewVC Help
Powered by ViewVC 1.1.5