ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 491 by ph10, Mon Mar 1 17:45:08 2010 UTC revision 1045 by ph10, Sun Sep 23 16:50:00 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.02 01-Mar-2010  Version 8.32
5    ------------
7    1.  Improved JIT compiler optimizations for first character search and single
8        character iterators.
10    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
11        Patch by Daniel Richard G.
13    3.  Single character iterator optimizations in the JIT compiler.
15    4.  Improved JIT compiler optimizations for character ranges.
17    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
18        Reported by Giuseppe D'Angelo.
20    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
21        of a line, was being set incorrectly in cases where .* appeared inside
22        atomic brackets at the start of a pattern, or where there was a subsequent
23        *PRUNE or *SKIP.
25    7.  Improved instruction cache flush for POWER/PowerPC.
26        Patch by Daniel Richard G.
28    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
29        grep:
31        (a) There is now no limit to the number of patterns to be matched.
33        (b) An error is given if a pattern is too long.
35        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
36            are now supported.
38        (d) --exclude-from and --include-from (multiple use) have been added.
40        (e) Exclusions and inclusions now apply to all files and directories, not
41            just to those obtained from scanning a directory recursively.
43        (f) Multiple uses of -f and --file-list are now supported.
45        (g) In a Windows environment, the default for -d has been changed from
46            "read" (the GNU grep default) to "skip", because otherwise the presence
47            of a directory in the file list provokes an error.
49        (h) The documentation has been revised and clarified in places.
51    9.  Improve the matching speed of capturing brackets.
53    10. Changed the meaning of \X so that it now matches a Unicode extended
54        grapheme cluster.
56    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
57        out POSIX threads when JIT support is configured.
59    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
61    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
62        structure could go wrong in environments where size_t is not the same size
63        as int.
65    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
66        set.
68    15. The EBCDIC support had decayed; later updates to the code had included
69        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
70        general tidy up of EBCDIC-related issues, and the documentation was also
71        not quite right. There is now a test that can be run on ASCII systems to
72        check some of the EBCDIC-related things (but is it not a full test).
74    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
75        in a small tidy to the code.
77    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
79    18. If the --only-matching (-o) option in pcregrep is specified multiple
80        times, each one causes appropriate output. For example, -o1 -o2 outputs the
81        substrings matched by the 1st and 2nd capturing parentheses. A separating
82        string can be specified by --om-separator (default empty).
84    19. Improving the first n character searches.
86    20. Turn case lists for horizontal and vertical white space into macros so that
87        they are defined only once.
89    21. This set of changes together give more compatible Unicode case-folding
90        behaviour for characters that have more than one other case.
92        (a) The Unicode property table now has offsets into a new table of sets of
93            three or more characters that are case-equivalent. The MultiStage2.py
94            script that generates these tables (the pcre_ucd.c file) now scans
95            CaseFolding.txt instead of UnicodeData.txt for character case
96            information.
98        (b) The code for adding characters or ranges of characters to a character
99            class has been abstracted into a generalized function that also handles
100            case-independence. In UTF-mode with UCP support, this uses the new data
101            to handle characters with more than one other case.
103        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
104            whose other case is greater than 256 are now correctly matched
105            caselessly. Previously, the high codepoint matched the low one, but not
106            vice versa.
108        (d) The processing of \h, \H, \v, and \ in character classes now makes use
109            of the new class addition function, using character lists defined as
110            macros alongside the case definitions of 20 above.
113    Version 8.31 06-July-2012
114    -------------------------
116    1.  Fixing a wrong JIT test case and some compiler warnings.
118    2.  Removed a bashism from the RunTest script.
120    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
121        to unsigned type, result still unsigned" that was given by an MS compiler
122        on encountering the code "-sizeof(xxx)".
124    4.  Partial matching support is added to the JIT compiler.
126    5.  Fixed several bugs concerned with partial matching of items that consist
127        of more than one character:
129        (a) /^(..)\1/ did not partially match "aba" because checking references was
130            done on an "all or nothing" basis. This also applied to repeated
131            references.
133        (b) \R did not give a hard partial match if \r was found at the end of the
134            subject.
136        (c) \X did not give a hard partial match after matching one or more
137            characters at the end of the subject.
139        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
140            a partial match for the string "\r".
142        (e) When newline was set to CRLF, the metacharacter "." did not recognize
143            a partial match for a CR character at the end of the subject string.
145    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
146        running pcretest, the text "(JIT)" added to the output whenever JIT is
147        actually used to run the match.
149    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
150        or /S+[+] with a digit between 1 and 7.
152    8.  OP_NOT now supports any UTF character not just single-byte ones.
154    9.  (*MARK) control verb is now supported by the JIT compiler.
156    10. The command "./RunTest list" lists the available tests without actually
157        running any of them. (Because I keep forgetting what they all are.)
161    12. Applied a (slightly modified) user-supplied patch that improves performance
162        when the heap is used for recursion (compiled with --disable-stack-for-
163        recursion). Instead of malloc and free for each heap frame each time a
164        logical recursion happens, frames are retained on a chain and re-used where
165        possible. This sometimes gives as much as 30% improvement.
167    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
168        call.
170    14. As documented, (*COMMIT) is now confined to within a positive assertion.
172    15. It is now possible to link pcretest with libedit as an alternative to
173        libreadline.
175    16. (*COMMIT) control verb is now supported by the JIT compiler.
177    17. The Unicode data tables have been updated to Unicode 6.1.0.
179    18. Added --file-list option to pcregrep.
181    19. Added binary file support to pcregrep, including the -a, --binary-files,
182        -I, and --text options.
184    20. The madvise function is renamed for posix_madvise for QNX compatibility
185        reasons. Fixed by Giuseppe D'Angelo.
187    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
189    22. Changed the option for creating symbolic links for 16-bit man pages from
190        -s to -sf so that re-installing does not cause issues.
192    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
194    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
195        matches in certain environments (the workspace was not being correctly
196        retained). Also added to pcre_dfa_exec() a simple plausibility check on
197        some of the workspace data at the beginning of a restart.
199    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
200        was not doing so when it should - probably a typo introduced by SVN 528
201        (change 8.10/14).
203    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
204        \w+ when the character tables indicated that \x{c4} was a word character.
205        There were several related cases, all because the tests for doing a table
206        lookup were testing for characters less than 127 instead of 255.
208    27. If a pattern contains capturing parentheses that are not used in a match,
209        their slots in the ovector are set to -1. For those that are higher than
210        any matched groups, this happens at the end of processing. In the case when
211        there were back references that the ovector was too small to contain
212        (causing temporary malloc'd memory to be used during matching), and the
213        highest capturing number was not used, memory off the end of the ovector
214        was incorrectly being set to -1. (It was using the size of the temporary
215        memory instead of the true size.)
217    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
218        ovector size, it uses memory at the end of the block that it has got.
220    29. Check for an overlong MARK name and give an error at compile time. The
221        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
223    30. JIT compiler update.
225    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
226        Rill for the patch.
228    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
230    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
232    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
233        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
234        was enabled.
236    35. Improve JIT code generation for greedy plus quantifier.
238    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
239        1 to "aa" instead of to an empty string. The bug affected repeated groups
240        that could potentially match an empty string.
242    37. Optimizing single character iterators in JIT.
244    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
245        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
246        codepoints that are too big for the mode are faulted, and in a UTF mode,
247        disallowed codepoints are also faulted.
249    39. If PCRE was compiled with UTF support, in three places in the DFA
250        matcher there was code that should only have been obeyed in UTF mode, but
251        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
252        processing when bytes with values greater than 127 were present. In 16-bit
253        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
254        both cases the values are those that cannot be the first data item in a UTF
255        character. The three items that might have provoked this were recursions,
256        possessively repeated groups, and atomic groups.
258    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
259        and pcregrep, because some OS require shared objects to be explicitly
260        passed to ld, causing the link step to fail if they are not.
262    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
263        mode, patterns that started with \h* or \R* might be incorrectly matched.
266    Version 8.30 04-February-2012
267    -----------------------------
269    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
270        name is defined in ctype.h.
272    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
273        only in quite long subpatterns.
275    3.  Removed the function pcre_info(), which has been obsolete and deprecated
276        since it was replaced by pcre_fullinfo() in February 2000.
278    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
279        match a (*MARK), and the match failed at the start of the subject, a
280        reference to memory before the start of the subject could occur. This bug
281        was introduced by fix 17 of release 8.21.
283    5.  A reference to an unset group with zero minimum repetition was giving
284        totally wrong answers (in non-JavaScript-compatibility mode). For example,
285        /(another)?(\1?)test/ matched against "hello world test". This bug was
286        introduced in release 8.13.
288    6.  Add support for 16-bit character strings (a large amount of work involving
289        many changes and refactorings).
291    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
292        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
293        from a file.
295    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
296        rounding is not applied in this particular case).
298    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
299        if they appear, or are escaped, in patterns.
301    10. Get rid of a number of -Wunused-but-set-variable warnings.
303    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
304        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
305        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
306        also returns the mark "x". This bug applied to capturing parentheses,
307        non-capturing parentheses, and atomic parentheses. It also applied to some
308        assertions.
310    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
311        information out of configure.ac instead of relying on pcre.h.generic, which
312        is not stored in the repository.
314    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
315        -lreadline.
317    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
319    15. Applied Graycode's patch to put the top-level frame on the stack rather
320        than the heap when not using the stack for recursion. This gives a
321        performance improvement in many cases when recursion is not deep.
323    16. Experimental code added to "pcretest -C" to output the stack frame size.
326    Version 8.21 12-Dec-2011
327    ------------------------
329    1.  Updating the JIT compiler.
331    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
332        are added as well.
334    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
335        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
336        calling _pcre_jit_exec. Some extra comments are added.
338    4.  (*MARK) settings inside atomic groups that do not contain any capturing
339        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
340        was introduced by change 18 for 8.20.
342    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
343        ECMA-262 standard.
345    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
346        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
347        This bug was probably introduced by change 9 of 8.13.
349    7.  While fixing 6 above, I noticed that a number of other items were being
350        incorrectly rejected as "not fixed length". This arose partly because newer
351        opcodes had not been added to the fixed-length checking code. I have (a)
352        corrected the bug and added tests for these items, and (b) arranged for an
353        error to occur if an unknown opcode is encountered while checking for fixed
354        length instead of just assuming "not fixed length". The items that were
355        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
356        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
357        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
359    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
360        being incorrectly compiled and would have given unpredicatble results.
362    9.  A possessively repeated subpattern with minimum repeat count greater than
363        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
364        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
365        the first (A) could occur when it should not.
367    10. Add a cast and remove a redundant test from the code.
369    11. JIT should use pcre_malloc/pcre_free for allocation.
371    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
372        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
373        is anything other than /usr, -L is still shown).
375    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
377    14. Perl does not support \N without a following name in a [] class; PCRE now
378        also gives an error.
380    15. If a forward reference was repeated with an upper limit of around 2000,
381        it caused the error "internal error: overran compiling workspace". The
382        maximum number of forward references (including repeats) was limited by the
383        internal workspace, and dependent on the LINK_SIZE. The code has been
384        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
385        the default depends on LINK_SIZE. There is a new upper limit (for safety)
386        of around 200,000 forward references. While doing this, I also speeded up
387        the filling in of repeated forward references.
389    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
390        incorrectly expecting the subject to contain another "a" after the start.
392    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
393        in the match, the SKIP should be ignored. This was not happening; instead
394        the SKIP was being treated as NOMATCH. For patterns such as
395        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
396        tested.
398    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
399        now much more compatible with Perl, in particular in cases where the result
400        is a non-match for a non-anchored pattern. For example, if
401        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
402        "m", where previously it did not return a name. A side effect of this
403        change is that for partial matches, the last encountered mark name is
404        returned, as for non matches. A number of tests that were previously not
405        Perl-compatible have been moved into the Perl-compatible test files. The
406        refactoring has had the pleasing side effect of removing one argument from
407        the match() function, thus reducing its stack requirements.
409    19. If the /S+ option was used in pcretest to study a pattern using JIT,
410        subsequent uses of /S (without +) incorrectly behaved like /S+.
412    21. Retrieve executable code size support for the JIT compiler and fixing
413        some warnings.
415    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
416        not work when the shorter character appeared right at the end of the
417        subject string.
419    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
420        systems.
422    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
423        output it when the /M option is used in pcretest.
425    25. The CheckMan script was not being included in the distribution. Also, added
426        an explicit "perl" to run Perl scripts from the PrepareRelease script
427        because this is reportedly needed in Windows.
429    26. If study data was being save in a file and studying had not found a set of
430        "starts with" bytes for the pattern, the data written to the file (though
431        never used) was taken from uninitialized memory and so caused valgrind to
432        complain.
434    27. Updated RunTest.bat as provided by Sheri Pierce.
436    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
438    29. Computation of memory usage for the table of capturing group names was
439        giving an unnecessarily large value.
442    Version 8.20 21-Oct-2011
443    ------------------------
445    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
446        a POSIX class. After further experiments with Perl, which convinced me that
447        Perl has bugs and confusions, a closing square bracket is no longer allowed
448        in a POSIX name. This bug also affected patterns with classes that started
449        with full stops.
451    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
452        captured substring, but while checking the failing first alternative,
453        substring 1 is temporarily captured. If the output vector supplied to
454        pcre_exec() was not big enough for this capture, the yield of the function
455        was still zero ("insufficient space for captured substrings"). This cannot
456        be totally fixed without adding another stack variable, which seems a lot
457        of expense for a edge case. However, I have improved the situation in cases
458        such as /(a)(b)x|abc/ matched against "abc", where the return code
459        indicates that fewer than the maximum number of slots in the ovector have
460        been set.
462    3.  Related to (2) above: when there are more back references in a pattern than
463        slots in the output vector, pcre_exec() uses temporary memory during
464        matching, and copies in the captures as far as possible afterwards. It was
465        using the entire output vector, but this conflicts with the specification
466        that only 2/3 is used for passing back captured substrings. Now it uses
467        only the first 2/3, for compatibility. This is, of course, another edge
468        case.
470    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
471        main code base, and can be used by building with --enable-jit. When this is
472        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
473        runtime --no-jit option is given.
475    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
476        ovector, the return from the function was zero, implying that there were
477        other matches that did not fit. The correct "exactly full" value is now
478        returned.
480    6.  If a subpattern that was called recursively or as a subroutine contained
481        (*PRUNE) or any other control that caused it to give a non-standard return,
482        invalid errors such as "Error -26 (nested recursion at the same subject
483        position)" or even infinite loops could occur.
485    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
486        computing the minimum length on reaching *ACCEPT, and so ended up with the
487        wrong value of 1 rather than 0. Further investigation indicates that
488        computing a minimum subject length in the presence of *ACCEPT is difficult
489        (think back references, subroutine calls), and so I have changed the code
490        so that no minimum is registered for a pattern that contains *ACCEPT.
492    8.  If (*THEN) was present in the first (true) branch of a conditional group,
493        it was not handled as intended. [But see 16 below.]
495    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
496        Sheri Pierce.
498    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
499        the first byte in a match must be "a".
501    11. Change 17 for 8.13 increased the recursion depth for patterns like
502        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
503        pattern contains any instances of (*THEN). If it does not, the old
504        optimizations are restored. It would be nice to do this on a per-group
505        basis, but at the moment that is not feasible.
507    12. In some environments, the output of pcretest -C is CRLF terminated. This
508        broke RunTest's code that checks for the link size. A single white space
509        character after the value is now allowed for.
511    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
512        For "fr", it uses the Windows-specific input and output files.
514    14. If (*THEN) appeared in a group that was called recursively or as a
515        subroutine, it did not work as intended. [But see next item.]
517    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
518        pattern fragments (but not containing any | characters). If A and B are
519        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
520        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
521        D. In other words, Perl considers parentheses that do not contain any |
522        characters to be part of a surrounding alternative, whereas PCRE was
523        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
524        differently. PCRE now behaves in the same way as Perl, except in the case
525        of subroutine/recursion calls such as (?1) which have in any case always
526        been different (but PCRE had them first :-).
528    16. Related to 15 above: Perl does not treat the | in a conditional group as
529        creating alternatives. Such a group is treated in the same way as an
530        ordinary group without any | characters when processing (*THEN). PCRE has
531        been changed to match Perl's behaviour.
533    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
534        RunGrepTest script failed.
536    18. Change 22 for version 13 caused atomic groups to use more stack. This is
537        inevitable for groups that contain captures, but it can lead to a lot of
538        stack use in large patterns. The old behaviour has been restored for atomic
539        groups that do not contain any capturing parentheses.
541    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
542        suppress the check for a minimum subject length at run time. (If it was
543        given to pcre_exec() or pcre_dfa_exec() it did work.)
545    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
546        fail to work when decoding hex characters in data strings in EBCDIC
547        environments.
549    21. It appears that in at least one Mac OS environment, the isxdigit() function
550        is implemented as a macro that evaluates to its argument more than once,
551        contravening the C 90 Standard (I haven't checked a later standard). There
552        was an instance in pcretest which caused it to go wrong when processing
553        \x{...} escapes in subject strings. The has been rewritten to avoid using
554        things like p++ in the argument of isxdigit().
557    Version 8.13 16-Aug-2011
558    ------------------------
560    1.  The Unicode data tables have been updated to Unicode 6.0.0.
562    2.  Two minor typos in pcre_internal.h have been fixed.
564    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
565        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
566        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
568    4.  There were a number of related bugs in the code for matching backrefences
569        caselessly in UTF-8 mode when codes for the characters concerned were
570        different numbers of bytes. For example, U+023A and U+2C65 are an upper
571        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
572        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
573        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
574        2-byte code at the end of the subject (it thought there wasn't enough data
575        left).
577    5.  Comprehensive information about what went wrong is now returned by
578        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
579        as the output vector has at least 2 elements. The offset of the start of
580        the failing character and a reason code are placed in the vector.
582    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
583        now returned is for the first byte of the failing character, instead of the
584        last byte inspected. This is an incompatible change, but I hope it is small
585        enough not to be a problem. It makes the returned offset consistent with
586        pcre_exec() and pcre_dfa_exec().
588    7.  pcretest now gives a text phrase as well as the error number when
589        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
590        failure, the offset and reason code are output.
592    8.  When \R was used with a maximizing quantifier it failed to skip backwards
593        over a \r\n pair if the subsequent match failed. Instead, it just skipped
594        back over a single character (\n). This seems wrong (because it treated the
595        two characters as a single entity when going forwards), conflicts with the
596        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
597        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
598        has been changed.
600    9.  Some internal refactoring has changed the processing so that the handling
601        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
602        time (the PCRE_DOTALL option was changed this way some time ago: version
603        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
604        which was always a bit of a fudge. It also means that there is one less
605        argument for the match() function, which reduces its stack requirements
606        slightly. This change also fixes an incompatibility with Perl: the pattern
607        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
609    10. More internal refactoring has drastically reduced the number of recursive
610        calls to match() for possessively repeated groups such as (abc)++ when
611        using pcre_exec().
613    11. While implementing 10, a number of bugs in the handling of groups were
614        discovered and fixed:
616        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
617        (a|)*(?1) gave a compile-time internal error.
618        ((a|)+)+  did not notice that the outer group could match an empty string.
619        (^a|^)+   was not marked as anchored.
620        (.*a|.*)+ was not marked as matching at start or after a newline.
622    12. Yet more internal refactoring has removed another argument from the match()
623        function. Special calls to this function are now indicated by setting a
624        value in a variable in the "match data" data block.
626    13. Be more explicit in pcre_study() instead of relying on "default" for
627        opcodes that mean there is no starting character; this means that when new
628        ones are added and accidentally left out of pcre_study(), testing should
629        pick them up.
631    14. The -s option of pcretest has been documented for ages as being an old
632        synonym of -m (show memory usage). I have changed it to mean "force study
633        for every regex", that is, assume /S for every regex. This is similar to -i
634        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
635        using it. It makes it easier to run collections of tests with and without
636        study enabled, and thereby test pcre_study() more easily. All the standard
637        tests are now run with and without -s (but some patterns can be marked as
638        "never study" - see 20 below).
640    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
641        restoration of the capturing data to the outer values was not happening
642        correctly.
644    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
645        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
646        pattern had matched an empty string, and so incorrectly returned a no
647        match.
649    17. There was optimizing code for the last branch of non-capturing parentheses,
650        and also for the obeyed branch of a conditional subexpression, which used
651        tail recursion to cut down on stack usage. Unfortunately, now that there is
652        the possibility of (*THEN) occurring in these branches, tail recursion is
653        no longer possible because the return has to be checked for (*THEN). These
654        two optimizations have therefore been removed. [But see 8.20/11 above.]
656    18. If a pattern containing \R was studied, it was assumed that \R always
657        matched two bytes, thus causing the minimum subject length to be
658        incorrectly computed because \R can also match just one byte.
660    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
661        was incorrectly computed.
663    20. If /S is present twice on a test pattern in pcretest input, it now
664        *disables* studying, thereby overriding the use of -s on the command line
665        (see 14 above). This is necessary for one or two tests to keep the output
666        identical in both cases.
668    21. When (*ACCEPT) was used in an assertion that matched an empty string and
669        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
671    22. When an atomic group that contained a capturing parenthesis was
672        successfully matched, but the branch in which it appeared failed, the
673        capturing was not being forgotten if a higher numbered group was later
674        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
675        group 1 to "a", when in fact it should be unset. This applied to multi-
676        branched capturing and non-capturing groups, repeated or not, and also to
677        positive assertions (capturing in negative assertions does not happen
678        in PCRE) and also to nested atomic groups.
680    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
681        subject after a captured substring, to make it easier to tell which of a
682        number of identical substrings has been captured.
684    24. The way atomic groups are processed by pcre_exec() has been changed so that
685        if they are repeated, backtracking one repetition now resets captured
686        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
687        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
688        "aaa". Previously, it would have been "a". As part of this code
689        refactoring, the way recursive calls are handled has also been changed.
691    25. If an assertion condition captured any substrings, they were not passed
692        back unless some other capturing happened later. For example, if
693        (?(?=(a))a) was matched against "a", no capturing was returned.
695    26. When studying a pattern that contained subroutine calls or assertions,
696        the code for finding the minimum length of a possible match was handling
697        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
698        group 1 called group 2 while simultaneously a separate group 2 called group
699        1). A stack overflow occurred in this case. I have fixed this by limiting
700        the recursion depth to 10.
702    27. Updated RunTest.bat in the distribution to the version supplied by Tom
703        Fortmann. This supports explicit test numbers on the command line, and has
704        argument validation and error reporting.
706    28. An instance of \X with an unlimited repeat could fail if at any point the
707        first character it looked at was a mark character.
709    29. Some minor code refactoring concerning Unicode properties and scripts
710        should reduce the stack requirement of match() slightly.
712    30. Added the '=' option to pcretest to check the setting of unused capturing
713        slots at the end of the pattern, which are documented as being -1, but are
714        not included in the return count.
716    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
717        compiled something random. Now it gives a compile-time error (as does
718        Perl).
720    32. A *MARK encountered during the processing of a positive assertion is now
721        recorded and passed back (compatible with Perl).
723    33. If --only-matching or --colour was set on a pcregrep call whose pattern
724        had alternative anchored branches, the search for a second match in a line
725        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
726        matched the line "0102" twice. The same bug affected patterns that started
727        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
728        twice.
730    34. Previously, PCRE did not allow quantification of assertions. However, Perl
731        does, and because of capturing effects, quantifying parenthesized
732        assertions may at times be useful. Quantifiers are now allowed for
733        parenthesized assertions.
735    35. A minor code tidy in pcre_compile() when checking options for \R usage.
737    36. \g was being checked for fancy things in a character class, when it should
738        just be a literal "g".
740    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
741        appearance of a nested POSIX class supersedes an apparent external class.
742        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
743        unescaped square brackets may also appear as part of class names. For
744        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
745        more like Perl. (But see 8.20/1 above.)
747    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
748        was because it thought it was \N{name}, which is not supported).
750    39. Add minix to OS list not supporting the -S option in pcretest.
752    40. PCRE tries to detect cases of infinite recursion at compile time, but it
753        cannot analyze patterns in sufficient detail to catch mutual recursions
754        such as ((?1))((?2)). There is now a runtime test that gives an error if a
755        subgroup is called recursively as a subpattern for a second time at the
756        same position in the subject string. In previous releases this might have
757        been caught by the recursion limit, or it might have run out of stack.
759    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
760        happen only once. PCRE was, however incorrectly giving a compile time error
761        "recursive call could loop indefinitely" because it cannot analyze the
762        pattern in sufficient detail. The compile time test no longer happens when
763        PCRE is compiling a conditional subpattern, but actual runaway loops are
764        now caught at runtime (see 40 above).
766    42. It seems that Perl allows any characters other than a closing parenthesis
767        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
768        has been changed to be the same.
770    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
771        as not to get warnings when autogen.sh is called. Also changed
772        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
774    44. To help people who use pcregrep to scan files containing exceedingly long
775        lines, the following changes have been made:
777        (a) The default value of the buffer size parameter has been increased from
778            8K to 20K. (The actual buffer used is three times this size.)
780        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
781            PCRE is built.
783        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
784            to be set at run time.
786        (d) Numerical values in pcregrep options can be followed by K or M, for
787            example --buffer-size=50K.
789        (e) If a line being scanned overflows pcregrep's buffer, an error is now
790            given and the return code is set to 2.
792    45. Add a pointer to the latest mark to the callout data block.
794    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
795        partial match of an empty string instead of no match. This was specific to
796        the use of ".".
798    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
799        complete match instead of a partial match. This bug was dependent on both
800        the PCRE_UTF8 and PCRE_DOTALL options being set.
802    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
803        starting byte set, because \b was not being ignored.
806    Version 8.12 15-Jan-2011
807    ------------------------
809    1.  Fixed some typos in the markup of the man pages, and wrote a script that
810        checks for such things as part of the documentation building process.
812    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
813        --match-limit and --recursion-limit options (added for 8.11). In
814        particular, this made one of the standard tests fail. (The integer value
815        went into the wrong half of a long int.)
817    3.  If the --colour option was given to pcregrep with -v (invert match), it
818        did strange things, either producing crazy output, or crashing. It should,
819        of course, ignore a request for colour when reporting lines that do not
820        match.
822    4.  Another pcregrep bug caused similar problems if --colour was specified with
823        -M (multiline) and the pattern match finished with a line ending.
825    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
826        matched in multiline mode, the following line was shown as part of the
827        match. This seems wrong, so I have changed it.
829    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
830        the check for further matches in the same line (so they could be coloured)
831        to overrun the end of the current line. If another match was found, it was
832        incorrectly shown (and then shown again when found in the next line).
834    7.  If pcregrep was compiled under Windows, there was a reference to the
835        function pcregrep_exit() before it was defined. I am assuming this was
836        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
837        reported by a user. I've moved the definition above the reference.
840    Version 8.11 10-Dec-2010
841    ------------------------
843    1.  (*THEN) was not working properly if there were untried alternatives prior
844        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
845        backtracked to try for "b" instead of moving to the next alternative branch
846        at the same level (in this case, to look for "c"). The Perl documentation
847        is clear that when (*THEN) is backtracked onto, it goes to the "next
848        alternative in the innermost enclosing group".
850    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
851        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
852        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
853        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
854        (*THEN).
856    3.  If \s appeared in a character class, it removed the VT character from
857        the class, even if it had been included by some previous item, for example
858        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
859        of \s, but is part of the POSIX "space" class.)
861    4.  A partial match never returns an empty string (because you can always
862        match an empty string at the end of the subject); however the checking for
863        an empty string was starting at the "start of match" point. This has been
864        changed to the "earliest inspected character" point, because the returned
865        data for a partial match starts at this character. This means that, for
866        example, /(?<=abc)def/ gives a partial match for the subject "abc"
867        (previously it gave "no match").
869    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
870        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
871        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
872        has an implication that the given string is incomplete (because a partial
873        match is preferred over a full match). For this reason, these items now
874        give a partial match in this situation. [Aside: previously, the one case
875        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
876        match rather than a full match, which was wrong by the old rules, but is
877        now correct.]
879    6.  There was a bug in the handling of #-introduced comments, recognized when
880        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
881        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
882        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
883        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
884        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
885        places in pcre_compile().
887    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
888        comments when looking ahead for named forward references to subpatterns,
889        the only newline sequence it recognized was NL. It now handles newlines
890        according to the set newline convention.
892    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
893        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
894        cater for a lack of strerror(). These oversights have been fixed.
896    9.  Added --match-limit and --recursion-limit to pcregrep.
898    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
900    11. When the -o option was used, pcregrep was setting a return code of 1, even
901        when matches were found, and --line-buffered was not being honoured.
903    12. Added an optional parentheses number to the -o and --only-matching options
904        of pcregrep.
906    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
907        can match an empty string. The code to do it in pcretest and pcredemo
908        needed fixing:
910        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
911            only one byte after an empty string match just before CRLF (this case
912            just got forgotten; "any" and "anycrlf" were OK).
914        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
915            mode when an empty string match preceded an ASCII character followed by
916            a non-ASCII character. (The code for advancing by one character rather
917            than one byte was nonsense.)
919        (c) The pcredemo.c sample program did not have any code at all to handle
920            the cases when CRLF is a valid newline sequence.
922    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
923        as a starting offset was within the subject string. There is now a new
924        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
925        negative or greater than the length of the string. In order to test this,
926        pcretest is extended to allow the setting of negative starting offsets.
928    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
929        starting offset points to the beginning of a UTF-8 character was
930        unnecessarily clumsy. I tidied it up.
932    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
933        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
935    17. Nobody had reported that the --include_dir option, which was added in
936        release 7.7 should have been called --include-dir (hyphen, not underscore)
937        for compatibility with GNU grep. I have changed it to --include-dir, but
938        left --include_dir as an undocumented synonym, and the same for
939        --exclude-dir, though that is not available in GNU grep, at least as of
940        release 2.5.4.
942    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
943        characters from a string of bytes) have been redefined so as not to use
944        loops, in order to improve performance in some environments. At the same
945        time, I abstracted some of the common code into auxiliary macros to save
946        repetition (this should not affect the compiled code).
948    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
949        compile-time error is now given if \c is not followed by an ASCII
950        character, that is, a byte less than 128. (In EBCDIC mode, the code is
951        different, and any byte value is allowed.)
953    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
954        START_OPTIMIZE option, which is now allowed at compile time - but just
955        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
956        to pcregrep and other applications that have no direct access to PCRE
957        options. The new /Y option in pcretest sets this option when calling
958        pcre_compile().
960    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
961        back references. Groups containing recursive back references were forced to
962        be atomic by that change, but in the case of named groups, the amount of
963        memory required was incorrectly computed, leading to "Failed: internal
964        error: code overflow". This has been fixed.
966    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
967        pcretest.c, to avoid build problems in some Borland environments.
970    Version 8.10 25-Jun-2010
971    ------------------------
973    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
974        THEN.
976    2.  (*ACCEPT) was not working when inside an atomic group.
978    3.  Inside a character class, \B is treated as a literal by default, but
979        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
980        causes the error). The code is unchanged, but I tidied the documentation.
982    4.  Inside a character class, PCRE always treated \R and \X as literals,
983        whereas Perl faults them if its -w option is set. I have changed PCRE so
984        that it faults them when PCRE_EXTRA is set.
986    5.  Added support for \N, which always matches any character other than
987        newline. (It is the same as "." when PCRE_DOTALL is not set.)
989    6.  When compiling pcregrep with newer versions of gcc which may have
990        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
991        declared with attribute warn_unused_result" were given. Just casting the
992        result to (void) does not stop the warnings; a more elaborate fudge is
993        needed. I've used a macro to implement this.
995    7.  Minor change to pcretest.c to avoid a compiler warning.
997    8.  Added four artifical Unicode properties to help with an option to make
998        \s etc use properties (see next item). The new properties are: Xan
999        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1001    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1002        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1003        this option. Modified pcretest to add /W to test this facility. Added
1004        REG_UCP to make it available via the POSIX interface.
1006    10. Added --line-buffered to pcregrep.
1008    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1009        studied, and the match started with a letter with a code point greater than
1010        127 whose first byte was different to the first byte of the other case of
1011        the letter, the other case of this starting letter was not recognized
1012        (#976).
1014    12. If a pattern that was studied started with a repeated Unicode property
1015        test, for example, \p{Nd}+, there was the theoretical possibility of
1016        setting up an incorrect bitmap of starting bytes, but fortunately it could
1017        not have actually happened in practice until change 8 above was made (it
1018        added property types that matched character-matching opcodes).
1020    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1021        possible starting bytes for non-anchored patterns.
1023    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1024        \R, and also a number of cases that involve Unicode properties, both
1025        explicit and implicit when PCRE_UCP is set.
1027    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1028        input, it could crash or give wrong results if characters with values
1029        greater than 0xc0 were present in the subject string. (Detail: it assumed
1030        UTF-8 input when processing these items.)
1032    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1033        size_t is 64-bit (#991).
1035    17. Added a check for running out of memory when PCRE is compiled with
1036        --disable-stack-for-recursion (#990).
1038    18. If the last data line in a file for pcretest does not have a newline on
1039        the end, a newline was missing in the output.
1041    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1042        less than 128) in its various bitmaps. However, there is a facility for
1043        generating tables according to the current locale when PCRE is compiled. It
1044        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1045        characters, are recognized by isspace() and therefore were getting set in
1046        these tables, and indeed these tables seem to approximate to ISO 8859. This
1047        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1048        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1049        which of course cannot start UTF-8 characters. I have changed the code so
1050        that only real ASCII characters (less than 128) and the correct starting
1051        bytes for UTF-8 encodings are set for characters greater than 127 when in
1052        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1053        altogether.)
1055    20. Added the /T option to pcretest so as to be able to run tests with non-
1056        standard character tables, thus making it possible to include the tests
1057        used for 19 above in the standard set of tests.
1059    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1060        reference to a subpattern the other side of a comment that contains an
1061        opening parenthesis caused either an internal compiling error, or a
1062        reference to the wrong subpattern.
1065    Version 8.02 19-Mar-2010
1066  ------------------------  ------------------------
1068  1.  The Unicode data tables have been updated to Unicode 5.2.0.  1.  The Unicode data tables have been updated to Unicode 5.2.0.
1070    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
1071        configured.
1073    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
1074        original author of that file, following a query about its status.
1076    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
1077        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1079    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1080        quantifier applied to a forward-referencing subroutine call, could compile
1081        incorrect code or give the error "internal error: previously-checked
1082        referenced subpattern not found".
1084    6.  Both MS Visual Studio and Symbian OS have problems with initializing
1085        variables to point to external functions. For these systems, therefore,
1086        pcre_malloc etc. are now initialized to local functions that call the
1087        relevant global functions.
1089    7.  There were two entries missing in the vectors called coptable and poptable
1090        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1091        I've fixed the data, and added a kludgy way of testing at compile time that
1092        the lengths are correct (equal to the number of opcodes).
1094    8.  Following on from 7, I added a similar kludge to check the length of the
1095        eint vector in pcreposix.c.
1097    9.  Error texts for pcre_compile() are held as one long string to avoid too
1098        much relocation at load time. To find a text, the string is searched,
1099        counting zeros. There was no check for running off the end of the string,
1100        which could happen if a new error number was added without updating the
1101        string.
1103    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1105    11. \K was not working if it appeared in an atomic group or in a group that
1106        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1107        \K is "not well defined" if used in an assertion. PCRE now accepts it if
1108        the assertion is positive, but not if it is negative.
1110    12. Change 11 fortuitously reduced the size of the stack frame used in the
1111        "match()" function of pcre_exec.c by one pointer. Forthcoming
1112        implementation of support for (*MARK) will need an extra pointer on the
1113        stack; I have reserved it now, so that the stack frame size does not
1114        decrease.
1116    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1117        item in branch that calls a recursion is a subroutine call - as in the
1118        second branch in the above example - was incorrectly given the compile-
1119        time error "recursive call could loop indefinitely" because pcre_compile()
1120        was not correctly checking the subroutine for matching a non-empty string.
1122    14. The checks for overrunning compiling workspace could trigger after an
1123        overrun had occurred. This is a "should never occur" error, but it can be
1124        triggered by pathological patterns such as hundreds of nested parentheses.
1125        The checks now trigger 100 bytes before the end of the workspace.
1127    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1130  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
1131  ------------------------  ------------------------

Removed from v.491  
changed lines
  Added in v.1045

  ViewVC Help
Powered by ViewVC 1.1.5