ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 1272 by zherczeg, Thu Mar 7 11:30:01 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 02-Aug-2011  Version 8.33 xx-xxxx-201x
5    -------------------------
7    1.  Added 'U' to some constants that are compared to unsigned integers, to
8        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
9        variables that are added to signed variables, to ensure the result is
10        signed and can be negated.
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
15    3.  Revise the creation of config.h.generic so that all boolean macros are
16        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
17        overriding via -D on the command line possible.
19    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
20        to unsigned int is reported to make a quite noticeable speed difference in
21        a specific Windows environment. Testing on Linux did also appear to show
22        some benefit (and it is clearly not harmful). Also fixed the definition of
23        Xop which should be unsigned.
25    5.  Related to (4), changing the definition of the intermediate variable cc
26        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
27        improvements.
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
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.
103    Version 8.32 30-November-2012
104    -----------------------------
106    1.  Improved JIT compiler optimizations for first character search and single
107        character iterators.
109    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
110        Patch by Daniel Richard G.
112    3.  Single character iterator optimizations in the JIT compiler.
114    4.  Improved JIT compiler optimizations for character ranges.
116    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
117        Reported by Giuseppe D'Angelo.
119    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
120        of a line, was being set incorrectly in cases where .* appeared inside
121        atomic brackets at the start of a pattern, or where there was a subsequent
122        *PRUNE or *SKIP.
124    7.  Improved instruction cache flush for POWER/PowerPC.
125        Patch by Daniel Richard G.
127    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
128        grep:
130        (a) There is now no limit to the number of patterns to be matched.
132        (b) An error is given if a pattern is too long.
134        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
135            are now supported.
137        (d) --exclude-from and --include-from (multiple use) have been added.
139        (e) Exclusions and inclusions now apply to all files and directories, not
140            just to those obtained from scanning a directory recursively.
142        (f) Multiple uses of -f and --file-list are now supported.
144        (g) In a Windows environment, the default for -d has been changed from
145            "read" (the GNU grep default) to "skip", because otherwise the presence
146            of a directory in the file list provokes an error.
148        (h) The documentation has been revised and clarified in places.
150    9.  Improve the matching speed of capturing brackets.
152    10. Changed the meaning of \X so that it now matches a Unicode extended
153        grapheme cluster.
155    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
156        out POSIX threads when JIT support is configured.
158    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
160    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
161        structure could go wrong in environments where size_t is not the same size
162        as int.
164    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
165        set.
167    15. The EBCDIC support had decayed; later updates to the code had included
168        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
169        general tidy up of EBCDIC-related issues, and the documentation was also
170        not quite right. There is now a test that can be run on ASCII systems to
171        check some of the EBCDIC-related things (but is it not a full test).
173    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
174        in a small tidy to the code.
176    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
178    18. If the --only-matching (-o) option in pcregrep is specified multiple
179        times, each one causes appropriate output. For example, -o1 -o2 outputs the
180        substrings matched by the 1st and 2nd capturing parentheses. A separating
181        string can be specified by --om-separator (default empty).
183    19. Improving the first n character searches.
185    20. Turn case lists for horizontal and vertical white space into macros so that
186        they are defined only once.
188    21. This set of changes together give more compatible Unicode case-folding
189        behaviour for characters that have more than one other case when UCP
190        support is available.
192        (a) The Unicode property table now has offsets into a new table of sets of
193            three or more characters that are case-equivalent. The MultiStage2.py
194            script that generates these tables (the pcre_ucd.c file) now scans
195            CaseFolding.txt instead of UnicodeData.txt for character case
196            information.
198        (b) The code for adding characters or ranges of characters to a character
199            class has been abstracted into a generalized function that also handles
200            case-independence. In UTF-mode with UCP support, this uses the new data
201            to handle characters with more than one other case.
203        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
204            whose other case is greater than 256 are now correctly matched
205            caselessly. Previously, the high codepoint matched the low one, but not
206            vice versa.
208        (d) The processing of \h, \H, \v, and \ in character classes now makes use
209            of the new class addition function, using character lists defined as
210            macros alongside the case definitions of 20 above.
212        (e) Caseless back references now work with characters that have more than
213            one other case.
215        (f) General caseless matching of characters with more than one other case
216            is supported.
218    22. Unicode character properties were updated from Unicode 6.2.0
220    23. Improved CMake support under Windows. Patch by Daniel Richard G.
222    24. Add support for 32-bit character strings, and UTF-32
224    25. Major JIT compiler update (code refactoring and bugfixing).
225        Experimental Sparc 32 support is added.
227    26. Applied a modified version of Daniel Richard G's patch to create
228        pcre.h.generic and config.h.generic by "make" instead of in the
229        PrepareRelease script.
231    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
232        pcre_compile.c when checking for a zero character.
234    28. Introducing a native interface for JIT. Through this interface, the compiled
235        machine code can be directly executed. The purpose of this interface is to
236        provide fast pattern matching, so several sanity checks are not performed.
237        However, feature tests are still performed. The new interface provides
238        1.4x speedup compared to the old one.
240    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
241        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
242        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
244    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
245        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
246        the "old" RFC 2279). Instead, it ended up passing a negative length to
247        pcre_exec().
249    31. Add support for GCC's visibility feature to hide internal functions.
251    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
252        "unknown -C option" after outputting 0 or 1.
254    33. There is now support for generating a code coverage report for the test
255        suite in environments where gcc is the compiler and lcov is installed. This
256        is mainly for the benefit of the developers.
258    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
259        unaddressable using valgrind annotations, allowing valgrind to detect
260        invalid memory accesses. This is mainly for the benefit of the developers.
262    25. (*UTF) can now be used to start a pattern in any of the three libraries.
264    26. Give configure error if --enable-cpp but no C++ compiler found.
267    Version 8.31 06-July-2012
268    -------------------------
270    1.  Fixing a wrong JIT test case and some compiler warnings.
272    2.  Removed a bashism from the RunTest script.
274    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
275        to unsigned type, result still unsigned" that was given by an MS compiler
276        on encountering the code "-sizeof(xxx)".
278    4.  Partial matching support is added to the JIT compiler.
280    5.  Fixed several bugs concerned with partial matching of items that consist
281        of more than one character:
283        (a) /^(..)\1/ did not partially match "aba" because checking references was
284            done on an "all or nothing" basis. This also applied to repeated
285            references.
287        (b) \R did not give a hard partial match if \r was found at the end of the
288            subject.
290        (c) \X did not give a hard partial match after matching one or more
291            characters at the end of the subject.
293        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
294            a partial match for the string "\r".
296        (e) When newline was set to CRLF, the metacharacter "." did not recognize
297            a partial match for a CR character at the end of the subject string.
299    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
300        running pcretest, the text "(JIT)" added to the output whenever JIT is
301        actually used to run the match.
303    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
304        or /S+[+] with a digit between 1 and 7.
306    8.  OP_NOT now supports any UTF character not just single-byte ones.
308    9.  (*MARK) control verb is now supported by the JIT compiler.
310    10. The command "./RunTest list" lists the available tests without actually
311        running any of them. (Because I keep forgetting what they all are.)
315    12. Applied a (slightly modified) user-supplied patch that improves performance
316        when the heap is used for recursion (compiled with --disable-stack-for-
317        recursion). Instead of malloc and free for each heap frame each time a
318        logical recursion happens, frames are retained on a chain and re-used where
319        possible. This sometimes gives as much as 30% improvement.
321    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
322        call.
324    14. As documented, (*COMMIT) is now confined to within a positive assertion.
326    15. It is now possible to link pcretest with libedit as an alternative to
327        libreadline.
329    16. (*COMMIT) control verb is now supported by the JIT compiler.
331    17. The Unicode data tables have been updated to Unicode 6.1.0.
333    18. Added --file-list option to pcregrep.
335    19. Added binary file support to pcregrep, including the -a, --binary-files,
336        -I, and --text options.
338    20. The madvise function is renamed for posix_madvise for QNX compatibility
339        reasons. Fixed by Giuseppe D'Angelo.
341    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
343    22. Changed the option for creating symbolic links for 16-bit man pages from
344        -s to -sf so that re-installing does not cause issues.
346    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
348    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
349        matches in certain environments (the workspace was not being correctly
350        retained). Also added to pcre_dfa_exec() a simple plausibility check on
351        some of the workspace data at the beginning of a restart.
353    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
354        was not doing so when it should - probably a typo introduced by SVN 528
355        (change 8.10/14).
357    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
358        \w+ when the character tables indicated that \x{c4} was a word character.
359        There were several related cases, all because the tests for doing a table
360        lookup were testing for characters less than 127 instead of 255.
362    27. If a pattern contains capturing parentheses that are not used in a match,
363        their slots in the ovector are set to -1. For those that are higher than
364        any matched groups, this happens at the end of processing. In the case when
365        there were back references that the ovector was too small to contain
366        (causing temporary malloc'd memory to be used during matching), and the
367        highest capturing number was not used, memory off the end of the ovector
368        was incorrectly being set to -1. (It was using the size of the temporary
369        memory instead of the true size.)
371    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
372        ovector size, it uses memory at the end of the block that it has got.
374    29. Check for an overlong MARK name and give an error at compile time. The
375        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
377    30. JIT compiler update.
379    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
380        Rill for the patch.
382    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
384    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
386    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
387        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
388        was enabled.
390    35. Improve JIT code generation for greedy plus quantifier.
392    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
393        1 to "aa" instead of to an empty string. The bug affected repeated groups
394        that could potentially match an empty string.
396    37. Optimizing single character iterators in JIT.
398    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
399        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
400        codepoints that are too big for the mode are faulted, and in a UTF mode,
401        disallowed codepoints are also faulted.
403    39. If PCRE was compiled with UTF support, in three places in the DFA
404        matcher there was code that should only have been obeyed in UTF mode, but
405        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
406        processing when bytes with values greater than 127 were present. In 16-bit
407        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
408        both cases the values are those that cannot be the first data item in a UTF
409        character. The three items that might have provoked this were recursions,
410        possessively repeated groups, and atomic groups.
412    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
413        and pcregrep, because some OS require shared objects to be explicitly
414        passed to ld, causing the link step to fail if they are not.
416    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
417        mode, patterns that started with \h* or \R* might be incorrectly matched.
420    Version 8.30 04-February-2012
421    -----------------------------
423    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
424        name is defined in ctype.h.
426    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
427        only in quite long subpatterns.
429    3.  Removed the function pcre_info(), which has been obsolete and deprecated
430        since it was replaced by pcre_fullinfo() in February 2000.
432    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
433        match a (*MARK), and the match failed at the start of the subject, a
434        reference to memory before the start of the subject could occur. This bug
435        was introduced by fix 17 of release 8.21.
437    5.  A reference to an unset group with zero minimum repetition was giving
438        totally wrong answers (in non-JavaScript-compatibility mode). For example,
439        /(another)?(\1?)test/ matched against "hello world test". This bug was
440        introduced in release 8.13.
442    6.  Add support for 16-bit character strings (a large amount of work involving
443        many changes and refactorings).
445    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
446        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
447        from a file.
449    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
450        rounding is not applied in this particular case).
452    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
453        if they appear, or are escaped, in patterns.
455    10. Get rid of a number of -Wunused-but-set-variable warnings.
457    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
458        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
459        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
460        also returns the mark "x". This bug applied to capturing parentheses,
461        non-capturing parentheses, and atomic parentheses. It also applied to some
462        assertions.
464    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
465        information out of configure.ac instead of relying on pcre.h.generic, which
466        is not stored in the repository.
468    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
469        -lreadline.
471    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
473    15. Applied Graycode's patch to put the top-level frame on the stack rather
474        than the heap when not using the stack for recursion. This gives a
475        performance improvement in many cases when recursion is not deep.
477    16. Experimental code added to "pcretest -C" to output the stack frame size.
480    Version 8.21 12-Dec-2011
481    ------------------------
483    1.  Updating the JIT compiler.
485    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
486        are added as well.
488    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
489        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
490        calling _pcre_jit_exec. Some extra comments are added.
492    4.  (*MARK) settings inside atomic groups that do not contain any capturing
493        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
494        was introduced by change 18 for 8.20.
496    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
497        ECMA-262 standard.
499    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
500        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
501        This bug was probably introduced by change 9 of 8.13.
503    7.  While fixing 6 above, I noticed that a number of other items were being
504        incorrectly rejected as "not fixed length". This arose partly because newer
505        opcodes had not been added to the fixed-length checking code. I have (a)
506        corrected the bug and added tests for these items, and (b) arranged for an
507        error to occur if an unknown opcode is encountered while checking for fixed
508        length instead of just assuming "not fixed length". The items that were
509        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
510        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
511        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
513    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
514        being incorrectly compiled and would have given unpredicatble results.
516    9.  A possessively repeated subpattern with minimum repeat count greater than
517        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
518        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
519        the first (A) could occur when it should not.
521    10. Add a cast and remove a redundant test from the code.
523    11. JIT should use pcre_malloc/pcre_free for allocation.
525    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
526        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
527        is anything other than /usr, -L is still shown).
529    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
531    14. Perl does not support \N without a following name in a [] class; PCRE now
532        also gives an error.
534    15. If a forward reference was repeated with an upper limit of around 2000,
535        it caused the error "internal error: overran compiling workspace". The
536        maximum number of forward references (including repeats) was limited by the
537        internal workspace, and dependent on the LINK_SIZE. The code has been
538        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
539        the default depends on LINK_SIZE. There is a new upper limit (for safety)
540        of around 200,000 forward references. While doing this, I also speeded up
541        the filling in of repeated forward references.
543    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
544        incorrectly expecting the subject to contain another "a" after the start.
546    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
547        in the match, the SKIP should be ignored. This was not happening; instead
548        the SKIP was being treated as NOMATCH. For patterns such as
549        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
550        tested.
552    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
553        now much more compatible with Perl, in particular in cases where the result
554        is a non-match for a non-anchored pattern. For example, if
555        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
556        "m", where previously it did not return a name. A side effect of this
557        change is that for partial matches, the last encountered mark name is
558        returned, as for non matches. A number of tests that were previously not
559        Perl-compatible have been moved into the Perl-compatible test files. The
560        refactoring has had the pleasing side effect of removing one argument from
561        the match() function, thus reducing its stack requirements.
563    19. If the /S+ option was used in pcretest to study a pattern using JIT,
564        subsequent uses of /S (without +) incorrectly behaved like /S+.
566    21. Retrieve executable code size support for the JIT compiler and fixing
567        some warnings.
569    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
570        not work when the shorter character appeared right at the end of the
571        subject string.
573    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
574        systems.
576    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
577        output it when the /M option is used in pcretest.
579    25. The CheckMan script was not being included in the distribution. Also, added
580        an explicit "perl" to run Perl scripts from the PrepareRelease script
581        because this is reportedly needed in Windows.
583    26. If study data was being save in a file and studying had not found a set of
584        "starts with" bytes for the pattern, the data written to the file (though
585        never used) was taken from uninitialized memory and so caused valgrind to
586        complain.
588    27. Updated RunTest.bat as provided by Sheri Pierce.
590    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
592    29. Computation of memory usage for the table of capturing group names was
593        giving an unnecessarily large value.
596    Version 8.20 21-Oct-2011
597    ------------------------
599    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
600        a POSIX class. After further experiments with Perl, which convinced me that
601        Perl has bugs and confusions, a closing square bracket is no longer allowed
602        in a POSIX name. This bug also affected patterns with classes that started
603        with full stops.
605    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
606        captured substring, but while checking the failing first alternative,
607        substring 1 is temporarily captured. If the output vector supplied to
608        pcre_exec() was not big enough for this capture, the yield of the function
609        was still zero ("insufficient space for captured substrings"). This cannot
610        be totally fixed without adding another stack variable, which seems a lot
611        of expense for a edge case. However, I have improved the situation in cases
612        such as /(a)(b)x|abc/ matched against "abc", where the return code
613        indicates that fewer than the maximum number of slots in the ovector have
614        been set.
616    3.  Related to (2) above: when there are more back references in a pattern than
617        slots in the output vector, pcre_exec() uses temporary memory during
618        matching, and copies in the captures as far as possible afterwards. It was
619        using the entire output vector, but this conflicts with the specification
620        that only 2/3 is used for passing back captured substrings. Now it uses
621        only the first 2/3, for compatibility. This is, of course, another edge
622        case.
624    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
625        main code base, and can be used by building with --enable-jit. When this is
626        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
627        runtime --no-jit option is given.
629    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
630        ovector, the return from the function was zero, implying that there were
631        other matches that did not fit. The correct "exactly full" value is now
632        returned.
634    6.  If a subpattern that was called recursively or as a subroutine contained
635        (*PRUNE) or any other control that caused it to give a non-standard return,
636        invalid errors such as "Error -26 (nested recursion at the same subject
637        position)" or even infinite loops could occur.
639    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
640        computing the minimum length on reaching *ACCEPT, and so ended up with the
641        wrong value of 1 rather than 0. Further investigation indicates that
642        computing a minimum subject length in the presence of *ACCEPT is difficult
643        (think back references, subroutine calls), and so I have changed the code
644        so that no minimum is registered for a pattern that contains *ACCEPT.
646    8.  If (*THEN) was present in the first (true) branch of a conditional group,
647        it was not handled as intended. [But see 16 below.]
649    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
650        Sheri Pierce.
652    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
653        the first byte in a match must be "a".
655    11. Change 17 for 8.13 increased the recursion depth for patterns like
656        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
657        pattern contains any instances of (*THEN). If it does not, the old
658        optimizations are restored. It would be nice to do this on a per-group
659        basis, but at the moment that is not feasible.
661    12. In some environments, the output of pcretest -C is CRLF terminated. This
662        broke RunTest's code that checks for the link size. A single white space
663        character after the value is now allowed for.
665    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
666        For "fr", it uses the Windows-specific input and output files.
668    14. If (*THEN) appeared in a group that was called recursively or as a
669        subroutine, it did not work as intended. [But see next item.]
671    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
672        pattern fragments (but not containing any | characters). If A and B are
673        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
674        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
675        D. In other words, Perl considers parentheses that do not contain any |
676        characters to be part of a surrounding alternative, whereas PCRE was
677        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
678        differently. PCRE now behaves in the same way as Perl, except in the case
679        of subroutine/recursion calls such as (?1) which have in any case always
680        been different (but PCRE had them first :-).
682    16. Related to 15 above: Perl does not treat the | in a conditional group as
683        creating alternatives. Such a group is treated in the same way as an
684        ordinary group without any | characters when processing (*THEN). PCRE has
685        been changed to match Perl's behaviour.
687    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
688        RunGrepTest script failed.
690    18. Change 22 for version 13 caused atomic groups to use more stack. This is
691        inevitable for groups that contain captures, but it can lead to a lot of
692        stack use in large patterns. The old behaviour has been restored for atomic
693        groups that do not contain any capturing parentheses.
695    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
696        suppress the check for a minimum subject length at run time. (If it was
697        given to pcre_exec() or pcre_dfa_exec() it did work.)
699    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
700        fail to work when decoding hex characters in data strings in EBCDIC
701        environments.
703    21. It appears that in at least one Mac OS environment, the isxdigit() function
704        is implemented as a macro that evaluates to its argument more than once,
705        contravening the C 90 Standard (I haven't checked a later standard). There
706        was an instance in pcretest which caused it to go wrong when processing
707        \x{...} escapes in subject strings. The has been rewritten to avoid using
708        things like p++ in the argument of isxdigit().
711    Version 8.13 16-Aug-2011
712  ------------------------  ------------------------
714  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 98  Version 8.13 02-Aug-2011 Line 805  Version 8.13 02-Aug-2011
805      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
806      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
807      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
808      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
810  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
811      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 896  Version 8.13 02-Aug-2011
896      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
897      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
898      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
899      more like Perl.      more like Perl. (But see 8.20/1 above.)
901  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
902      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 931  Version 8.13 02-Aug-2011
931      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
932          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
934      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
935          PCRE is built.          PCRE is built.
937      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 245  Version 8.13 02-Aug-2011 Line 952  Version 8.13 02-Aug-2011
952  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
953      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
954      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
956  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
957      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
960  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011

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

  ViewVC Help
Powered by ViewVC 1.1.5