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 1538 by ph10, Sun Mar 29 11:22:24 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.21  Version 8.37 xx-xxx-2015
5  ------------  ------------------------
7    1.  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
8        for those parentheses to be closed with whatever has been captured so far.
9        However, it was failing to mark any other groups between the hightest
10        capture so far and the currrent group as "unset". Thus, the ovector for
11        those groups contained whatever was previously there. An example is the
12        pattern /(x)|((*ACCEPT))/ when matched against "abcd".
14    2.  If an assertion condition was quantified with a minimum of zero (an odd
15        thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
17    3.  If a pattern in pcretest input had the P (POSIX) modifier followed by an
18        unrecognized modifier, a crash could occur.
20    4.  An attempt to do global matching in pcretest with a zero-length ovector
21        caused a crash.
23    5.  Fixed a memory leak during matching that could occur for a subpattern
24        subroutine call (recursive or otherwise) if the number of captured groups
25        that had to be saved was greater than ten.
27    6.  Catch a bad opcode during auto-possessification after compiling a bad UTF
28        string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
29        UTF with NO_UTF_CHECK is documented as having an undefined outcome.
31    7.  A UTF pattern containing a "not" match of a non-ASCII character and a
32        subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
34    8. When a pattern is compiled, it remembers the highest back reference so that
35       when matching, if the ovector is too small, extra memory can be obtained to
36       use instead. A conditional subpattern whose condition is a check on a
37       capture having happened, such as, for example in the pattern
38       /^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
39       setting the highest backreference number. This mattered only if pcre_exec()
40       was called with an ovector that was too small to hold the capture, and there
41       was no other kind of back reference (a situation which is probably quite
42       rare). The effect of the bug was that the condition was always treated as
43       FALSE when the capture could not be consulted, leading to a incorrect
44       behaviour by pcre2_match(). This bug has been fixed.
46    9. A reference to a duplicated named group (either a back reference or a test
47       for being set in a conditional) that occurred in a part of the pattern where
48       PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
49       to be incorrectly calculated, leading to overwriting.
51    10. A mutually recursive set of back references such as (\2)(\1) caused a
52        segfault at study time (while trying to find the minimum matching length).
53        The infinite loop is now broken (with the minimum length unset, that is,
54        zero).
56    11. If an assertion that was used as a condition was quantified with a minimum
57        of zero, matching went wrong. In particular, if the whole group had
58        unlimited repetition and could match an empty string, a segfault was
59        likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
60        assertions to be quantified, but not if they are being used as conditions,
61        so the above pattern is faulted by Perl. PCRE has now been changed so that
62        it also rejects such patterns.
64    12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
65        failed to allow the zero-repeat case if pcre2_exec() was called with an
66        ovector too small to capture the group.
68    13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
69        Red Hat Product Security:
71        (a) A crash if /K and /F were both set with the option to save the compiled
72        pattern.
74        (b) Another crash if the option to print captured substrings in a callout
75        was combined with setting a null ovector, for example \O\C+ as a subject
76        string.
78    14. A pattern such as "((?2){0,1999}())?", which has a group containing a
79        forward reference repeated a large (but limited) number of times within a
80        repeated outer group that has a zero minimum quantifier, caused incorrect
81        code to be compiled, leading to the error "internal error:
82        previously-checked referenced subpattern not found" when an incorrect
83        memory address was read. This bug was reported as "heap overflow",
84        discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
85        CVE-2015-2325.
87    23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
88        call within a group that also contained a recursive back reference caused
89        incorrect code to be compiled. This bug was reported as "heap overflow",
90        discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
91        number CVE-2015-2326.
93    24. Computing the size of the JIT read-only data in advance has been a source
94        of various issues, and new ones are still appear unfortunately. To fix
95        existing and future issues, size computation is eliminated from the code,
96        and replaced by on-demand memory allocation.
98    25. A pattern such as /(?i)[A-`]/, where characters in the other case are
99        adjacent to the end of the range, and the range contained characters with
100        more than one other case, caused incorrect behaviour when compiled in UTF
101        mode. In that example, the range a-j was left out of the class.
103    26. Fix JIT compilation of conditional blocks, which assertion
104        is converted to (*FAIL). E.g: /(?(?!))/.
106    27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
107        discovered by the LLVM fuzzer.
109    28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
110        when this assertion was used as a condition, for example (?(?!)a|b). In
111        pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
112        error about an unsupported item.
114    29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
115        possessification code could take exponential time to complete. A recursion
116        depth limit of 1000 has been imposed to limit the resources used by this
117        optimization.
119    30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
120        such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
121        because \S ensures they are all in the class. The code for doing this was
122        interacting badly with the code for computing the amount of space needed to
123        compile the pattern, leading to a buffer overflow. This bug was discovered
124        by the LLVM fuzzer.
126    31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
127        other kinds of group caused stack overflow at compile time. This bug was
128        discovered by the LLVM fuzzer.
130    32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
131        between a subroutine call and its quantifier was incorrectly compiled,
132        leading to buffer overflow or other errors. This bug was discovered by the
133        LLVM fuzzer.
136    Version 8.36 26-September-2014
137    ------------------------------
139    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
140        -Wmissing-field-initializers and -Wunused-parameter.
142    2.  The tests for quantifiers being too big (greater than 65535) were being
143        applied after reading the number, and stupidly assuming that integer
144        overflow would give a negative number. The tests are now applied as the
145        numbers are read.
147    3.  Tidy code in pcre_exec.c where two branches that used to be different are
148        now the same.
150    4.  The JIT compiler did not generate match limit checks for certain
151        bracketed expressions with quantifiers. This may lead to exponential
152        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
153        issue should be resolved now.
155    5.  Fixed an issue, which occures when nested alternatives are optimized
156        with table jumps.
158    6.  Inserted two casts and changed some ints to size_t in the light of some
159        reported 64-bit compiler warnings (Bugzilla 1477).
161    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
162        an empty string, which sometimes were behaving incorrectly in the
163        interpreter (though correctly in the JIT matcher). This pcretest input is
164        an example:
166          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
169        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
170        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
171        for an empty string was breaking the inner loop and carrying on at a lower
172        level, when possessive repeated groups should always return to a higher
173        level as they have no backtrack points in them. The empty string test now
174        occurs at the outer level.
176    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
177        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
179    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
180        doesn't).
182    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
183        to hold a pattern to be incorrectly computed (too small) when there were
184        named back references to duplicated names. This could cause "internal
185        error: code overflow" or "double free or corruption" or other memory
186        handling errors.
188    11. When named subpatterns had the same prefixes, back references could be
189        confused. For example, in this pattern:
191          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
193        the reference to 'Name' was incorrectly treated as a reference to a
194        duplicate name.
196    12. A pattern such as /^s?c/mi8 where the optional character has more than
197        one "other case" was incorrectly compiled such that it would only try to
198        match starting at "c".
200    13. When a pattern starting with \s was studied, VT was not included in the
201        list of possible starting characters; this should have been part of the
202        8.34/18 patch.
204    14. If a character class started [\Qx]... where x is any character, the class
205        was incorrectly terminated at the ].
207    15. If a pattern that started with a caseless match for a character with more
208        than one "other case" was studied, PCRE did not set up the starting code
209        unit bit map for the list of possible characters. Now it does. This is an
210        optimization improvement, not a bug fix.
212    16. The Unicode data tables have been updated to Unicode 7.0.0.
214    17. Fixed a number of memory leaks in pcregrep.
216    18. Avoid a compiler warning (from some compilers) for a function call with
217        a cast that removes "const" from an lvalue by using an intermediate
218        variable (to which the compiler does not object).
220    19. Incorrect code was compiled if a group that contained an internal recursive
221        back reference was optional (had quantifier with a minimum of zero). This
222        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
223        caused segmentation faults because of stack overflows at compile time.
225    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
226        group that is quantified with an indefinite repeat, caused a compile-time
227        loop which used up all the system stack and provoked a segmentation fault.
228        This was not the same bug as 19 above.
230    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
231        Patch by Mike Frysinger.
234    Version 8.35 04-April-2014
235    --------------------------
237    1.  A new flag is set, when property checks are present in an XCLASS.
238        When this flag is not set, PCRE can perform certain optimizations
239        such as studying these XCLASS-es.
241    2.  The auto-possessification of character sets were improved: a normal
242        and an extended character set can be compared now. Furthermore
243        the JIT compiler optimizes more character set checks.
245    3.  Got rid of some compiler warnings for potentially uninitialized variables
246        that show up only when compiled with -O2.
248    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
249        of a match later then the end of the match. The pcretest program was not
250        handling the case sensibly - it was outputting from the start to the next
251        binary zero. It now reports this situation in a message, and outputs the
252        text from the end to the start.
254    5.  Fast forward search is improved in JIT. Instead of the first three
255        characters, any three characters with fixed position can be searched.
256        Search order: first, last, middle.
258    6.  Improve character range checks in JIT. Characters are read by an inprecise
259        function now, which returns with an unknown value if the character code is
260        above a certain threshold (e.g: 256). The only limitation is that the value
261        must be bigger than the threshold as well. This function is useful when
262        the characters above the threshold are handled in the same way.
264    7.  The macros whose names start with RAWUCHAR are placeholders for a future
265        mode in which only the bottom 21 bits of 32-bit data items are used. To
266        make this more memorable for those maintaining the code, the names have
267        been changed to start with UCHAR21, and an extensive comment has been added
268        to their definition.
270    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
271        to the export list in Makefile.am (they were accidentally omitted from the
272        8.34 tarball).
274    9.  The informational output from pcretest used the phrase "starting byte set"
275        which is inappropriate for the 16-bit and 32-bit libraries. As the output
276        for "first char" and "need char" really means "non-UTF-char", I've changed
277        "byte" to "char", and slightly reworded the output. The documentation about
278        these values has also been (I hope) clarified.
280    10. Another JIT related optimization: use table jumps for selecting the correct
281        backtracking path, when more than four alternatives are present inside a
282        bracket.
284    11. Empty match is not possible, when the minimum length is greater than zero,
285        and there is no \K in the pattern. JIT should avoid empty match checks in
286        such cases.
288    12. In a caseless character class with UCP support, when a character with more
289        than one alternative case was not the first character of a range, not all
290        the alternative cases were added to the class. For example, s and \x{17f}
291        are both alternative cases for S: the class [RST] was handled correctly,
292        but [R-T] was not.
294    13. The configure.ac file always checked for pthread support when JIT was
295        enabled. This is not used in Windows, so I have put this test inside a
296        check for the presence of windows.h (which was already tested for).
298    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
299        The algorithm provides a way to skip certain starting offsets, and usually
300        faster than linear prefix searches.
302    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
303        as for 'fr_FR' and 'french'. For some reason, however, it then used the
304        Windows-specific input and output files, which have 'french' screwed in.
305        So this could never have worked. One of the problems with locales is that
306        they aren't always the same. I have now updated RunTest so that it checks
307        the output of the locale test (test 3) against three different output
308        files, and it allows the test to pass if any one of them matches. With luck
309        this should make the test pass on some versions of Solaris where it was
310        failing. Because of the uncertainty, the script did not used to stop if
311        test 3 failed; it now does. If further versions of a French locale ever
312        come to light, they can now easily be added.
314    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
315        there was a message during ./configure, but it did not stop. This now
316        provokes an error. The invalid example in README has been corrected.
317        If a value less than the minimum is given, the minimum value has always
318        been used, but now a warning is given.
320    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
321        was a bug in the test system, which is now fixed. Also, the list of various
322        configurations that are tested for each release did not have one with both
323        16/32 bits and --enable-bar-anycrlf. It now does.
325    18. pcretest was missing "-C bsr" for displaying the \R default setting.
327    19. Little endian PowerPC systems are supported now by the JIT compiler.
329    20. The fast forward newline mechanism could enter to an infinite loop on
330        certain invalid UTF-8 input. Although we don't support these cases
331        this issue can be fixed by a performance optimization.
333    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
334        not take account if existing stack usage. There is now a new global
335        variable called pcre_stack_guard that can be set to point to an external
336        function to check stack availability. It is called at the start of
337        processing every parenthesized group.
339    22. A typo in the code meant that in ungreedy mode the max/min qualifier
340        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
341        not match "ab".
343    23. When UTF was disabled, the JIT program reported some incorrect compile
344        errors. These messages are silenced now.
346    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
347        compiler.
349    25. Change all the temporary files used in RunGrepTest to be different to those
350        used by RunTest so that the tests can be run simultaneously, for example by
351        "make -j check".
354    Version 8.34 15-December-2013
355    -----------------------------
357    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
358        executable memory. Patch inspired by Carsten Klein.
360    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
361        this macro is never tested and has no effect, because the work to support
362        coverage involves only compiling and linking options and special targets in
363        the Makefile. The comment in config.h implied that defining the macro would
364        enable coverage support, which is totally false. There was also support for
365        setting this macro in the CMake files (my fault, I just copied it from
366        configure). SUPPORT_GCOV has now been removed.
368    3.  Make a small performance improvement in strlen16() and strlen32() in
369        pcretest.
371    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
372        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
373        these cases). There was also one in pcretest.c.
375    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
377    6.  In UTF mode, the code for checking whether a group could match an empty
378        string (which is used for indefinitely repeated groups to allow for
379        breaking an infinite loop) was broken when the group contained a repeated
380        negated single-character class with a character that occupied more than one
381        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
382        UTF-8 mode). The effect was undefined: the group might or might not be
383        deemed as matching an empty string, or the program might have crashed.
385    7.  The code for checking whether a group could match an empty string was not
386        recognizing that \h, \H, \v, \V, and \R must match a character.
388    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
389        an empty string. If it can, pcretest shows this in its information output.
391    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
392        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
393        matched by pcre_exec() without using JIT:
395        (a) If the rest of the pattern did not match after a maximal run of
396            grapheme clusters, the code for backing up to try with fewer of them
397            did not always back up over a full grapheme when characters that do not
398            have the modifier quality were involved, e.g. Hangul syllables.
400        (b) If the match point in a subject started with modifier character, and
401            there was no match, the code could incorrectly back up beyond the match
402            point, and potentially beyond the first character in the subject,
403            leading to a segfault or an incorrect match result.
405    10. A conditional group with an assertion condition could lead to PCRE
406        recording an incorrect first data item for a match if no other first data
407        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
408        first data item, and therefore matched "ca" after "c" instead of at the
409        start.
411    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
412        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
414    12. The source of pcregrep now includes z/OS-specific code so that it can be
415        compiled for z/OS as part of the special z/OS distribution.
417    13. Added the -T and -TM options to pcretest.
419    14. The code in pcre_compile.c for creating the table of named capturing groups
420        has been refactored. Instead of creating the table dynamically during the
421        actual compiling pass, the information is remembered during the pre-compile
422        pass (on the stack unless there are more than 20 named groups, in which
423        case malloc() is used) and the whole table is created before the actual
424        compile happens. This has simplified the code (it is now nearly 150 lines
425        shorter) and prepared the way for better handling of references to groups
426        with duplicate names.
428    15. A back reference to a named subpattern when there is more than one of the
429        same name now checks them in the order in which they appear in the pattern.
430        The first one that is set is used for the reference. Previously only the
431        first one was inspected. This change makes PCRE more compatible with Perl.
433    16. Unicode character properties were updated from Unicode 6.3.0.
435    17. The compile-time code for auto-possessification has been refactored, based
436        on a patch by Zoltan Herczeg. It now happens after instead of during
437        compilation. The code is cleaner, and more cases are handled. The option
438        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
439        options in pcretest are provided to set it. It can also be set by
440        (*NO_AUTO_POSSESS) at the start of a pattern.
442    18. The character VT has been added to the default ("C" locale) set of
443        characters that match \s and are generally treated as white space,
444        following this same change in Perl 5.18. There is now no difference between
445        "Perl space" and "POSIX space". Whether VT is treated as white space in
446        other locales depends on the locale.
448    19. The code for checking named groups as conditions, either for being set or
449        for being recursed, has been refactored (this is related to 14 and 15
450        above). Processing unduplicated named groups should now be as fast at
451        numerical groups, and processing duplicated groups should be faster than
452        before.
454    20. Two patches to the CMake build system, by Alexander Barkov:
456          (1) Replace the "source" command by "." in CMakeLists.txt because
457              "source" is a bash-ism.
459          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
460              without these the CMake build does not work on Solaris.
462    21. Perl has changed its handling of \8 and \9. If there is no previously
463        encountered capturing group of those numbers, they are treated as the
464        literal characters 8 and 9 instead of a binary zero followed by the
465        literals. PCRE now does the same.
467    22. Following Perl, added \o{} to specify codepoints in octal, making it
468        possible to specify values greater than 0777 and also making them
469        unambiguous.
471    23. Perl now gives an error for missing closing braces after \x{... instead of
472        treating the string as literal. PCRE now does the same.
474    24. RunTest used to grumble if an inappropriate test was selected explicitly,
475        but just skip it when running all tests. This make it awkward to run ranges
476        of tests when one of them was inappropriate. Now it just skips any
477        inappropriate tests, as it always did when running all tests.
479    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
480        character types such as \d or \w, too many callouts were inserted, and the
481        data that they returned was rubbish.
483    26. In UCP mode, \s was not matching two of the characters that Perl matches,
484        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
485        were matched by \h. The code has now been refactored so that the lists of
486        the horizontal and vertical whitespace characters used for \h and \v (which
487        are defined only in one place) are now also used for \s.
489    27. Add JIT support for the 64 bit TileGX architecture.
490        Patch by Jiong Wang (Tilera Corporation).
492    28. Possessive quantifiers for classes (both explicit and automatically
493        generated) now use special opcodes instead of wrapping in ONCE brackets.
495    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
496        (because it's meaningless), this was not happening when PCRE_CASELESS was
497        set. Not wrong, but inefficient.
499    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
500        properties for \w, \d, etc) is present in a test regex. Otherwise if the
501        test contains no characters greater than 255, Perl doesn't realise it
502        should be using Unicode semantics.
504    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
505        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
506        does in Unicode mode.
508    32. Added the "forbid" facility to pcretest so that putting tests into the
509        wrong test files can sometimes be quickly detected.
511    33. There is now a limit (default 250) on the depth of nesting of parentheses.
512        This limit is imposed to control the amount of system stack used at compile
513        time. It can be changed at build time by --with-parens-nest-limit=xxx or
514        the equivalent in CMake.
516    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
517        errors. Perl warns for these when in warning mode, but PCRE has no facility
518        for giving warnings.
520    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
521        However, this was not working for (?!) because it is optimized to (*FAIL),
522        for which PCRE does not allow quantifiers. The optimization is now disabled
523        when a quantifier follows (?!). I can't see any use for this, but it makes
524        things uniform.
526    36. Perl no longer allows group names to start with digits, so I have made this
527        change also in PCRE. It simplifies the code a bit.
529    37. In extended mode, Perl ignores spaces before a + that indicates a
530        possessive quantifier. PCRE allowed a space before the quantifier, but not
531        before the possessive +. It now does.
533    38. The use of \K (reset reported match start) within a repeated possessive
534        group such as (a\Kb)*+ was not working.
536    40. Document that the same character tables must be used at compile time and
537        run time, and that the facility to pass tables to pcre_exec() and
538        pcre_dfa_exec() is for use only with saved/restored patterns.
540    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
541        features for Builds with MSVC:
543        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
544           builds). The .rc files can be used to set FileDescription and many other
545           attributes.
547        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
548           This allows higher-level build scripts which want .pdb files to avoid
549           hard-coding the exact files needed."
551    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
552        mean "start of word" and "end of word", respectively, as a transition aid.
554    43. A minimizing repeat of a class containing codepoints greater than 255 in
555        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
556        compiled to use the heap for recursion.
558    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
559        is configured.
562    Version 8.33 28-May-2013
563    ------------------------
565    1.  Added 'U' to some constants that are compared to unsigned integers, to
566        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
567        variables that are added to signed variables, to ensure the result is
568        signed and can be negated.
570    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
571        CMake config files.
573    3.  Revise the creation of config.h.generic so that all boolean macros are
574        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
575        overriding via -D on the command line possible.
577    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
578        to unsigned int is reported to make a quite noticeable speed difference in
579        a specific Windows environment. Testing on Linux did also appear to show
580        some benefit (and it is clearly not harmful). Also fixed the definition of
581        Xop which should be unsigned.
583    5.  Related to (4), changing the definition of the intermediate variable cc
584        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
585        improvements.
587    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
588        unnecessary spaces.
590    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
591        and later.
593    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
595    9.  Optimizing fast_forward_start_bits in JIT.
597    10. Adding support for callouts in JIT, and fixing some issues revealed
598        during this work. Namely:
600        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
602        (b) Minimum length was not checked before the matching is started.
604    11. The value of capture_last that is passed to callouts was incorrect in some
605        cases when there was a capture on one path that was subsequently abandoned
606        after a backtrack. Also, the capture_last value is now reset after a
607        recursion, since all captures are also reset in this case.
609    12. The interpreter no longer returns the "too many substrings" error in the
610        case when an overflowing capture is in a branch that is subsequently
611        abandoned after a backtrack.
613    13. In the pathological case when an offset vector of size 2 is used, pcretest
614        now prints out the matched string after a yield of 0 or 1.
616    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
617        Only supported by the JIT compiler at the moment.
619    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
621    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
622        offset of the starting point of the matching process, provided the offsets
623        vector is large enough.
625    17. The \A escape now records a lookbehind value of 1, though its execution
626        does not actually inspect the previous character. This is to ensure that,
627        in partial multi-segment matching, at least one character from the old
628        segment is retained when a new segment is processed. Otherwise, if there
629        are no lookbehinds in the pattern, \A might match incorrectly at the start
630        of a new segment.
632    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
634    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
635        gives some modest performance improvement in 8-bit mode.
637    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
638        be expressed in certain programming languages using Universal Character
639        Names.
641    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
642        which points out that "non characters" are not "characters that may not
643        appear in Unicode strings" but rather "characters that are reserved for
644        internal use and have only local meaning".
646    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
647        there was a conditional group that depended on an assertion, if the
648        assertion was false, the callout that immediately followed the alternation
649        in the condition was skipped when pcre_exec() was used for matching.
651    23. Allow an explicit callout to be inserted before an assertion that is the
652        condition for a conditional group, for compatibility with automatic
653        callouts, which always insert a callout at this point.
655    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
656        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
658    25. (*PRUNE) is now supported by the JIT compiler.
660    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
662    27. Fix the case where there are two or more SKIPs with arguments that may be
663        ignored.
665    28. (*SKIP) is now supported by the JIT compiler.
667    29. (*THEN) is now supported by the JIT compiler.
669    30. Update RunTest with additional test selector options.
671    31. The way PCRE handles backtracking verbs has been changed in two ways.
673        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
674        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
675        backtracking. In some cases this makes it more Perl-compatible, but Perl's
676        rather obscure rules do not always do the same thing.
678        (2) Previously, backtracking verbs were confined within assertions. This is
679        no longer the case for positive assertions, except for (*ACCEPT). Again,
680        this sometimes improves Perl compatibility, and sometimes does not.
682    32. A number of tests that were in test 2 because Perl did things differently
683        have been moved to test 1, because either Perl or PCRE has changed, and
684        these tests are now compatible.
686    32. Backtracking control verbs are now handled in the same way in JIT and
687        interpreter.
689    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
690        contained a forward subroutine reference caused a compile error.
692    34. Auto-detect and optimize limited repetitions in JIT.
694    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
695        blocking (*UTF) etc.
697    36. In the interpreter, maximizing pattern repetitions for characters and
698        character types now use tail recursion, which reduces stack usage.
700    37. The value of the max lookbehind was not correctly preserved if a compiled
701        and saved regex was reloaded on a host of different endianness.
703    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
704        of the compiled pattern block, expand the flags field from 16 to 32 bits
705        because it was almost full.
707    39. Try madvise first before posix_madvise.
709    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
710        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
711        original change locked out all matches of empty strings. This has been
712        changed so that one match of an empty string per line is recognized.
713        Subsequent searches on the same line (for colouring or for --only-matching,
714        for example) do not recognize empty strings.
716    41. Applied a user patch to fix a number of spelling mistakes in comments.
718    42. Data lines longer than 65536 caused pcretest to crash.
720    43. Clarified the data type for length and startoffset arguments for pcre_exec
721        and pcre_dfa_exec in the function-specific man pages, where they were
722        explicitly stated to be in bytes, never having been updated. I also added
723        some clarification to the pcreapi man page.
725    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
726        a segmentation fault.
729    Version 8.32 30-November-2012
730    -----------------------------
732    1.  Improved JIT compiler optimizations for first character search and single
733        character iterators.
735    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
736        Patch by Daniel Richard G.
738    3.  Single character iterator optimizations in the JIT compiler.
740    4.  Improved JIT compiler optimizations for character ranges.
742    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
743        Reported by Giuseppe D'Angelo.
745    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
746        of a line, was being set incorrectly in cases where .* appeared inside
747        atomic brackets at the start of a pattern, or where there was a subsequent
748        *PRUNE or *SKIP.
750    7.  Improved instruction cache flush for POWER/PowerPC.
751        Patch by Daniel Richard G.
753    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
754        grep:
756        (a) There is now no limit to the number of patterns to be matched.
758        (b) An error is given if a pattern is too long.
760        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
761            are now supported.
763        (d) --exclude-from and --include-from (multiple use) have been added.
765        (e) Exclusions and inclusions now apply to all files and directories, not
766            just to those obtained from scanning a directory recursively.
768        (f) Multiple uses of -f and --file-list are now supported.
770        (g) In a Windows environment, the default for -d has been changed from
771            "read" (the GNU grep default) to "skip", because otherwise the presence
772            of a directory in the file list provokes an error.
774        (h) The documentation has been revised and clarified in places.
776    9.  Improve the matching speed of capturing brackets.
778    10. Changed the meaning of \X so that it now matches a Unicode extended
779        grapheme cluster.
781    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
782        out POSIX threads when JIT support is configured.
784    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
786    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
787        structure could go wrong in environments where size_t is not the same size
788        as int.
790    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
791        set.
793    15. The EBCDIC support had decayed; later updates to the code had included
794        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
795        general tidy up of EBCDIC-related issues, and the documentation was also
796        not quite right. There is now a test that can be run on ASCII systems to
797        check some of the EBCDIC-related things (but is it not a full test).
799    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
800        in a small tidy to the code.
802    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
804    18. If the --only-matching (-o) option in pcregrep is specified multiple
805        times, each one causes appropriate output. For example, -o1 -o2 outputs the
806        substrings matched by the 1st and 2nd capturing parentheses. A separating
807        string can be specified by --om-separator (default empty).
809    19. Improving the first n character searches.
811    20. Turn case lists for horizontal and vertical white space into macros so that
812        they are defined only once.
814    21. This set of changes together give more compatible Unicode case-folding
815        behaviour for characters that have more than one other case when UCP
816        support is available.
818        (a) The Unicode property table now has offsets into a new table of sets of
819            three or more characters that are case-equivalent. The MultiStage2.py
820            script that generates these tables (the pcre_ucd.c file) now scans
821            CaseFolding.txt instead of UnicodeData.txt for character case
822            information.
824        (b) The code for adding characters or ranges of characters to a character
825            class has been abstracted into a generalized function that also handles
826            case-independence. In UTF-mode with UCP support, this uses the new data
827            to handle characters with more than one other case.
829        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
830            whose other case is greater than 256 are now correctly matched
831            caselessly. Previously, the high codepoint matched the low one, but not
832            vice versa.
834        (d) The processing of \h, \H, \v, and \ in character classes now makes use
835            of the new class addition function, using character lists defined as
836            macros alongside the case definitions of 20 above.
838        (e) Caseless back references now work with characters that have more than
839            one other case.
841        (f) General caseless matching of characters with more than one other case
842            is supported.
844    22. Unicode character properties were updated from Unicode 6.2.0
846    23. Improved CMake support under Windows. Patch by Daniel Richard G.
848    24. Add support for 32-bit character strings, and UTF-32
850    25. Major JIT compiler update (code refactoring and bugfixing).
851        Experimental Sparc 32 support is added.
853    26. Applied a modified version of Daniel Richard G's patch to create
854        pcre.h.generic and config.h.generic by "make" instead of in the
855        PrepareRelease script.
857    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
858        pcre_compile.c when checking for a zero character.
860    28. Introducing a native interface for JIT. Through this interface, the compiled
861        machine code can be directly executed. The purpose of this interface is to
862        provide fast pattern matching, so several sanity checks are not performed.
863        However, feature tests are still performed. The new interface provides
864        1.4x speedup compared to the old one.
866    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
867        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
868        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
870    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
871        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
872        the "old" RFC 2279). Instead, it ended up passing a negative length to
873        pcre_exec().
875    31. Add support for GCC's visibility feature to hide internal functions.
877    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
878        "unknown -C option" after outputting 0 or 1.
880    33. There is now support for generating a code coverage report for the test
881        suite in environments where gcc is the compiler and lcov is installed. This
882        is mainly for the benefit of the developers.
884    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
885        unaddressable using valgrind annotations, allowing valgrind to detect
886        invalid memory accesses. This is mainly for the benefit of the developers.
888    25. (*UTF) can now be used to start a pattern in any of the three libraries.
890    26. Give configure error if --enable-cpp but no C++ compiler found.
893    Version 8.31 06-July-2012
894    -------------------------
896    1.  Fixing a wrong JIT test case and some compiler warnings.
898    2.  Removed a bashism from the RunTest script.
900    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
901        to unsigned type, result still unsigned" that was given by an MS compiler
902        on encountering the code "-sizeof(xxx)".
904    4.  Partial matching support is added to the JIT compiler.
906    5.  Fixed several bugs concerned with partial matching of items that consist
907        of more than one character:
909        (a) /^(..)\1/ did not partially match "aba" because checking references was
910            done on an "all or nothing" basis. This also applied to repeated
911            references.
913        (b) \R did not give a hard partial match if \r was found at the end of the
914            subject.
916        (c) \X did not give a hard partial match after matching one or more
917            characters at the end of the subject.
919        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
920            a partial match for the string "\r".
922        (e) When newline was set to CRLF, the metacharacter "." did not recognize
923            a partial match for a CR character at the end of the subject string.
925    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
926        running pcretest, the text "(JIT)" added to the output whenever JIT is
927        actually used to run the match.
929    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
930        or /S+[+] with a digit between 1 and 7.
932    8.  OP_NOT now supports any UTF character not just single-byte ones.
934    9.  (*MARK) control verb is now supported by the JIT compiler.
936    10. The command "./RunTest list" lists the available tests without actually
937        running any of them. (Because I keep forgetting what they all are.)
941    12. Applied a (slightly modified) user-supplied patch that improves performance
942        when the heap is used for recursion (compiled with --disable-stack-for-
943        recursion). Instead of malloc and free for each heap frame each time a
944        logical recursion happens, frames are retained on a chain and re-used where
945        possible. This sometimes gives as much as 30% improvement.
947    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
948        call.
950    14. As documented, (*COMMIT) is now confined to within a positive assertion.
952    15. It is now possible to link pcretest with libedit as an alternative to
953        libreadline.
955    16. (*COMMIT) control verb is now supported by the JIT compiler.
957    17. The Unicode data tables have been updated to Unicode 6.1.0.
959    18. Added --file-list option to pcregrep.
961    19. Added binary file support to pcregrep, including the -a, --binary-files,
962        -I, and --text options.
964    20. The madvise function is renamed for posix_madvise for QNX compatibility
965        reasons. Fixed by Giuseppe D'Angelo.
967    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
969    22. Changed the option for creating symbolic links for 16-bit man pages from
970        -s to -sf so that re-installing does not cause issues.
972    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
974    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
975        matches in certain environments (the workspace was not being correctly
976        retained). Also added to pcre_dfa_exec() a simple plausibility check on
977        some of the workspace data at the beginning of a restart.
979    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
980        was not doing so when it should - probably a typo introduced by SVN 528
981        (change 8.10/14).
983    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
984        \w+ when the character tables indicated that \x{c4} was a word character.
985        There were several related cases, all because the tests for doing a table
986        lookup were testing for characters less than 127 instead of 255.
988    27. If a pattern contains capturing parentheses that are not used in a match,
989        their slots in the ovector are set to -1. For those that are higher than
990        any matched groups, this happens at the end of processing. In the case when
991        there were back references that the ovector was too small to contain
992        (causing temporary malloc'd memory to be used during matching), and the
993        highest capturing number was not used, memory off the end of the ovector
994        was incorrectly being set to -1. (It was using the size of the temporary
995        memory instead of the true size.)
997    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
998        ovector size, it uses memory at the end of the block that it has got.
1000    29. Check for an overlong MARK name and give an error at compile time. The
1001        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
1003    30. JIT compiler update.
1005    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
1006        Rill for the patch.
1008    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
1010    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
1012    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
1013        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
1014        was enabled.
1016    35. Improve JIT code generation for greedy plus quantifier.
1018    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
1019        1 to "aa" instead of to an empty string. The bug affected repeated groups
1020        that could potentially match an empty string.
1022    37. Optimizing single character iterators in JIT.
1024    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
1025        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
1026        codepoints that are too big for the mode are faulted, and in a UTF mode,
1027        disallowed codepoints are also faulted.
1029    39. If PCRE was compiled with UTF support, in three places in the DFA
1030        matcher there was code that should only have been obeyed in UTF mode, but
1031        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
1032        processing when bytes with values greater than 127 were present. In 16-bit
1033        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
1034        both cases the values are those that cannot be the first data item in a UTF
1035        character. The three items that might have provoked this were recursions,
1036        possessively repeated groups, and atomic groups.
1038    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
1039        and pcregrep, because some OS require shared objects to be explicitly
1040        passed to ld, causing the link step to fail if they are not.
1042    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
1043        mode, patterns that started with \h* or \R* might be incorrectly matched.
1046    Version 8.30 04-February-2012
1047    -----------------------------
1049    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
1050        name is defined in ctype.h.
1052    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
1053        only in quite long subpatterns.
1055    3.  Removed the function pcre_info(), which has been obsolete and deprecated
1056        since it was replaced by pcre_fullinfo() in February 2000.
1058    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
1059        match a (*MARK), and the match failed at the start of the subject, a
1060        reference to memory before the start of the subject could occur. This bug
1061        was introduced by fix 17 of release 8.21.
1063    5.  A reference to an unset group with zero minimum repetition was giving
1064        totally wrong answers (in non-JavaScript-compatibility mode). For example,
1065        /(another)?(\1?)test/ matched against "hello world test". This bug was
1066        introduced in release 8.13.
1068    6.  Add support for 16-bit character strings (a large amount of work involving
1069        many changes and refactorings).
1071    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
1072        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
1073        from a file.
1075    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
1076        rounding is not applied in this particular case).
1078    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
1079        if they appear, or are escaped, in patterns.
1081    10. Get rid of a number of -Wunused-but-set-variable warnings.
1083    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
1084        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
1085        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
1086        also returns the mark "x". This bug applied to capturing parentheses,
1087        non-capturing parentheses, and atomic parentheses. It also applied to some
1088        assertions.
1090    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
1091        information out of configure.ac instead of relying on pcre.h.generic, which
1092        is not stored in the repository.
1094    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
1095        -lreadline.
1097    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
1099    15. Applied Graycode's patch to put the top-level frame on the stack rather
1100        than the heap when not using the stack for recursion. This gives a
1101        performance improvement in many cases when recursion is not deep.
1103    16. Experimental code added to "pcretest -C" to output the stack frame size.
1106    Version 8.21 12-Dec-2011
1107    ------------------------
1109  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
# Line 13  Version 8.21 Line 1115  Version 8.21
1115      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
1116      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
1118  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
1119      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
1120      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
# Line 22  Version 8.21 Line 1124  Version 8.21
1125  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
1126      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
1127      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
1129  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
1130      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
1131      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)
1132      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
1133      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
1134      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
1135      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
1136      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
1137      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
1139  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
1140      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
1142  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
1143      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
1144      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
1145      the first (A) could occur when it should not.      the first (A) could occur when it should not.
1147  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
1149  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
1151  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
1152      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
1153      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
1155    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
1157    14. Perl does not support \N without a following name in a [] class; PCRE now
1158        also gives an error.
1160    15. If a forward reference was repeated with an upper limit of around 2000,
1161        it caused the error "internal error: overran compiling workspace". The
1162        maximum number of forward references (including repeats) was limited by the
1163        internal workspace, and dependent on the LINK_SIZE. The code has been
1164        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
1165        the default depends on LINK_SIZE. There is a new upper limit (for safety)
1166        of around 200,000 forward references. While doing this, I also speeded up
1167        the filling in of repeated forward references.
1169    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
1170        incorrectly expecting the subject to contain another "a" after the start.
1172    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
1173        in the match, the SKIP should be ignored. This was not happening; instead
1174        the SKIP was being treated as NOMATCH. For patterns such as
1175        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
1176        tested.
1178    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
1179        now much more compatible with Perl, in particular in cases where the result
1180        is a non-match for a non-anchored pattern. For example, if
1181        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
1182        "m", where previously it did not return a name. A side effect of this
1183        change is that for partial matches, the last encountered mark name is
1184        returned, as for non matches. A number of tests that were previously not
1185        Perl-compatible have been moved into the Perl-compatible test files. The
1186        refactoring has had the pleasing side effect of removing one argument from
1187        the match() function, thus reducing its stack requirements.
1189    19. If the /S+ option was used in pcretest to study a pattern using JIT,
1190        subsequent uses of /S (without +) incorrectly behaved like /S+.
1192    21. Retrieve executable code size support for the JIT compiler and fixing
1193        some warnings.
1195    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
1196        not work when the shorter character appeared right at the end of the
1197        subject string.
1199    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
1200        systems.
1202    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
1203        output it when the /M option is used in pcretest.
1205    25. The CheckMan script was not being included in the distribution. Also, added
1206        an explicit "perl" to run Perl scripts from the PrepareRelease script
1207        because this is reportedly needed in Windows.
1209    26. If study data was being save in a file and studying had not found a set of
1210        "starts with" bytes for the pattern, the data written to the file (though
1211        never used) was taken from uninitialized memory and so caused valgrind to
1212        complain.
1214    27. Updated RunTest.bat as provided by Sheri Pierce.
1216    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
1218    29. Computation of memory usage for the table of capturing group names was
1219        giving an unnecessarily large value.
1222  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
# Line 1065  Version 7.9 11-Apr-09 Line 2233  Version 7.9 11-Apr-09
2233  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
2234      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
2235      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2236      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2237        8.33.]
2239  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
2240      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 1308  Version 7.7 07-May-08 Line 2477  Version 7.7 07-May-08
2477      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2478      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2479      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2480      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2481      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2482      was subsequently set up correctly.)      was subsequently set up correctly.)

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

  ViewVC Help
Powered by ViewVC 1.1.5