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

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

  ViewVC Help
Powered by ViewVC 1.1.5