ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 740 by zherczeg, Mon Oct 31 06:10:14 2011 UTC revision 1342 by ph10, Mon Jul 1 12:28:12 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.21  Version 8.34 xx-xxxx-201x
5  ------------  --------------------------
7    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
8        executable memory. Patch inspired by Carsten Klein.
10    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
11        this macro is never tested and has no effect, because the work to support
12        coverage involves only compiling and linking options and special targets in
13        the Makefile. The comment in config.h implied that defining the macro would
14        enable coverage support, which is totally false. There was also support for
15        setting this macro in the CMake files (my fault, I just copied it from
16        configure). SUPPORT_GCOV has now been removed.
19    Version 8.33 28-May-2013
20    --------------------------
22    1.  Added 'U' to some constants that are compared to unsigned integers, to
23        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
24        variables that are added to signed variables, to ensure the result is
25        signed and can be negated.
27    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
28        CMake config files.
30    3.  Revise the creation of config.h.generic so that all boolean macros are
31        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
32        overriding via -D on the command line possible.
34    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
35        to unsigned int is reported to make a quite noticeable speed difference in
36        a specific Windows environment. Testing on Linux did also appear to show
37        some benefit (and it is clearly not harmful). Also fixed the definition of
38        Xop which should be unsigned.
40    5.  Related to (4), changing the definition of the intermediate variable cc
41        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
42        improvements.
44    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
45        unnecessary spaces.
47    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
48        and later.
50    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
52    9.  Optimizing fast_forward_start_bits in JIT.
54    10. Adding support for callouts in JIT, and fixing some issues revealed
55        during this work. Namely:
57        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
59        (b) Minimum length was not checked before the matching is started.
61    11. The value of capture_last that is passed to callouts was incorrect in some
62        cases when there was a capture on one path that was subsequently abandoned
63        after a backtrack. Also, the capture_last value is now reset after a
64        recursion, since all captures are also reset in this case.
66    12. The interpreter no longer returns the "too many substrings" error in the
67        case when an overflowing capture is in a branch that is subsequently
68        abandoned after a backtrack.
70    13. In the pathological case when an offset vector of size 2 is used, pcretest
71        now prints out the matched string after a yield of 0 or 1.
73    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
74        Only supported by the JIT compiler at the moment.
76    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
78    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
79        offset of the starting point of the matching process, provided the offsets
80        vector is large enough.
82    17. The \A escape now records a lookbehind value of 1, though its execution
83        does not actually inspect the previous character. This is to ensure that,
84        in partial multi-segment matching, at least one character from the old
85        segment is retained when a new segment is processed. Otherwise, if there
86        are no lookbehinds in the pattern, \A might match incorrectly at the start
87        of a new segment.
89    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
91    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
92        gives some modest performance improvement in 8-bit mode.
94    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
95        be expressed in certain programming languages using Universal Character
96        Names.
98    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
99        which points out that "non characters" are not "characters that may not
100        appear in Unicode strings" but rather "characters that are reserved for
101        internal use and have only local meaning".
103    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
104        there was a conditional group that depended on an assertion, if the
105        assertion was false, the callout that immediately followed the alternation
106        in the condition was skipped when pcre_exec() was used for matching.
108    23. Allow an explicit callout to be inserted before an assertion that is the
109        condition for a conditional group, for compatibility with automatic
110        callouts, which always insert a callout at this point.
112    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
113        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
115    25. (*PRUNE) is now supported by the JIT compiler.
117    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
119    27. Fix the case where there are two or more SKIPs with arguments that may be
120        ignored.
122    28. (*SKIP) is now supported by the JIT compiler.
124    29. (*THEN) is now supported by the JIT compiler.
126    30. Update RunTest with additional test selector options.
128    31. The way PCRE handles backtracking verbs has been changed in two ways.
130        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
131        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
132        backtracking. In some cases this makes it more Perl-compatible, but Perl's
133        rather obscure rules do not always do the same thing.
135        (2) Previously, backtracking verbs were confined within assertions. This is
136        no longer the case for positive assertions, except for (*ACCEPT). Again,
137        this sometimes improves Perl compatibility, and sometimes does not.
139    32. A number of tests that were in test 2 because Perl did things differently
140        have been moved to test 1, because either Perl or PCRE has changed, and
141        these tests are now compatible.
143    32. Backtracking control verbs are now handled in the same way in JIT and
144        interpreter.
146    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
147        contained a forward subroutine reference caused a compile error.
149    34. Auto-detect and optimize limited repetitions in JIT.
151    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
152        blocking (*UTF) etc.
154    36. In the interpreter, maximizing pattern repetitions for characters and
155        character types now use tail recursion, which reduces stack usage.
157    37. The value of the max lookbehind was not correctly preserved if a compiled
158        and saved regex was reloaded on a host of different endianness.
160    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
161        of the compiled pattern block, expand the flags field from 16 to 32 bits
162        because it was almost full.
164    39. Try madvise first before posix_madvise.
166    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
167        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
168        original change locked out all matches of empty strings. This has been
169        changed so that one match of an empty string per line is recognized.
170        Subsequent searches on the same line (for colouring or for --only-matching,
171        for example) do not recognize empty strings.
173    41. Applied a user patch to fix a number of spelling mistakes in comments.
175    42. Data lines longer than 65536 caused pcretest to crash.
177    43. Clarified the data type for length and startoffset arguments for pcre_exec
178        and pcre_dfa_exec in the function-specific man pages, where they were
179        explicitly stated to be in bytes, never having been updated. I also added
180        some clarification to the pcreapi man page.
182    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
183        a segmentation fault.
186    Version 8.32 30-November-2012
187    -----------------------------
189    1.  Improved JIT compiler optimizations for first character search and single
190        character iterators.
192    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
193        Patch by Daniel Richard G.
195    3.  Single character iterator optimizations in the JIT compiler.
197    4.  Improved JIT compiler optimizations for character ranges.
199    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
200        Reported by Giuseppe D'Angelo.
202    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
203        of a line, was being set incorrectly in cases where .* appeared inside
204        atomic brackets at the start of a pattern, or where there was a subsequent
205        *PRUNE or *SKIP.
207    7.  Improved instruction cache flush for POWER/PowerPC.
208        Patch by Daniel Richard G.
210    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
211        grep:
213        (a) There is now no limit to the number of patterns to be matched.
215        (b) An error is given if a pattern is too long.
217        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
218            are now supported.
220        (d) --exclude-from and --include-from (multiple use) have been added.
222        (e) Exclusions and inclusions now apply to all files and directories, not
223            just to those obtained from scanning a directory recursively.
225        (f) Multiple uses of -f and --file-list are now supported.
227        (g) In a Windows environment, the default for -d has been changed from
228            "read" (the GNU grep default) to "skip", because otherwise the presence
229            of a directory in the file list provokes an error.
231        (h) The documentation has been revised and clarified in places.
233    9.  Improve the matching speed of capturing brackets.
235    10. Changed the meaning of \X so that it now matches a Unicode extended
236        grapheme cluster.
238    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
239        out POSIX threads when JIT support is configured.
241    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
243    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
244        structure could go wrong in environments where size_t is not the same size
245        as int.
247    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
248        set.
250    15. The EBCDIC support had decayed; later updates to the code had included
251        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
252        general tidy up of EBCDIC-related issues, and the documentation was also
253        not quite right. There is now a test that can be run on ASCII systems to
254        check some of the EBCDIC-related things (but is it not a full test).
256    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
257        in a small tidy to the code.
259    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
261    18. If the --only-matching (-o) option in pcregrep is specified multiple
262        times, each one causes appropriate output. For example, -o1 -o2 outputs the
263        substrings matched by the 1st and 2nd capturing parentheses. A separating
264        string can be specified by --om-separator (default empty).
266    19. Improving the first n character searches.
268    20. Turn case lists for horizontal and vertical white space into macros so that
269        they are defined only once.
271    21. This set of changes together give more compatible Unicode case-folding
272        behaviour for characters that have more than one other case when UCP
273        support is available.
275        (a) The Unicode property table now has offsets into a new table of sets of
276            three or more characters that are case-equivalent. The MultiStage2.py
277            script that generates these tables (the pcre_ucd.c file) now scans
278            CaseFolding.txt instead of UnicodeData.txt for character case
279            information.
281        (b) The code for adding characters or ranges of characters to a character
282            class has been abstracted into a generalized function that also handles
283            case-independence. In UTF-mode with UCP support, this uses the new data
284            to handle characters with more than one other case.
286        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
287            whose other case is greater than 256 are now correctly matched
288            caselessly. Previously, the high codepoint matched the low one, but not
289            vice versa.
291        (d) The processing of \h, \H, \v, and \ in character classes now makes use
292            of the new class addition function, using character lists defined as
293            macros alongside the case definitions of 20 above.
295        (e) Caseless back references now work with characters that have more than
296            one other case.
298        (f) General caseless matching of characters with more than one other case
299            is supported.
301    22. Unicode character properties were updated from Unicode 6.2.0
303    23. Improved CMake support under Windows. Patch by Daniel Richard G.
305    24. Add support for 32-bit character strings, and UTF-32
307    25. Major JIT compiler update (code refactoring and bugfixing).
308        Experimental Sparc 32 support is added.
310    26. Applied a modified version of Daniel Richard G's patch to create
311        pcre.h.generic and config.h.generic by "make" instead of in the
312        PrepareRelease script.
314    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
315        pcre_compile.c when checking for a zero character.
317    28. Introducing a native interface for JIT. Through this interface, the compiled
318        machine code can be directly executed. The purpose of this interface is to
319        provide fast pattern matching, so several sanity checks are not performed.
320        However, feature tests are still performed. The new interface provides
321        1.4x speedup compared to the old one.
323    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
324        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
325        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
327    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
328        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
329        the "old" RFC 2279). Instead, it ended up passing a negative length to
330        pcre_exec().
332    31. Add support for GCC's visibility feature to hide internal functions.
334    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
335        "unknown -C option" after outputting 0 or 1.
337    33. There is now support for generating a code coverage report for the test
338        suite in environments where gcc is the compiler and lcov is installed. This
339        is mainly for the benefit of the developers.
341    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
342        unaddressable using valgrind annotations, allowing valgrind to detect
343        invalid memory accesses. This is mainly for the benefit of the developers.
345    25. (*UTF) can now be used to start a pattern in any of the three libraries.
347    26. Give configure error if --enable-cpp but no C++ compiler found.
350    Version 8.31 06-July-2012
351    -------------------------
353    1.  Fixing a wrong JIT test case and some compiler warnings.
355    2.  Removed a bashism from the RunTest script.
357    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
358        to unsigned type, result still unsigned" that was given by an MS compiler
359        on encountering the code "-sizeof(xxx)".
361    4.  Partial matching support is added to the JIT compiler.
363    5.  Fixed several bugs concerned with partial matching of items that consist
364        of more than one character:
366        (a) /^(..)\1/ did not partially match "aba" because checking references was
367            done on an "all or nothing" basis. This also applied to repeated
368            references.
370        (b) \R did not give a hard partial match if \r was found at the end of the
371            subject.
373        (c) \X did not give a hard partial match after matching one or more
374            characters at the end of the subject.
376        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
377            a partial match for the string "\r".
379        (e) When newline was set to CRLF, the metacharacter "." did not recognize
380            a partial match for a CR character at the end of the subject string.
382    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
383        running pcretest, the text "(JIT)" added to the output whenever JIT is
384        actually used to run the match.
386    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
387        or /S+[+] with a digit between 1 and 7.
389    8.  OP_NOT now supports any UTF character not just single-byte ones.
391    9.  (*MARK) control verb is now supported by the JIT compiler.
393    10. The command "./RunTest list" lists the available tests without actually
394        running any of them. (Because I keep forgetting what they all are.)
398    12. Applied a (slightly modified) user-supplied patch that improves performance
399        when the heap is used for recursion (compiled with --disable-stack-for-
400        recursion). Instead of malloc and free for each heap frame each time a
401        logical recursion happens, frames are retained on a chain and re-used where
402        possible. This sometimes gives as much as 30% improvement.
404    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
405        call.
407    14. As documented, (*COMMIT) is now confined to within a positive assertion.
409    15. It is now possible to link pcretest with libedit as an alternative to
410        libreadline.
412    16. (*COMMIT) control verb is now supported by the JIT compiler.
414    17. The Unicode data tables have been updated to Unicode 6.1.0.
416    18. Added --file-list option to pcregrep.
418    19. Added binary file support to pcregrep, including the -a, --binary-files,
419        -I, and --text options.
421    20. The madvise function is renamed for posix_madvise for QNX compatibility
422        reasons. Fixed by Giuseppe D'Angelo.
424    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
426    22. Changed the option for creating symbolic links for 16-bit man pages from
427        -s to -sf so that re-installing does not cause issues.
429    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
431    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
432        matches in certain environments (the workspace was not being correctly
433        retained). Also added to pcre_dfa_exec() a simple plausibility check on
434        some of the workspace data at the beginning of a restart.
436    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
437        was not doing so when it should - probably a typo introduced by SVN 528
438        (change 8.10/14).
440    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
441        \w+ when the character tables indicated that \x{c4} was a word character.
442        There were several related cases, all because the tests for doing a table
443        lookup were testing for characters less than 127 instead of 255.
445    27. If a pattern contains capturing parentheses that are not used in a match,
446        their slots in the ovector are set to -1. For those that are higher than
447        any matched groups, this happens at the end of processing. In the case when
448        there were back references that the ovector was too small to contain
449        (causing temporary malloc'd memory to be used during matching), and the
450        highest capturing number was not used, memory off the end of the ovector
451        was incorrectly being set to -1. (It was using the size of the temporary
452        memory instead of the true size.)
454    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
455        ovector size, it uses memory at the end of the block that it has got.
457    29. Check for an overlong MARK name and give an error at compile time. The
458        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
460    30. JIT compiler update.
462    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
463        Rill for the patch.
465    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
467    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
469    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
470        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
471        was enabled.
473    35. Improve JIT code generation for greedy plus quantifier.
475    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
476        1 to "aa" instead of to an empty string. The bug affected repeated groups
477        that could potentially match an empty string.
479    37. Optimizing single character iterators in JIT.
481    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
482        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
483        codepoints that are too big for the mode are faulted, and in a UTF mode,
484        disallowed codepoints are also faulted.
486    39. If PCRE was compiled with UTF support, in three places in the DFA
487        matcher there was code that should only have been obeyed in UTF mode, but
488        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
489        processing when bytes with values greater than 127 were present. In 16-bit
490        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
491        both cases the values are those that cannot be the first data item in a UTF
492        character. The three items that might have provoked this were recursions,
493        possessively repeated groups, and atomic groups.
495    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
496        and pcregrep, because some OS require shared objects to be explicitly
497        passed to ld, causing the link step to fail if they are not.
499    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
500        mode, patterns that started with \h* or \R* might be incorrectly matched.
503    Version 8.30 04-February-2012
504    -----------------------------
506    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
507        name is defined in ctype.h.
509    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
510        only in quite long subpatterns.
512    3.  Removed the function pcre_info(), which has been obsolete and deprecated
513        since it was replaced by pcre_fullinfo() in February 2000.
515    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
516        match a (*MARK), and the match failed at the start of the subject, a
517        reference to memory before the start of the subject could occur. This bug
518        was introduced by fix 17 of release 8.21.
520    5.  A reference to an unset group with zero minimum repetition was giving
521        totally wrong answers (in non-JavaScript-compatibility mode). For example,
522        /(another)?(\1?)test/ matched against "hello world test". This bug was
523        introduced in release 8.13.
525    6.  Add support for 16-bit character strings (a large amount of work involving
526        many changes and refactorings).
528    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
529        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
530        from a file.
532    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
533        rounding is not applied in this particular case).
535    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
536        if they appear, or are escaped, in patterns.
538    10. Get rid of a number of -Wunused-but-set-variable warnings.
540    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
541        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
542        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
543        also returns the mark "x". This bug applied to capturing parentheses,
544        non-capturing parentheses, and atomic parentheses. It also applied to some
545        assertions.
547    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
548        information out of configure.ac instead of relying on pcre.h.generic, which
549        is not stored in the repository.
551    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
552        -lreadline.
554    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
556    15. Applied Graycode's patch to put the top-level frame on the stack rather
557        than the heap when not using the stack for recursion. This gives a
558        performance improvement in many cases when recursion is not deep.
560    16. Experimental code added to "pcretest -C" to output the stack frame size.
563    Version 8.21 12-Dec-2011
564    ------------------------
566  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
568    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
569        are added as well.
571    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
572        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
573        calling _pcre_jit_exec. Some extra comments are added.
575    4.  (*MARK) settings inside atomic groups that do not contain any capturing
576        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
577        was introduced by change 18 for 8.20.
579    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
580        ECMA-262 standard.
582    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
583        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
584        This bug was probably introduced by change 9 of 8.13.
586    7.  While fixing 6 above, I noticed that a number of other items were being
587        incorrectly rejected as "not fixed length". This arose partly because newer
588        opcodes had not been added to the fixed-length checking code. I have (a)
589        corrected the bug and added tests for these items, and (b) arranged for an
590        error to occur if an unknown opcode is encountered while checking for fixed
591        length instead of just assuming "not fixed length". The items that were
592        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
593        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
594        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
596    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
597        being incorrectly compiled and would have given unpredicatble results.
599    9.  A possessively repeated subpattern with minimum repeat count greater than
600        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
601        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
602        the first (A) could occur when it should not.
604    10. Add a cast and remove a redundant test from the code.
606    11. JIT should use pcre_malloc/pcre_free for allocation.
608    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
609        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
610        is anything other than /usr, -L is still shown).
612    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
614    14. Perl does not support \N without a following name in a [] class; PCRE now
615        also gives an error.
617    15. If a forward reference was repeated with an upper limit of around 2000,
618        it caused the error "internal error: overran compiling workspace". The
619        maximum number of forward references (including repeats) was limited by the
620        internal workspace, and dependent on the LINK_SIZE. The code has been
621        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
622        the default depends on LINK_SIZE. There is a new upper limit (for safety)
623        of around 200,000 forward references. While doing this, I also speeded up
624        the filling in of repeated forward references.
626    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
627        incorrectly expecting the subject to contain another "a" after the start.
629    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
630        in the match, the SKIP should be ignored. This was not happening; instead
631        the SKIP was being treated as NOMATCH. For patterns such as
632        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
633        tested.
635    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
636        now much more compatible with Perl, in particular in cases where the result
637        is a non-match for a non-anchored pattern. For example, if
638        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
639        "m", where previously it did not return a name. A side effect of this
640        change is that for partial matches, the last encountered mark name is
641        returned, as for non matches. A number of tests that were previously not
642        Perl-compatible have been moved into the Perl-compatible test files. The
643        refactoring has had the pleasing side effect of removing one argument from
644        the match() function, thus reducing its stack requirements.
646    19. If the /S+ option was used in pcretest to study a pattern using JIT,
647        subsequent uses of /S (without +) incorrectly behaved like /S+.
649    21. Retrieve executable code size support for the JIT compiler and fixing
650        some warnings.
652    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
653        not work when the shorter character appeared right at the end of the
654        subject string.
656    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
657        systems.
659    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
660        output it when the /M option is used in pcretest.
662    25. The CheckMan script was not being included in the distribution. Also, added
663        an explicit "perl" to run Perl scripts from the PrepareRelease script
664        because this is reportedly needed in Windows.
666    26. If study data was being save in a file and studying had not found a set of
667        "starts with" bytes for the pattern, the data written to the file (though
668        never used) was taken from uninitialized memory and so caused valgrind to
669        complain.
671    27. Updated RunTest.bat as provided by Sheri Pierce.
673    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
675    29. Computation of memory usage for the table of capturing group names was
676        giving an unnecessarily large value.
679  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
680  ------------------------  ------------------------
# Line 1021  Version 7.9 11-Apr-09 Line 1690  Version 7.9 11-Apr-09
1690  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
1691      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
1692      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1693      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1694        8.33.]
1696  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1697      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 1264  Version 7.7 07-May-08 Line 1934  Version 7.7 07-May-08
1934      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
1935      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
1936      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
1937      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
1938      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
1939      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.740  
changed lines
  Added in v.1342

  ViewVC Help
Powered by ViewVC 1.1.5