ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 760 by ph10, Tue Nov 22 11:23:43 2011 UTC revision 1523 by ph10, Sun Feb 8 18:00:45 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.
65    Version 8.36 26-September-2014
66    ------------------------------
68    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
69        -Wmissing-field-initializers and -Wunused-parameter.
71    2.  The tests for quantifiers being too big (greater than 65535) were being
72        applied after reading the number, and stupidly assuming that integer
73        overflow would give a negative number. The tests are now applied as the
74        numbers are read.
76    3.  Tidy code in pcre_exec.c where two branches that used to be different are
77        now the same.
79    4.  The JIT compiler did not generate match limit checks for certain
80        bracketed expressions with quantifiers. This may lead to exponential
81        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
82        issue should be resolved now.
84    5.  Fixed an issue, which occures when nested alternatives are optimized
85        with table jumps.
87    6.  Inserted two casts and changed some ints to size_t in the light of some
88        reported 64-bit compiler warnings (Bugzilla 1477).
90    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
91        an empty string, which sometimes were behaving incorrectly in the
92        interpreter (though correctly in the JIT matcher). This pcretest input is
93        an example:
95          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
98        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
99        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
100        for an empty string was breaking the inner loop and carrying on at a lower
101        level, when possessive repeated groups should always return to a higher
102        level as they have no backtrack points in them. The empty string test now
103        occurs at the outer level.
105    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
106        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
108    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
109        doesn't).
111    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
112        to hold a pattern to be incorrectly computed (too small) when there were
113        named back references to duplicated names. This could cause "internal
114        error: code overflow" or "double free or corruption" or other memory
115        handling errors.
117    11. When named subpatterns had the same prefixes, back references could be
118        confused. For example, in this pattern:
120          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
122        the reference to 'Name' was incorrectly treated as a reference to a
123        duplicate name.
125    12. A pattern such as /^s?c/mi8 where the optional character has more than
126        one "other case" was incorrectly compiled such that it would only try to
127        match starting at "c".
129    13. When a pattern starting with \s was studied, VT was not included in the
130        list of possible starting characters; this should have been part of the
131        8.34/18 patch.
133    14. If a character class started [\Qx]... where x is any character, the class
134        was incorrectly terminated at the ].
136    15. If a pattern that started with a caseless match for a character with more
137        than one "other case" was studied, PCRE did not set up the starting code
138        unit bit map for the list of possible characters. Now it does. This is an
139        optimization improvement, not a bug fix.
141    16. The Unicode data tables have been updated to Unicode 7.0.0.
143    17. Fixed a number of memory leaks in pcregrep.
145    18. Avoid a compiler warning (from some compilers) for a function call with
146        a cast that removes "const" from an lvalue by using an intermediate
147        variable (to which the compiler does not object).
149    19. Incorrect code was compiled if a group that contained an internal recursive
150        back reference was optional (had quantifier with a minimum of zero). This
151        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
152        caused segmentation faults because of stack overflows at compile time.
154    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
155        group that is quantified with an indefinite repeat, caused a compile-time
156        loop which used up all the system stack and provoked a segmentation fault.
157        This was not the same bug as 19 above.
159    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
160        Patch by Mike Frysinger.
163    Version 8.35 04-April-2014
164    --------------------------
166    1.  A new flag is set, when property checks are present in an XCLASS.
167        When this flag is not set, PCRE can perform certain optimizations
168        such as studying these XCLASS-es.
170    2.  The auto-possessification of character sets were improved: a normal
171        and an extended character set can be compared now. Furthermore
172        the JIT compiler optimizes more character set checks.
174    3.  Got rid of some compiler warnings for potentially uninitialized variables
175        that show up only when compiled with -O2.
177    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
178        of a match later then the end of the match. The pcretest program was not
179        handling the case sensibly - it was outputting from the start to the next
180        binary zero. It now reports this situation in a message, and outputs the
181        text from the end to the start.
183    5.  Fast forward search is improved in JIT. Instead of the first three
184        characters, any three characters with fixed position can be searched.
185        Search order: first, last, middle.
187    6.  Improve character range checks in JIT. Characters are read by an inprecise
188        function now, which returns with an unknown value if the character code is
189        above a certain threshold (e.g: 256). The only limitation is that the value
190        must be bigger than the threshold as well. This function is useful when
191        the characters above the threshold are handled in the same way.
193    7.  The macros whose names start with RAWUCHAR are placeholders for a future
194        mode in which only the bottom 21 bits of 32-bit data items are used. To
195        make this more memorable for those maintaining the code, the names have
196        been changed to start with UCHAR21, and an extensive comment has been added
197        to their definition.
199    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
200        to the export list in Makefile.am (they were accidentally omitted from the
201        8.34 tarball).
203    9.  The informational output from pcretest used the phrase "starting byte set"
204        which is inappropriate for the 16-bit and 32-bit libraries. As the output
205        for "first char" and "need char" really means "non-UTF-char", I've changed
206        "byte" to "char", and slightly reworded the output. The documentation about
207        these values has also been (I hope) clarified.
209    10. Another JIT related optimization: use table jumps for selecting the correct
210        backtracking path, when more than four alternatives are present inside a
211        bracket.
213    11. Empty match is not possible, when the minimum length is greater than zero,
214        and there is no \K in the pattern. JIT should avoid empty match checks in
215        such cases.
217    12. In a caseless character class with UCP support, when a character with more
218        than one alternative case was not the first character of a range, not all
219        the alternative cases were added to the class. For example, s and \x{17f}
220        are both alternative cases for S: the class [RST] was handled correctly,
221        but [R-T] was not.
223    13. The configure.ac file always checked for pthread support when JIT was
224        enabled. This is not used in Windows, so I have put this test inside a
225        check for the presence of windows.h (which was already tested for).
227    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
228        The algorithm provides a way to skip certain starting offsets, and usually
229        faster than linear prefix searches.
231    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
232        as for 'fr_FR' and 'french'. For some reason, however, it then used the
233        Windows-specific input and output files, which have 'french' screwed in.
234        So this could never have worked. One of the problems with locales is that
235        they aren't always the same. I have now updated RunTest so that it checks
236        the output of the locale test (test 3) against three different output
237        files, and it allows the test to pass if any one of them matches. With luck
238        this should make the test pass on some versions of Solaris where it was
239        failing. Because of the uncertainty, the script did not used to stop if
240        test 3 failed; it now does. If further versions of a French locale ever
241        come to light, they can now easily be added.
243    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
244        there was a message during ./configure, but it did not stop. This now
245        provokes an error. The invalid example in README has been corrected.
246        If a value less than the minimum is given, the minimum value has always
247        been used, but now a warning is given.
249    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
250        was a bug in the test system, which is now fixed. Also, the list of various
251        configurations that are tested for each release did not have one with both
252        16/32 bits and --enable-bar-anycrlf. It now does.
254    18. pcretest was missing "-C bsr" for displaying the \R default setting.
256    19. Little endian PowerPC systems are supported now by the JIT compiler.
258    20. The fast forward newline mechanism could enter to an infinite loop on
259        certain invalid UTF-8 input. Although we don't support these cases
260        this issue can be fixed by a performance optimization.
262    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
263        not take account if existing stack usage. There is now a new global
264        variable called pcre_stack_guard that can be set to point to an external
265        function to check stack availability. It is called at the start of
266        processing every parenthesized group.
268    22. A typo in the code meant that in ungreedy mode the max/min qualifier
269        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
270        not match "ab".
272    23. When UTF was disabled, the JIT program reported some incorrect compile
273        errors. These messages are silenced now.
275    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
276        compiler.
278    25. Change all the temporary files used in RunGrepTest to be different to those
279        used by RunTest so that the tests can be run simultaneously, for example by
280        "make -j check".
283    Version 8.34 15-December-2013
284    -----------------------------
286    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
287        executable memory. Patch inspired by Carsten Klein.
289    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
290        this macro is never tested and has no effect, because the work to support
291        coverage involves only compiling and linking options and special targets in
292        the Makefile. The comment in config.h implied that defining the macro would
293        enable coverage support, which is totally false. There was also support for
294        setting this macro in the CMake files (my fault, I just copied it from
295        configure). SUPPORT_GCOV has now been removed.
297    3.  Make a small performance improvement in strlen16() and strlen32() in
298        pcretest.
300    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
301        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
302        these cases). There was also one in pcretest.c.
304    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
306    6.  In UTF mode, the code for checking whether a group could match an empty
307        string (which is used for indefinitely repeated groups to allow for
308        breaking an infinite loop) was broken when the group contained a repeated
309        negated single-character class with a character that occupied more than one
310        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
311        UTF-8 mode). The effect was undefined: the group might or might not be
312        deemed as matching an empty string, or the program might have crashed.
314    7.  The code for checking whether a group could match an empty string was not
315        recognizing that \h, \H, \v, \V, and \R must match a character.
317    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
318        an empty string. If it can, pcretest shows this in its information output.
320    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
321        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
322        matched by pcre_exec() without using JIT:
324        (a) If the rest of the pattern did not match after a maximal run of
325            grapheme clusters, the code for backing up to try with fewer of them
326            did not always back up over a full grapheme when characters that do not
327            have the modifier quality were involved, e.g. Hangul syllables.
329        (b) If the match point in a subject started with modifier character, and
330            there was no match, the code could incorrectly back up beyond the match
331            point, and potentially beyond the first character in the subject,
332            leading to a segfault or an incorrect match result.
334    10. A conditional group with an assertion condition could lead to PCRE
335        recording an incorrect first data item for a match if no other first data
336        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
337        first data item, and therefore matched "ca" after "c" instead of at the
338        start.
340    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
341        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
343    12. The source of pcregrep now includes z/OS-specific code so that it can be
344        compiled for z/OS as part of the special z/OS distribution.
346    13. Added the -T and -TM options to pcretest.
348    14. The code in pcre_compile.c for creating the table of named capturing groups
349        has been refactored. Instead of creating the table dynamically during the
350        actual compiling pass, the information is remembered during the pre-compile
351        pass (on the stack unless there are more than 20 named groups, in which
352        case malloc() is used) and the whole table is created before the actual
353        compile happens. This has simplified the code (it is now nearly 150 lines
354        shorter) and prepared the way for better handling of references to groups
355        with duplicate names.
357    15. A back reference to a named subpattern when there is more than one of the
358        same name now checks them in the order in which they appear in the pattern.
359        The first one that is set is used for the reference. Previously only the
360        first one was inspected. This change makes PCRE more compatible with Perl.
362    16. Unicode character properties were updated from Unicode 6.3.0.
364    17. The compile-time code for auto-possessification has been refactored, based
365        on a patch by Zoltan Herczeg. It now happens after instead of during
366        compilation. The code is cleaner, and more cases are handled. The option
367        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
368        options in pcretest are provided to set it. It can also be set by
369        (*NO_AUTO_POSSESS) at the start of a pattern.
371    18. The character VT has been added to the default ("C" locale) set of
372        characters that match \s and are generally treated as white space,
373        following this same change in Perl 5.18. There is now no difference between
374        "Perl space" and "POSIX space". Whether VT is treated as white space in
375        other locales depends on the locale.
377    19. The code for checking named groups as conditions, either for being set or
378        for being recursed, has been refactored (this is related to 14 and 15
379        above). Processing unduplicated named groups should now be as fast at
380        numerical groups, and processing duplicated groups should be faster than
381        before.
383    20. Two patches to the CMake build system, by Alexander Barkov:
385          (1) Replace the "source" command by "." in CMakeLists.txt because
386              "source" is a bash-ism.
388          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
389              without these the CMake build does not work on Solaris.
391    21. Perl has changed its handling of \8 and \9. If there is no previously
392        encountered capturing group of those numbers, they are treated as the
393        literal characters 8 and 9 instead of a binary zero followed by the
394        literals. PCRE now does the same.
396    22. Following Perl, added \o{} to specify codepoints in octal, making it
397        possible to specify values greater than 0777 and also making them
398        unambiguous.
400    23. Perl now gives an error for missing closing braces after \x{... instead of
401        treating the string as literal. PCRE now does the same.
403    24. RunTest used to grumble if an inappropriate test was selected explicitly,
404        but just skip it when running all tests. This make it awkward to run ranges
405        of tests when one of them was inappropriate. Now it just skips any
406        inappropriate tests, as it always did when running all tests.
408    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
409        character types such as \d or \w, too many callouts were inserted, and the
410        data that they returned was rubbish.
412    26. In UCP mode, \s was not matching two of the characters that Perl matches,
413        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
414        were matched by \h. The code has now been refactored so that the lists of
415        the horizontal and vertical whitespace characters used for \h and \v (which
416        are defined only in one place) are now also used for \s.
418    27. Add JIT support for the 64 bit TileGX architecture.
419        Patch by Jiong Wang (Tilera Corporation).
421    28. Possessive quantifiers for classes (both explicit and automatically
422        generated) now use special opcodes instead of wrapping in ONCE brackets.
424    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
425        (because it's meaningless), this was not happening when PCRE_CASELESS was
426        set. Not wrong, but inefficient.
428    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
429        properties for \w, \d, etc) is present in a test regex. Otherwise if the
430        test contains no characters greater than 255, Perl doesn't realise it
431        should be using Unicode semantics.
433    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
434        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
435        does in Unicode mode.
437    32. Added the "forbid" facility to pcretest so that putting tests into the
438        wrong test files can sometimes be quickly detected.
440    33. There is now a limit (default 250) on the depth of nesting of parentheses.
441        This limit is imposed to control the amount of system stack used at compile
442        time. It can be changed at build time by --with-parens-nest-limit=xxx or
443        the equivalent in CMake.
445    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
446        errors. Perl warns for these when in warning mode, but PCRE has no facility
447        for giving warnings.
449    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
450        However, this was not working for (?!) because it is optimized to (*FAIL),
451        for which PCRE does not allow quantifiers. The optimization is now disabled
452        when a quantifier follows (?!). I can't see any use for this, but it makes
453        things uniform.
455    36. Perl no longer allows group names to start with digits, so I have made this
456        change also in PCRE. It simplifies the code a bit.
458    37. In extended mode, Perl ignores spaces before a + that indicates a
459        possessive quantifier. PCRE allowed a space before the quantifier, but not
460        before the possessive +. It now does.
462    38. The use of \K (reset reported match start) within a repeated possessive
463        group such as (a\Kb)*+ was not working.
465    40. Document that the same character tables must be used at compile time and
466        run time, and that the facility to pass tables to pcre_exec() and
467        pcre_dfa_exec() is for use only with saved/restored patterns.
469    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
470        features for Builds with MSVC:
472        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
473           builds). The .rc files can be used to set FileDescription and many other
474           attributes.
476        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
477           This allows higher-level build scripts which want .pdb files to avoid
478           hard-coding the exact files needed."
480    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
481        mean "start of word" and "end of word", respectively, as a transition aid.
483    43. A minimizing repeat of a class containing codepoints greater than 255 in
484        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
485        compiled to use the heap for recursion.
487    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
488        is configured.
491    Version 8.33 28-May-2013
492    ------------------------
494    1.  Added 'U' to some constants that are compared to unsigned integers, to
495        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
496        variables that are added to signed variables, to ensure the result is
497        signed and can be negated.
499    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
500        CMake config files.
502    3.  Revise the creation of config.h.generic so that all boolean macros are
503        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
504        overriding via -D on the command line possible.
506    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
507        to unsigned int is reported to make a quite noticeable speed difference in
508        a specific Windows environment. Testing on Linux did also appear to show
509        some benefit (and it is clearly not harmful). Also fixed the definition of
510        Xop which should be unsigned.
512    5.  Related to (4), changing the definition of the intermediate variable cc
513        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
514        improvements.
516    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
517        unnecessary spaces.
519    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
520        and later.
522    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
524    9.  Optimizing fast_forward_start_bits in JIT.
526    10. Adding support for callouts in JIT, and fixing some issues revealed
527        during this work. Namely:
529        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
531        (b) Minimum length was not checked before the matching is started.
533    11. The value of capture_last that is passed to callouts was incorrect in some
534        cases when there was a capture on one path that was subsequently abandoned
535        after a backtrack. Also, the capture_last value is now reset after a
536        recursion, since all captures are also reset in this case.
538    12. The interpreter no longer returns the "too many substrings" error in the
539        case when an overflowing capture is in a branch that is subsequently
540        abandoned after a backtrack.
542    13. In the pathological case when an offset vector of size 2 is used, pcretest
543        now prints out the matched string after a yield of 0 or 1.
545    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
546        Only supported by the JIT compiler at the moment.
548    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
550    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
551        offset of the starting point of the matching process, provided the offsets
552        vector is large enough.
554    17. The \A escape now records a lookbehind value of 1, though its execution
555        does not actually inspect the previous character. This is to ensure that,
556        in partial multi-segment matching, at least one character from the old
557        segment is retained when a new segment is processed. Otherwise, if there
558        are no lookbehinds in the pattern, \A might match incorrectly at the start
559        of a new segment.
561    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
563    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
564        gives some modest performance improvement in 8-bit mode.
566    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
567        be expressed in certain programming languages using Universal Character
568        Names.
570    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
571        which points out that "non characters" are not "characters that may not
572        appear in Unicode strings" but rather "characters that are reserved for
573        internal use and have only local meaning".
575    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
576        there was a conditional group that depended on an assertion, if the
577        assertion was false, the callout that immediately followed the alternation
578        in the condition was skipped when pcre_exec() was used for matching.
580    23. Allow an explicit callout to be inserted before an assertion that is the
581        condition for a conditional group, for compatibility with automatic
582        callouts, which always insert a callout at this point.
584    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
585        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
587    25. (*PRUNE) is now supported by the JIT compiler.
589    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
591    27. Fix the case where there are two or more SKIPs with arguments that may be
592        ignored.
594    28. (*SKIP) is now supported by the JIT compiler.
596    29. (*THEN) is now supported by the JIT compiler.
598    30. Update RunTest with additional test selector options.
600    31. The way PCRE handles backtracking verbs has been changed in two ways.
602        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
603        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
604        backtracking. In some cases this makes it more Perl-compatible, but Perl's
605        rather obscure rules do not always do the same thing.
607        (2) Previously, backtracking verbs were confined within assertions. This is
608        no longer the case for positive assertions, except for (*ACCEPT). Again,
609        this sometimes improves Perl compatibility, and sometimes does not.
611    32. A number of tests that were in test 2 because Perl did things differently
612        have been moved to test 1, because either Perl or PCRE has changed, and
613        these tests are now compatible.
615    32. Backtracking control verbs are now handled in the same way in JIT and
616        interpreter.
618    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
619        contained a forward subroutine reference caused a compile error.
621    34. Auto-detect and optimize limited repetitions in JIT.
623    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
624        blocking (*UTF) etc.
626    36. In the interpreter, maximizing pattern repetitions for characters and
627        character types now use tail recursion, which reduces stack usage.
629    37. The value of the max lookbehind was not correctly preserved if a compiled
630        and saved regex was reloaded on a host of different endianness.
632    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
633        of the compiled pattern block, expand the flags field from 16 to 32 bits
634        because it was almost full.
636    39. Try madvise first before posix_madvise.
638    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
639        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
640        original change locked out all matches of empty strings. This has been
641        changed so that one match of an empty string per line is recognized.
642        Subsequent searches on the same line (for colouring or for --only-matching,
643        for example) do not recognize empty strings.
645    41. Applied a user patch to fix a number of spelling mistakes in comments.
647    42. Data lines longer than 65536 caused pcretest to crash.
649    43. Clarified the data type for length and startoffset arguments for pcre_exec
650        and pcre_dfa_exec in the function-specific man pages, where they were
651        explicitly stated to be in bytes, never having been updated. I also added
652        some clarification to the pcreapi man page.
654    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
655        a segmentation fault.
658    Version 8.32 30-November-2012
659    -----------------------------
661    1.  Improved JIT compiler optimizations for first character search and single
662        character iterators.
664    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
665        Patch by Daniel Richard G.
667    3.  Single character iterator optimizations in the JIT compiler.
669    4.  Improved JIT compiler optimizations for character ranges.
671    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
672        Reported by Giuseppe D'Angelo.
674    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
675        of a line, was being set incorrectly in cases where .* appeared inside
676        atomic brackets at the start of a pattern, or where there was a subsequent
677        *PRUNE or *SKIP.
679    7.  Improved instruction cache flush for POWER/PowerPC.
680        Patch by Daniel Richard G.
682    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
683        grep:
685        (a) There is now no limit to the number of patterns to be matched.
687        (b) An error is given if a pattern is too long.
689        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
690            are now supported.
692        (d) --exclude-from and --include-from (multiple use) have been added.
694        (e) Exclusions and inclusions now apply to all files and directories, not
695            just to those obtained from scanning a directory recursively.
697        (f) Multiple uses of -f and --file-list are now supported.
699        (g) In a Windows environment, the default for -d has been changed from
700            "read" (the GNU grep default) to "skip", because otherwise the presence
701            of a directory in the file list provokes an error.
703        (h) The documentation has been revised and clarified in places.
705    9.  Improve the matching speed of capturing brackets.
707    10. Changed the meaning of \X so that it now matches a Unicode extended
708        grapheme cluster.
710    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
711        out POSIX threads when JIT support is configured.
713    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
715    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
716        structure could go wrong in environments where size_t is not the same size
717        as int.
719    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
720        set.
722    15. The EBCDIC support had decayed; later updates to the code had included
723        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
724        general tidy up of EBCDIC-related issues, and the documentation was also
725        not quite right. There is now a test that can be run on ASCII systems to
726        check some of the EBCDIC-related things (but is it not a full test).
728    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
729        in a small tidy to the code.
731    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
733    18. If the --only-matching (-o) option in pcregrep is specified multiple
734        times, each one causes appropriate output. For example, -o1 -o2 outputs the
735        substrings matched by the 1st and 2nd capturing parentheses. A separating
736        string can be specified by --om-separator (default empty).
738    19. Improving the first n character searches.
740    20. Turn case lists for horizontal and vertical white space into macros so that
741        they are defined only once.
743    21. This set of changes together give more compatible Unicode case-folding
744        behaviour for characters that have more than one other case when UCP
745        support is available.
747        (a) The Unicode property table now has offsets into a new table of sets of
748            three or more characters that are case-equivalent. The MultiStage2.py
749            script that generates these tables (the pcre_ucd.c file) now scans
750            CaseFolding.txt instead of UnicodeData.txt for character case
751            information.
753        (b) The code for adding characters or ranges of characters to a character
754            class has been abstracted into a generalized function that also handles
755            case-independence. In UTF-mode with UCP support, this uses the new data
756            to handle characters with more than one other case.
758        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
759            whose other case is greater than 256 are now correctly matched
760            caselessly. Previously, the high codepoint matched the low one, but not
761            vice versa.
763        (d) The processing of \h, \H, \v, and \ in character classes now makes use
764            of the new class addition function, using character lists defined as
765            macros alongside the case definitions of 20 above.
767        (e) Caseless back references now work with characters that have more than
768            one other case.
770        (f) General caseless matching of characters with more than one other case
771            is supported.
773    22. Unicode character properties were updated from Unicode 6.2.0
775    23. Improved CMake support under Windows. Patch by Daniel Richard G.
777    24. Add support for 32-bit character strings, and UTF-32
779    25. Major JIT compiler update (code refactoring and bugfixing).
780        Experimental Sparc 32 support is added.
782    26. Applied a modified version of Daniel Richard G's patch to create
783        pcre.h.generic and config.h.generic by "make" instead of in the
784        PrepareRelease script.
786    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
787        pcre_compile.c when checking for a zero character.
789    28. Introducing a native interface for JIT. Through this interface, the compiled
790        machine code can be directly executed. The purpose of this interface is to
791        provide fast pattern matching, so several sanity checks are not performed.
792        However, feature tests are still performed. The new interface provides
793        1.4x speedup compared to the old one.
795    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
796        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
797        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
799    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
800        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
801        the "old" RFC 2279). Instead, it ended up passing a negative length to
802        pcre_exec().
804    31. Add support for GCC's visibility feature to hide internal functions.
806    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
807        "unknown -C option" after outputting 0 or 1.
809    33. There is now support for generating a code coverage report for the test
810        suite in environments where gcc is the compiler and lcov is installed. This
811        is mainly for the benefit of the developers.
813    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
814        unaddressable using valgrind annotations, allowing valgrind to detect
815        invalid memory accesses. This is mainly for the benefit of the developers.
817    25. (*UTF) can now be used to start a pattern in any of the three libraries.
819    26. Give configure error if --enable-cpp but no C++ compiler found.
822    Version 8.31 06-July-2012
823    -------------------------
825    1.  Fixing a wrong JIT test case and some compiler warnings.
827    2.  Removed a bashism from the RunTest script.
829    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
830        to unsigned type, result still unsigned" that was given by an MS compiler
831        on encountering the code "-sizeof(xxx)".
833    4.  Partial matching support is added to the JIT compiler.
835    5.  Fixed several bugs concerned with partial matching of items that consist
836        of more than one character:
838        (a) /^(..)\1/ did not partially match "aba" because checking references was
839            done on an "all or nothing" basis. This also applied to repeated
840            references.
842        (b) \R did not give a hard partial match if \r was found at the end of the
843            subject.
845        (c) \X did not give a hard partial match after matching one or more
846            characters at the end of the subject.
848        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
849            a partial match for the string "\r".
851        (e) When newline was set to CRLF, the metacharacter "." did not recognize
852            a partial match for a CR character at the end of the subject string.
854    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
855        running pcretest, the text "(JIT)" added to the output whenever JIT is
856        actually used to run the match.
858    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
859        or /S+[+] with a digit between 1 and 7.
861    8.  OP_NOT now supports any UTF character not just single-byte ones.
863    9.  (*MARK) control verb is now supported by the JIT compiler.
865    10. The command "./RunTest list" lists the available tests without actually
866        running any of them. (Because I keep forgetting what they all are.)
870    12. Applied a (slightly modified) user-supplied patch that improves performance
871        when the heap is used for recursion (compiled with --disable-stack-for-
872        recursion). Instead of malloc and free for each heap frame each time a
873        logical recursion happens, frames are retained on a chain and re-used where
874        possible. This sometimes gives as much as 30% improvement.
876    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
877        call.
879    14. As documented, (*COMMIT) is now confined to within a positive assertion.
881    15. It is now possible to link pcretest with libedit as an alternative to
882        libreadline.
884    16. (*COMMIT) control verb is now supported by the JIT compiler.
886    17. The Unicode data tables have been updated to Unicode 6.1.0.
888    18. Added --file-list option to pcregrep.
890    19. Added binary file support to pcregrep, including the -a, --binary-files,
891        -I, and --text options.
893    20. The madvise function is renamed for posix_madvise for QNX compatibility
894        reasons. Fixed by Giuseppe D'Angelo.
896    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
898    22. Changed the option for creating symbolic links for 16-bit man pages from
899        -s to -sf so that re-installing does not cause issues.
901    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
903    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
904        matches in certain environments (the workspace was not being correctly
905        retained). Also added to pcre_dfa_exec() a simple plausibility check on
906        some of the workspace data at the beginning of a restart.
908    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
909        was not doing so when it should - probably a typo introduced by SVN 528
910        (change 8.10/14).
912    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
913        \w+ when the character tables indicated that \x{c4} was a word character.
914        There were several related cases, all because the tests for doing a table
915        lookup were testing for characters less than 127 instead of 255.
917    27. If a pattern contains capturing parentheses that are not used in a match,
918        their slots in the ovector are set to -1. For those that are higher than
919        any matched groups, this happens at the end of processing. In the case when
920        there were back references that the ovector was too small to contain
921        (causing temporary malloc'd memory to be used during matching), and the
922        highest capturing number was not used, memory off the end of the ovector
923        was incorrectly being set to -1. (It was using the size of the temporary
924        memory instead of the true size.)
926    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
927        ovector size, it uses memory at the end of the block that it has got.
929    29. Check for an overlong MARK name and give an error at compile time. The
930        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
932    30. JIT compiler update.
934    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
935        Rill for the patch.
937    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
939    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
941    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
942        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
943        was enabled.
945    35. Improve JIT code generation for greedy plus quantifier.
947    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
948        1 to "aa" instead of to an empty string. The bug affected repeated groups
949        that could potentially match an empty string.
951    37. Optimizing single character iterators in JIT.
953    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
954        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
955        codepoints that are too big for the mode are faulted, and in a UTF mode,
956        disallowed codepoints are also faulted.
958    39. If PCRE was compiled with UTF support, in three places in the DFA
959        matcher there was code that should only have been obeyed in UTF mode, but
960        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
961        processing when bytes with values greater than 127 were present. In 16-bit
962        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
963        both cases the values are those that cannot be the first data item in a UTF
964        character. The three items that might have provoked this were recursions,
965        possessively repeated groups, and atomic groups.
967    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
968        and pcregrep, because some OS require shared objects to be explicitly
969        passed to ld, causing the link step to fail if they are not.
971    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
972        mode, patterns that started with \h* or \R* might be incorrectly matched.
975    Version 8.30 04-February-2012
976    -----------------------------
978    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
979        name is defined in ctype.h.
981    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
982        only in quite long subpatterns.
984    3.  Removed the function pcre_info(), which has been obsolete and deprecated
985        since it was replaced by pcre_fullinfo() in February 2000.
987    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
988        match a (*MARK), and the match failed at the start of the subject, a
989        reference to memory before the start of the subject could occur. This bug
990        was introduced by fix 17 of release 8.21.
992    5.  A reference to an unset group with zero minimum repetition was giving
993        totally wrong answers (in non-JavaScript-compatibility mode). For example,
994        /(another)?(\1?)test/ matched against "hello world test". This bug was
995        introduced in release 8.13.
997    6.  Add support for 16-bit character strings (a large amount of work involving
998        many changes and refactorings).
1000    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
1001        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
1002        from a file.
1004    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
1005        rounding is not applied in this particular case).
1007    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
1008        if they appear, or are escaped, in patterns.
1010    10. Get rid of a number of -Wunused-but-set-variable warnings.
1012    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
1013        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
1014        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
1015        also returns the mark "x". This bug applied to capturing parentheses,
1016        non-capturing parentheses, and atomic parentheses. It also applied to some
1017        assertions.
1019    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
1020        information out of configure.ac instead of relying on pcre.h.generic, which
1021        is not stored in the repository.
1023    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
1024        -lreadline.
1026    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
1028    15. Applied Graycode's patch to put the top-level frame on the stack rather
1029        than the heap when not using the stack for recursion. This gives a
1030        performance improvement in many cases when recursion is not deep.
1032    16. Experimental code added to "pcretest -C" to output the stack frame size.
1035    Version 8.21 12-Dec-2011
1036    ------------------------
1038  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
# Line 13  Version 8.21 Line 1044  Version 8.21
1044      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
1045      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
1047  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
1048      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
1049      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
# Line 22  Version 8.21 Line 1053  Version 8.21
1054  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
1055      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
1056      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
1058  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
1059      incorrectly rejected as "not fixed length". This arose partly because newer      incorrectly rejected as "not fixed length". This arose partly because newer
1060      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)
1061      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
1062      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
1063      length instead of just assuming "not fixed length". The items that were      length instead of just assuming "not fixed length". The items that were
1064      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),      rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
1065      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed      (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
1066      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.      repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
1068  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was  8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
1069      being incorrectly compiled and would have given unpredicatble results.      being incorrectly compiled and would have given unpredicatble results.
1071  9.  A possessively repeated subpattern with minimum repeat count greater than  9.  A possessively repeated subpattern with minimum repeat count greater than
1072      one behaved incorrectly. For example, (A){2,}+ behaved as if it was      one behaved incorrectly. For example, (A){2,}+ behaved as if it was
1073      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into      (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
1074      the first (A) could occur when it should not.      the first (A) could occur when it should not.
1076  10. Add a cast and remove a redundant test from the code.  10. Add a cast and remove a redundant test from the code.
1078  11. JIT should use pcre_malloc/pcre_free for allocation.  11. JIT should use pcre_malloc/pcre_free for allocation.
1080  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
1081      best practice nowadays, and helps with cross-compiling. (If the exec_prefix      best practice nowadays, and helps with cross-compiling. (If the exec_prefix
1082      is anything other than /usr, -L is still shown).      is anything other than /usr, -L is still shown).
1084  13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.  13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
1086  14. Perl does not support \N without a following name in a [] class; PCRE now  14. Perl does not support \N without a following name in a [] class; PCRE now
1087      also gives an error.      also gives an error.
1089  15. If a forward reference was repeated with an upper limit of around 2000,  15. If a forward reference was repeated with an upper limit of around 2000,
1090      it caused the error "internal error: overran compiling workspace". This      it caused the error "internal error: overran compiling workspace". The
1091      is now checked, and causes "too many forward references" instead.      maximum number of forward references (including repeats) was limited by the
1092        internal workspace, and dependent on the LINK_SIZE. The code has been
1093        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
1094        the default depends on LINK_SIZE. There is a new upper limit (for safety)
1095        of around 200,000 forward references. While doing this, I also speeded up
1096        the filling in of repeated forward references.
1098    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
1099        incorrectly expecting the subject to contain another "a" after the start.
1101    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
1102        in the match, the SKIP should be ignored. This was not happening; instead
1103        the SKIP was being treated as NOMATCH. For patterns such as
1104        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
1105        tested.
1107    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
1108        now much more compatible with Perl, in particular in cases where the result
1109        is a non-match for a non-anchored pattern. For example, if
1110        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
1111        "m", where previously it did not return a name. A side effect of this
1112        change is that for partial matches, the last encountered mark name is
1113        returned, as for non matches. A number of tests that were previously not
1114        Perl-compatible have been moved into the Perl-compatible test files. The
1115        refactoring has had the pleasing side effect of removing one argument from
1116        the match() function, thus reducing its stack requirements.
1118    19. If the /S+ option was used in pcretest to study a pattern using JIT,
1119        subsequent uses of /S (without +) incorrectly behaved like /S+.
1121    21. Retrieve executable code size support for the JIT compiler and fixing
1122        some warnings.
1124    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
1125        not work when the shorter character appeared right at the end of the
1126        subject string.
1128    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
1129        systems.
1131    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
1132        output it when the /M option is used in pcretest.
1134    25. The CheckMan script was not being included in the distribution. Also, added
1135        an explicit "perl" to run Perl scripts from the PrepareRelease script
1136        because this is reportedly needed in Windows.
1138    26. If study data was being save in a file and studying had not found a set of
1139        "starts with" bytes for the pattern, the data written to the file (though
1140        never used) was taken from uninitialized memory and so caused valgrind to
1141        complain.
1143    27. Updated RunTest.bat as provided by Sheri Pierce.
1145    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
1147    29. Computation of memory usage for the table of capturing group names was
1148        giving an unnecessarily large value.
1151  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011
# Line 1074  Version 7.9 11-Apr-09 Line 2162  Version 7.9 11-Apr-09
2162  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
2163      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
2164      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2165      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2166        8.33.]
2168  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
2169      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 1317  Version 7.7 07-May-08 Line 2406  Version 7.7 07-May-08
2406      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2407      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2408      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2409      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2410      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2411      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.760  
changed lines
  Added in v.1523

  ViewVC Help
Powered by ViewVC 1.1.5