ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.581  
changed lines
  Added in v.1283

  ViewVC Help
Powered by ViewVC 1.1.5