ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 753 by ph10, Sat Nov 19 17:03:35 2011 UTC revision 1313 by ph10, Wed Apr 24 12:07:09 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.21  Version 8.33 xx-xxxx-201x
5  ------------  -------------------------
7    1.  Added 'U' to some constants that are compared to unsigned integers, to
8        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
9        variables that are added to signed variables, to ensure the result is
10        signed and can be negated.
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
15    3.  Revise the creation of config.h.generic so that all boolean macros are
16        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
17        overriding via -D on the command line possible.
19    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
20        to unsigned int is reported to make a quite noticeable speed difference in
21        a specific Windows environment. Testing on Linux did also appear to show
22        some benefit (and it is clearly not harmful). Also fixed the definition of
23        Xop which should be unsigned.
25    5.  Related to (4), changing the definition of the intermediate variable cc
26        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
27        improvements.
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
37    9.  Optimizing fast_forward_start_bits in JIT.
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
44        (b) Minimum length was not checked before the matching is started.
46    11. The value of capture_last that is passed to callouts was incorrect in some
47        cases when there was a capture on one path that was subsequently abandoned
48        after a backtrack. Also, the capture_last value is now reset after a
49        recursion, since all captures are also reset in this case.
51    12. The interpreter no longer returns the "too many substrings" error in the
52        case when an overflowing capture is in a branch that is subsequently
53        abandoned after a backtrack.
55    13. In the pathological case when an offset vector of size 2 is used, pcretest
56        now prints out the matched string after a yield of 0 or 1.
58    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
59        Only supported by the JIT compiler at the moment.
61    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
63    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
64        offset of the starting point of the matching process, provided the offsets
65        vector is large enough.
67    17. The \A escape now records a lookbehind value of 1, though its execution
68        does not actually inspect the previous character. This is to ensure that,
69        in partial multi-segment matching, at least one character from the old
70        segment is retained when a new segment is processed. Otherwise, if there
71        are no lookbehinds in the pattern, \A might match incorrectly at the start
72        of a new segment.
74    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
76    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
77        gives some modest performance improvement in 8-bit mode.
79    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
80        be expressed in certain programming languages using Universal Character
81        Names.
83    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
84        which points out that "non characters" are not "characters that may not
85        appear in Unicode strings" but rather "characters that are reserved for
86        internal use and have only local meaning".
88    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
89        there was a conditional group that depended on an assertion, if the
90        assertion was false, the callout that immediately followed the alternation
91        in the condition was skipped when pcre_exec() was used for matching.
93    23. Allow an explicit callout to be inserted before an assertion that is the
94        condition for a conditional group, for compatibility with automatic
95        callouts, which always insert a callout at this point.
97    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
98        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
100    25. (*PRUNE) is now supported by the JIT compiler.
102    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
104    27. Fix the case where there are two or more SKIPs with arguments that may be
105        ignored.
107    28. (*SKIP) is now supported by the JIT compiler.
109    29. (*THEN) is now supported by the JIT compiler.
111    30. Update RunTest with additional test selector options.
113    31. The way PCRE handles backtracking verbs has been changed in two ways.
115        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
116        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
117        backtracking. In some cases this makes it more Perl-compatible, but Perl's
118        rather obscure rules do not always do the same thing.
120        (2) Previously, backtracking verbs were confined within assertions. This is
121        no longer the case for positive assertions, except for (*ACCEPT). Again,
122        this sometimes improves Perl compatibility, and sometimes does not.
124    32. A number of tests that were in test 2 because Perl did things differently
125        have been moved to test 1, because either Perl or PCRE has changed, and
126        these tests are now compatible.
128    32. Control verbs are handled in the same way in JIT and interpreter.
130    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
131        contained a forward subroutine reference caused a compile error.
133    34. Auto-detect and optimize limited repetitions in JIT.
135    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
136        blocking (*UTF) etc.
138    36. In the interpreter, maximizing pattern repetitions for characters and
139        character types now use tail recursion, which reduces stack usage.
141    37. The value of the max lookbehind was not correctly preserved if a compiled
142        and saved regex was reloaded on a host of different endianness.
144    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION).
147    Version 8.32 30-November-2012
148    -----------------------------
150    1.  Improved JIT compiler optimizations for first character search and single
151        character iterators.
153    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
154        Patch by Daniel Richard G.
156    3.  Single character iterator optimizations in the JIT compiler.
158    4.  Improved JIT compiler optimizations for character ranges.
160    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
161        Reported by Giuseppe D'Angelo.
163    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
164        of a line, was being set incorrectly in cases where .* appeared inside
165        atomic brackets at the start of a pattern, or where there was a subsequent
166        *PRUNE or *SKIP.
168    7.  Improved instruction cache flush for POWER/PowerPC.
169        Patch by Daniel Richard G.
171    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
172        grep:
174        (a) There is now no limit to the number of patterns to be matched.
176        (b) An error is given if a pattern is too long.
178        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
179            are now supported.
181        (d) --exclude-from and --include-from (multiple use) have been added.
183        (e) Exclusions and inclusions now apply to all files and directories, not
184            just to those obtained from scanning a directory recursively.
186        (f) Multiple uses of -f and --file-list are now supported.
188        (g) In a Windows environment, the default for -d has been changed from
189            "read" (the GNU grep default) to "skip", because otherwise the presence
190            of a directory in the file list provokes an error.
192        (h) The documentation has been revised and clarified in places.
194    9.  Improve the matching speed of capturing brackets.
196    10. Changed the meaning of \X so that it now matches a Unicode extended
197        grapheme cluster.
199    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
200        out POSIX threads when JIT support is configured.
202    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
204    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
205        structure could go wrong in environments where size_t is not the same size
206        as int.
208    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
209        set.
211    15. The EBCDIC support had decayed; later updates to the code had included
212        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
213        general tidy up of EBCDIC-related issues, and the documentation was also
214        not quite right. There is now a test that can be run on ASCII systems to
215        check some of the EBCDIC-related things (but is it not a full test).
217    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
218        in a small tidy to the code.
220    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
222    18. If the --only-matching (-o) option in pcregrep is specified multiple
223        times, each one causes appropriate output. For example, -o1 -o2 outputs the
224        substrings matched by the 1st and 2nd capturing parentheses. A separating
225        string can be specified by --om-separator (default empty).
227    19. Improving the first n character searches.
229    20. Turn case lists for horizontal and vertical white space into macros so that
230        they are defined only once.
232    21. This set of changes together give more compatible Unicode case-folding
233        behaviour for characters that have more than one other case when UCP
234        support is available.
236        (a) The Unicode property table now has offsets into a new table of sets of
237            three or more characters that are case-equivalent. The MultiStage2.py
238            script that generates these tables (the pcre_ucd.c file) now scans
239            CaseFolding.txt instead of UnicodeData.txt for character case
240            information.
242        (b) The code for adding characters or ranges of characters to a character
243            class has been abstracted into a generalized function that also handles
244            case-independence. In UTF-mode with UCP support, this uses the new data
245            to handle characters with more than one other case.
247        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
248            whose other case is greater than 256 are now correctly matched
249            caselessly. Previously, the high codepoint matched the low one, but not
250            vice versa.
252        (d) The processing of \h, \H, \v, and \ in character classes now makes use
253            of the new class addition function, using character lists defined as
254            macros alongside the case definitions of 20 above.
256        (e) Caseless back references now work with characters that have more than
257            one other case.
259        (f) General caseless matching of characters with more than one other case
260            is supported.
262    22. Unicode character properties were updated from Unicode 6.2.0
264    23. Improved CMake support under Windows. Patch by Daniel Richard G.
266    24. Add support for 32-bit character strings, and UTF-32
268    25. Major JIT compiler update (code refactoring and bugfixing).
269        Experimental Sparc 32 support is added.
271    26. Applied a modified version of Daniel Richard G's patch to create
272        pcre.h.generic and config.h.generic by "make" instead of in the
273        PrepareRelease script.
275    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
276        pcre_compile.c when checking for a zero character.
278    28. Introducing a native interface for JIT. Through this interface, the compiled
279        machine code can be directly executed. The purpose of this interface is to
280        provide fast pattern matching, so several sanity checks are not performed.
281        However, feature tests are still performed. The new interface provides
282        1.4x speedup compared to the old one.
284    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
285        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
286        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
288    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
289        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
290        the "old" RFC 2279). Instead, it ended up passing a negative length to
291        pcre_exec().
293    31. Add support for GCC's visibility feature to hide internal functions.
295    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
296        "unknown -C option" after outputting 0 or 1.
298    33. There is now support for generating a code coverage report for the test
299        suite in environments where gcc is the compiler and lcov is installed. This
300        is mainly for the benefit of the developers.
302    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
303        unaddressable using valgrind annotations, allowing valgrind to detect
304        invalid memory accesses. This is mainly for the benefit of the developers.
306    25. (*UTF) can now be used to start a pattern in any of the three libraries.
308    26. Give configure error if --enable-cpp but no C++ compiler found.
311    Version 8.31 06-July-2012
312    -------------------------
314    1.  Fixing a wrong JIT test case and some compiler warnings.
316    2.  Removed a bashism from the RunTest script.
318    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
319        to unsigned type, result still unsigned" that was given by an MS compiler
320        on encountering the code "-sizeof(xxx)".
322    4.  Partial matching support is added to the JIT compiler.
324    5.  Fixed several bugs concerned with partial matching of items that consist
325        of more than one character:
327        (a) /^(..)\1/ did not partially match "aba" because checking references was
328            done on an "all or nothing" basis. This also applied to repeated
329            references.
331        (b) \R did not give a hard partial match if \r was found at the end of the
332            subject.
334        (c) \X did not give a hard partial match after matching one or more
335            characters at the end of the subject.
337        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
338            a partial match for the string "\r".
340        (e) When newline was set to CRLF, the metacharacter "." did not recognize
341            a partial match for a CR character at the end of the subject string.
343    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
344        running pcretest, the text "(JIT)" added to the output whenever JIT is
345        actually used to run the match.
347    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
348        or /S+[+] with a digit between 1 and 7.
350    8.  OP_NOT now supports any UTF character not just single-byte ones.
352    9.  (*MARK) control verb is now supported by the JIT compiler.
354    10. The command "./RunTest list" lists the available tests without actually
355        running any of them. (Because I keep forgetting what they all are.)
359    12. Applied a (slightly modified) user-supplied patch that improves performance
360        when the heap is used for recursion (compiled with --disable-stack-for-
361        recursion). Instead of malloc and free for each heap frame each time a
362        logical recursion happens, frames are retained on a chain and re-used where
363        possible. This sometimes gives as much as 30% improvement.
365    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
366        call.
368    14. As documented, (*COMMIT) is now confined to within a positive assertion.
370    15. It is now possible to link pcretest with libedit as an alternative to
371        libreadline.
373    16. (*COMMIT) control verb is now supported by the JIT compiler.
375    17. The Unicode data tables have been updated to Unicode 6.1.0.
377    18. Added --file-list option to pcregrep.
379    19. Added binary file support to pcregrep, including the -a, --binary-files,
380        -I, and --text options.
382    20. The madvise function is renamed for posix_madvise for QNX compatibility
383        reasons. Fixed by Giuseppe D'Angelo.
385    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
387    22. Changed the option for creating symbolic links for 16-bit man pages from
388        -s to -sf so that re-installing does not cause issues.
390    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
392    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
393        matches in certain environments (the workspace was not being correctly
394        retained). Also added to pcre_dfa_exec() a simple plausibility check on
395        some of the workspace data at the beginning of a restart.
397    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
398        was not doing so when it should - probably a typo introduced by SVN 528
399        (change 8.10/14).
401    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
402        \w+ when the character tables indicated that \x{c4} was a word character.
403        There were several related cases, all because the tests for doing a table
404        lookup were testing for characters less than 127 instead of 255.
406    27. If a pattern contains capturing parentheses that are not used in a match,
407        their slots in the ovector are set to -1. For those that are higher than
408        any matched groups, this happens at the end of processing. In the case when
409        there were back references that the ovector was too small to contain
410        (causing temporary malloc'd memory to be used during matching), and the
411        highest capturing number was not used, memory off the end of the ovector
412        was incorrectly being set to -1. (It was using the size of the temporary
413        memory instead of the true size.)
415    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
416        ovector size, it uses memory at the end of the block that it has got.
418    29. Check for an overlong MARK name and give an error at compile time. The
419        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
421    30. JIT compiler update.
423    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
424        Rill for the patch.
426    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
428    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
430    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
431        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
432        was enabled.
434    35. Improve JIT code generation for greedy plus quantifier.
436    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
437        1 to "aa" instead of to an empty string. The bug affected repeated groups
438        that could potentially match an empty string.
440    37. Optimizing single character iterators in JIT.
442    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
443        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
444        codepoints that are too big for the mode are faulted, and in a UTF mode,
445        disallowed codepoints are also faulted.
447    39. If PCRE was compiled with UTF support, in three places in the DFA
448        matcher there was code that should only have been obeyed in UTF mode, but
449        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
450        processing when bytes with values greater than 127 were present. In 16-bit
451        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
452        both cases the values are those that cannot be the first data item in a UTF
453        character. The three items that might have provoked this were recursions,
454        possessively repeated groups, and atomic groups.
456    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
457        and pcregrep, because some OS require shared objects to be explicitly
458        passed to ld, causing the link step to fail if they are not.
460    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
461        mode, patterns that started with \h* or \R* might be incorrectly matched.
464    Version 8.30 04-February-2012
465    -----------------------------
467    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
468        name is defined in ctype.h.
470    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
471        only in quite long subpatterns.
473    3.  Removed the function pcre_info(), which has been obsolete and deprecated
474        since it was replaced by pcre_fullinfo() in February 2000.
476    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
477        match a (*MARK), and the match failed at the start of the subject, a
478        reference to memory before the start of the subject could occur. This bug
479        was introduced by fix 17 of release 8.21.
481    5.  A reference to an unset group with zero minimum repetition was giving
482        totally wrong answers (in non-JavaScript-compatibility mode). For example,
483        /(another)?(\1?)test/ matched against "hello world test". This bug was
484        introduced in release 8.13.
486    6.  Add support for 16-bit character strings (a large amount of work involving
487        many changes and refactorings).
489    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
490        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
491        from a file.
493    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
494        rounding is not applied in this particular case).
496    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
497        if they appear, or are escaped, in patterns.
499    10. Get rid of a number of -Wunused-but-set-variable warnings.
501    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
502        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
503        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
504        also returns the mark "x". This bug applied to capturing parentheses,
505        non-capturing parentheses, and atomic parentheses. It also applied to some
506        assertions.
508    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
509        information out of configure.ac instead of relying on pcre.h.generic, which
510        is not stored in the repository.
512    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
513        -lreadline.
515    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
517    15. Applied Graycode's patch to put the top-level frame on the stack rather
518        than the heap when not using the stack for recursion. This gives a
519        performance improvement in many cases when recursion is not deep.
521    16. Experimental code added to "pcretest -C" to output the stack frame size.
524    Version 8.21 12-Dec-2011
525    ------------------------
527  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
# Line 13  Version 8.21 Line 533  Version 8.21
533      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
534      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
536  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
537      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
538      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
# Line 22  Version 8.21 Line 542  Version 8.21
543  6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were  6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
544      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
545      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
547  7.  While fixing 6 above, I noticed that a number of other items were being  7.  While fixing 6 above, I noticed that a number of other items were being
548      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
549      opcodes had not been added to the fixed-length checking code. I have (a)      opcodes had not been added to the fixed-length checking code. I have (a)
550      corrected the bug and added tests for these items, and (b) arranged for an      corrected the bug and added tests for these items, and (b) arranged for an
551      error to occur if an unknown opcode is encountered while checking for fixed      error to occur if an unknown opcode is encountered while checking for fixed
552      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
553      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
554      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
555      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
557  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
558      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
560  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
561      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
562      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
563      the first (A) could occur when it should not.      the first (A) could occur when it should not.
565  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
567  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
569  12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems  12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
570      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
571      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
573    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
575    14. Perl does not support \N without a following name in a [] class; PCRE now
576        also gives an error.
578    15. If a forward reference was repeated with an upper limit of around 2000,
579        it caused the error "internal error: overran compiling workspace". The
580        maximum number of forward references (including repeats) was limited by the
581        internal workspace, and dependent on the LINK_SIZE. The code has been
582        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
583        the default depends on LINK_SIZE. There is a new upper limit (for safety)
584        of around 200,000 forward references. While doing this, I also speeded up
585        the filling in of repeated forward references.
587    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
588        incorrectly expecting the subject to contain another "a" after the start.
590    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
591        in the match, the SKIP should be ignored. This was not happening; instead
592        the SKIP was being treated as NOMATCH. For patterns such as
593        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
594        tested.
596    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
597        now much more compatible with Perl, in particular in cases where the result
598        is a non-match for a non-anchored pattern. For example, if
599        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
600        "m", where previously it did not return a name. A side effect of this
601        change is that for partial matches, the last encountered mark name is
602        returned, as for non matches. A number of tests that were previously not
603        Perl-compatible have been moved into the Perl-compatible test files. The
604        refactoring has had the pleasing side effect of removing one argument from
605        the match() function, thus reducing its stack requirements.
607    19. If the /S+ option was used in pcretest to study a pattern using JIT,
608        subsequent uses of /S (without +) incorrectly behaved like /S+.
610    21. Retrieve executable code size support for the JIT compiler and fixing
611        some warnings.
613    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
614        not work when the shorter character appeared right at the end of the
615        subject string.
617    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
618        systems.
620    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
621        output it when the /M option is used in pcretest.
623    25. The CheckMan script was not being included in the distribution. Also, added
624        an explicit "perl" to run Perl scripts from the PrepareRelease script
625        because this is reportedly needed in Windows.
627    26. If study data was being save in a file and studying had not found a set of
628        "starts with" bytes for the pattern, the data written to the file (though
629        never used) was taken from uninitialized memory and so caused valgrind to
630        complain.
632    27. Updated RunTest.bat as provided by Sheri Pierce.
634    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
636    29. Computation of memory usage for the table of capturing group names was
637        giving an unnecessarily large value.
640  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011

Removed from v.753  
changed lines
  Added in v.1313

  ViewVC Help
Powered by ViewVC 1.1.5