ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 654 by ph10, Tue Aug 2 11:00:40 2011 UTC revision 1046 by ph10, Tue Sep 25 16:27:58 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 02-Aug-2011  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 when UCP
91        support is available.
93        (a) The Unicode property table now has offsets into a new table of sets of
94            three or more characters that are case-equivalent. The MultiStage2.py
95            script that generates these tables (the pcre_ucd.c file) now scans
96            CaseFolding.txt instead of UnicodeData.txt for character case
97            information.
99        (b) The code for adding characters or ranges of characters to a character
100            class has been abstracted into a generalized function that also handles
101            case-independence. In UTF-mode with UCP support, this uses the new data
102            to handle characters with more than one other case.
104        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
105            whose other case is greater than 256 are now correctly matched
106            caselessly. Previously, the high codepoint matched the low one, but not
107            vice versa.
109        (d) The processing of \h, \H, \v, and \ in character classes now makes use
110            of the new class addition function, using character lists defined as
111            macros alongside the case definitions of 20 above.
113        (e) Caseless back references now work with characters that have more than
114            one other case.
116        (f) General caseless matching of characters with more than one other case
117            is supported.
120    Version 8.31 06-July-2012
121    -------------------------
123    1.  Fixing a wrong JIT test case and some compiler warnings.
125    2.  Removed a bashism from the RunTest script.
127    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
128        to unsigned type, result still unsigned" that was given by an MS compiler
129        on encountering the code "-sizeof(xxx)".
131    4.  Partial matching support is added to the JIT compiler.
133    5.  Fixed several bugs concerned with partial matching of items that consist
134        of more than one character:
136        (a) /^(..)\1/ did not partially match "aba" because checking references was
137            done on an "all or nothing" basis. This also applied to repeated
138            references.
140        (b) \R did not give a hard partial match if \r was found at the end of the
141            subject.
143        (c) \X did not give a hard partial match after matching one or more
144            characters at the end of the subject.
146        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
147            a partial match for the string "\r".
149        (e) When newline was set to CRLF, the metacharacter "." did not recognize
150            a partial match for a CR character at the end of the subject string.
152    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
153        running pcretest, the text "(JIT)" added to the output whenever JIT is
154        actually used to run the match.
156    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
157        or /S+[+] with a digit between 1 and 7.
159    8.  OP_NOT now supports any UTF character not just single-byte ones.
161    9.  (*MARK) control verb is now supported by the JIT compiler.
163    10. The command "./RunTest list" lists the available tests without actually
164        running any of them. (Because I keep forgetting what they all are.)
168    12. Applied a (slightly modified) user-supplied patch that improves performance
169        when the heap is used for recursion (compiled with --disable-stack-for-
170        recursion). Instead of malloc and free for each heap frame each time a
171        logical recursion happens, frames are retained on a chain and re-used where
172        possible. This sometimes gives as much as 30% improvement.
174    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
175        call.
177    14. As documented, (*COMMIT) is now confined to within a positive assertion.
179    15. It is now possible to link pcretest with libedit as an alternative to
180        libreadline.
182    16. (*COMMIT) control verb is now supported by the JIT compiler.
184    17. The Unicode data tables have been updated to Unicode 6.1.0.
186    18. Added --file-list option to pcregrep.
188    19. Added binary file support to pcregrep, including the -a, --binary-files,
189        -I, and --text options.
191    20. The madvise function is renamed for posix_madvise for QNX compatibility
192        reasons. Fixed by Giuseppe D'Angelo.
194    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
196    22. Changed the option for creating symbolic links for 16-bit man pages from
197        -s to -sf so that re-installing does not cause issues.
199    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
201    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
202        matches in certain environments (the workspace was not being correctly
203        retained). Also added to pcre_dfa_exec() a simple plausibility check on
204        some of the workspace data at the beginning of a restart.
206    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
207        was not doing so when it should - probably a typo introduced by SVN 528
208        (change 8.10/14).
210    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
211        \w+ when the character tables indicated that \x{c4} was a word character.
212        There were several related cases, all because the tests for doing a table
213        lookup were testing for characters less than 127 instead of 255.
215    27. If a pattern contains capturing parentheses that are not used in a match,
216        their slots in the ovector are set to -1. For those that are higher than
217        any matched groups, this happens at the end of processing. In the case when
218        there were back references that the ovector was too small to contain
219        (causing temporary malloc'd memory to be used during matching), and the
220        highest capturing number was not used, memory off the end of the ovector
221        was incorrectly being set to -1. (It was using the size of the temporary
222        memory instead of the true size.)
224    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
225        ovector size, it uses memory at the end of the block that it has got.
227    29. Check for an overlong MARK name and give an error at compile time. The
228        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
230    30. JIT compiler update.
232    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
233        Rill for the patch.
235    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
237    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
239    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
240        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
241        was enabled.
243    35. Improve JIT code generation for greedy plus quantifier.
245    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
246        1 to "aa" instead of to an empty string. The bug affected repeated groups
247        that could potentially match an empty string.
249    37. Optimizing single character iterators in JIT.
251    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
252        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
253        codepoints that are too big for the mode are faulted, and in a UTF mode,
254        disallowed codepoints are also faulted.
256    39. If PCRE was compiled with UTF support, in three places in the DFA
257        matcher there was code that should only have been obeyed in UTF mode, but
258        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
259        processing when bytes with values greater than 127 were present. In 16-bit
260        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
261        both cases the values are those that cannot be the first data item in a UTF
262        character. The three items that might have provoked this were recursions,
263        possessively repeated groups, and atomic groups.
265    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
266        and pcregrep, because some OS require shared objects to be explicitly
267        passed to ld, causing the link step to fail if they are not.
269    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
270        mode, patterns that started with \h* or \R* might be incorrectly matched.
273    Version 8.30 04-February-2012
274    -----------------------------
276    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
277        name is defined in ctype.h.
279    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
280        only in quite long subpatterns.
282    3.  Removed the function pcre_info(), which has been obsolete and deprecated
283        since it was replaced by pcre_fullinfo() in February 2000.
285    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
286        match a (*MARK), and the match failed at the start of the subject, a
287        reference to memory before the start of the subject could occur. This bug
288        was introduced by fix 17 of release 8.21.
290    5.  A reference to an unset group with zero minimum repetition was giving
291        totally wrong answers (in non-JavaScript-compatibility mode). For example,
292        /(another)?(\1?)test/ matched against "hello world test". This bug was
293        introduced in release 8.13.
295    6.  Add support for 16-bit character strings (a large amount of work involving
296        many changes and refactorings).
298    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
299        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
300        from a file.
302    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
303        rounding is not applied in this particular case).
305    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
306        if they appear, or are escaped, in patterns.
308    10. Get rid of a number of -Wunused-but-set-variable warnings.
310    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
311        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
312        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
313        also returns the mark "x". This bug applied to capturing parentheses,
314        non-capturing parentheses, and atomic parentheses. It also applied to some
315        assertions.
317    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
318        information out of configure.ac instead of relying on pcre.h.generic, which
319        is not stored in the repository.
321    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
322        -lreadline.
324    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
326    15. Applied Graycode's patch to put the top-level frame on the stack rather
327        than the heap when not using the stack for recursion. This gives a
328        performance improvement in many cases when recursion is not deep.
330    16. Experimental code added to "pcretest -C" to output the stack frame size.
333    Version 8.21 12-Dec-2011
334    ------------------------
336    1.  Updating the JIT compiler.
338    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
339        are added as well.
341    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
342        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
343        calling _pcre_jit_exec. Some extra comments are added.
345    4.  (*MARK) settings inside atomic groups that do not contain any capturing
346        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
347        was introduced by change 18 for 8.20.
349    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
350        ECMA-262 standard.
352    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
353        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
354        This bug was probably introduced by change 9 of 8.13.
356    7.  While fixing 6 above, I noticed that a number of other items were being
357        incorrectly rejected as "not fixed length". This arose partly because newer
358        opcodes had not been added to the fixed-length checking code. I have (a)
359        corrected the bug and added tests for these items, and (b) arranged for an
360        error to occur if an unknown opcode is encountered while checking for fixed
361        length instead of just assuming "not fixed length". The items that were
362        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
363        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
364        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
366    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
367        being incorrectly compiled and would have given unpredicatble results.
369    9.  A possessively repeated subpattern with minimum repeat count greater than
370        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
371        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
372        the first (A) could occur when it should not.
374    10. Add a cast and remove a redundant test from the code.
376    11. JIT should use pcre_malloc/pcre_free for allocation.
378    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
379        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
380        is anything other than /usr, -L is still shown).
382    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
384    14. Perl does not support \N without a following name in a [] class; PCRE now
385        also gives an error.
387    15. If a forward reference was repeated with an upper limit of around 2000,
388        it caused the error "internal error: overran compiling workspace". The
389        maximum number of forward references (including repeats) was limited by the
390        internal workspace, and dependent on the LINK_SIZE. The code has been
391        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
392        the default depends on LINK_SIZE. There is a new upper limit (for safety)
393        of around 200,000 forward references. While doing this, I also speeded up
394        the filling in of repeated forward references.
396    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
397        incorrectly expecting the subject to contain another "a" after the start.
399    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
400        in the match, the SKIP should be ignored. This was not happening; instead
401        the SKIP was being treated as NOMATCH. For patterns such as
402        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
403        tested.
405    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
406        now much more compatible with Perl, in particular in cases where the result
407        is a non-match for a non-anchored pattern. For example, if
408        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
409        "m", where previously it did not return a name. A side effect of this
410        change is that for partial matches, the last encountered mark name is
411        returned, as for non matches. A number of tests that were previously not
412        Perl-compatible have been moved into the Perl-compatible test files. The
413        refactoring has had the pleasing side effect of removing one argument from
414        the match() function, thus reducing its stack requirements.
416    19. If the /S+ option was used in pcretest to study a pattern using JIT,
417        subsequent uses of /S (without +) incorrectly behaved like /S+.
419    21. Retrieve executable code size support for the JIT compiler and fixing
420        some warnings.
422    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
423        not work when the shorter character appeared right at the end of the
424        subject string.
426    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
427        systems.
429    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
430        output it when the /M option is used in pcretest.
432    25. The CheckMan script was not being included in the distribution. Also, added
433        an explicit "perl" to run Perl scripts from the PrepareRelease script
434        because this is reportedly needed in Windows.
436    26. If study data was being save in a file and studying had not found a set of
437        "starts with" bytes for the pattern, the data written to the file (though
438        never used) was taken from uninitialized memory and so caused valgrind to
439        complain.
441    27. Updated RunTest.bat as provided by Sheri Pierce.
443    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
445    29. Computation of memory usage for the table of capturing group names was
446        giving an unnecessarily large value.
449    Version 8.20 21-Oct-2011
450    ------------------------
452    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
453        a POSIX class. After further experiments with Perl, which convinced me that
454        Perl has bugs and confusions, a closing square bracket is no longer allowed
455        in a POSIX name. This bug also affected patterns with classes that started
456        with full stops.
458    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
459        captured substring, but while checking the failing first alternative,
460        substring 1 is temporarily captured. If the output vector supplied to
461        pcre_exec() was not big enough for this capture, the yield of the function
462        was still zero ("insufficient space for captured substrings"). This cannot
463        be totally fixed without adding another stack variable, which seems a lot
464        of expense for a edge case. However, I have improved the situation in cases
465        such as /(a)(b)x|abc/ matched against "abc", where the return code
466        indicates that fewer than the maximum number of slots in the ovector have
467        been set.
469    3.  Related to (2) above: when there are more back references in a pattern than
470        slots in the output vector, pcre_exec() uses temporary memory during
471        matching, and copies in the captures as far as possible afterwards. It was
472        using the entire output vector, but this conflicts with the specification
473        that only 2/3 is used for passing back captured substrings. Now it uses
474        only the first 2/3, for compatibility. This is, of course, another edge
475        case.
477    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
478        main code base, and can be used by building with --enable-jit. When this is
479        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
480        runtime --no-jit option is given.
482    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
483        ovector, the return from the function was zero, implying that there were
484        other matches that did not fit. The correct "exactly full" value is now
485        returned.
487    6.  If a subpattern that was called recursively or as a subroutine contained
488        (*PRUNE) or any other control that caused it to give a non-standard return,
489        invalid errors such as "Error -26 (nested recursion at the same subject
490        position)" or even infinite loops could occur.
492    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
493        computing the minimum length on reaching *ACCEPT, and so ended up with the
494        wrong value of 1 rather than 0. Further investigation indicates that
495        computing a minimum subject length in the presence of *ACCEPT is difficult
496        (think back references, subroutine calls), and so I have changed the code
497        so that no minimum is registered for a pattern that contains *ACCEPT.
499    8.  If (*THEN) was present in the first (true) branch of a conditional group,
500        it was not handled as intended. [But see 16 below.]
502    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
503        Sheri Pierce.
505    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
506        the first byte in a match must be "a".
508    11. Change 17 for 8.13 increased the recursion depth for patterns like
509        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
510        pattern contains any instances of (*THEN). If it does not, the old
511        optimizations are restored. It would be nice to do this on a per-group
512        basis, but at the moment that is not feasible.
514    12. In some environments, the output of pcretest -C is CRLF terminated. This
515        broke RunTest's code that checks for the link size. A single white space
516        character after the value is now allowed for.
518    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
519        For "fr", it uses the Windows-specific input and output files.
521    14. If (*THEN) appeared in a group that was called recursively or as a
522        subroutine, it did not work as intended. [But see next item.]
524    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
525        pattern fragments (but not containing any | characters). If A and B are
526        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
527        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
528        D. In other words, Perl considers parentheses that do not contain any |
529        characters to be part of a surrounding alternative, whereas PCRE was
530        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
531        differently. PCRE now behaves in the same way as Perl, except in the case
532        of subroutine/recursion calls such as (?1) which have in any case always
533        been different (but PCRE had them first :-).
535    16. Related to 15 above: Perl does not treat the | in a conditional group as
536        creating alternatives. Such a group is treated in the same way as an
537        ordinary group without any | characters when processing (*THEN). PCRE has
538        been changed to match Perl's behaviour.
540    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
541        RunGrepTest script failed.
543    18. Change 22 for version 13 caused atomic groups to use more stack. This is
544        inevitable for groups that contain captures, but it can lead to a lot of
545        stack use in large patterns. The old behaviour has been restored for atomic
546        groups that do not contain any capturing parentheses.
548    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
549        suppress the check for a minimum subject length at run time. (If it was
550        given to pcre_exec() or pcre_dfa_exec() it did work.)
552    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
553        fail to work when decoding hex characters in data strings in EBCDIC
554        environments.
556    21. It appears that in at least one Mac OS environment, the isxdigit() function
557        is implemented as a macro that evaluates to its argument more than once,
558        contravening the C 90 Standard (I haven't checked a later standard). There
559        was an instance in pcretest which caused it to go wrong when processing
560        \x{...} escapes in subject strings. The has been rewritten to avoid using
561        things like p++ in the argument of isxdigit().
564    Version 8.13 16-Aug-2011
565  ------------------------  ------------------------
567  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 658  Version 8.13 02-Aug-2011
658      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
659      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
660      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
661      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
663  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
664      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 749  Version 8.13 02-Aug-2011
749      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
750      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
751      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
752      more like Perl.      more like Perl. (But see 8.20/1 above.)
754  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
755      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 784  Version 8.13 02-Aug-2011
784      (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
785          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
787      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
788          PCRE is built.          PCRE is built.
790      (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 246  Version 8.13 02-Aug-2011 Line 806  Version 8.13 02-Aug-2011
806      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
807      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
809    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
810        starting byte set, because \b was not being ignored.
813  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
814  ------------------------  ------------------------

Removed from v.654  
changed lines
  Added in v.1046

  ViewVC Help
Powered by ViewVC 1.1.5