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

  ViewVC Help
Powered by ViewVC 1.1.5