ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 1526 by ph10, Fri Feb 20 10:51:07 2015 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 02-Aug-2011  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.
79    Version 8.36 26-September-2014
80    ------------------------------
82    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
83        -Wmissing-field-initializers and -Wunused-parameter.
85    2.  The tests for quantifiers being too big (greater than 65535) were being
86        applied after reading the number, and stupidly assuming that integer
87        overflow would give a negative number. The tests are now applied as the
88        numbers are read.
90    3.  Tidy code in pcre_exec.c where two branches that used to be different are
91        now the same.
93    4.  The JIT compiler did not generate match limit checks for certain
94        bracketed expressions with quantifiers. This may lead to exponential
95        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
96        issue should be resolved now.
98    5.  Fixed an issue, which occures when nested alternatives are optimized
99        with table jumps.
101    6.  Inserted two casts and changed some ints to size_t in the light of some
102        reported 64-bit compiler warnings (Bugzilla 1477).
104    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
105        an empty string, which sometimes were behaving incorrectly in the
106        interpreter (though correctly in the JIT matcher). This pcretest input is
107        an example:
109          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
112        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
113        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
114        for an empty string was breaking the inner loop and carrying on at a lower
115        level, when possessive repeated groups should always return to a higher
116        level as they have no backtrack points in them. The empty string test now
117        occurs at the outer level.
119    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
120        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
122    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
123        doesn't).
125    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
126        to hold a pattern to be incorrectly computed (too small) when there were
127        named back references to duplicated names. This could cause "internal
128        error: code overflow" or "double free or corruption" or other memory
129        handling errors.
131    11. When named subpatterns had the same prefixes, back references could be
132        confused. For example, in this pattern:
134          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
136        the reference to 'Name' was incorrectly treated as a reference to a
137        duplicate name.
139    12. A pattern such as /^s?c/mi8 where the optional character has more than
140        one "other case" was incorrectly compiled such that it would only try to
141        match starting at "c".
143    13. When a pattern starting with \s was studied, VT was not included in the
144        list of possible starting characters; this should have been part of the
145        8.34/18 patch.
147    14. If a character class started [\Qx]... where x is any character, the class
148        was incorrectly terminated at the ].
150    15. If a pattern that started with a caseless match for a character with more
151        than one "other case" was studied, PCRE did not set up the starting code
152        unit bit map for the list of possible characters. Now it does. This is an
153        optimization improvement, not a bug fix.
155    16. The Unicode data tables have been updated to Unicode 7.0.0.
157    17. Fixed a number of memory leaks in pcregrep.
159    18. Avoid a compiler warning (from some compilers) for a function call with
160        a cast that removes "const" from an lvalue by using an intermediate
161        variable (to which the compiler does not object).
163    19. Incorrect code was compiled if a group that contained an internal recursive
164        back reference was optional (had quantifier with a minimum of zero). This
165        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
166        caused segmentation faults because of stack overflows at compile time.
168    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
169        group that is quantified with an indefinite repeat, caused a compile-time
170        loop which used up all the system stack and provoked a segmentation fault.
171        This was not the same bug as 19 above.
173    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
174        Patch by Mike Frysinger.
177    Version 8.35 04-April-2014
178    --------------------------
180    1.  A new flag is set, when property checks are present in an XCLASS.
181        When this flag is not set, PCRE can perform certain optimizations
182        such as studying these XCLASS-es.
184    2.  The auto-possessification of character sets were improved: a normal
185        and an extended character set can be compared now. Furthermore
186        the JIT compiler optimizes more character set checks.
188    3.  Got rid of some compiler warnings for potentially uninitialized variables
189        that show up only when compiled with -O2.
191    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
192        of a match later then the end of the match. The pcretest program was not
193        handling the case sensibly - it was outputting from the start to the next
194        binary zero. It now reports this situation in a message, and outputs the
195        text from the end to the start.
197    5.  Fast forward search is improved in JIT. Instead of the first three
198        characters, any three characters with fixed position can be searched.
199        Search order: first, last, middle.
201    6.  Improve character range checks in JIT. Characters are read by an inprecise
202        function now, which returns with an unknown value if the character code is
203        above a certain threshold (e.g: 256). The only limitation is that the value
204        must be bigger than the threshold as well. This function is useful when
205        the characters above the threshold are handled in the same way.
207    7.  The macros whose names start with RAWUCHAR are placeholders for a future
208        mode in which only the bottom 21 bits of 32-bit data items are used. To
209        make this more memorable for those maintaining the code, the names have
210        been changed to start with UCHAR21, and an extensive comment has been added
211        to their definition.
213    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
214        to the export list in Makefile.am (they were accidentally omitted from the
215        8.34 tarball).
217    9.  The informational output from pcretest used the phrase "starting byte set"
218        which is inappropriate for the 16-bit and 32-bit libraries. As the output
219        for "first char" and "need char" really means "non-UTF-char", I've changed
220        "byte" to "char", and slightly reworded the output. The documentation about
221        these values has also been (I hope) clarified.
223    10. Another JIT related optimization: use table jumps for selecting the correct
224        backtracking path, when more than four alternatives are present inside a
225        bracket.
227    11. Empty match is not possible, when the minimum length is greater than zero,
228        and there is no \K in the pattern. JIT should avoid empty match checks in
229        such cases.
231    12. In a caseless character class with UCP support, when a character with more
232        than one alternative case was not the first character of a range, not all
233        the alternative cases were added to the class. For example, s and \x{17f}
234        are both alternative cases for S: the class [RST] was handled correctly,
235        but [R-T] was not.
237    13. The configure.ac file always checked for pthread support when JIT was
238        enabled. This is not used in Windows, so I have put this test inside a
239        check for the presence of windows.h (which was already tested for).
241    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
242        The algorithm provides a way to skip certain starting offsets, and usually
243        faster than linear prefix searches.
245    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
246        as for 'fr_FR' and 'french'. For some reason, however, it then used the
247        Windows-specific input and output files, which have 'french' screwed in.
248        So this could never have worked. One of the problems with locales is that
249        they aren't always the same. I have now updated RunTest so that it checks
250        the output of the locale test (test 3) against three different output
251        files, and it allows the test to pass if any one of them matches. With luck
252        this should make the test pass on some versions of Solaris where it was
253        failing. Because of the uncertainty, the script did not used to stop if
254        test 3 failed; it now does. If further versions of a French locale ever
255        come to light, they can now easily be added.
257    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
258        there was a message during ./configure, but it did not stop. This now
259        provokes an error. The invalid example in README has been corrected.
260        If a value less than the minimum is given, the minimum value has always
261        been used, but now a warning is given.
263    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
264        was a bug in the test system, which is now fixed. Also, the list of various
265        configurations that are tested for each release did not have one with both
266        16/32 bits and --enable-bar-anycrlf. It now does.
268    18. pcretest was missing "-C bsr" for displaying the \R default setting.
270    19. Little endian PowerPC systems are supported now by the JIT compiler.
272    20. The fast forward newline mechanism could enter to an infinite loop on
273        certain invalid UTF-8 input. Although we don't support these cases
274        this issue can be fixed by a performance optimization.
276    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
277        not take account if existing stack usage. There is now a new global
278        variable called pcre_stack_guard that can be set to point to an external
279        function to check stack availability. It is called at the start of
280        processing every parenthesized group.
282    22. A typo in the code meant that in ungreedy mode the max/min qualifier
283        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
284        not match "ab".
286    23. When UTF was disabled, the JIT program reported some incorrect compile
287        errors. These messages are silenced now.
289    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
290        compiler.
292    25. Change all the temporary files used in RunGrepTest to be different to those
293        used by RunTest so that the tests can be run simultaneously, for example by
294        "make -j check".
297    Version 8.34 15-December-2013
298    -----------------------------
300    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
301        executable memory. Patch inspired by Carsten Klein.
303    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
304        this macro is never tested and has no effect, because the work to support
305        coverage involves only compiling and linking options and special targets in
306        the Makefile. The comment in config.h implied that defining the macro would
307        enable coverage support, which is totally false. There was also support for
308        setting this macro in the CMake files (my fault, I just copied it from
309        configure). SUPPORT_GCOV has now been removed.
311    3.  Make a small performance improvement in strlen16() and strlen32() in
312        pcretest.
314    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
315        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
316        these cases). There was also one in pcretest.c.
318    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
320    6.  In UTF mode, the code for checking whether a group could match an empty
321        string (which is used for indefinitely repeated groups to allow for
322        breaking an infinite loop) was broken when the group contained a repeated
323        negated single-character class with a character that occupied more than one
324        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
325        UTF-8 mode). The effect was undefined: the group might or might not be
326        deemed as matching an empty string, or the program might have crashed.
328    7.  The code for checking whether a group could match an empty string was not
329        recognizing that \h, \H, \v, \V, and \R must match a character.
331    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
332        an empty string. If it can, pcretest shows this in its information output.
334    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
335        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
336        matched by pcre_exec() without using JIT:
338        (a) If the rest of the pattern did not match after a maximal run of
339            grapheme clusters, the code for backing up to try with fewer of them
340            did not always back up over a full grapheme when characters that do not
341            have the modifier quality were involved, e.g. Hangul syllables.
343        (b) If the match point in a subject started with modifier character, and
344            there was no match, the code could incorrectly back up beyond the match
345            point, and potentially beyond the first character in the subject,
346            leading to a segfault or an incorrect match result.
348    10. A conditional group with an assertion condition could lead to PCRE
349        recording an incorrect first data item for a match if no other first data
350        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
351        first data item, and therefore matched "ca" after "c" instead of at the
352        start.
354    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
355        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
357    12. The source of pcregrep now includes z/OS-specific code so that it can be
358        compiled for z/OS as part of the special z/OS distribution.
360    13. Added the -T and -TM options to pcretest.
362    14. The code in pcre_compile.c for creating the table of named capturing groups
363        has been refactored. Instead of creating the table dynamically during the
364        actual compiling pass, the information is remembered during the pre-compile
365        pass (on the stack unless there are more than 20 named groups, in which
366        case malloc() is used) and the whole table is created before the actual
367        compile happens. This has simplified the code (it is now nearly 150 lines
368        shorter) and prepared the way for better handling of references to groups
369        with duplicate names.
371    15. A back reference to a named subpattern when there is more than one of the
372        same name now checks them in the order in which they appear in the pattern.
373        The first one that is set is used for the reference. Previously only the
374        first one was inspected. This change makes PCRE more compatible with Perl.
376    16. Unicode character properties were updated from Unicode 6.3.0.
378    17. The compile-time code for auto-possessification has been refactored, based
379        on a patch by Zoltan Herczeg. It now happens after instead of during
380        compilation. The code is cleaner, and more cases are handled. The option
381        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
382        options in pcretest are provided to set it. It can also be set by
383        (*NO_AUTO_POSSESS) at the start of a pattern.
385    18. The character VT has been added to the default ("C" locale) set of
386        characters that match \s and are generally treated as white space,
387        following this same change in Perl 5.18. There is now no difference between
388        "Perl space" and "POSIX space". Whether VT is treated as white space in
389        other locales depends on the locale.
391    19. The code for checking named groups as conditions, either for being set or
392        for being recursed, has been refactored (this is related to 14 and 15
393        above). Processing unduplicated named groups should now be as fast at
394        numerical groups, and processing duplicated groups should be faster than
395        before.
397    20. Two patches to the CMake build system, by Alexander Barkov:
399          (1) Replace the "source" command by "." in CMakeLists.txt because
400              "source" is a bash-ism.
402          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
403              without these the CMake build does not work on Solaris.
405    21. Perl has changed its handling of \8 and \9. If there is no previously
406        encountered capturing group of those numbers, they are treated as the
407        literal characters 8 and 9 instead of a binary zero followed by the
408        literals. PCRE now does the same.
410    22. Following Perl, added \o{} to specify codepoints in octal, making it
411        possible to specify values greater than 0777 and also making them
412        unambiguous.
414    23. Perl now gives an error for missing closing braces after \x{... instead of
415        treating the string as literal. PCRE now does the same.
417    24. RunTest used to grumble if an inappropriate test was selected explicitly,
418        but just skip it when running all tests. This make it awkward to run ranges
419        of tests when one of them was inappropriate. Now it just skips any
420        inappropriate tests, as it always did when running all tests.
422    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
423        character types such as \d or \w, too many callouts were inserted, and the
424        data that they returned was rubbish.
426    26. In UCP mode, \s was not matching two of the characters that Perl matches,
427        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
428        were matched by \h. The code has now been refactored so that the lists of
429        the horizontal and vertical whitespace characters used for \h and \v (which
430        are defined only in one place) are now also used for \s.
432    27. Add JIT support for the 64 bit TileGX architecture.
433        Patch by Jiong Wang (Tilera Corporation).
435    28. Possessive quantifiers for classes (both explicit and automatically
436        generated) now use special opcodes instead of wrapping in ONCE brackets.
438    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
439        (because it's meaningless), this was not happening when PCRE_CASELESS was
440        set. Not wrong, but inefficient.
442    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
443        properties for \w, \d, etc) is present in a test regex. Otherwise if the
444        test contains no characters greater than 255, Perl doesn't realise it
445        should be using Unicode semantics.
447    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
448        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
449        does in Unicode mode.
451    32. Added the "forbid" facility to pcretest so that putting tests into the
452        wrong test files can sometimes be quickly detected.
454    33. There is now a limit (default 250) on the depth of nesting of parentheses.
455        This limit is imposed to control the amount of system stack used at compile
456        time. It can be changed at build time by --with-parens-nest-limit=xxx or
457        the equivalent in CMake.
459    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
460        errors. Perl warns for these when in warning mode, but PCRE has no facility
461        for giving warnings.
463    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
464        However, this was not working for (?!) because it is optimized to (*FAIL),
465        for which PCRE does not allow quantifiers. The optimization is now disabled
466        when a quantifier follows (?!). I can't see any use for this, but it makes
467        things uniform.
469    36. Perl no longer allows group names to start with digits, so I have made this
470        change also in PCRE. It simplifies the code a bit.
472    37. In extended mode, Perl ignores spaces before a + that indicates a
473        possessive quantifier. PCRE allowed a space before the quantifier, but not
474        before the possessive +. It now does.
476    38. The use of \K (reset reported match start) within a repeated possessive
477        group such as (a\Kb)*+ was not working.
479    40. Document that the same character tables must be used at compile time and
480        run time, and that the facility to pass tables to pcre_exec() and
481        pcre_dfa_exec() is for use only with saved/restored patterns.
483    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
484        features for Builds with MSVC:
486        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
487           builds). The .rc files can be used to set FileDescription and many other
488           attributes.
490        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
491           This allows higher-level build scripts which want .pdb files to avoid
492           hard-coding the exact files needed."
494    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
495        mean "start of word" and "end of word", respectively, as a transition aid.
497    43. A minimizing repeat of a class containing codepoints greater than 255 in
498        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
499        compiled to use the heap for recursion.
501    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
502        is configured.
505    Version 8.33 28-May-2013
506    ------------------------
508    1.  Added 'U' to some constants that are compared to unsigned integers, to
509        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
510        variables that are added to signed variables, to ensure the result is
511        signed and can be negated.
513    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
514        CMake config files.
516    3.  Revise the creation of config.h.generic so that all boolean macros are
517        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
518        overriding via -D on the command line possible.
520    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
521        to unsigned int is reported to make a quite noticeable speed difference in
522        a specific Windows environment. Testing on Linux did also appear to show
523        some benefit (and it is clearly not harmful). Also fixed the definition of
524        Xop which should be unsigned.
526    5.  Related to (4), changing the definition of the intermediate variable cc
527        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
528        improvements.
530    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
531        unnecessary spaces.
533    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
534        and later.
536    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
538    9.  Optimizing fast_forward_start_bits in JIT.
540    10. Adding support for callouts in JIT, and fixing some issues revealed
541        during this work. Namely:
543        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
545        (b) Minimum length was not checked before the matching is started.
547    11. The value of capture_last that is passed to callouts was incorrect in some
548        cases when there was a capture on one path that was subsequently abandoned
549        after a backtrack. Also, the capture_last value is now reset after a
550        recursion, since all captures are also reset in this case.
552    12. The interpreter no longer returns the "too many substrings" error in the
553        case when an overflowing capture is in a branch that is subsequently
554        abandoned after a backtrack.
556    13. In the pathological case when an offset vector of size 2 is used, pcretest
557        now prints out the matched string after a yield of 0 or 1.
559    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
560        Only supported by the JIT compiler at the moment.
562    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
564    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
565        offset of the starting point of the matching process, provided the offsets
566        vector is large enough.
568    17. The \A escape now records a lookbehind value of 1, though its execution
569        does not actually inspect the previous character. This is to ensure that,
570        in partial multi-segment matching, at least one character from the old
571        segment is retained when a new segment is processed. Otherwise, if there
572        are no lookbehinds in the pattern, \A might match incorrectly at the start
573        of a new segment.
575    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
577    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
578        gives some modest performance improvement in 8-bit mode.
580    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
581        be expressed in certain programming languages using Universal Character
582        Names.
584    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
585        which points out that "non characters" are not "characters that may not
586        appear in Unicode strings" but rather "characters that are reserved for
587        internal use and have only local meaning".
589    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
590        there was a conditional group that depended on an assertion, if the
591        assertion was false, the callout that immediately followed the alternation
592        in the condition was skipped when pcre_exec() was used for matching.
594    23. Allow an explicit callout to be inserted before an assertion that is the
595        condition for a conditional group, for compatibility with automatic
596        callouts, which always insert a callout at this point.
598    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
599        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
601    25. (*PRUNE) is now supported by the JIT compiler.
603    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
605    27. Fix the case where there are two or more SKIPs with arguments that may be
606        ignored.
608    28. (*SKIP) is now supported by the JIT compiler.
610    29. (*THEN) is now supported by the JIT compiler.
612    30. Update RunTest with additional test selector options.
614    31. The way PCRE handles backtracking verbs has been changed in two ways.
616        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
617        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
618        backtracking. In some cases this makes it more Perl-compatible, but Perl's
619        rather obscure rules do not always do the same thing.
621        (2) Previously, backtracking verbs were confined within assertions. This is
622        no longer the case for positive assertions, except for (*ACCEPT). Again,
623        this sometimes improves Perl compatibility, and sometimes does not.
625    32. A number of tests that were in test 2 because Perl did things differently
626        have been moved to test 1, because either Perl or PCRE has changed, and
627        these tests are now compatible.
629    32. Backtracking control verbs are now handled in the same way in JIT and
630        interpreter.
632    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
633        contained a forward subroutine reference caused a compile error.
635    34. Auto-detect and optimize limited repetitions in JIT.
637    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
638        blocking (*UTF) etc.
640    36. In the interpreter, maximizing pattern repetitions for characters and
641        character types now use tail recursion, which reduces stack usage.
643    37. The value of the max lookbehind was not correctly preserved if a compiled
644        and saved regex was reloaded on a host of different endianness.
646    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
647        of the compiled pattern block, expand the flags field from 16 to 32 bits
648        because it was almost full.
650    39. Try madvise first before posix_madvise.
652    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
653        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
654        original change locked out all matches of empty strings. This has been
655        changed so that one match of an empty string per line is recognized.
656        Subsequent searches on the same line (for colouring or for --only-matching,
657        for example) do not recognize empty strings.
659    41. Applied a user patch to fix a number of spelling mistakes in comments.
661    42. Data lines longer than 65536 caused pcretest to crash.
663    43. Clarified the data type for length and startoffset arguments for pcre_exec
664        and pcre_dfa_exec in the function-specific man pages, where they were
665        explicitly stated to be in bytes, never having been updated. I also added
666        some clarification to the pcreapi man page.
668    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
669        a segmentation fault.
672    Version 8.32 30-November-2012
673    -----------------------------
675    1.  Improved JIT compiler optimizations for first character search and single
676        character iterators.
678    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
679        Patch by Daniel Richard G.
681    3.  Single character iterator optimizations in the JIT compiler.
683    4.  Improved JIT compiler optimizations for character ranges.
685    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
686        Reported by Giuseppe D'Angelo.
688    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
689        of a line, was being set incorrectly in cases where .* appeared inside
690        atomic brackets at the start of a pattern, or where there was a subsequent
691        *PRUNE or *SKIP.
693    7.  Improved instruction cache flush for POWER/PowerPC.
694        Patch by Daniel Richard G.
696    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
697        grep:
699        (a) There is now no limit to the number of patterns to be matched.
701        (b) An error is given if a pattern is too long.
703        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
704            are now supported.
706        (d) --exclude-from and --include-from (multiple use) have been added.
708        (e) Exclusions and inclusions now apply to all files and directories, not
709            just to those obtained from scanning a directory recursively.
711        (f) Multiple uses of -f and --file-list are now supported.
713        (g) In a Windows environment, the default for -d has been changed from
714            "read" (the GNU grep default) to "skip", because otherwise the presence
715            of a directory in the file list provokes an error.
717        (h) The documentation has been revised and clarified in places.
719    9.  Improve the matching speed of capturing brackets.
721    10. Changed the meaning of \X so that it now matches a Unicode extended
722        grapheme cluster.
724    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
725        out POSIX threads when JIT support is configured.
727    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
729    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
730        structure could go wrong in environments where size_t is not the same size
731        as int.
733    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
734        set.
736    15. The EBCDIC support had decayed; later updates to the code had included
737        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
738        general tidy up of EBCDIC-related issues, and the documentation was also
739        not quite right. There is now a test that can be run on ASCII systems to
740        check some of the EBCDIC-related things (but is it not a full test).
742    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
743        in a small tidy to the code.
745    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
747    18. If the --only-matching (-o) option in pcregrep is specified multiple
748        times, each one causes appropriate output. For example, -o1 -o2 outputs the
749        substrings matched by the 1st and 2nd capturing parentheses. A separating
750        string can be specified by --om-separator (default empty).
752    19. Improving the first n character searches.
754    20. Turn case lists for horizontal and vertical white space into macros so that
755        they are defined only once.
757    21. This set of changes together give more compatible Unicode case-folding
758        behaviour for characters that have more than one other case when UCP
759        support is available.
761        (a) The Unicode property table now has offsets into a new table of sets of
762            three or more characters that are case-equivalent. The MultiStage2.py
763            script that generates these tables (the pcre_ucd.c file) now scans
764            CaseFolding.txt instead of UnicodeData.txt for character case
765            information.
767        (b) The code for adding characters or ranges of characters to a character
768            class has been abstracted into a generalized function that also handles
769            case-independence. In UTF-mode with UCP support, this uses the new data
770            to handle characters with more than one other case.
772        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
773            whose other case is greater than 256 are now correctly matched
774            caselessly. Previously, the high codepoint matched the low one, but not
775            vice versa.
777        (d) The processing of \h, \H, \v, and \ in character classes now makes use
778            of the new class addition function, using character lists defined as
779            macros alongside the case definitions of 20 above.
781        (e) Caseless back references now work with characters that have more than
782            one other case.
784        (f) General caseless matching of characters with more than one other case
785            is supported.
787    22. Unicode character properties were updated from Unicode 6.2.0
789    23. Improved CMake support under Windows. Patch by Daniel Richard G.
791    24. Add support for 32-bit character strings, and UTF-32
793    25. Major JIT compiler update (code refactoring and bugfixing).
794        Experimental Sparc 32 support is added.
796    26. Applied a modified version of Daniel Richard G's patch to create
797        pcre.h.generic and config.h.generic by "make" instead of in the
798        PrepareRelease script.
800    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
801        pcre_compile.c when checking for a zero character.
803    28. Introducing a native interface for JIT. Through this interface, the compiled
804        machine code can be directly executed. The purpose of this interface is to
805        provide fast pattern matching, so several sanity checks are not performed.
806        However, feature tests are still performed. The new interface provides
807        1.4x speedup compared to the old one.
809    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
810        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
811        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
813    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
814        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
815        the "old" RFC 2279). Instead, it ended up passing a negative length to
816        pcre_exec().
818    31. Add support for GCC's visibility feature to hide internal functions.
820    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
821        "unknown -C option" after outputting 0 or 1.
823    33. There is now support for generating a code coverage report for the test
824        suite in environments where gcc is the compiler and lcov is installed. This
825        is mainly for the benefit of the developers.
827    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
828        unaddressable using valgrind annotations, allowing valgrind to detect
829        invalid memory accesses. This is mainly for the benefit of the developers.
831    25. (*UTF) can now be used to start a pattern in any of the three libraries.
833    26. Give configure error if --enable-cpp but no C++ compiler found.
836    Version 8.31 06-July-2012
837    -------------------------
839    1.  Fixing a wrong JIT test case and some compiler warnings.
841    2.  Removed a bashism from the RunTest script.
843    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
844        to unsigned type, result still unsigned" that was given by an MS compiler
845        on encountering the code "-sizeof(xxx)".
847    4.  Partial matching support is added to the JIT compiler.
849    5.  Fixed several bugs concerned with partial matching of items that consist
850        of more than one character:
852        (a) /^(..)\1/ did not partially match "aba" because checking references was
853            done on an "all or nothing" basis. This also applied to repeated
854            references.
856        (b) \R did not give a hard partial match if \r was found at the end of the
857            subject.
859        (c) \X did not give a hard partial match after matching one or more
860            characters at the end of the subject.
862        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
863            a partial match for the string "\r".
865        (e) When newline was set to CRLF, the metacharacter "." did not recognize
866            a partial match for a CR character at the end of the subject string.
868    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
869        running pcretest, the text "(JIT)" added to the output whenever JIT is
870        actually used to run the match.
872    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
873        or /S+[+] with a digit between 1 and 7.
875    8.  OP_NOT now supports any UTF character not just single-byte ones.
877    9.  (*MARK) control verb is now supported by the JIT compiler.
879    10. The command "./RunTest list" lists the available tests without actually
880        running any of them. (Because I keep forgetting what they all are.)
884    12. Applied a (slightly modified) user-supplied patch that improves performance
885        when the heap is used for recursion (compiled with --disable-stack-for-
886        recursion). Instead of malloc and free for each heap frame each time a
887        logical recursion happens, frames are retained on a chain and re-used where
888        possible. This sometimes gives as much as 30% improvement.
890    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
891        call.
893    14. As documented, (*COMMIT) is now confined to within a positive assertion.
895    15. It is now possible to link pcretest with libedit as an alternative to
896        libreadline.
898    16. (*COMMIT) control verb is now supported by the JIT compiler.
900    17. The Unicode data tables have been updated to Unicode 6.1.0.
902    18. Added --file-list option to pcregrep.
904    19. Added binary file support to pcregrep, including the -a, --binary-files,
905        -I, and --text options.
907    20. The madvise function is renamed for posix_madvise for QNX compatibility
908        reasons. Fixed by Giuseppe D'Angelo.
910    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
912    22. Changed the option for creating symbolic links for 16-bit man pages from
913        -s to -sf so that re-installing does not cause issues.
915    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
917    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
918        matches in certain environments (the workspace was not being correctly
919        retained). Also added to pcre_dfa_exec() a simple plausibility check on
920        some of the workspace data at the beginning of a restart.
922    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
923        was not doing so when it should - probably a typo introduced by SVN 528
924        (change 8.10/14).
926    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
927        \w+ when the character tables indicated that \x{c4} was a word character.
928        There were several related cases, all because the tests for doing a table
929        lookup were testing for characters less than 127 instead of 255.
931    27. If a pattern contains capturing parentheses that are not used in a match,
932        their slots in the ovector are set to -1. For those that are higher than
933        any matched groups, this happens at the end of processing. In the case when
934        there were back references that the ovector was too small to contain
935        (causing temporary malloc'd memory to be used during matching), and the
936        highest capturing number was not used, memory off the end of the ovector
937        was incorrectly being set to -1. (It was using the size of the temporary
938        memory instead of the true size.)
940    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
941        ovector size, it uses memory at the end of the block that it has got.
943    29. Check for an overlong MARK name and give an error at compile time. The
944        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
946    30. JIT compiler update.
948    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
949        Rill for the patch.
951    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
953    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
955    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
956        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
957        was enabled.
959    35. Improve JIT code generation for greedy plus quantifier.
961    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
962        1 to "aa" instead of to an empty string. The bug affected repeated groups
963        that could potentially match an empty string.
965    37. Optimizing single character iterators in JIT.
967    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
968        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
969        codepoints that are too big for the mode are faulted, and in a UTF mode,
970        disallowed codepoints are also faulted.
972    39. If PCRE was compiled with UTF support, in three places in the DFA
973        matcher there was code that should only have been obeyed in UTF mode, but
974        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
975        processing when bytes with values greater than 127 were present. In 16-bit
976        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
977        both cases the values are those that cannot be the first data item in a UTF
978        character. The three items that might have provoked this were recursions,
979        possessively repeated groups, and atomic groups.
981    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
982        and pcregrep, because some OS require shared objects to be explicitly
983        passed to ld, causing the link step to fail if they are not.
985    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
986        mode, patterns that started with \h* or \R* might be incorrectly matched.
989    Version 8.30 04-February-2012
990    -----------------------------
992    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
993        name is defined in ctype.h.
995    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
996        only in quite long subpatterns.
998    3.  Removed the function pcre_info(), which has been obsolete and deprecated
999        since it was replaced by pcre_fullinfo() in February 2000.
1001    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
1002        match a (*MARK), and the match failed at the start of the subject, a
1003        reference to memory before the start of the subject could occur. This bug
1004        was introduced by fix 17 of release 8.21.
1006    5.  A reference to an unset group with zero minimum repetition was giving
1007        totally wrong answers (in non-JavaScript-compatibility mode). For example,
1008        /(another)?(\1?)test/ matched against "hello world test". This bug was
1009        introduced in release 8.13.
1011    6.  Add support for 16-bit character strings (a large amount of work involving
1012        many changes and refactorings).
1014    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
1015        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
1016        from a file.
1018    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
1019        rounding is not applied in this particular case).
1021    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
1022        if they appear, or are escaped, in patterns.
1024    10. Get rid of a number of -Wunused-but-set-variable warnings.
1026    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
1027        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
1028        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
1029        also returns the mark "x". This bug applied to capturing parentheses,
1030        non-capturing parentheses, and atomic parentheses. It also applied to some
1031        assertions.
1033    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
1034        information out of configure.ac instead of relying on pcre.h.generic, which
1035        is not stored in the repository.
1037    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
1038        -lreadline.
1040    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
1042    15. Applied Graycode's patch to put the top-level frame on the stack rather
1043        than the heap when not using the stack for recursion. This gives a
1044        performance improvement in many cases when recursion is not deep.
1046    16. Experimental code added to "pcretest -C" to output the stack frame size.
1049    Version 8.21 12-Dec-2011
1050    ------------------------
1052    1.  Updating the JIT compiler.
1054    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
1055        are added as well.
1057    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
1058        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
1059        calling _pcre_jit_exec. Some extra comments are added.
1061    4.  (*MARK) settings inside atomic groups that do not contain any capturing
1062        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
1063        was introduced by change 18 for 8.20.
1065    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
1066        ECMA-262 standard.
1068    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
1069        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
1070        This bug was probably introduced by change 9 of 8.13.
1072    7.  While fixing 6 above, I noticed that a number of other items were being
1073        incorrectly rejected as "not fixed length". This arose partly because newer
1074        opcodes had not been added to the fixed-length checking code. I have (a)
1075        corrected the bug and added tests for these items, and (b) arranged for an
1076        error to occur if an unknown opcode is encountered while checking for fixed
1077        length instead of just assuming "not fixed length". The items that were
1078        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
1079        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
1080        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
1082    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
1083        being incorrectly compiled and would have given unpredicatble results.
1085    9.  A possessively repeated subpattern with minimum repeat count greater than
1086        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
1087        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
1088        the first (A) could occur when it should not.
1090    10. Add a cast and remove a redundant test from the code.
1092    11. JIT should use pcre_malloc/pcre_free for allocation.
1094    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
1095        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
1096        is anything other than /usr, -L is still shown).
1098    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
1100    14. Perl does not support \N without a following name in a [] class; PCRE now
1101        also gives an error.
1103    15. If a forward reference was repeated with an upper limit of around 2000,
1104        it caused the error "internal error: overran compiling workspace". The
1105        maximum number of forward references (including repeats) was limited by the
1106        internal workspace, and dependent on the LINK_SIZE. The code has been
1107        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
1108        the default depends on LINK_SIZE. There is a new upper limit (for safety)
1109        of around 200,000 forward references. While doing this, I also speeded up
1110        the filling in of repeated forward references.
1112    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
1113        incorrectly expecting the subject to contain another "a" after the start.
1115    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
1116        in the match, the SKIP should be ignored. This was not happening; instead
1117        the SKIP was being treated as NOMATCH. For patterns such as
1118        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
1119        tested.
1121    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
1122        now much more compatible with Perl, in particular in cases where the result
1123        is a non-match for a non-anchored pattern. For example, if
1124        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
1125        "m", where previously it did not return a name. A side effect of this
1126        change is that for partial matches, the last encountered mark name is
1127        returned, as for non matches. A number of tests that were previously not
1128        Perl-compatible have been moved into the Perl-compatible test files. The
1129        refactoring has had the pleasing side effect of removing one argument from
1130        the match() function, thus reducing its stack requirements.
1132    19. If the /S+ option was used in pcretest to study a pattern using JIT,
1133        subsequent uses of /S (without +) incorrectly behaved like /S+.
1135    21. Retrieve executable code size support for the JIT compiler and fixing
1136        some warnings.
1138    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
1139        not work when the shorter character appeared right at the end of the
1140        subject string.
1142    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
1143        systems.
1145    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
1146        output it when the /M option is used in pcretest.
1148    25. The CheckMan script was not being included in the distribution. Also, added
1149        an explicit "perl" to run Perl scripts from the PrepareRelease script
1150        because this is reportedly needed in Windows.
1152    26. If study data was being save in a file and studying had not found a set of
1153        "starts with" bytes for the pattern, the data written to the file (though
1154        never used) was taken from uninitialized memory and so caused valgrind to
1155        complain.
1157    27. Updated RunTest.bat as provided by Sheri Pierce.
1159    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
1161    29. Computation of memory usage for the table of capturing group names was
1162        giving an unnecessarily large value.
1165    Version 8.20 21-Oct-2011
1166    ------------------------
1168    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
1169        a POSIX class. After further experiments with Perl, which convinced me that
1170        Perl has bugs and confusions, a closing square bracket is no longer allowed
1171        in a POSIX name. This bug also affected patterns with classes that started
1172        with full stops.
1174    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
1175        captured substring, but while checking the failing first alternative,
1176        substring 1 is temporarily captured. If the output vector supplied to
1177        pcre_exec() was not big enough for this capture, the yield of the function
1178        was still zero ("insufficient space for captured substrings"). This cannot
1179        be totally fixed without adding another stack variable, which seems a lot
1180        of expense for a edge case. However, I have improved the situation in cases
1181        such as /(a)(b)x|abc/ matched against "abc", where the return code
1182        indicates that fewer than the maximum number of slots in the ovector have
1183        been set.
1185    3.  Related to (2) above: when there are more back references in a pattern than
1186        slots in the output vector, pcre_exec() uses temporary memory during
1187        matching, and copies in the captures as far as possible afterwards. It was
1188        using the entire output vector, but this conflicts with the specification
1189        that only 2/3 is used for passing back captured substrings. Now it uses
1190        only the first 2/3, for compatibility. This is, of course, another edge
1191        case.
1193    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
1194        main code base, and can be used by building with --enable-jit. When this is
1195        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
1196        runtime --no-jit option is given.
1198    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
1199        ovector, the return from the function was zero, implying that there were
1200        other matches that did not fit. The correct "exactly full" value is now
1201        returned.
1203    6.  If a subpattern that was called recursively or as a subroutine contained
1204        (*PRUNE) or any other control that caused it to give a non-standard return,
1205        invalid errors such as "Error -26 (nested recursion at the same subject
1206        position)" or even infinite loops could occur.
1208    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
1209        computing the minimum length on reaching *ACCEPT, and so ended up with the
1210        wrong value of 1 rather than 0. Further investigation indicates that
1211        computing a minimum subject length in the presence of *ACCEPT is difficult
1212        (think back references, subroutine calls), and so I have changed the code
1213        so that no minimum is registered for a pattern that contains *ACCEPT.
1215    8.  If (*THEN) was present in the first (true) branch of a conditional group,
1216        it was not handled as intended. [But see 16 below.]
1218    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
1219        Sheri Pierce.
1221    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
1222        the first byte in a match must be "a".
1224    11. Change 17 for 8.13 increased the recursion depth for patterns like
1225        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
1226        pattern contains any instances of (*THEN). If it does not, the old
1227        optimizations are restored. It would be nice to do this on a per-group
1228        basis, but at the moment that is not feasible.
1230    12. In some environments, the output of pcretest -C is CRLF terminated. This
1231        broke RunTest's code that checks for the link size. A single white space
1232        character after the value is now allowed for.
1234    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
1235        For "fr", it uses the Windows-specific input and output files.
1237    14. If (*THEN) appeared in a group that was called recursively or as a
1238        subroutine, it did not work as intended. [But see next item.]
1240    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
1241        pattern fragments (but not containing any | characters). If A and B are
1242        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
1243        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
1244        D. In other words, Perl considers parentheses that do not contain any |
1245        characters to be part of a surrounding alternative, whereas PCRE was
1246        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
1247        differently. PCRE now behaves in the same way as Perl, except in the case
1248        of subroutine/recursion calls such as (?1) which have in any case always
1249        been different (but PCRE had them first :-).
1251    16. Related to 15 above: Perl does not treat the | in a conditional group as
1252        creating alternatives. Such a group is treated in the same way as an
1253        ordinary group without any | characters when processing (*THEN). PCRE has
1254        been changed to match Perl's behaviour.
1256    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
1257        RunGrepTest script failed.
1259    18. Change 22 for version 13 caused atomic groups to use more stack. This is
1260        inevitable for groups that contain captures, but it can lead to a lot of
1261        stack use in large patterns. The old behaviour has been restored for atomic
1262        groups that do not contain any capturing parentheses.
1264    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
1265        suppress the check for a minimum subject length at run time. (If it was
1266        given to pcre_exec() or pcre_dfa_exec() it did work.)
1268    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
1269        fail to work when decoding hex characters in data strings in EBCDIC
1270        environments.
1272    21. It appears that in at least one Mac OS environment, the isxdigit() function
1273        is implemented as a macro that evaluates to its argument more than once,
1274        contravening the C 90 Standard (I haven't checked a later standard). There
1275        was an instance in pcretest which caused it to go wrong when processing
1276        \x{...} escapes in subject strings. The has been rewritten to avoid using
1277        things like p++ in the argument of isxdigit().
1280    Version 8.13 16-Aug-2011
1281  ------------------------  ------------------------
1283  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 98  Version 8.13 02-Aug-2011 Line 1374  Version 8.13 02-Aug-2011
1374      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
1375      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
1376      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
1377      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
1379  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
1380      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 1465  Version 8.13 02-Aug-2011
1465      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1466      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
1467      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1468      more like Perl.      more like Perl. (But see 8.20/1 above.)
1470  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1471      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 1500  Version 8.13 02-Aug-2011
1500      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
1501          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
1503      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1504          PCRE is built.          PCRE is built.
1506      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 245  Version 8.13 02-Aug-2011 Line 1521  Version 8.13 02-Aug-2011
1521  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1522      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
1523      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
1525  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1526      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
1529  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
# Line 900  Version 7.9 11-Apr-09 Line 2176  Version 7.9 11-Apr-09
2176  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
2177      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
2178      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2179      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2180        8.33.]
2182  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
2183      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 1143  Version 7.7 07-May-08 Line 2420  Version 7.7 07-May-08
2420      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2421      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2422      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2423      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2424      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2425      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.657  
changed lines
  Added in v.1526

  ViewVC Help
Powered by ViewVC 1.1.5