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 1504 by ph10, Fri Sep 26 09:21:46 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 02-Aug-2011  Version 8.36 26-September-2014
5    ------------------------------
7    1.  Got rid of some compiler warnings in the C++ modules that were shown up by
8        -Wmissing-field-initializers and -Wunused-parameter.
10    2.  The tests for quantifiers being too big (greater than 65535) were being
11        applied after reading the number, and stupidly assuming that integer
12        overflow would give a negative number. The tests are now applied as the
13        numbers are read.
15    3.  Tidy code in pcre_exec.c where two branches that used to be different are
16        now the same.
18    4.  The JIT compiler did not generate match limit checks for certain
19        bracketed expressions with quantifiers. This may lead to exponential
20        backtracking, instead of returning with PCRE_ERROR_MATCHLIMIT. This
21        issue should be resolved now.
23    5.  Fixed an issue, which occures when nested alternatives are optimized
24        with table jumps.
26    6.  Inserted two casts and changed some ints to size_t in the light of some
27        reported 64-bit compiler warnings (Bugzilla 1477).
29    7.  Fixed a bug concerned with zero-minimum possessive groups that could match
30        an empty string, which sometimes were behaving incorrectly in the
31        interpreter (though correctly in the JIT matcher). This pcretest input is
32        an example:
34          '\A(?:[^"]++|"(?:[^"]*+|"")*+")++'
37        the interpreter was reporting a match of 'NON QUOTED ' only, whereas the
38        JIT matcher and Perl both matched 'NON QUOTED "QUOT""ED" AFTER '. The test
39        for an empty string was breaking the inner loop and carrying on at a lower
40        level, when possessive repeated groups should always return to a higher
41        level as they have no backtrack points in them. The empty string test now
42        occurs at the outer level.
44    8.  Fixed a bug that was incorrectly auto-possessifying \w+ in the pattern
45        ^\w+(?>\s*)(?<=\w) which caused it not to match "test test".
47    9.  Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
48        doesn't).
50    10. Change 8.34/15 introduced a bug that caused the amount of memory needed
51        to hold a pattern to be incorrectly computed (too small) when there were
52        named back references to duplicated names. This could cause "internal
53        error: code overflow" or "double free or corruption" or other memory
54        handling errors.
56    11. When named subpatterns had the same prefixes, back references could be
57        confused. For example, in this pattern:
59          /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
61        the reference to 'Name' was incorrectly treated as a reference to a
62        duplicate name.
64    12. A pattern such as /^s?c/mi8 where the optional character has more than
65        one "other case" was incorrectly compiled such that it would only try to
66        match starting at "c".
68    13. When a pattern starting with \s was studied, VT was not included in the
69        list of possible starting characters; this should have been part of the
70        8.34/18 patch.
72    14. If a character class started [\Qx]... where x is any character, the class
73        was incorrectly terminated at the ].
75    15. If a pattern that started with a caseless match for a character with more
76        than one "other case" was studied, PCRE did not set up the starting code
77        unit bit map for the list of possible characters. Now it does. This is an
78        optimization improvement, not a bug fix.
80    16. The Unicode data tables have been updated to Unicode 7.0.0.
82    17. Fixed a number of memory leaks in pcregrep.
84    18. Avoid a compiler warning (from some compilers) for a function call with
85        a cast that removes "const" from an lvalue by using an intermediate
86        variable (to which the compiler does not object).
88    19. Incorrect code was compiled if a group that contained an internal recursive
89        back reference was optional (had quantifier with a minimum of zero). This
90        example compiled incorrect code: /(((a\2)|(a*)\g<-1>))*/ and other examples
91        caused segmentation faults because of stack overflows at compile time.
93    20. A pattern such as /((?(R)a|(?1)))+/, which contains a recursion within a
94        group that is quantified with an indefinite repeat, caused a compile-time
95        loop which used up all the system stack and provoked a segmentation fault.
96        This was not the same bug as 19 above.
98    21. Add PCRECPP_EXP_DECL declaration to operator<< in pcre_stringpiece.h.
99        Patch by Mike Frysinger.
102    Version 8.35 04-April-2014
103    --------------------------
105    1.  A new flag is set, when property checks are present in an XCLASS.
106        When this flag is not set, PCRE can perform certain optimizations
107        such as studying these XCLASS-es.
109    2.  The auto-possessification of character sets were improved: a normal
110        and an extended character set can be compared now. Furthermore
111        the JIT compiler optimizes more character set checks.
113    3.  Got rid of some compiler warnings for potentially uninitialized variables
114        that show up only when compiled with -O2.
116    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
117        of a match later then the end of the match. The pcretest program was not
118        handling the case sensibly - it was outputting from the start to the next
119        binary zero. It now reports this situation in a message, and outputs the
120        text from the end to the start.
122    5.  Fast forward search is improved in JIT. Instead of the first three
123        characters, any three characters with fixed position can be searched.
124        Search order: first, last, middle.
126    6.  Improve character range checks in JIT. Characters are read by an inprecise
127        function now, which returns with an unknown value if the character code is
128        above a certain threshold (e.g: 256). The only limitation is that the value
129        must be bigger than the threshold as well. This function is useful when
130        the characters above the threshold are handled in the same way.
132    7.  The macros whose names start with RAWUCHAR are placeholders for a future
133        mode in which only the bottom 21 bits of 32-bit data items are used. To
134        make this more memorable for those maintaining the code, the names have
135        been changed to start with UCHAR21, and an extensive comment has been added
136        to their definition.
138    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
139        to the export list in Makefile.am (they were accidentally omitted from the
140        8.34 tarball).
142    9.  The informational output from pcretest used the phrase "starting byte set"
143        which is inappropriate for the 16-bit and 32-bit libraries. As the output
144        for "first char" and "need char" really means "non-UTF-char", I've changed
145        "byte" to "char", and slightly reworded the output. The documentation about
146        these values has also been (I hope) clarified.
148    10. Another JIT related optimization: use table jumps for selecting the correct
149        backtracking path, when more than four alternatives are present inside a
150        bracket.
152    11. Empty match is not possible, when the minimum length is greater than zero,
153        and there is no \K in the pattern. JIT should avoid empty match checks in
154        such cases.
156    12. In a caseless character class with UCP support, when a character with more
157        than one alternative case was not the first character of a range, not all
158        the alternative cases were added to the class. For example, s and \x{17f}
159        are both alternative cases for S: the class [RST] was handled correctly,
160        but [R-T] was not.
162    13. The configure.ac file always checked for pthread support when JIT was
163        enabled. This is not used in Windows, so I have put this test inside a
164        check for the presence of windows.h (which was already tested for).
166    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
167        The algorithm provides a way to skip certain starting offsets, and usually
168        faster than linear prefix searches.
170    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
171        as for 'fr_FR' and 'french'. For some reason, however, it then used the
172        Windows-specific input and output files, which have 'french' screwed in.
173        So this could never have worked. One of the problems with locales is that
174        they aren't always the same. I have now updated RunTest so that it checks
175        the output of the locale test (test 3) against three different output
176        files, and it allows the test to pass if any one of them matches. With luck
177        this should make the test pass on some versions of Solaris where it was
178        failing. Because of the uncertainty, the script did not used to stop if
179        test 3 failed; it now does. If further versions of a French locale ever
180        come to light, they can now easily be added.
182    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
183        there was a message during ./configure, but it did not stop. This now
184        provokes an error. The invalid example in README has been corrected.
185        If a value less than the minimum is given, the minimum value has always
186        been used, but now a warning is given.
188    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
189        was a bug in the test system, which is now fixed. Also, the list of various
190        configurations that are tested for each release did not have one with both
191        16/32 bits and --enable-bar-anycrlf. It now does.
193    18. pcretest was missing "-C bsr" for displaying the \R default setting.
195    19. Little endian PowerPC systems are supported now by the JIT compiler.
197    20. The fast forward newline mechanism could enter to an infinite loop on
198        certain invalid UTF-8 input. Although we don't support these cases
199        this issue can be fixed by a performance optimization.
201    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
202        not take account if existing stack usage. There is now a new global
203        variable called pcre_stack_guard that can be set to point to an external
204        function to check stack availability. It is called at the start of
205        processing every parenthesized group.
207    22. A typo in the code meant that in ungreedy mode the max/min qualifier
208        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
209        not match "ab".
211    23. When UTF was disabled, the JIT program reported some incorrect compile
212        errors. These messages are silenced now.
214    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
215        compiler.
217    25. Change all the temporary files used in RunGrepTest to be different to those
218        used by RunTest so that the tests can be run simultaneously, for example by
219        "make -j check".
222    Version 8.34 15-December-2013
223    -----------------------------
225    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
226        executable memory. Patch inspired by Carsten Klein.
228    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
229        this macro is never tested and has no effect, because the work to support
230        coverage involves only compiling and linking options and special targets in
231        the Makefile. The comment in config.h implied that defining the macro would
232        enable coverage support, which is totally false. There was also support for
233        setting this macro in the CMake files (my fault, I just copied it from
234        configure). SUPPORT_GCOV has now been removed.
236    3.  Make a small performance improvement in strlen16() and strlen32() in
237        pcretest.
239    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
240        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
241        these cases). There was also one in pcretest.c.
243    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
245    6.  In UTF mode, the code for checking whether a group could match an empty
246        string (which is used for indefinitely repeated groups to allow for
247        breaking an infinite loop) was broken when the group contained a repeated
248        negated single-character class with a character that occupied more than one
249        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
250        UTF-8 mode). The effect was undefined: the group might or might not be
251        deemed as matching an empty string, or the program might have crashed.
253    7.  The code for checking whether a group could match an empty string was not
254        recognizing that \h, \H, \v, \V, and \R must match a character.
256    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
257        an empty string. If it can, pcretest shows this in its information output.
259    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
260        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
261        matched by pcre_exec() without using JIT:
263        (a) If the rest of the pattern did not match after a maximal run of
264            grapheme clusters, the code for backing up to try with fewer of them
265            did not always back up over a full grapheme when characters that do not
266            have the modifier quality were involved, e.g. Hangul syllables.
268        (b) If the match point in a subject started with modifier character, and
269            there was no match, the code could incorrectly back up beyond the match
270            point, and potentially beyond the first character in the subject,
271            leading to a segfault or an incorrect match result.
273    10. A conditional group with an assertion condition could lead to PCRE
274        recording an incorrect first data item for a match if no other first data
275        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
276        first data item, and therefore matched "ca" after "c" instead of at the
277        start.
279    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
280        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
282    12. The source of pcregrep now includes z/OS-specific code so that it can be
283        compiled for z/OS as part of the special z/OS distribution.
285    13. Added the -T and -TM options to pcretest.
287    14. The code in pcre_compile.c for creating the table of named capturing groups
288        has been refactored. Instead of creating the table dynamically during the
289        actual compiling pass, the information is remembered during the pre-compile
290        pass (on the stack unless there are more than 20 named groups, in which
291        case malloc() is used) and the whole table is created before the actual
292        compile happens. This has simplified the code (it is now nearly 150 lines
293        shorter) and prepared the way for better handling of references to groups
294        with duplicate names.
296    15. A back reference to a named subpattern when there is more than one of the
297        same name now checks them in the order in which they appear in the pattern.
298        The first one that is set is used for the reference. Previously only the
299        first one was inspected. This change makes PCRE more compatible with Perl.
301    16. Unicode character properties were updated from Unicode 6.3.0.
303    17. The compile-time code for auto-possessification has been refactored, based
304        on a patch by Zoltan Herczeg. It now happens after instead of during
305        compilation. The code is cleaner, and more cases are handled. The option
306        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
307        options in pcretest are provided to set it. It can also be set by
308        (*NO_AUTO_POSSESS) at the start of a pattern.
310    18. The character VT has been added to the default ("C" locale) set of
311        characters that match \s and are generally treated as white space,
312        following this same change in Perl 5.18. There is now no difference between
313        "Perl space" and "POSIX space". Whether VT is treated as white space in
314        other locales depends on the locale.
316    19. The code for checking named groups as conditions, either for being set or
317        for being recursed, has been refactored (this is related to 14 and 15
318        above). Processing unduplicated named groups should now be as fast at
319        numerical groups, and processing duplicated groups should be faster than
320        before.
322    20. Two patches to the CMake build system, by Alexander Barkov:
324          (1) Replace the "source" command by "." in CMakeLists.txt because
325              "source" is a bash-ism.
327          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
328              without these the CMake build does not work on Solaris.
330    21. Perl has changed its handling of \8 and \9. If there is no previously
331        encountered capturing group of those numbers, they are treated as the
332        literal characters 8 and 9 instead of a binary zero followed by the
333        literals. PCRE now does the same.
335    22. Following Perl, added \o{} to specify codepoints in octal, making it
336        possible to specify values greater than 0777 and also making them
337        unambiguous.
339    23. Perl now gives an error for missing closing braces after \x{... instead of
340        treating the string as literal. PCRE now does the same.
342    24. RunTest used to grumble if an inappropriate test was selected explicitly,
343        but just skip it when running all tests. This make it awkward to run ranges
344        of tests when one of them was inappropriate. Now it just skips any
345        inappropriate tests, as it always did when running all tests.
347    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
348        character types such as \d or \w, too many callouts were inserted, and the
349        data that they returned was rubbish.
351    26. In UCP mode, \s was not matching two of the characters that Perl matches,
352        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
353        were matched by \h. The code has now been refactored so that the lists of
354        the horizontal and vertical whitespace characters used for \h and \v (which
355        are defined only in one place) are now also used for \s.
357    27. Add JIT support for the 64 bit TileGX architecture.
358        Patch by Jiong Wang (Tilera Corporation).
360    28. Possessive quantifiers for classes (both explicit and automatically
361        generated) now use special opcodes instead of wrapping in ONCE brackets.
363    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
364        (because it's meaningless), this was not happening when PCRE_CASELESS was
365        set. Not wrong, but inefficient.
367    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
368        properties for \w, \d, etc) is present in a test regex. Otherwise if the
369        test contains no characters greater than 255, Perl doesn't realise it
370        should be using Unicode semantics.
372    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
373        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
374        does in Unicode mode.
376    32. Added the "forbid" facility to pcretest so that putting tests into the
377        wrong test files can sometimes be quickly detected.
379    33. There is now a limit (default 250) on the depth of nesting of parentheses.
380        This limit is imposed to control the amount of system stack used at compile
381        time. It can be changed at build time by --with-parens-nest-limit=xxx or
382        the equivalent in CMake.
384    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
385        errors. Perl warns for these when in warning mode, but PCRE has no facility
386        for giving warnings.
388    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
389        However, this was not working for (?!) because it is optimized to (*FAIL),
390        for which PCRE does not allow quantifiers. The optimization is now disabled
391        when a quantifier follows (?!). I can't see any use for this, but it makes
392        things uniform.
394    36. Perl no longer allows group names to start with digits, so I have made this
395        change also in PCRE. It simplifies the code a bit.
397    37. In extended mode, Perl ignores spaces before a + that indicates a
398        possessive quantifier. PCRE allowed a space before the quantifier, but not
399        before the possessive +. It now does.
401    38. The use of \K (reset reported match start) within a repeated possessive
402        group such as (a\Kb)*+ was not working.
404    40. Document that the same character tables must be used at compile time and
405        run time, and that the facility to pass tables to pcre_exec() and
406        pcre_dfa_exec() is for use only with saved/restored patterns.
408    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
409        features for Builds with MSVC:
411        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
412           builds). The .rc files can be used to set FileDescription and many other
413           attributes.
415        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
416           This allows higher-level build scripts which want .pdb files to avoid
417           hard-coding the exact files needed."
419    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
420        mean "start of word" and "end of word", respectively, as a transition aid.
422    43. A minimizing repeat of a class containing codepoints greater than 255 in
423        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
424        compiled to use the heap for recursion.
426    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
427        is configured.
430    Version 8.33 28-May-2013
431    ------------------------
433    1.  Added 'U' to some constants that are compared to unsigned integers, to
434        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
435        variables that are added to signed variables, to ensure the result is
436        signed and can be negated.
438    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
439        CMake config files.
441    3.  Revise the creation of config.h.generic so that all boolean macros are
442        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
443        overriding via -D on the command line possible.
445    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
446        to unsigned int is reported to make a quite noticeable speed difference in
447        a specific Windows environment. Testing on Linux did also appear to show
448        some benefit (and it is clearly not harmful). Also fixed the definition of
449        Xop which should be unsigned.
451    5.  Related to (4), changing the definition of the intermediate variable cc
452        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
453        improvements.
455    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
456        unnecessary spaces.
458    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
459        and later.
461    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
463    9.  Optimizing fast_forward_start_bits in JIT.
465    10. Adding support for callouts in JIT, and fixing some issues revealed
466        during this work. Namely:
468        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
470        (b) Minimum length was not checked before the matching is started.
472    11. The value of capture_last that is passed to callouts was incorrect in some
473        cases when there was a capture on one path that was subsequently abandoned
474        after a backtrack. Also, the capture_last value is now reset after a
475        recursion, since all captures are also reset in this case.
477    12. The interpreter no longer returns the "too many substrings" error in the
478        case when an overflowing capture is in a branch that is subsequently
479        abandoned after a backtrack.
481    13. In the pathological case when an offset vector of size 2 is used, pcretest
482        now prints out the matched string after a yield of 0 or 1.
484    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
485        Only supported by the JIT compiler at the moment.
487    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
489    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
490        offset of the starting point of the matching process, provided the offsets
491        vector is large enough.
493    17. The \A escape now records a lookbehind value of 1, though its execution
494        does not actually inspect the previous character. This is to ensure that,
495        in partial multi-segment matching, at least one character from the old
496        segment is retained when a new segment is processed. Otherwise, if there
497        are no lookbehinds in the pattern, \A might match incorrectly at the start
498        of a new segment.
500    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
502    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
503        gives some modest performance improvement in 8-bit mode.
505    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
506        be expressed in certain programming languages using Universal Character
507        Names.
509    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
510        which points out that "non characters" are not "characters that may not
511        appear in Unicode strings" but rather "characters that are reserved for
512        internal use and have only local meaning".
514    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
515        there was a conditional group that depended on an assertion, if the
516        assertion was false, the callout that immediately followed the alternation
517        in the condition was skipped when pcre_exec() was used for matching.
519    23. Allow an explicit callout to be inserted before an assertion that is the
520        condition for a conditional group, for compatibility with automatic
521        callouts, which always insert a callout at this point.
523    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
524        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
526    25. (*PRUNE) is now supported by the JIT compiler.
528    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
530    27. Fix the case where there are two or more SKIPs with arguments that may be
531        ignored.
533    28. (*SKIP) is now supported by the JIT compiler.
535    29. (*THEN) is now supported by the JIT compiler.
537    30. Update RunTest with additional test selector options.
539    31. The way PCRE handles backtracking verbs has been changed in two ways.
541        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
542        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
543        backtracking. In some cases this makes it more Perl-compatible, but Perl's
544        rather obscure rules do not always do the same thing.
546        (2) Previously, backtracking verbs were confined within assertions. This is
547        no longer the case for positive assertions, except for (*ACCEPT). Again,
548        this sometimes improves Perl compatibility, and sometimes does not.
550    32. A number of tests that were in test 2 because Perl did things differently
551        have been moved to test 1, because either Perl or PCRE has changed, and
552        these tests are now compatible.
554    32. Backtracking control verbs are now handled in the same way in JIT and
555        interpreter.
557    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
558        contained a forward subroutine reference caused a compile error.
560    34. Auto-detect and optimize limited repetitions in JIT.
562    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
563        blocking (*UTF) etc.
565    36. In the interpreter, maximizing pattern repetitions for characters and
566        character types now use tail recursion, which reduces stack usage.
568    37. The value of the max lookbehind was not correctly preserved if a compiled
569        and saved regex was reloaded on a host of different endianness.
571    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
572        of the compiled pattern block, expand the flags field from 16 to 32 bits
573        because it was almost full.
575    39. Try madvise first before posix_madvise.
577    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
578        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
579        original change locked out all matches of empty strings. This has been
580        changed so that one match of an empty string per line is recognized.
581        Subsequent searches on the same line (for colouring or for --only-matching,
582        for example) do not recognize empty strings.
584    41. Applied a user patch to fix a number of spelling mistakes in comments.
586    42. Data lines longer than 65536 caused pcretest to crash.
588    43. Clarified the data type for length and startoffset arguments for pcre_exec
589        and pcre_dfa_exec in the function-specific man pages, where they were
590        explicitly stated to be in bytes, never having been updated. I also added
591        some clarification to the pcreapi man page.
593    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
594        a segmentation fault.
597    Version 8.32 30-November-2012
598    -----------------------------
600    1.  Improved JIT compiler optimizations for first character search and single
601        character iterators.
603    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
604        Patch by Daniel Richard G.
606    3.  Single character iterator optimizations in the JIT compiler.
608    4.  Improved JIT compiler optimizations for character ranges.
610    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
611        Reported by Giuseppe D'Angelo.
613    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
614        of a line, was being set incorrectly in cases where .* appeared inside
615        atomic brackets at the start of a pattern, or where there was a subsequent
616        *PRUNE or *SKIP.
618    7.  Improved instruction cache flush for POWER/PowerPC.
619        Patch by Daniel Richard G.
621    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
622        grep:
624        (a) There is now no limit to the number of patterns to be matched.
626        (b) An error is given if a pattern is too long.
628        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
629            are now supported.
631        (d) --exclude-from and --include-from (multiple use) have been added.
633        (e) Exclusions and inclusions now apply to all files and directories, not
634            just to those obtained from scanning a directory recursively.
636        (f) Multiple uses of -f and --file-list are now supported.
638        (g) In a Windows environment, the default for -d has been changed from
639            "read" (the GNU grep default) to "skip", because otherwise the presence
640            of a directory in the file list provokes an error.
642        (h) The documentation has been revised and clarified in places.
644    9.  Improve the matching speed of capturing brackets.
646    10. Changed the meaning of \X so that it now matches a Unicode extended
647        grapheme cluster.
649    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
650        out POSIX threads when JIT support is configured.
652    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
654    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
655        structure could go wrong in environments where size_t is not the same size
656        as int.
658    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
659        set.
661    15. The EBCDIC support had decayed; later updates to the code had included
662        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
663        general tidy up of EBCDIC-related issues, and the documentation was also
664        not quite right. There is now a test that can be run on ASCII systems to
665        check some of the EBCDIC-related things (but is it not a full test).
667    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
668        in a small tidy to the code.
670    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
672    18. If the --only-matching (-o) option in pcregrep is specified multiple
673        times, each one causes appropriate output. For example, -o1 -o2 outputs the
674        substrings matched by the 1st and 2nd capturing parentheses. A separating
675        string can be specified by --om-separator (default empty).
677    19. Improving the first n character searches.
679    20. Turn case lists for horizontal and vertical white space into macros so that
680        they are defined only once.
682    21. This set of changes together give more compatible Unicode case-folding
683        behaviour for characters that have more than one other case when UCP
684        support is available.
686        (a) The Unicode property table now has offsets into a new table of sets of
687            three or more characters that are case-equivalent. The MultiStage2.py
688            script that generates these tables (the pcre_ucd.c file) now scans
689            CaseFolding.txt instead of UnicodeData.txt for character case
690            information.
692        (b) The code for adding characters or ranges of characters to a character
693            class has been abstracted into a generalized function that also handles
694            case-independence. In UTF-mode with UCP support, this uses the new data
695            to handle characters with more than one other case.
697        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
698            whose other case is greater than 256 are now correctly matched
699            caselessly. Previously, the high codepoint matched the low one, but not
700            vice versa.
702        (d) The processing of \h, \H, \v, and \ in character classes now makes use
703            of the new class addition function, using character lists defined as
704            macros alongside the case definitions of 20 above.
706        (e) Caseless back references now work with characters that have more than
707            one other case.
709        (f) General caseless matching of characters with more than one other case
710            is supported.
712    22. Unicode character properties were updated from Unicode 6.2.0
714    23. Improved CMake support under Windows. Patch by Daniel Richard G.
716    24. Add support for 32-bit character strings, and UTF-32
718    25. Major JIT compiler update (code refactoring and bugfixing).
719        Experimental Sparc 32 support is added.
721    26. Applied a modified version of Daniel Richard G's patch to create
722        pcre.h.generic and config.h.generic by "make" instead of in the
723        PrepareRelease script.
725    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
726        pcre_compile.c when checking for a zero character.
728    28. Introducing a native interface for JIT. Through this interface, the compiled
729        machine code can be directly executed. The purpose of this interface is to
730        provide fast pattern matching, so several sanity checks are not performed.
731        However, feature tests are still performed. The new interface provides
732        1.4x speedup compared to the old one.
734    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
735        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
736        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
738    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
739        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
740        the "old" RFC 2279). Instead, it ended up passing a negative length to
741        pcre_exec().
743    31. Add support for GCC's visibility feature to hide internal functions.
745    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
746        "unknown -C option" after outputting 0 or 1.
748    33. There is now support for generating a code coverage report for the test
749        suite in environments where gcc is the compiler and lcov is installed. This
750        is mainly for the benefit of the developers.
752    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
753        unaddressable using valgrind annotations, allowing valgrind to detect
754        invalid memory accesses. This is mainly for the benefit of the developers.
756    25. (*UTF) can now be used to start a pattern in any of the three libraries.
758    26. Give configure error if --enable-cpp but no C++ compiler found.
761    Version 8.31 06-July-2012
762    -------------------------
764    1.  Fixing a wrong JIT test case and some compiler warnings.
766    2.  Removed a bashism from the RunTest script.
768    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
769        to unsigned type, result still unsigned" that was given by an MS compiler
770        on encountering the code "-sizeof(xxx)".
772    4.  Partial matching support is added to the JIT compiler.
774    5.  Fixed several bugs concerned with partial matching of items that consist
775        of more than one character:
777        (a) /^(..)\1/ did not partially match "aba" because checking references was
778            done on an "all or nothing" basis. This also applied to repeated
779            references.
781        (b) \R did not give a hard partial match if \r was found at the end of the
782            subject.
784        (c) \X did not give a hard partial match after matching one or more
785            characters at the end of the subject.
787        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
788            a partial match for the string "\r".
790        (e) When newline was set to CRLF, the metacharacter "." did not recognize
791            a partial match for a CR character at the end of the subject string.
793    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
794        running pcretest, the text "(JIT)" added to the output whenever JIT is
795        actually used to run the match.
797    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
798        or /S+[+] with a digit between 1 and 7.
800    8.  OP_NOT now supports any UTF character not just single-byte ones.
802    9.  (*MARK) control verb is now supported by the JIT compiler.
804    10. The command "./RunTest list" lists the available tests without actually
805        running any of them. (Because I keep forgetting what they all are.)
809    12. Applied a (slightly modified) user-supplied patch that improves performance
810        when the heap is used for recursion (compiled with --disable-stack-for-
811        recursion). Instead of malloc and free for each heap frame each time a
812        logical recursion happens, frames are retained on a chain and re-used where
813        possible. This sometimes gives as much as 30% improvement.
815    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
816        call.
818    14. As documented, (*COMMIT) is now confined to within a positive assertion.
820    15. It is now possible to link pcretest with libedit as an alternative to
821        libreadline.
823    16. (*COMMIT) control verb is now supported by the JIT compiler.
825    17. The Unicode data tables have been updated to Unicode 6.1.0.
827    18. Added --file-list option to pcregrep.
829    19. Added binary file support to pcregrep, including the -a, --binary-files,
830        -I, and --text options.
832    20. The madvise function is renamed for posix_madvise for QNX compatibility
833        reasons. Fixed by Giuseppe D'Angelo.
835    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
837    22. Changed the option for creating symbolic links for 16-bit man pages from
838        -s to -sf so that re-installing does not cause issues.
840    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
842    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
843        matches in certain environments (the workspace was not being correctly
844        retained). Also added to pcre_dfa_exec() a simple plausibility check on
845        some of the workspace data at the beginning of a restart.
847    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
848        was not doing so when it should - probably a typo introduced by SVN 528
849        (change 8.10/14).
851    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
852        \w+ when the character tables indicated that \x{c4} was a word character.
853        There were several related cases, all because the tests for doing a table
854        lookup were testing for characters less than 127 instead of 255.
856    27. If a pattern contains capturing parentheses that are not used in a match,
857        their slots in the ovector are set to -1. For those that are higher than
858        any matched groups, this happens at the end of processing. In the case when
859        there were back references that the ovector was too small to contain
860        (causing temporary malloc'd memory to be used during matching), and the
861        highest capturing number was not used, memory off the end of the ovector
862        was incorrectly being set to -1. (It was using the size of the temporary
863        memory instead of the true size.)
865    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
866        ovector size, it uses memory at the end of the block that it has got.
868    29. Check for an overlong MARK name and give an error at compile time. The
869        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
871    30. JIT compiler update.
873    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
874        Rill for the patch.
876    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
878    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
880    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
881        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
882        was enabled.
884    35. Improve JIT code generation for greedy plus quantifier.
886    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
887        1 to "aa" instead of to an empty string. The bug affected repeated groups
888        that could potentially match an empty string.
890    37. Optimizing single character iterators in JIT.
892    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
893        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
894        codepoints that are too big for the mode are faulted, and in a UTF mode,
895        disallowed codepoints are also faulted.
897    39. If PCRE was compiled with UTF support, in three places in the DFA
898        matcher there was code that should only have been obeyed in UTF mode, but
899        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
900        processing when bytes with values greater than 127 were present. In 16-bit
901        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
902        both cases the values are those that cannot be the first data item in a UTF
903        character. The three items that might have provoked this were recursions,
904        possessively repeated groups, and atomic groups.
906    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
907        and pcregrep, because some OS require shared objects to be explicitly
908        passed to ld, causing the link step to fail if they are not.
910    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
911        mode, patterns that started with \h* or \R* might be incorrectly matched.
914    Version 8.30 04-February-2012
915    -----------------------------
917    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
918        name is defined in ctype.h.
920    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
921        only in quite long subpatterns.
923    3.  Removed the function pcre_info(), which has been obsolete and deprecated
924        since it was replaced by pcre_fullinfo() in February 2000.
926    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
927        match a (*MARK), and the match failed at the start of the subject, a
928        reference to memory before the start of the subject could occur. This bug
929        was introduced by fix 17 of release 8.21.
931    5.  A reference to an unset group with zero minimum repetition was giving
932        totally wrong answers (in non-JavaScript-compatibility mode). For example,
933        /(another)?(\1?)test/ matched against "hello world test". This bug was
934        introduced in release 8.13.
936    6.  Add support for 16-bit character strings (a large amount of work involving
937        many changes and refactorings).
939    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
940        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
941        from a file.
943    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
944        rounding is not applied in this particular case).
946    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
947        if they appear, or are escaped, in patterns.
949    10. Get rid of a number of -Wunused-but-set-variable warnings.
951    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
952        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
953        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
954        also returns the mark "x". This bug applied to capturing parentheses,
955        non-capturing parentheses, and atomic parentheses. It also applied to some
956        assertions.
958    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
959        information out of configure.ac instead of relying on pcre.h.generic, which
960        is not stored in the repository.
962    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
963        -lreadline.
965    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
967    15. Applied Graycode's patch to put the top-level frame on the stack rather
968        than the heap when not using the stack for recursion. This gives a
969        performance improvement in many cases when recursion is not deep.
971    16. Experimental code added to "pcretest -C" to output the stack frame size.
974    Version 8.21 12-Dec-2011
975    ------------------------
977    1.  Updating the JIT compiler.
979    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
980        are added as well.
982    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
983        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
984        calling _pcre_jit_exec. Some extra comments are added.
986    4.  (*MARK) settings inside atomic groups that do not contain any capturing
987        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
988        was introduced by change 18 for 8.20.
990    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
991        ECMA-262 standard.
993    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
994        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
995        This bug was probably introduced by change 9 of 8.13.
997    7.  While fixing 6 above, I noticed that a number of other items were being
998        incorrectly rejected as "not fixed length". This arose partly because newer
999        opcodes had not been added to the fixed-length checking code. I have (a)
1000        corrected the bug and added tests for these items, and (b) arranged for an
1001        error to occur if an unknown opcode is encountered while checking for fixed
1002        length instead of just assuming "not fixed length". The items that were
1003        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
1004        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
1005        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
1007    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
1008        being incorrectly compiled and would have given unpredicatble results.
1010    9.  A possessively repeated subpattern with minimum repeat count greater than
1011        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
1012        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
1013        the first (A) could occur when it should not.
1015    10. Add a cast and remove a redundant test from the code.
1017    11. JIT should use pcre_malloc/pcre_free for allocation.
1019    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
1020        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
1021        is anything other than /usr, -L is still shown).
1023    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
1025    14. Perl does not support \N without a following name in a [] class; PCRE now
1026        also gives an error.
1028    15. If a forward reference was repeated with an upper limit of around 2000,
1029        it caused the error "internal error: overran compiling workspace". The
1030        maximum number of forward references (including repeats) was limited by the
1031        internal workspace, and dependent on the LINK_SIZE. The code has been
1032        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
1033        the default depends on LINK_SIZE. There is a new upper limit (for safety)
1034        of around 200,000 forward references. While doing this, I also speeded up
1035        the filling in of repeated forward references.
1037    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
1038        incorrectly expecting the subject to contain another "a" after the start.
1040    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
1041        in the match, the SKIP should be ignored. This was not happening; instead
1042        the SKIP was being treated as NOMATCH. For patterns such as
1043        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
1044        tested.
1046    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
1047        now much more compatible with Perl, in particular in cases where the result
1048        is a non-match for a non-anchored pattern. For example, if
1049        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
1050        "m", where previously it did not return a name. A side effect of this
1051        change is that for partial matches, the last encountered mark name is
1052        returned, as for non matches. A number of tests that were previously not
1053        Perl-compatible have been moved into the Perl-compatible test files. The
1054        refactoring has had the pleasing side effect of removing one argument from
1055        the match() function, thus reducing its stack requirements.
1057    19. If the /S+ option was used in pcretest to study a pattern using JIT,
1058        subsequent uses of /S (without +) incorrectly behaved like /S+.
1060    21. Retrieve executable code size support for the JIT compiler and fixing
1061        some warnings.
1063    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
1064        not work when the shorter character appeared right at the end of the
1065        subject string.
1067    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
1068        systems.
1070    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
1071        output it when the /M option is used in pcretest.
1073    25. The CheckMan script was not being included in the distribution. Also, added
1074        an explicit "perl" to run Perl scripts from the PrepareRelease script
1075        because this is reportedly needed in Windows.
1077    26. If study data was being save in a file and studying had not found a set of
1078        "starts with" bytes for the pattern, the data written to the file (though
1079        never used) was taken from uninitialized memory and so caused valgrind to
1080        complain.
1082    27. Updated RunTest.bat as provided by Sheri Pierce.
1084    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
1086    29. Computation of memory usage for the table of capturing group names was
1087        giving an unnecessarily large value.
1090    Version 8.20 21-Oct-2011
1091    ------------------------
1093    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
1094        a POSIX class. After further experiments with Perl, which convinced me that
1095        Perl has bugs and confusions, a closing square bracket is no longer allowed
1096        in a POSIX name. This bug also affected patterns with classes that started
1097        with full stops.
1099    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
1100        captured substring, but while checking the failing first alternative,
1101        substring 1 is temporarily captured. If the output vector supplied to
1102        pcre_exec() was not big enough for this capture, the yield of the function
1103        was still zero ("insufficient space for captured substrings"). This cannot
1104        be totally fixed without adding another stack variable, which seems a lot
1105        of expense for a edge case. However, I have improved the situation in cases
1106        such as /(a)(b)x|abc/ matched against "abc", where the return code
1107        indicates that fewer than the maximum number of slots in the ovector have
1108        been set.
1110    3.  Related to (2) above: when there are more back references in a pattern than
1111        slots in the output vector, pcre_exec() uses temporary memory during
1112        matching, and copies in the captures as far as possible afterwards. It was
1113        using the entire output vector, but this conflicts with the specification
1114        that only 2/3 is used for passing back captured substrings. Now it uses
1115        only the first 2/3, for compatibility. This is, of course, another edge
1116        case.
1118    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
1119        main code base, and can be used by building with --enable-jit. When this is
1120        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
1121        runtime --no-jit option is given.
1123    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
1124        ovector, the return from the function was zero, implying that there were
1125        other matches that did not fit. The correct "exactly full" value is now
1126        returned.
1128    6.  If a subpattern that was called recursively or as a subroutine contained
1129        (*PRUNE) or any other control that caused it to give a non-standard return,
1130        invalid errors such as "Error -26 (nested recursion at the same subject
1131        position)" or even infinite loops could occur.
1133    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
1134        computing the minimum length on reaching *ACCEPT, and so ended up with the
1135        wrong value of 1 rather than 0. Further investigation indicates that
1136        computing a minimum subject length in the presence of *ACCEPT is difficult
1137        (think back references, subroutine calls), and so I have changed the code
1138        so that no minimum is registered for a pattern that contains *ACCEPT.
1140    8.  If (*THEN) was present in the first (true) branch of a conditional group,
1141        it was not handled as intended. [But see 16 below.]
1143    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
1144        Sheri Pierce.
1146    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
1147        the first byte in a match must be "a".
1149    11. Change 17 for 8.13 increased the recursion depth for patterns like
1150        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
1151        pattern contains any instances of (*THEN). If it does not, the old
1152        optimizations are restored. It would be nice to do this on a per-group
1153        basis, but at the moment that is not feasible.
1155    12. In some environments, the output of pcretest -C is CRLF terminated. This
1156        broke RunTest's code that checks for the link size. A single white space
1157        character after the value is now allowed for.
1159    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
1160        For "fr", it uses the Windows-specific input and output files.
1162    14. If (*THEN) appeared in a group that was called recursively or as a
1163        subroutine, it did not work as intended. [But see next item.]
1165    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
1166        pattern fragments (but not containing any | characters). If A and B are
1167        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
1168        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
1169        D. In other words, Perl considers parentheses that do not contain any |
1170        characters to be part of a surrounding alternative, whereas PCRE was
1171        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
1172        differently. PCRE now behaves in the same way as Perl, except in the case
1173        of subroutine/recursion calls such as (?1) which have in any case always
1174        been different (but PCRE had them first :-).
1176    16. Related to 15 above: Perl does not treat the | in a conditional group as
1177        creating alternatives. Such a group is treated in the same way as an
1178        ordinary group without any | characters when processing (*THEN). PCRE has
1179        been changed to match Perl's behaviour.
1181    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
1182        RunGrepTest script failed.
1184    18. Change 22 for version 13 caused atomic groups to use more stack. This is
1185        inevitable for groups that contain captures, but it can lead to a lot of
1186        stack use in large patterns. The old behaviour has been restored for atomic
1187        groups that do not contain any capturing parentheses.
1189    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
1190        suppress the check for a minimum subject length at run time. (If it was
1191        given to pcre_exec() or pcre_dfa_exec() it did work.)
1193    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
1194        fail to work when decoding hex characters in data strings in EBCDIC
1195        environments.
1197    21. It appears that in at least one Mac OS environment, the isxdigit() function
1198        is implemented as a macro that evaluates to its argument more than once,
1199        contravening the C 90 Standard (I haven't checked a later standard). There
1200        was an instance in pcretest which caused it to go wrong when processing
1201        \x{...} escapes in subject strings. The has been rewritten to avoid using
1202        things like p++ in the argument of isxdigit().
1205    Version 8.13 16-Aug-2011
1206  ------------------------  ------------------------
1208  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 1299  Version 8.13 02-Aug-2011
1299      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
1300      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
1301      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
1302      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
1304  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
1305      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 1390  Version 8.13 02-Aug-2011
1390      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1391      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
1392      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1393      more like Perl.      more like Perl. (But see 8.20/1 above.)
1395  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
1396      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 1425  Version 8.13 02-Aug-2011
1425      (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
1426          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
1428      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1429          PCRE is built.          PCRE is built.
1431      (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 1446  Version 8.13 02-Aug-2011
1446  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
1447      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
1448      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
1450  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
1451      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
1454  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
# Line 900  Version 7.9 11-Apr-09 Line 2101  Version 7.9 11-Apr-09
2101  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
2102      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
2103      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2104      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
2105        8.33.]
2107  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
2108      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 2345  Version 7.7 07-May-08
2345      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2346      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2347      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2348      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2349      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2350      was subsequently set up correctly.)      was subsequently set up correctly.)

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

  ViewVC Help
Powered by ViewVC 1.1.5