ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 580 by ph10, Fri Nov 26 11:16:43 2010 UTC revision 1253 by ph10, Fri Feb 22 11:38:35 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.11 24-Nov-2010  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.
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
44        (b) Minimum length was not checked before the matching is started.
46    11. The value of capture_last that is passed to callouts was incorrect in some
47        cases when there was a capture on one path that was subsequently abandoned
48        after a backtrack. Also, the capture_last value is now reset after a
49        recursion, since all captures are also reset in this case.
51    12. The interpreter no longer returns the "too many substrings" error in the
52        case when an overflowing capture is in a branch that is subsequently
53        abandoned after a backtrack.
55    13. In the pathological case when an offset vector of size 2 is used, pcretest
56        now prints out the matched string after a yield of 0 or 1.
58    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
59        Only supported by the JIT compiler at the moment.
61    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
63    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
64        offset of the starting point of the matching process, provided the offsets
65        vector is large enough.
67    17. The \A escape now records a lookbehind value of 1, though its execution
68        does not actually inspect the previous character. This is to ensure that,
69        in partial multi-segment matching, at least one character from the old
70        segment is retained when a new segment is processed. Otherwise, if there
71        are no lookbehinds in the pattern, \A might match incorrectly at the start
72        of a new segment.
75    Version 8.32 30-November-2012
76    -----------------------------
78    1.  Improved JIT compiler optimizations for first character search and single
79        character iterators.
81    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
82        Patch by Daniel Richard G.
84    3.  Single character iterator optimizations in the JIT compiler.
86    4.  Improved JIT compiler optimizations for character ranges.
88    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
89        Reported by Giuseppe D'Angelo.
91    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
92        of a line, was being set incorrectly in cases where .* appeared inside
93        atomic brackets at the start of a pattern, or where there was a subsequent
94        *PRUNE or *SKIP.
96    7.  Improved instruction cache flush for POWER/PowerPC.
97        Patch by Daniel Richard G.
99    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
100        grep:
102        (a) There is now no limit to the number of patterns to be matched.
104        (b) An error is given if a pattern is too long.
106        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
107            are now supported.
109        (d) --exclude-from and --include-from (multiple use) have been added.
111        (e) Exclusions and inclusions now apply to all files and directories, not
112            just to those obtained from scanning a directory recursively.
114        (f) Multiple uses of -f and --file-list are now supported.
116        (g) In a Windows environment, the default for -d has been changed from
117            "read" (the GNU grep default) to "skip", because otherwise the presence
118            of a directory in the file list provokes an error.
120        (h) The documentation has been revised and clarified in places.
122    9.  Improve the matching speed of capturing brackets.
124    10. Changed the meaning of \X so that it now matches a Unicode extended
125        grapheme cluster.
127    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
128        out POSIX threads when JIT support is configured.
130    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
132    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
133        structure could go wrong in environments where size_t is not the same size
134        as int.
136    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
137        set.
139    15. The EBCDIC support had decayed; later updates to the code had included
140        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
141        general tidy up of EBCDIC-related issues, and the documentation was also
142        not quite right. There is now a test that can be run on ASCII systems to
143        check some of the EBCDIC-related things (but is it not a full test).
145    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
146        in a small tidy to the code.
148    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
150    18. If the --only-matching (-o) option in pcregrep is specified multiple
151        times, each one causes appropriate output. For example, -o1 -o2 outputs the
152        substrings matched by the 1st and 2nd capturing parentheses. A separating
153        string can be specified by --om-separator (default empty).
155    19. Improving the first n character searches.
157    20. Turn case lists for horizontal and vertical white space into macros so that
158        they are defined only once.
160    21. This set of changes together give more compatible Unicode case-folding
161        behaviour for characters that have more than one other case when UCP
162        support is available.
164        (a) The Unicode property table now has offsets into a new table of sets of
165            three or more characters that are case-equivalent. The MultiStage2.py
166            script that generates these tables (the pcre_ucd.c file) now scans
167            CaseFolding.txt instead of UnicodeData.txt for character case
168            information.
170        (b) The code for adding characters or ranges of characters to a character
171            class has been abstracted into a generalized function that also handles
172            case-independence. In UTF-mode with UCP support, this uses the new data
173            to handle characters with more than one other case.
175        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
176            whose other case is greater than 256 are now correctly matched
177            caselessly. Previously, the high codepoint matched the low one, but not
178            vice versa.
180        (d) The processing of \h, \H, \v, and \ in character classes now makes use
181            of the new class addition function, using character lists defined as
182            macros alongside the case definitions of 20 above.
184        (e) Caseless back references now work with characters that have more than
185            one other case.
187        (f) General caseless matching of characters with more than one other case
188            is supported.
190    22. Unicode character properties were updated from Unicode 6.2.0
192    23. Improved CMake support under Windows. Patch by Daniel Richard G.
194    24. Add support for 32-bit character strings, and UTF-32
196    25. Major JIT compiler update (code refactoring and bugfixing).
197        Experimental Sparc 32 support is added.
199    26. Applied a modified version of Daniel Richard G's patch to create
200        pcre.h.generic and config.h.generic by "make" instead of in the
201        PrepareRelease script.
203    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
204        pcre_compile.c when checking for a zero character.
206    28. Introducing a native interface for JIT. Through this interface, the compiled
207        machine code can be directly executed. The purpose of this interface is to
208        provide fast pattern matching, so several sanity checks are not performed.
209        However, feature tests are still performed. The new interface provides
210        1.4x speedup compared to the old one.
212    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
213        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
214        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
216    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
217        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
218        the "old" RFC 2279). Instead, it ended up passing a negative length to
219        pcre_exec().
221    31. Add support for GCC's visibility feature to hide internal functions.
223    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
224        "unknown -C option" after outputting 0 or 1.
226    33. There is now support for generating a code coverage report for the test
227        suite in environments where gcc is the compiler and lcov is installed. This
228        is mainly for the benefit of the developers.
230    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
231        unaddressable using valgrind annotations, allowing valgrind to detect
232        invalid memory accesses. This is mainly for the benefit of the developers.
234    25. (*UTF) can now be used to start a pattern in any of the three libraries.
236    26. Give configure error if --enable-cpp but no C++ compiler found.
239    Version 8.31 06-July-2012
240    -------------------------
242    1.  Fixing a wrong JIT test case and some compiler warnings.
244    2.  Removed a bashism from the RunTest script.
246    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
247        to unsigned type, result still unsigned" that was given by an MS compiler
248        on encountering the code "-sizeof(xxx)".
250    4.  Partial matching support is added to the JIT compiler.
252    5.  Fixed several bugs concerned with partial matching of items that consist
253        of more than one character:
255        (a) /^(..)\1/ did not partially match "aba" because checking references was
256            done on an "all or nothing" basis. This also applied to repeated
257            references.
259        (b) \R did not give a hard partial match if \r was found at the end of the
260            subject.
262        (c) \X did not give a hard partial match after matching one or more
263            characters at the end of the subject.
265        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
266            a partial match for the string "\r".
268        (e) When newline was set to CRLF, the metacharacter "." did not recognize
269            a partial match for a CR character at the end of the subject string.
271    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
272        running pcretest, the text "(JIT)" added to the output whenever JIT is
273        actually used to run the match.
275    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
276        or /S+[+] with a digit between 1 and 7.
278    8.  OP_NOT now supports any UTF character not just single-byte ones.
280    9.  (*MARK) control verb is now supported by the JIT compiler.
282    10. The command "./RunTest list" lists the available tests without actually
283        running any of them. (Because I keep forgetting what they all are.)
287    12. Applied a (slightly modified) user-supplied patch that improves performance
288        when the heap is used for recursion (compiled with --disable-stack-for-
289        recursion). Instead of malloc and free for each heap frame each time a
290        logical recursion happens, frames are retained on a chain and re-used where
291        possible. This sometimes gives as much as 30% improvement.
293    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
294        call.
296    14. As documented, (*COMMIT) is now confined to within a positive assertion.
298    15. It is now possible to link pcretest with libedit as an alternative to
299        libreadline.
301    16. (*COMMIT) control verb is now supported by the JIT compiler.
303    17. The Unicode data tables have been updated to Unicode 6.1.0.
305    18. Added --file-list option to pcregrep.
307    19. Added binary file support to pcregrep, including the -a, --binary-files,
308        -I, and --text options.
310    20. The madvise function is renamed for posix_madvise for QNX compatibility
311        reasons. Fixed by Giuseppe D'Angelo.
313    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
315    22. Changed the option for creating symbolic links for 16-bit man pages from
316        -s to -sf so that re-installing does not cause issues.
318    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
320    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
321        matches in certain environments (the workspace was not being correctly
322        retained). Also added to pcre_dfa_exec() a simple plausibility check on
323        some of the workspace data at the beginning of a restart.
325    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
326        was not doing so when it should - probably a typo introduced by SVN 528
327        (change 8.10/14).
329    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
330        \w+ when the character tables indicated that \x{c4} was a word character.
331        There were several related cases, all because the tests for doing a table
332        lookup were testing for characters less than 127 instead of 255.
334    27. If a pattern contains capturing parentheses that are not used in a match,
335        their slots in the ovector are set to -1. For those that are higher than
336        any matched groups, this happens at the end of processing. In the case when
337        there were back references that the ovector was too small to contain
338        (causing temporary malloc'd memory to be used during matching), and the
339        highest capturing number was not used, memory off the end of the ovector
340        was incorrectly being set to -1. (It was using the size of the temporary
341        memory instead of the true size.)
343    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
344        ovector size, it uses memory at the end of the block that it has got.
346    29. Check for an overlong MARK name and give an error at compile time. The
347        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
349    30. JIT compiler update.
351    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
352        Rill for the patch.
354    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
356    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
358    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
359        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
360        was enabled.
362    35. Improve JIT code generation for greedy plus quantifier.
364    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
365        1 to "aa" instead of to an empty string. The bug affected repeated groups
366        that could potentially match an empty string.
368    37. Optimizing single character iterators in JIT.
370    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
371        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
372        codepoints that are too big for the mode are faulted, and in a UTF mode,
373        disallowed codepoints are also faulted.
375    39. If PCRE was compiled with UTF support, in three places in the DFA
376        matcher there was code that should only have been obeyed in UTF mode, but
377        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
378        processing when bytes with values greater than 127 were present. In 16-bit
379        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
380        both cases the values are those that cannot be the first data item in a UTF
381        character. The three items that might have provoked this were recursions,
382        possessively repeated groups, and atomic groups.
384    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
385        and pcregrep, because some OS require shared objects to be explicitly
386        passed to ld, causing the link step to fail if they are not.
388    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
389        mode, patterns that started with \h* or \R* might be incorrectly matched.
392    Version 8.30 04-February-2012
393    -----------------------------
395    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
396        name is defined in ctype.h.
398    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
399        only in quite long subpatterns.
401    3.  Removed the function pcre_info(), which has been obsolete and deprecated
402        since it was replaced by pcre_fullinfo() in February 2000.
404    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
405        match a (*MARK), and the match failed at the start of the subject, a
406        reference to memory before the start of the subject could occur. This bug
407        was introduced by fix 17 of release 8.21.
409    5.  A reference to an unset group with zero minimum repetition was giving
410        totally wrong answers (in non-JavaScript-compatibility mode). For example,
411        /(another)?(\1?)test/ matched against "hello world test". This bug was
412        introduced in release 8.13.
414    6.  Add support for 16-bit character strings (a large amount of work involving
415        many changes and refactorings).
417    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
418        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
419        from a file.
421    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
422        rounding is not applied in this particular case).
424    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
425        if they appear, or are escaped, in patterns.
427    10. Get rid of a number of -Wunused-but-set-variable warnings.
429    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
430        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
431        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
432        also returns the mark "x". This bug applied to capturing parentheses,
433        non-capturing parentheses, and atomic parentheses. It also applied to some
434        assertions.
436    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
437        information out of configure.ac instead of relying on pcre.h.generic, which
438        is not stored in the repository.
440    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
441        -lreadline.
443    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
445    15. Applied Graycode's patch to put the top-level frame on the stack rather
446        than the heap when not using the stack for recursion. This gives a
447        performance improvement in many cases when recursion is not deep.
449    16. Experimental code added to "pcretest -C" to output the stack frame size.
452    Version 8.21 12-Dec-2011
453    ------------------------
455    1.  Updating the JIT compiler.
457    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
458        are added as well.
460    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
461        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
462        calling _pcre_jit_exec. Some extra comments are added.
464    4.  (*MARK) settings inside atomic groups that do not contain any capturing
465        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
466        was introduced by change 18 for 8.20.
468    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
469        ECMA-262 standard.
471    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
472        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
473        This bug was probably introduced by change 9 of 8.13.
475    7.  While fixing 6 above, I noticed that a number of other items were being
476        incorrectly rejected as "not fixed length". This arose partly because newer
477        opcodes had not been added to the fixed-length checking code. I have (a)
478        corrected the bug and added tests for these items, and (b) arranged for an
479        error to occur if an unknown opcode is encountered while checking for fixed
480        length instead of just assuming "not fixed length". The items that were
481        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
482        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
483        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
485    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
486        being incorrectly compiled and would have given unpredicatble results.
488    9.  A possessively repeated subpattern with minimum repeat count greater than
489        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
490        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
491        the first (A) could occur when it should not.
493    10. Add a cast and remove a redundant test from the code.
495    11. JIT should use pcre_malloc/pcre_free for allocation.
497    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
498        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
499        is anything other than /usr, -L is still shown).
501    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
503    14. Perl does not support \N without a following name in a [] class; PCRE now
504        also gives an error.
506    15. If a forward reference was repeated with an upper limit of around 2000,
507        it caused the error "internal error: overran compiling workspace". The
508        maximum number of forward references (including repeats) was limited by the
509        internal workspace, and dependent on the LINK_SIZE. The code has been
510        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
511        the default depends on LINK_SIZE. There is a new upper limit (for safety)
512        of around 200,000 forward references. While doing this, I also speeded up
513        the filling in of repeated forward references.
515    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
516        incorrectly expecting the subject to contain another "a" after the start.
518    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
519        in the match, the SKIP should be ignored. This was not happening; instead
520        the SKIP was being treated as NOMATCH. For patterns such as
521        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
522        tested.
524    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
525        now much more compatible with Perl, in particular in cases where the result
526        is a non-match for a non-anchored pattern. For example, if
527        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
528        "m", where previously it did not return a name. A side effect of this
529        change is that for partial matches, the last encountered mark name is
530        returned, as for non matches. A number of tests that were previously not
531        Perl-compatible have been moved into the Perl-compatible test files. The
532        refactoring has had the pleasing side effect of removing one argument from
533        the match() function, thus reducing its stack requirements.
535    19. If the /S+ option was used in pcretest to study a pattern using JIT,
536        subsequent uses of /S (without +) incorrectly behaved like /S+.
538    21. Retrieve executable code size support for the JIT compiler and fixing
539        some warnings.
541    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
542        not work when the shorter character appeared right at the end of the
543        subject string.
545    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
546        systems.
548    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
549        output it when the /M option is used in pcretest.
551    25. The CheckMan script was not being included in the distribution. Also, added
552        an explicit "perl" to run Perl scripts from the PrepareRelease script
553        because this is reportedly needed in Windows.
555    26. If study data was being save in a file and studying had not found a set of
556        "starts with" bytes for the pattern, the data written to the file (though
557        never used) was taken from uninitialized memory and so caused valgrind to
558        complain.
560    27. Updated RunTest.bat as provided by Sheri Pierce.
562    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
564    29. Computation of memory usage for the table of capturing group names was
565        giving an unnecessarily large value.
568    Version 8.20 21-Oct-2011
569    ------------------------
571    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
572        a POSIX class. After further experiments with Perl, which convinced me that
573        Perl has bugs and confusions, a closing square bracket is no longer allowed
574        in a POSIX name. This bug also affected patterns with classes that started
575        with full stops.
577    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
578        captured substring, but while checking the failing first alternative,
579        substring 1 is temporarily captured. If the output vector supplied to
580        pcre_exec() was not big enough for this capture, the yield of the function
581        was still zero ("insufficient space for captured substrings"). This cannot
582        be totally fixed without adding another stack variable, which seems a lot
583        of expense for a edge case. However, I have improved the situation in cases
584        such as /(a)(b)x|abc/ matched against "abc", where the return code
585        indicates that fewer than the maximum number of slots in the ovector have
586        been set.
588    3.  Related to (2) above: when there are more back references in a pattern than
589        slots in the output vector, pcre_exec() uses temporary memory during
590        matching, and copies in the captures as far as possible afterwards. It was
591        using the entire output vector, but this conflicts with the specification
592        that only 2/3 is used for passing back captured substrings. Now it uses
593        only the first 2/3, for compatibility. This is, of course, another edge
594        case.
596    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
597        main code base, and can be used by building with --enable-jit. When this is
598        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
599        runtime --no-jit option is given.
601    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
602        ovector, the return from the function was zero, implying that there were
603        other matches that did not fit. The correct "exactly full" value is now
604        returned.
606    6.  If a subpattern that was called recursively or as a subroutine contained
607        (*PRUNE) or any other control that caused it to give a non-standard return,
608        invalid errors such as "Error -26 (nested recursion at the same subject
609        position)" or even infinite loops could occur.
611    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
612        computing the minimum length on reaching *ACCEPT, and so ended up with the
613        wrong value of 1 rather than 0. Further investigation indicates that
614        computing a minimum subject length in the presence of *ACCEPT is difficult
615        (think back references, subroutine calls), and so I have changed the code
616        so that no minimum is registered for a pattern that contains *ACCEPT.
618    8.  If (*THEN) was present in the first (true) branch of a conditional group,
619        it was not handled as intended. [But see 16 below.]
621    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
622        Sheri Pierce.
624    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
625        the first byte in a match must be "a".
627    11. Change 17 for 8.13 increased the recursion depth for patterns like
628        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
629        pattern contains any instances of (*THEN). If it does not, the old
630        optimizations are restored. It would be nice to do this on a per-group
631        basis, but at the moment that is not feasible.
633    12. In some environments, the output of pcretest -C is CRLF terminated. This
634        broke RunTest's code that checks for the link size. A single white space
635        character after the value is now allowed for.
637    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
638        For "fr", it uses the Windows-specific input and output files.
640    14. If (*THEN) appeared in a group that was called recursively or as a
641        subroutine, it did not work as intended. [But see next item.]
643    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
644        pattern fragments (but not containing any | characters). If A and B are
645        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
646        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
647        D. In other words, Perl considers parentheses that do not contain any |
648        characters to be part of a surrounding alternative, whereas PCRE was
649        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
650        differently. PCRE now behaves in the same way as Perl, except in the case
651        of subroutine/recursion calls such as (?1) which have in any case always
652        been different (but PCRE had them first :-).
654    16. Related to 15 above: Perl does not treat the | in a conditional group as
655        creating alternatives. Such a group is treated in the same way as an
656        ordinary group without any | characters when processing (*THEN). PCRE has
657        been changed to match Perl's behaviour.
659    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
660        RunGrepTest script failed.
662    18. Change 22 for version 13 caused atomic groups to use more stack. This is
663        inevitable for groups that contain captures, but it can lead to a lot of
664        stack use in large patterns. The old behaviour has been restored for atomic
665        groups that do not contain any capturing parentheses.
667    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
668        suppress the check for a minimum subject length at run time. (If it was
669        given to pcre_exec() or pcre_dfa_exec() it did work.)
671    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
672        fail to work when decoding hex characters in data strings in EBCDIC
673        environments.
675    21. It appears that in at least one Mac OS environment, the isxdigit() function
676        is implemented as a macro that evaluates to its argument more than once,
677        contravening the C 90 Standard (I haven't checked a later standard). There
678        was an instance in pcretest which caused it to go wrong when processing
679        \x{...} escapes in subject strings. The has been rewritten to avoid using
680        things like p++ in the argument of isxdigit().
683    Version 8.13 16-Aug-2011
684    ------------------------
686    1.  The Unicode data tables have been updated to Unicode 6.0.0.
688    2.  Two minor typos in pcre_internal.h have been fixed.
690    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
691        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
692        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
694    4.  There were a number of related bugs in the code for matching backrefences
695        caselessly in UTF-8 mode when codes for the characters concerned were
696        different numbers of bytes. For example, U+023A and U+2C65 are an upper
697        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
698        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
699        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
700        2-byte code at the end of the subject (it thought there wasn't enough data
701        left).
703    5.  Comprehensive information about what went wrong is now returned by
704        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
705        as the output vector has at least 2 elements. The offset of the start of
706        the failing character and a reason code are placed in the vector.
708    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
709        now returned is for the first byte of the failing character, instead of the
710        last byte inspected. This is an incompatible change, but I hope it is small
711        enough not to be a problem. It makes the returned offset consistent with
712        pcre_exec() and pcre_dfa_exec().
714    7.  pcretest now gives a text phrase as well as the error number when
715        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
716        failure, the offset and reason code are output.
718    8.  When \R was used with a maximizing quantifier it failed to skip backwards
719        over a \r\n pair if the subsequent match failed. Instead, it just skipped
720        back over a single character (\n). This seems wrong (because it treated the
721        two characters as a single entity when going forwards), conflicts with the
722        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
723        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
724        has been changed.
726    9.  Some internal refactoring has changed the processing so that the handling
727        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
728        time (the PCRE_DOTALL option was changed this way some time ago: version
729        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
730        which was always a bit of a fudge. It also means that there is one less
731        argument for the match() function, which reduces its stack requirements
732        slightly. This change also fixes an incompatibility with Perl: the pattern
733        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
735    10. More internal refactoring has drastically reduced the number of recursive
736        calls to match() for possessively repeated groups such as (abc)++ when
737        using pcre_exec().
739    11. While implementing 10, a number of bugs in the handling of groups were
740        discovered and fixed:
742        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
743        (a|)*(?1) gave a compile-time internal error.
744        ((a|)+)+  did not notice that the outer group could match an empty string.
745        (^a|^)+   was not marked as anchored.
746        (.*a|.*)+ was not marked as matching at start or after a newline.
748    12. Yet more internal refactoring has removed another argument from the match()
749        function. Special calls to this function are now indicated by setting a
750        value in a variable in the "match data" data block.
752    13. Be more explicit in pcre_study() instead of relying on "default" for
753        opcodes that mean there is no starting character; this means that when new
754        ones are added and accidentally left out of pcre_study(), testing should
755        pick them up.
757    14. The -s option of pcretest has been documented for ages as being an old
758        synonym of -m (show memory usage). I have changed it to mean "force study
759        for every regex", that is, assume /S for every regex. This is similar to -i
760        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
761        using it. It makes it easier to run collections of tests with and without
762        study enabled, and thereby test pcre_study() more easily. All the standard
763        tests are now run with and without -s (but some patterns can be marked as
764        "never study" - see 20 below).
766    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
767        restoration of the capturing data to the outer values was not happening
768        correctly.
770    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
771        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
772        pattern had matched an empty string, and so incorrectly returned a no
773        match.
775    17. There was optimizing code for the last branch of non-capturing parentheses,
776        and also for the obeyed branch of a conditional subexpression, which used
777        tail recursion to cut down on stack usage. Unfortunately, now that there is
778        the possibility of (*THEN) occurring in these branches, tail recursion is
779        no longer possible because the return has to be checked for (*THEN). These
780        two optimizations have therefore been removed. [But see 8.20/11 above.]
782    18. If a pattern containing \R was studied, it was assumed that \R always
783        matched two bytes, thus causing the minimum subject length to be
784        incorrectly computed because \R can also match just one byte.
786    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
787        was incorrectly computed.
789    20. If /S is present twice on a test pattern in pcretest input, it now
790        *disables* studying, thereby overriding the use of -s on the command line
791        (see 14 above). This is necessary for one or two tests to keep the output
792        identical in both cases.
794    21. When (*ACCEPT) was used in an assertion that matched an empty string and
795        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
797    22. When an atomic group that contained a capturing parenthesis was
798        successfully matched, but the branch in which it appeared failed, the
799        capturing was not being forgotten if a higher numbered group was later
800        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
801        group 1 to "a", when in fact it should be unset. This applied to multi-
802        branched capturing and non-capturing groups, repeated or not, and also to
803        positive assertions (capturing in negative assertions does not happen
804        in PCRE) and also to nested atomic groups.
806    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
807        subject after a captured substring, to make it easier to tell which of a
808        number of identical substrings has been captured.
810    24. The way atomic groups are processed by pcre_exec() has been changed so that
811        if they are repeated, backtracking one repetition now resets captured
812        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
813        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
814        "aaa". Previously, it would have been "a". As part of this code
815        refactoring, the way recursive calls are handled has also been changed.
817    25. If an assertion condition captured any substrings, they were not passed
818        back unless some other capturing happened later. For example, if
819        (?(?=(a))a) was matched against "a", no capturing was returned.
821    26. When studying a pattern that contained subroutine calls or assertions,
822        the code for finding the minimum length of a possible match was handling
823        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
824        group 1 called group 2 while simultaneously a separate group 2 called group
825        1). A stack overflow occurred in this case. I have fixed this by limiting
826        the recursion depth to 10.
828    27. Updated RunTest.bat in the distribution to the version supplied by Tom
829        Fortmann. This supports explicit test numbers on the command line, and has
830        argument validation and error reporting.
832    28. An instance of \X with an unlimited repeat could fail if at any point the
833        first character it looked at was a mark character.
835    29. Some minor code refactoring concerning Unicode properties and scripts
836        should reduce the stack requirement of match() slightly.
838    30. Added the '=' option to pcretest to check the setting of unused capturing
839        slots at the end of the pattern, which are documented as being -1, but are
840        not included in the return count.
842    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
843        compiled something random. Now it gives a compile-time error (as does
844        Perl).
846    32. A *MARK encountered during the processing of a positive assertion is now
847        recorded and passed back (compatible with Perl).
849    33. If --only-matching or --colour was set on a pcregrep call whose pattern
850        had alternative anchored branches, the search for a second match in a line
851        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
852        matched the line "0102" twice. The same bug affected patterns that started
853        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
854        twice.
856    34. Previously, PCRE did not allow quantification of assertions. However, Perl
857        does, and because of capturing effects, quantifying parenthesized
858        assertions may at times be useful. Quantifiers are now allowed for
859        parenthesized assertions.
861    35. A minor code tidy in pcre_compile() when checking options for \R usage.
863    36. \g was being checked for fancy things in a character class, when it should
864        just be a literal "g".
866    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
867        appearance of a nested POSIX class supersedes an apparent external class.
868        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
869        unescaped square brackets may also appear as part of class names. For
870        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
871        more like Perl. (But see 8.20/1 above.)
873    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
874        was because it thought it was \N{name}, which is not supported).
876    39. Add minix to OS list not supporting the -S option in pcretest.
878    40. PCRE tries to detect cases of infinite recursion at compile time, but it
879        cannot analyze patterns in sufficient detail to catch mutual recursions
880        such as ((?1))((?2)). There is now a runtime test that gives an error if a
881        subgroup is called recursively as a subpattern for a second time at the
882        same position in the subject string. In previous releases this might have
883        been caught by the recursion limit, or it might have run out of stack.
885    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
886        happen only once. PCRE was, however incorrectly giving a compile time error
887        "recursive call could loop indefinitely" because it cannot analyze the
888        pattern in sufficient detail. The compile time test no longer happens when
889        PCRE is compiling a conditional subpattern, but actual runaway loops are
890        now caught at runtime (see 40 above).
892    42. It seems that Perl allows any characters other than a closing parenthesis
893        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
894        has been changed to be the same.
896    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
897        as not to get warnings when autogen.sh is called. Also changed
898        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
900    44. To help people who use pcregrep to scan files containing exceedingly long
901        lines, the following changes have been made:
903        (a) The default value of the buffer size parameter has been increased from
904            8K to 20K. (The actual buffer used is three times this size.)
906        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
907            PCRE is built.
909        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
910            to be set at run time.
912        (d) Numerical values in pcregrep options can be followed by K or M, for
913            example --buffer-size=50K.
915        (e) If a line being scanned overflows pcregrep's buffer, an error is now
916            given and the return code is set to 2.
918    45. Add a pointer to the latest mark to the callout data block.
920    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
921        partial match of an empty string instead of no match. This was specific to
922        the use of ".".
924    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
925        complete match instead of a partial match. This bug was dependent on both
926        the PCRE_UTF8 and PCRE_DOTALL options being set.
928    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
929        starting byte set, because \b was not being ignored.
932    Version 8.12 15-Jan-2011
933    ------------------------
935    1.  Fixed some typos in the markup of the man pages, and wrote a script that
936        checks for such things as part of the documentation building process.
938    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
939        --match-limit and --recursion-limit options (added for 8.11). In
940        particular, this made one of the standard tests fail. (The integer value
941        went into the wrong half of a long int.)
943    3.  If the --colour option was given to pcregrep with -v (invert match), it
944        did strange things, either producing crazy output, or crashing. It should,
945        of course, ignore a request for colour when reporting lines that do not
946        match.
948    4.  Another pcregrep bug caused similar problems if --colour was specified with
949        -M (multiline) and the pattern match finished with a line ending.
951    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
952        matched in multiline mode, the following line was shown as part of the
953        match. This seems wrong, so I have changed it.
955    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
956        the check for further matches in the same line (so they could be coloured)
957        to overrun the end of the current line. If another match was found, it was
958        incorrectly shown (and then shown again when found in the next line).
960    7.  If pcregrep was compiled under Windows, there was a reference to the
961        function pcregrep_exit() before it was defined. I am assuming this was
962        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
963        reported by a user. I've moved the definition above the reference.
966    Version 8.11 10-Dec-2010
967  ------------------------  ------------------------
969  1.  (*THEN) was not working properly if there were untried alternatives prior  1.  (*THEN) was not working properly if there were untried alternatives prior

Removed from v.580  
changed lines
  Added in v.1253

  ViewVC Help
Powered by ViewVC 1.1.5