ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 167 by ph10, Wed May 9 15:53:54 2007 UTC revision 1494 by ph10, Thu Jul 10 16:38:05 2014 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.2 01-May-07  Version 8.36 xx-xxx-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).
89    Version 8.35 04-April-2014
90    --------------------------
92    1.  A new flag is set, when property checks are present in an XCLASS.
93        When this flag is not set, PCRE can perform certain optimizations
94        such as studying these XCLASS-es.
96    2.  The auto-possessification of character sets were improved: a normal
97        and an extended character set can be compared now. Furthermore
98        the JIT compiler optimizes more character set checks.
100    3.  Got rid of some compiler warnings for potentially uninitialized variables
101        that show up only when compiled with -O2.
103    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
104        of a match later then the end of the match. The pcretest program was not
105        handling the case sensibly - it was outputting from the start to the next
106        binary zero. It now reports this situation in a message, and outputs the
107        text from the end to the start.
109    5.  Fast forward search is improved in JIT. Instead of the first three
110        characters, any three characters with fixed position can be searched.
111        Search order: first, last, middle.
113    6.  Improve character range checks in JIT. Characters are read by an inprecise
114        function now, which returns with an unknown value if the character code is
115        above a certain treshold (e.g: 256). The only limitation is that the value
116        must be bigger than the treshold as well. This function is useful, when
117        the characters above the treshold are handled in the same way.
119    7.  The macros whose names start with RAWUCHAR are placeholders for a future
120        mode in which only the bottom 21 bits of 32-bit data items are used. To
121        make this more memorable for those maintaining the code, the names have
122        been changed to start with UCHAR21, and an extensive comment has been added
123        to their definition.
125    8.  Add missing (new) files sljitNativeTILEGX.c and sljitNativeTILEGX-encoder.c
126        to the export list in Makefile.am (they were accidentally omitted from the
127        8.34 tarball).
129    9.  The informational output from pcretest used the phrase "starting byte set"
130        which is inappropriate for the 16-bit and 32-bit libraries. As the output
131        for "first char" and "need char" really means "non-UTF-char", I've changed
132        "byte" to "char", and slightly reworded the output. The documentation about
133        these values has also been (I hope) clarified.
135    10. Another JIT related optimization: use table jumps for selecting the correct
136        backtracking path, when more than four alternatives are present inside a
137        bracket.
139    11. Empty match is not possible, when the minimum length is greater than zero,
140        and there is no \K in the pattern. JIT should avoid empty match checks in
141        such cases.
143    12. In a caseless character class with UCP support, when a character with more
144        than one alternative case was not the first character of a range, not all
145        the alternative cases were added to the class. For example, s and \x{17f}
146        are both alternative cases for S: the class [RST] was handled correctly,
147        but [R-T] was not.
149    13. The configure.ac file always checked for pthread support when JIT was
150        enabled. This is not used in Windows, so I have put this test inside a
151        check for the presence of windows.h (which was already tested for).
153    14. Improve pattern prefix search by a simplified Boyer-Moore algorithm in JIT.
154        The algorithm provides a way to skip certain starting offsets, and usually
155        faster than linear prefix searches.
157    15. Change 13 for 8.20 updated RunTest to check for the 'fr' locale as well
158        as for 'fr_FR' and 'french'. For some reason, however, it then used the
159        Windows-specific input and output files, which have 'french' screwed in.
160        So this could never have worked. One of the problems with locales is that
161        they aren't always the same. I have now updated RunTest so that it checks
162        the output of the locale test (test 3) against three different output
163        files, and it allows the test to pass if any one of them matches. With luck
164        this should make the test pass on some versions of Solaris where it was
165        failing. Because of the uncertainty, the script did not used to stop if
166        test 3 failed; it now does. If further versions of a French locale ever
167        come to light, they can now easily be added.
169    16. If --with-pcregrep-bufsize was given a non-integer value such as "50K",
170        there was a message during ./configure, but it did not stop. This now
171        provokes an error. The invalid example in README has been corrected.
172        If a value less than the minimum is given, the minimum value has always
173        been used, but now a warning is given.
175    17. If --enable-bsr-anycrlf was set, the special 16/32-bit test failed. This
176        was a bug in the test system, which is now fixed. Also, the list of various
177        configurations that are tested for each release did not have one with both
178        16/32 bits and --enable-bar-anycrlf. It now does.
180    18. pcretest was missing "-C bsr" for displaying the \R default setting.
182    19. Little endian PowerPC systems are supported now by the JIT compiler.
184    20. The fast forward newline mechanism could enter to an infinite loop on
185        certain invalid UTF-8 input. Although we don't support these cases
186        this issue can be fixed by a performance optimization.
188    21. Change 33 of 8.34 is not sufficient to ensure stack safety because it does
189        not take account if existing stack usage. There is now a new global
190        variable called pcre_stack_guard that can be set to point to an external
191        function to check stack availability. It is called at the start of
192        processing every parenthesized group.
194    22. A typo in the code meant that in ungreedy mode the max/min qualifier
195        behaved like a min-possessive qualifier, and, for example, /a{1,3}b/U did
196        not match "ab".
198    23. When UTF was disabled, the JIT program reported some incorrect compile
199        errors. These messages are silenced now.
201    24. Experimental support for ARM-64 and MIPS-64 has been added to the JIT
202        compiler.
204    25. Change all the temporary files used in RunGrepTest to be different to those
205        used by RunTest so that the tests can be run simultaneously, for example by
206        "make -j check".
209    Version 8.34 15-December-2013
210    -----------------------------
212    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
213        executable memory. Patch inspired by Carsten Klein.
215    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
216        this macro is never tested and has no effect, because the work to support
217        coverage involves only compiling and linking options and special targets in
218        the Makefile. The comment in config.h implied that defining the macro would
219        enable coverage support, which is totally false. There was also support for
220        setting this macro in the CMake files (my fault, I just copied it from
221        configure). SUPPORT_GCOV has now been removed.
223    3.  Make a small performance improvement in strlen16() and strlen32() in
224        pcretest.
226    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
227        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
228        these cases). There was also one in pcretest.c.
230    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
232    6.  In UTF mode, the code for checking whether a group could match an empty
233        string (which is used for indefinitely repeated groups to allow for
234        breaking an infinite loop) was broken when the group contained a repeated
235        negated single-character class with a character that occupied more than one
236        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
237        UTF-8 mode). The effect was undefined: the group might or might not be
238        deemed as matching an empty string, or the program might have crashed.
240    7.  The code for checking whether a group could match an empty string was not
241        recognizing that \h, \H, \v, \V, and \R must match a character.
243    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
244        an empty string. If it can, pcretest shows this in its information output.
246    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
247        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
248        matched by pcre_exec() without using JIT:
250        (a) If the rest of the pattern did not match after a maximal run of
251            grapheme clusters, the code for backing up to try with fewer of them
252            did not always back up over a full grapheme when characters that do not
253            have the modifier quality were involved, e.g. Hangul syllables.
255        (b) If the match point in a subject started with modifier character, and
256            there was no match, the code could incorrectly back up beyond the match
257            point, and potentially beyond the first character in the subject,
258            leading to a segfault or an incorrect match result.
260    10. A conditional group with an assertion condition could lead to PCRE
261        recording an incorrect first data item for a match if no other first data
262        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
263        first data item, and therefore matched "ca" after "c" instead of at the
264        start.
266    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
267        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
269    12. The source of pcregrep now includes z/OS-specific code so that it can be
270        compiled for z/OS as part of the special z/OS distribution.
272    13. Added the -T and -TM options to pcretest.
274    14. The code in pcre_compile.c for creating the table of named capturing groups
275        has been refactored. Instead of creating the table dynamically during the
276        actual compiling pass, the information is remembered during the pre-compile
277        pass (on the stack unless there are more than 20 named groups, in which
278        case malloc() is used) and the whole table is created before the actual
279        compile happens. This has simplified the code (it is now nearly 150 lines
280        shorter) and prepared the way for better handling of references to groups
281        with duplicate names.
283    15. A back reference to a named subpattern when there is more than one of the
284        same name now checks them in the order in which they appear in the pattern.
285        The first one that is set is used for the reference. Previously only the
286        first one was inspected. This change makes PCRE more compatible with Perl.
288    16. Unicode character properties were updated from Unicode 6.3.0.
290    17. The compile-time code for auto-possessification has been refactored, based
291        on a patch by Zoltan Herczeg. It now happens after instead of during
292        compilation. The code is cleaner, and more cases are handled. The option
293        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
294        options in pcretest are provided to set it. It can also be set by
295        (*NO_AUTO_POSSESS) at the start of a pattern.
297    18. The character VT has been added to the default ("C" locale) set of
298        characters that match \s and are generally treated as white space,
299        following this same change in Perl 5.18. There is now no difference between
300        "Perl space" and "POSIX space". Whether VT is treated as white space in
301        other locales depends on the locale.
303    19. The code for checking named groups as conditions, either for being set or
304        for being recursed, has been refactored (this is related to 14 and 15
305        above). Processing unduplicated named groups should now be as fast at
306        numerical groups, and processing duplicated groups should be faster than
307        before.
309    20. Two patches to the CMake build system, by Alexander Barkov:
311          (1) Replace the "source" command by "." in CMakeLists.txt because
312              "source" is a bash-ism.
314          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
315              without these the CMake build does not work on Solaris.
317    21. Perl has changed its handling of \8 and \9. If there is no previously
318        encountered capturing group of those numbers, they are treated as the
319        literal characters 8 and 9 instead of a binary zero followed by the
320        literals. PCRE now does the same.
322    22. Following Perl, added \o{} to specify codepoints in octal, making it
323        possible to specify values greater than 0777 and also making them
324        unambiguous.
326    23. Perl now gives an error for missing closing braces after \x{... instead of
327        treating the string as literal. PCRE now does the same.
329    24. RunTest used to grumble if an inappropriate test was selected explicitly,
330        but just skip it when running all tests. This make it awkward to run ranges
331        of tests when one of them was inappropriate. Now it just skips any
332        inappropriate tests, as it always did when running all tests.
334    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
335        character types such as \d or \w, too many callouts were inserted, and the
336        data that they returned was rubbish.
338    26. In UCP mode, \s was not matching two of the characters that Perl matches,
339        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
340        were matched by \h. The code has now been refactored so that the lists of
341        the horizontal and vertical whitespace characters used for \h and \v (which
342        are defined only in one place) are now also used for \s.
344    27. Add JIT support for the 64 bit TileGX architecture.
345        Patch by Jiong Wang (Tilera Corporation).
347    28. Possessive quantifiers for classes (both explicit and automatically
348        generated) now use special opcodes instead of wrapping in ONCE brackets.
350    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
351        (because it's meaningless), this was not happening when PCRE_CASELESS was
352        set. Not wrong, but inefficient.
354    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
355        properties for \w, \d, etc) is present in a test regex. Otherwise if the
356        test contains no characters greater than 255, Perl doesn't realise it
357        should be using Unicode semantics.
359    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
360        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
361        does in Unicode mode.
363    32. Added the "forbid" facility to pcretest so that putting tests into the
364        wrong test files can sometimes be quickly detected.
366    33. There is now a limit (default 250) on the depth of nesting of parentheses.
367        This limit is imposed to control the amount of system stack used at compile
368        time. It can be changed at build time by --with-parens-nest-limit=xxx or
369        the equivalent in CMake.
371    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
372        errors. Perl warns for these when in warning mode, but PCRE has no facility
373        for giving warnings.
375    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
376        However, this was not working for (?!) because it is optimized to (*FAIL),
377        for which PCRE does not allow quantifiers. The optimization is now disabled
378        when a quantifier follows (?!). I can't see any use for this, but it makes
379        things uniform.
381    36. Perl no longer allows group names to start with digits, so I have made this
382        change also in PCRE. It simplifies the code a bit.
384    37. In extended mode, Perl ignores spaces before a + that indicates a
385        possessive quantifier. PCRE allowed a space before the quantifier, but not
386        before the possessive +. It now does.
388    38. The use of \K (reset reported match start) within a repeated possessive
389        group such as (a\Kb)*+ was not working.
391    40. Document that the same character tables must be used at compile time and
392        run time, and that the facility to pass tables to pcre_exec() and
393        pcre_dfa_exec() is for use only with saved/restored patterns.
395    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
396        features for Builds with MSVC:
398        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
399           builds). The .rc files can be used to set FileDescription and many other
400           attributes.
402        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
403           This allows higher-level build scripts which want .pdb files to avoid
404           hard-coding the exact files needed."
406    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
407        mean "start of word" and "end of word", respectively, as a transition aid.
409    43. A minimizing repeat of a class containing codepoints greater than 255 in
410        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
411        compiled to use the heap for recursion.
413    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
414        is configured.
417    Version 8.33 28-May-2013
418    ------------------------
420    1.  Added 'U' to some constants that are compared to unsigned integers, to
421        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
422        variables that are added to signed variables, to ensure the result is
423        signed and can be negated.
425    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
426        CMake config files.
428    3.  Revise the creation of config.h.generic so that all boolean macros are
429        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
430        overriding via -D on the command line possible.
432    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
433        to unsigned int is reported to make a quite noticeable speed difference in
434        a specific Windows environment. Testing on Linux did also appear to show
435        some benefit (and it is clearly not harmful). Also fixed the definition of
436        Xop which should be unsigned.
438    5.  Related to (4), changing the definition of the intermediate variable cc
439        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
440        improvements.
442    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
443        unnecessary spaces.
445    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
446        and later.
448    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
450    9.  Optimizing fast_forward_start_bits in JIT.
452    10. Adding support for callouts in JIT, and fixing some issues revealed
453        during this work. Namely:
455        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
457        (b) Minimum length was not checked before the matching is started.
459    11. The value of capture_last that is passed to callouts was incorrect in some
460        cases when there was a capture on one path that was subsequently abandoned
461        after a backtrack. Also, the capture_last value is now reset after a
462        recursion, since all captures are also reset in this case.
464    12. The interpreter no longer returns the "too many substrings" error in the
465        case when an overflowing capture is in a branch that is subsequently
466        abandoned after a backtrack.
468    13. In the pathological case when an offset vector of size 2 is used, pcretest
469        now prints out the matched string after a yield of 0 or 1.
471    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
472        Only supported by the JIT compiler at the moment.
474    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
476    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
477        offset of the starting point of the matching process, provided the offsets
478        vector is large enough.
480    17. The \A escape now records a lookbehind value of 1, though its execution
481        does not actually inspect the previous character. This is to ensure that,
482        in partial multi-segment matching, at least one character from the old
483        segment is retained when a new segment is processed. Otherwise, if there
484        are no lookbehinds in the pattern, \A might match incorrectly at the start
485        of a new segment.
487    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
489    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
490        gives some modest performance improvement in 8-bit mode.
492    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
493        be expressed in certain programming languages using Universal Character
494        Names.
496    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
497        which points out that "non characters" are not "characters that may not
498        appear in Unicode strings" but rather "characters that are reserved for
499        internal use and have only local meaning".
501    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
502        there was a conditional group that depended on an assertion, if the
503        assertion was false, the callout that immediately followed the alternation
504        in the condition was skipped when pcre_exec() was used for matching.
506    23. Allow an explicit callout to be inserted before an assertion that is the
507        condition for a conditional group, for compatibility with automatic
508        callouts, which always insert a callout at this point.
510    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
511        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
513    25. (*PRUNE) is now supported by the JIT compiler.
515    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
517    27. Fix the case where there are two or more SKIPs with arguments that may be
518        ignored.
520    28. (*SKIP) is now supported by the JIT compiler.
522    29. (*THEN) is now supported by the JIT compiler.
524    30. Update RunTest with additional test selector options.
526    31. The way PCRE handles backtracking verbs has been changed in two ways.
528        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
529        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
530        backtracking. In some cases this makes it more Perl-compatible, but Perl's
531        rather obscure rules do not always do the same thing.
533        (2) Previously, backtracking verbs were confined within assertions. This is
534        no longer the case for positive assertions, except for (*ACCEPT). Again,
535        this sometimes improves Perl compatibility, and sometimes does not.
537    32. A number of tests that were in test 2 because Perl did things differently
538        have been moved to test 1, because either Perl or PCRE has changed, and
539        these tests are now compatible.
541    32. Backtracking control verbs are now handled in the same way in JIT and
542        interpreter.
544    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
545        contained a forward subroutine reference caused a compile error.
547    34. Auto-detect and optimize limited repetitions in JIT.
549    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
550        blocking (*UTF) etc.
552    36. In the interpreter, maximizing pattern repetitions for characters and
553        character types now use tail recursion, which reduces stack usage.
555    37. The value of the max lookbehind was not correctly preserved if a compiled
556        and saved regex was reloaded on a host of different endianness.
558    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
559        of the compiled pattern block, expand the flags field from 16 to 32 bits
560        because it was almost full.
562    39. Try madvise first before posix_madvise.
564    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
565        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
566        original change locked out all matches of empty strings. This has been
567        changed so that one match of an empty string per line is recognized.
568        Subsequent searches on the same line (for colouring or for --only-matching,
569        for example) do not recognize empty strings.
571    41. Applied a user patch to fix a number of spelling mistakes in comments.
573    42. Data lines longer than 65536 caused pcretest to crash.
575    43. Clarified the data type for length and startoffset arguments for pcre_exec
576        and pcre_dfa_exec in the function-specific man pages, where they were
577        explicitly stated to be in bytes, never having been updated. I also added
578        some clarification to the pcreapi man page.
580    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
581        a segmentation fault.
584    Version 8.32 30-November-2012
585    -----------------------------
587    1.  Improved JIT compiler optimizations for first character search and single
588        character iterators.
590    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
591        Patch by Daniel Richard G.
593    3.  Single character iterator optimizations in the JIT compiler.
595    4.  Improved JIT compiler optimizations for character ranges.
597    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
598        Reported by Giuseppe D'Angelo.
600    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
601        of a line, was being set incorrectly in cases where .* appeared inside
602        atomic brackets at the start of a pattern, or where there was a subsequent
603        *PRUNE or *SKIP.
605    7.  Improved instruction cache flush for POWER/PowerPC.
606        Patch by Daniel Richard G.
608    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
609        grep:
611        (a) There is now no limit to the number of patterns to be matched.
613        (b) An error is given if a pattern is too long.
615        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
616            are now supported.
618        (d) --exclude-from and --include-from (multiple use) have been added.
620        (e) Exclusions and inclusions now apply to all files and directories, not
621            just to those obtained from scanning a directory recursively.
623        (f) Multiple uses of -f and --file-list are now supported.
625        (g) In a Windows environment, the default for -d has been changed from
626            "read" (the GNU grep default) to "skip", because otherwise the presence
627            of a directory in the file list provokes an error.
629        (h) The documentation has been revised and clarified in places.
631    9.  Improve the matching speed of capturing brackets.
633    10. Changed the meaning of \X so that it now matches a Unicode extended
634        grapheme cluster.
636    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
637        out POSIX threads when JIT support is configured.
639    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
641    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
642        structure could go wrong in environments where size_t is not the same size
643        as int.
645    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
646        set.
648    15. The EBCDIC support had decayed; later updates to the code had included
649        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
650        general tidy up of EBCDIC-related issues, and the documentation was also
651        not quite right. There is now a test that can be run on ASCII systems to
652        check some of the EBCDIC-related things (but is it not a full test).
654    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
655        in a small tidy to the code.
657    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
659    18. If the --only-matching (-o) option in pcregrep is specified multiple
660        times, each one causes appropriate output. For example, -o1 -o2 outputs the
661        substrings matched by the 1st and 2nd capturing parentheses. A separating
662        string can be specified by --om-separator (default empty).
664    19. Improving the first n character searches.
666    20. Turn case lists for horizontal and vertical white space into macros so that
667        they are defined only once.
669    21. This set of changes together give more compatible Unicode case-folding
670        behaviour for characters that have more than one other case when UCP
671        support is available.
673        (a) The Unicode property table now has offsets into a new table of sets of
674            three or more characters that are case-equivalent. The MultiStage2.py
675            script that generates these tables (the pcre_ucd.c file) now scans
676            CaseFolding.txt instead of UnicodeData.txt for character case
677            information.
679        (b) The code for adding characters or ranges of characters to a character
680            class has been abstracted into a generalized function that also handles
681            case-independence. In UTF-mode with UCP support, this uses the new data
682            to handle characters with more than one other case.
684        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
685            whose other case is greater than 256 are now correctly matched
686            caselessly. Previously, the high codepoint matched the low one, but not
687            vice versa.
689        (d) The processing of \h, \H, \v, and \ in character classes now makes use
690            of the new class addition function, using character lists defined as
691            macros alongside the case definitions of 20 above.
693        (e) Caseless back references now work with characters that have more than
694            one other case.
696        (f) General caseless matching of characters with more than one other case
697            is supported.
699    22. Unicode character properties were updated from Unicode 6.2.0
701    23. Improved CMake support under Windows. Patch by Daniel Richard G.
703    24. Add support for 32-bit character strings, and UTF-32
705    25. Major JIT compiler update (code refactoring and bugfixing).
706        Experimental Sparc 32 support is added.
708    26. Applied a modified version of Daniel Richard G's patch to create
709        pcre.h.generic and config.h.generic by "make" instead of in the
710        PrepareRelease script.
712    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
713        pcre_compile.c when checking for a zero character.
715    28. Introducing a native interface for JIT. Through this interface, the compiled
716        machine code can be directly executed. The purpose of this interface is to
717        provide fast pattern matching, so several sanity checks are not performed.
718        However, feature tests are still performed. The new interface provides
719        1.4x speedup compared to the old one.
721    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
722        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
723        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
725    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
726        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
727        the "old" RFC 2279). Instead, it ended up passing a negative length to
728        pcre_exec().
730    31. Add support for GCC's visibility feature to hide internal functions.
732    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
733        "unknown -C option" after outputting 0 or 1.
735    33. There is now support for generating a code coverage report for the test
736        suite in environments where gcc is the compiler and lcov is installed. This
737        is mainly for the benefit of the developers.
739    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
740        unaddressable using valgrind annotations, allowing valgrind to detect
741        invalid memory accesses. This is mainly for the benefit of the developers.
743    25. (*UTF) can now be used to start a pattern in any of the three libraries.
745    26. Give configure error if --enable-cpp but no C++ compiler found.
748    Version 8.31 06-July-2012
749    -------------------------
751    1.  Fixing a wrong JIT test case and some compiler warnings.
753    2.  Removed a bashism from the RunTest script.
755    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
756        to unsigned type, result still unsigned" that was given by an MS compiler
757        on encountering the code "-sizeof(xxx)".
759    4.  Partial matching support is added to the JIT compiler.
761    5.  Fixed several bugs concerned with partial matching of items that consist
762        of more than one character:
764        (a) /^(..)\1/ did not partially match "aba" because checking references was
765            done on an "all or nothing" basis. This also applied to repeated
766            references.
768        (b) \R did not give a hard partial match if \r was found at the end of the
769            subject.
771        (c) \X did not give a hard partial match after matching one or more
772            characters at the end of the subject.
774        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
775            a partial match for the string "\r".
777        (e) When newline was set to CRLF, the metacharacter "." did not recognize
778            a partial match for a CR character at the end of the subject string.
780    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
781        running pcretest, the text "(JIT)" added to the output whenever JIT is
782        actually used to run the match.
784    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
785        or /S+[+] with a digit between 1 and 7.
787    8.  OP_NOT now supports any UTF character not just single-byte ones.
789    9.  (*MARK) control verb is now supported by the JIT compiler.
791    10. The command "./RunTest list" lists the available tests without actually
792        running any of them. (Because I keep forgetting what they all are.)
796    12. Applied a (slightly modified) user-supplied patch that improves performance
797        when the heap is used for recursion (compiled with --disable-stack-for-
798        recursion). Instead of malloc and free for each heap frame each time a
799        logical recursion happens, frames are retained on a chain and re-used where
800        possible. This sometimes gives as much as 30% improvement.
802    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
803        call.
805    14. As documented, (*COMMIT) is now confined to within a positive assertion.
807    15. It is now possible to link pcretest with libedit as an alternative to
808        libreadline.
810    16. (*COMMIT) control verb is now supported by the JIT compiler.
812    17. The Unicode data tables have been updated to Unicode 6.1.0.
814    18. Added --file-list option to pcregrep.
816    19. Added binary file support to pcregrep, including the -a, --binary-files,
817        -I, and --text options.
819    20. The madvise function is renamed for posix_madvise for QNX compatibility
820        reasons. Fixed by Giuseppe D'Angelo.
822    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
824    22. Changed the option for creating symbolic links for 16-bit man pages from
825        -s to -sf so that re-installing does not cause issues.
827    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
829    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
830        matches in certain environments (the workspace was not being correctly
831        retained). Also added to pcre_dfa_exec() a simple plausibility check on
832        some of the workspace data at the beginning of a restart.
834    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
835        was not doing so when it should - probably a typo introduced by SVN 528
836        (change 8.10/14).
838    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
839        \w+ when the character tables indicated that \x{c4} was a word character.
840        There were several related cases, all because the tests for doing a table
841        lookup were testing for characters less than 127 instead of 255.
843    27. If a pattern contains capturing parentheses that are not used in a match,
844        their slots in the ovector are set to -1. For those that are higher than
845        any matched groups, this happens at the end of processing. In the case when
846        there were back references that the ovector was too small to contain
847        (causing temporary malloc'd memory to be used during matching), and the
848        highest capturing number was not used, memory off the end of the ovector
849        was incorrectly being set to -1. (It was using the size of the temporary
850        memory instead of the true size.)
852    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
853        ovector size, it uses memory at the end of the block that it has got.
855    29. Check for an overlong MARK name and give an error at compile time. The
856        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
858    30. JIT compiler update.
860    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
861        Rill for the patch.
863    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
865    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
867    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
868        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
869        was enabled.
871    35. Improve JIT code generation for greedy plus quantifier.
873    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
874        1 to "aa" instead of to an empty string. The bug affected repeated groups
875        that could potentially match an empty string.
877    37. Optimizing single character iterators in JIT.
879    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
880        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
881        codepoints that are too big for the mode are faulted, and in a UTF mode,
882        disallowed codepoints are also faulted.
884    39. If PCRE was compiled with UTF support, in three places in the DFA
885        matcher there was code that should only have been obeyed in UTF mode, but
886        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
887        processing when bytes with values greater than 127 were present. In 16-bit
888        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
889        both cases the values are those that cannot be the first data item in a UTF
890        character. The three items that might have provoked this were recursions,
891        possessively repeated groups, and atomic groups.
893    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
894        and pcregrep, because some OS require shared objects to be explicitly
895        passed to ld, causing the link step to fail if they are not.
897    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
898        mode, patterns that started with \h* or \R* might be incorrectly matched.
901    Version 8.30 04-February-2012
902    -----------------------------
904    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
905        name is defined in ctype.h.
907    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
908        only in quite long subpatterns.
910    3.  Removed the function pcre_info(), which has been obsolete and deprecated
911        since it was replaced by pcre_fullinfo() in February 2000.
913    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
914        match a (*MARK), and the match failed at the start of the subject, a
915        reference to memory before the start of the subject could occur. This bug
916        was introduced by fix 17 of release 8.21.
918    5.  A reference to an unset group with zero minimum repetition was giving
919        totally wrong answers (in non-JavaScript-compatibility mode). For example,
920        /(another)?(\1?)test/ matched against "hello world test". This bug was
921        introduced in release 8.13.
923    6.  Add support for 16-bit character strings (a large amount of work involving
924        many changes and refactorings).
926    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
927        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
928        from a file.
930    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
931        rounding is not applied in this particular case).
933    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
934        if they appear, or are escaped, in patterns.
936    10. Get rid of a number of -Wunused-but-set-variable warnings.
938    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
939        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
940        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
941        also returns the mark "x". This bug applied to capturing parentheses,
942        non-capturing parentheses, and atomic parentheses. It also applied to some
943        assertions.
945    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
946        information out of configure.ac instead of relying on pcre.h.generic, which
947        is not stored in the repository.
949    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
950        -lreadline.
952    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
954    15. Applied Graycode's patch to put the top-level frame on the stack rather
955        than the heap when not using the stack for recursion. This gives a
956        performance improvement in many cases when recursion is not deep.
958    16. Experimental code added to "pcretest -C" to output the stack frame size.
961    Version 8.21 12-Dec-2011
962    ------------------------
964    1.  Updating the JIT compiler.
966    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
967        are added as well.
969    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
970        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
971        calling _pcre_jit_exec. Some extra comments are added.
973    4.  (*MARK) settings inside atomic groups that do not contain any capturing
974        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
975        was introduced by change 18 for 8.20.
977    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
978        ECMA-262 standard.
980    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
981        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
982        This bug was probably introduced by change 9 of 8.13.
984    7.  While fixing 6 above, I noticed that a number of other items were being
985        incorrectly rejected as "not fixed length". This arose partly because newer
986        opcodes had not been added to the fixed-length checking code. I have (a)
987        corrected the bug and added tests for these items, and (b) arranged for an
988        error to occur if an unknown opcode is encountered while checking for fixed
989        length instead of just assuming "not fixed length". The items that were
990        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
991        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
992        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
994    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
995        being incorrectly compiled and would have given unpredicatble results.
997    9.  A possessively repeated subpattern with minimum repeat count greater than
998        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
999        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
1000        the first (A) could occur when it should not.
1002    10. Add a cast and remove a redundant test from the code.
1004    11. JIT should use pcre_malloc/pcre_free for allocation.
1006    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
1007        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
1008        is anything other than /usr, -L is still shown).
1010    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
1012    14. Perl does not support \N without a following name in a [] class; PCRE now
1013        also gives an error.
1015    15. If a forward reference was repeated with an upper limit of around 2000,
1016        it caused the error "internal error: overran compiling workspace". The
1017        maximum number of forward references (including repeats) was limited by the
1018        internal workspace, and dependent on the LINK_SIZE. The code has been
1019        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
1020        the default depends on LINK_SIZE. There is a new upper limit (for safety)
1021        of around 200,000 forward references. While doing this, I also speeded up
1022        the filling in of repeated forward references.
1024    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
1025        incorrectly expecting the subject to contain another "a" after the start.
1027    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
1028        in the match, the SKIP should be ignored. This was not happening; instead
1029        the SKIP was being treated as NOMATCH. For patterns such as
1030        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
1031        tested.
1033    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
1034        now much more compatible with Perl, in particular in cases where the result
1035        is a non-match for a non-anchored pattern. For example, if
1036        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
1037        "m", where previously it did not return a name. A side effect of this
1038        change is that for partial matches, the last encountered mark name is
1039        returned, as for non matches. A number of tests that were previously not
1040        Perl-compatible have been moved into the Perl-compatible test files. The
1041        refactoring has had the pleasing side effect of removing one argument from
1042        the match() function, thus reducing its stack requirements.
1044    19. If the /S+ option was used in pcretest to study a pattern using JIT,
1045        subsequent uses of /S (without +) incorrectly behaved like /S+.
1047    21. Retrieve executable code size support for the JIT compiler and fixing
1048        some warnings.
1050    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
1051        not work when the shorter character appeared right at the end of the
1052        subject string.
1054    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
1055        systems.
1057    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
1058        output it when the /M option is used in pcretest.
1060    25. The CheckMan script was not being included in the distribution. Also, added
1061        an explicit "perl" to run Perl scripts from the PrepareRelease script
1062        because this is reportedly needed in Windows.
1064    26. If study data was being save in a file and studying had not found a set of
1065        "starts with" bytes for the pattern, the data written to the file (though
1066        never used) was taken from uninitialized memory and so caused valgrind to
1067        complain.
1069    27. Updated RunTest.bat as provided by Sheri Pierce.
1071    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
1073    29. Computation of memory usage for the table of capturing group names was
1074        giving an unnecessarily large value.
1077    Version 8.20 21-Oct-2011
1078    ------------------------
1080    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
1081        a POSIX class. After further experiments with Perl, which convinced me that
1082        Perl has bugs and confusions, a closing square bracket is no longer allowed
1083        in a POSIX name. This bug also affected patterns with classes that started
1084        with full stops.
1086    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
1087        captured substring, but while checking the failing first alternative,
1088        substring 1 is temporarily captured. If the output vector supplied to
1089        pcre_exec() was not big enough for this capture, the yield of the function
1090        was still zero ("insufficient space for captured substrings"). This cannot
1091        be totally fixed without adding another stack variable, which seems a lot
1092        of expense for a edge case. However, I have improved the situation in cases
1093        such as /(a)(b)x|abc/ matched against "abc", where the return code
1094        indicates that fewer than the maximum number of slots in the ovector have
1095        been set.
1097    3.  Related to (2) above: when there are more back references in a pattern than
1098        slots in the output vector, pcre_exec() uses temporary memory during
1099        matching, and copies in the captures as far as possible afterwards. It was
1100        using the entire output vector, but this conflicts with the specification
1101        that only 2/3 is used for passing back captured substrings. Now it uses
1102        only the first 2/3, for compatibility. This is, of course, another edge
1103        case.
1105    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
1106        main code base, and can be used by building with --enable-jit. When this is
1107        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
1108        runtime --no-jit option is given.
1110    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
1111        ovector, the return from the function was zero, implying that there were
1112        other matches that did not fit. The correct "exactly full" value is now
1113        returned.
1115    6.  If a subpattern that was called recursively or as a subroutine contained
1116        (*PRUNE) or any other control that caused it to give a non-standard return,
1117        invalid errors such as "Error -26 (nested recursion at the same subject
1118        position)" or even infinite loops could occur.
1120    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
1121        computing the minimum length on reaching *ACCEPT, and so ended up with the
1122        wrong value of 1 rather than 0. Further investigation indicates that
1123        computing a minimum subject length in the presence of *ACCEPT is difficult
1124        (think back references, subroutine calls), and so I have changed the code
1125        so that no minimum is registered for a pattern that contains *ACCEPT.
1127    8.  If (*THEN) was present in the first (true) branch of a conditional group,
1128        it was not handled as intended. [But see 16 below.]
1130    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
1131        Sheri Pierce.
1133    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
1134        the first byte in a match must be "a".
1136    11. Change 17 for 8.13 increased the recursion depth for patterns like
1137        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
1138        pattern contains any instances of (*THEN). If it does not, the old
1139        optimizations are restored. It would be nice to do this on a per-group
1140        basis, but at the moment that is not feasible.
1142    12. In some environments, the output of pcretest -C is CRLF terminated. This
1143        broke RunTest's code that checks for the link size. A single white space
1144        character after the value is now allowed for.
1146    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
1147        For "fr", it uses the Windows-specific input and output files.
1149    14. If (*THEN) appeared in a group that was called recursively or as a
1150        subroutine, it did not work as intended. [But see next item.]
1152    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
1153        pattern fragments (but not containing any | characters). If A and B are
1154        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
1155        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
1156        D. In other words, Perl considers parentheses that do not contain any |
1157        characters to be part of a surrounding alternative, whereas PCRE was
1158        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
1159        differently. PCRE now behaves in the same way as Perl, except in the case
1160        of subroutine/recursion calls such as (?1) which have in any case always
1161        been different (but PCRE had them first :-).
1163    16. Related to 15 above: Perl does not treat the | in a conditional group as
1164        creating alternatives. Such a group is treated in the same way as an
1165        ordinary group without any | characters when processing (*THEN). PCRE has
1166        been changed to match Perl's behaviour.
1168    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
1169        RunGrepTest script failed.
1171    18. Change 22 for version 13 caused atomic groups to use more stack. This is
1172        inevitable for groups that contain captures, but it can lead to a lot of
1173        stack use in large patterns. The old behaviour has been restored for atomic
1174        groups that do not contain any capturing parentheses.
1176    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
1177        suppress the check for a minimum subject length at run time. (If it was
1178        given to pcre_exec() or pcre_dfa_exec() it did work.)
1180    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
1181        fail to work when decoding hex characters in data strings in EBCDIC
1182        environments.
1184    21. It appears that in at least one Mac OS environment, the isxdigit() function
1185        is implemented as a macro that evaluates to its argument more than once,
1186        contravening the C 90 Standard (I haven't checked a later standard). There
1187        was an instance in pcretest which caused it to go wrong when processing
1188        \x{...} escapes in subject strings. The has been rewritten to avoid using
1189        things like p++ in the argument of isxdigit().
1192    Version 8.13 16-Aug-2011
1193    ------------------------
1195    1.  The Unicode data tables have been updated to Unicode 6.0.0.
1197    2.  Two minor typos in pcre_internal.h have been fixed.
1199    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
1200        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
1201        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
1203    4.  There were a number of related bugs in the code for matching backrefences
1204        caselessly in UTF-8 mode when codes for the characters concerned were
1205        different numbers of bytes. For example, U+023A and U+2C65 are an upper
1206        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
1207        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
1208        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
1209        2-byte code at the end of the subject (it thought there wasn't enough data
1210        left).
1212    5.  Comprehensive information about what went wrong is now returned by
1213        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
1214        as the output vector has at least 2 elements. The offset of the start of
1215        the failing character and a reason code are placed in the vector.
1217    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
1218        now returned is for the first byte of the failing character, instead of the
1219        last byte inspected. This is an incompatible change, but I hope it is small
1220        enough not to be a problem. It makes the returned offset consistent with
1221        pcre_exec() and pcre_dfa_exec().
1223    7.  pcretest now gives a text phrase as well as the error number when
1224        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
1225        failure, the offset and reason code are output.
1227    8.  When \R was used with a maximizing quantifier it failed to skip backwards
1228        over a \r\n pair if the subsequent match failed. Instead, it just skipped
1229        back over a single character (\n). This seems wrong (because it treated the
1230        two characters as a single entity when going forwards), conflicts with the
1231        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
1232        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
1233        has been changed.
1235    9.  Some internal refactoring has changed the processing so that the handling
1236        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
1237        time (the PCRE_DOTALL option was changed this way some time ago: version
1238        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
1239        which was always a bit of a fudge. It also means that there is one less
1240        argument for the match() function, which reduces its stack requirements
1241        slightly. This change also fixes an incompatibility with Perl: the pattern
1242        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
1244    10. More internal refactoring has drastically reduced the number of recursive
1245        calls to match() for possessively repeated groups such as (abc)++ when
1246        using pcre_exec().
1248    11. While implementing 10, a number of bugs in the handling of groups were
1249        discovered and fixed:
1251        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
1252        (a|)*(?1) gave a compile-time internal error.
1253        ((a|)+)+  did not notice that the outer group could match an empty string.
1254        (^a|^)+   was not marked as anchored.
1255        (.*a|.*)+ was not marked as matching at start or after a newline.
1257    12. Yet more internal refactoring has removed another argument from the match()
1258        function. Special calls to this function are now indicated by setting a
1259        value in a variable in the "match data" data block.
1261    13. Be more explicit in pcre_study() instead of relying on "default" for
1262        opcodes that mean there is no starting character; this means that when new
1263        ones are added and accidentally left out of pcre_study(), testing should
1264        pick them up.
1266    14. The -s option of pcretest has been documented for ages as being an old
1267        synonym of -m (show memory usage). I have changed it to mean "force study
1268        for every regex", that is, assume /S for every regex. This is similar to -i
1269        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
1270        using it. It makes it easier to run collections of tests with and without
1271        study enabled, and thereby test pcre_study() more easily. All the standard
1272        tests are now run with and without -s (but some patterns can be marked as
1273        "never study" - see 20 below).
1275    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
1276        restoration of the capturing data to the outer values was not happening
1277        correctly.
1279    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
1280        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
1281        pattern had matched an empty string, and so incorrectly returned a no
1282        match.
1284    17. There was optimizing code for the last branch of non-capturing parentheses,
1285        and also for the obeyed branch of a conditional subexpression, which used
1286        tail recursion to cut down on stack usage. Unfortunately, now that there is
1287        the possibility of (*THEN) occurring in these branches, tail recursion is
1288        no longer possible because the return has to be checked for (*THEN). These
1289        two optimizations have therefore been removed. [But see 8.20/11 above.]
1291    18. If a pattern containing \R was studied, it was assumed that \R always
1292        matched two bytes, thus causing the minimum subject length to be
1293        incorrectly computed because \R can also match just one byte.
1295    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
1296        was incorrectly computed.
1298    20. If /S is present twice on a test pattern in pcretest input, it now
1299        *disables* studying, thereby overriding the use of -s on the command line
1300        (see 14 above). This is necessary for one or two tests to keep the output
1301        identical in both cases.
1303    21. When (*ACCEPT) was used in an assertion that matched an empty string and
1304        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
1306    22. When an atomic group that contained a capturing parenthesis was
1307        successfully matched, but the branch in which it appeared failed, the
1308        capturing was not being forgotten if a higher numbered group was later
1309        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
1310        group 1 to "a", when in fact it should be unset. This applied to multi-
1311        branched capturing and non-capturing groups, repeated or not, and also to
1312        positive assertions (capturing in negative assertions does not happen
1313        in PCRE) and also to nested atomic groups.
1315    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
1316        subject after a captured substring, to make it easier to tell which of a
1317        number of identical substrings has been captured.
1319    24. The way atomic groups are processed by pcre_exec() has been changed so that
1320        if they are repeated, backtracking one repetition now resets captured
1321        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
1322        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
1323        "aaa". Previously, it would have been "a". As part of this code
1324        refactoring, the way recursive calls are handled has also been changed.
1326    25. If an assertion condition captured any substrings, they were not passed
1327        back unless some other capturing happened later. For example, if
1328        (?(?=(a))a) was matched against "a", no capturing was returned.
1330    26. When studying a pattern that contained subroutine calls or assertions,
1331        the code for finding the minimum length of a possible match was handling
1332        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
1333        group 1 called group 2 while simultaneously a separate group 2 called group
1334        1). A stack overflow occurred in this case. I have fixed this by limiting
1335        the recursion depth to 10.
1337    27. Updated RunTest.bat in the distribution to the version supplied by Tom
1338        Fortmann. This supports explicit test numbers on the command line, and has
1339        argument validation and error reporting.
1341    28. An instance of \X with an unlimited repeat could fail if at any point the
1342        first character it looked at was a mark character.
1344    29. Some minor code refactoring concerning Unicode properties and scripts
1345        should reduce the stack requirement of match() slightly.
1347    30. Added the '=' option to pcretest to check the setting of unused capturing
1348        slots at the end of the pattern, which are documented as being -1, but are
1349        not included in the return count.
1351    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
1352        compiled something random. Now it gives a compile-time error (as does
1353        Perl).
1355    32. A *MARK encountered during the processing of a positive assertion is now
1356        recorded and passed back (compatible with Perl).
1358    33. If --only-matching or --colour was set on a pcregrep call whose pattern
1359        had alternative anchored branches, the search for a second match in a line
1360        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
1361        matched the line "0102" twice. The same bug affected patterns that started
1362        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
1363        twice.
1365    34. Previously, PCRE did not allow quantification of assertions. However, Perl
1366        does, and because of capturing effects, quantifying parenthesized
1367        assertions may at times be useful. Quantifiers are now allowed for
1368        parenthesized assertions.
1370    35. A minor code tidy in pcre_compile() when checking options for \R usage.
1372    36. \g was being checked for fancy things in a character class, when it should
1373        just be a literal "g".
1375    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
1376        appearance of a nested POSIX class supersedes an apparent external class.
1377        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1378        unescaped square brackets may also appear as part of class names. For
1379        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1380        more like Perl. (But see 8.20/1 above.)
1382    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1383        was because it thought it was \N{name}, which is not supported).
1385    39. Add minix to OS list not supporting the -S option in pcretest.
1387    40. PCRE tries to detect cases of infinite recursion at compile time, but it
1388        cannot analyze patterns in sufficient detail to catch mutual recursions
1389        such as ((?1))((?2)). There is now a runtime test that gives an error if a
1390        subgroup is called recursively as a subpattern for a second time at the
1391        same position in the subject string. In previous releases this might have
1392        been caught by the recursion limit, or it might have run out of stack.
1394    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
1395        happen only once. PCRE was, however incorrectly giving a compile time error
1396        "recursive call could loop indefinitely" because it cannot analyze the
1397        pattern in sufficient detail. The compile time test no longer happens when
1398        PCRE is compiling a conditional subpattern, but actual runaway loops are
1399        now caught at runtime (see 40 above).
1401    42. It seems that Perl allows any characters other than a closing parenthesis
1402        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
1403        has been changed to be the same.
1405    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
1406        as not to get warnings when autogen.sh is called. Also changed
1407        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
1409    44. To help people who use pcregrep to scan files containing exceedingly long
1410        lines, the following changes have been made:
1412        (a) The default value of the buffer size parameter has been increased from
1413            8K to 20K. (The actual buffer used is three times this size.)
1415        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1416            PCRE is built.
1418        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
1419            to be set at run time.
1421        (d) Numerical values in pcregrep options can be followed by K or M, for
1422            example --buffer-size=50K.
1424        (e) If a line being scanned overflows pcregrep's buffer, an error is now
1425            given and the return code is set to 2.
1427    45. Add a pointer to the latest mark to the callout data block.
1429    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1430        partial match of an empty string instead of no match. This was specific to
1431        the use of ".".
1433    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1434        complete match instead of a partial match. This bug was dependent on both
1435        the PCRE_UTF8 and PCRE_DOTALL options being set.
1437    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1438        starting byte set, because \b was not being ignored.
1441    Version 8.12 15-Jan-2011
1442    ------------------------
1444    1.  Fixed some typos in the markup of the man pages, and wrote a script that
1445        checks for such things as part of the documentation building process.
1447    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
1448        --match-limit and --recursion-limit options (added for 8.11). In
1449        particular, this made one of the standard tests fail. (The integer value
1450        went into the wrong half of a long int.)
1452    3.  If the --colour option was given to pcregrep with -v (invert match), it
1453        did strange things, either producing crazy output, or crashing. It should,
1454        of course, ignore a request for colour when reporting lines that do not
1455        match.
1457    4.  Another pcregrep bug caused similar problems if --colour was specified with
1458        -M (multiline) and the pattern match finished with a line ending.
1460    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
1461        matched in multiline mode, the following line was shown as part of the
1462        match. This seems wrong, so I have changed it.
1464    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
1465        the check for further matches in the same line (so they could be coloured)
1466        to overrun the end of the current line. If another match was found, it was
1467        incorrectly shown (and then shown again when found in the next line).
1469    7.  If pcregrep was compiled under Windows, there was a reference to the
1470        function pcregrep_exit() before it was defined. I am assuming this was
1471        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1472        reported by a user. I've moved the definition above the reference.
1475    Version 8.11 10-Dec-2010
1476    ------------------------
1478    1.  (*THEN) was not working properly if there were untried alternatives prior
1479        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1480        backtracked to try for "b" instead of moving to the next alternative branch
1481        at the same level (in this case, to look for "c"). The Perl documentation
1482        is clear that when (*THEN) is backtracked onto, it goes to the "next
1483        alternative in the innermost enclosing group".
1485    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1486        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
1487        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1488        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1489        (*THEN).
1491    3.  If \s appeared in a character class, it removed the VT character from
1492        the class, even if it had been included by some previous item, for example
1493        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1494        of \s, but is part of the POSIX "space" class.)
1496    4.  A partial match never returns an empty string (because you can always
1497        match an empty string at the end of the subject); however the checking for
1498        an empty string was starting at the "start of match" point. This has been
1499        changed to the "earliest inspected character" point, because the returned
1500        data for a partial match starts at this character. This means that, for
1501        example, /(?<=abc)def/ gives a partial match for the subject "abc"
1502        (previously it gave "no match").
1504    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1505        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1506        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1507        has an implication that the given string is incomplete (because a partial
1508        match is preferred over a full match). For this reason, these items now
1509        give a partial match in this situation. [Aside: previously, the one case
1510        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1511        match rather than a full match, which was wrong by the old rules, but is
1512        now correct.]
1514    6.  There was a bug in the handling of #-introduced comments, recognized when
1515        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1516        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1517        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1518        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1519        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1520        places in pcre_compile().
1522    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1523        comments when looking ahead for named forward references to subpatterns,
1524        the only newline sequence it recognized was NL. It now handles newlines
1525        according to the set newline convention.
1527    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1528        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1529        cater for a lack of strerror(). These oversights have been fixed.
1531    9.  Added --match-limit and --recursion-limit to pcregrep.
1533    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1535    11. When the -o option was used, pcregrep was setting a return code of 1, even
1536        when matches were found, and --line-buffered was not being honoured.
1538    12. Added an optional parentheses number to the -o and --only-matching options
1539        of pcregrep.
1541    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1542        can match an empty string. The code to do it in pcretest and pcredemo
1543        needed fixing:
1545        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1546            only one byte after an empty string match just before CRLF (this case
1547            just got forgotten; "any" and "anycrlf" were OK).
1549        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1550            mode when an empty string match preceded an ASCII character followed by
1551            a non-ASCII character. (The code for advancing by one character rather
1552            than one byte was nonsense.)
1554        (c) The pcredemo.c sample program did not have any code at all to handle
1555            the cases when CRLF is a valid newline sequence.
1557    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1558        as a starting offset was within the subject string. There is now a new
1559        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1560        negative or greater than the length of the string. In order to test this,
1561        pcretest is extended to allow the setting of negative starting offsets.
1563    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1564        starting offset points to the beginning of a UTF-8 character was
1565        unnecessarily clumsy. I tidied it up.
1567    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1568        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1570    17. Nobody had reported that the --include_dir option, which was added in
1571        release 7.7 should have been called --include-dir (hyphen, not underscore)
1572        for compatibility with GNU grep. I have changed it to --include-dir, but
1573        left --include_dir as an undocumented synonym, and the same for
1574        --exclude-dir, though that is not available in GNU grep, at least as of
1575        release 2.5.4.
1577    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1578        characters from a string of bytes) have been redefined so as not to use
1579        loops, in order to improve performance in some environments. At the same
1580        time, I abstracted some of the common code into auxiliary macros to save
1581        repetition (this should not affect the compiled code).
1583    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1584        compile-time error is now given if \c is not followed by an ASCII
1585        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1586        different, and any byte value is allowed.)
1588    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1589        START_OPTIMIZE option, which is now allowed at compile time - but just
1590        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1591        to pcregrep and other applications that have no direct access to PCRE
1592        options. The new /Y option in pcretest sets this option when calling
1593        pcre_compile().
1595    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1596        back references. Groups containing recursive back references were forced to
1597        be atomic by that change, but in the case of named groups, the amount of
1598        memory required was incorrectly computed, leading to "Failed: internal
1599        error: code overflow". This has been fixed.
1601    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1602        pcretest.c, to avoid build problems in some Borland environments.
1605    Version 8.10 25-Jun-2010
1606    ------------------------
1608    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1609        THEN.
1611    2.  (*ACCEPT) was not working when inside an atomic group.
1613    3.  Inside a character class, \B is treated as a literal by default, but
1614        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1615        causes the error). The code is unchanged, but I tidied the documentation.
1617    4.  Inside a character class, PCRE always treated \R and \X as literals,
1618        whereas Perl faults them if its -w option is set. I have changed PCRE so
1619        that it faults them when PCRE_EXTRA is set.
1621    5.  Added support for \N, which always matches any character other than
1622        newline. (It is the same as "." when PCRE_DOTALL is not set.)
1624    6.  When compiling pcregrep with newer versions of gcc which may have
1625        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1626        declared with attribute warn_unused_result" were given. Just casting the
1627        result to (void) does not stop the warnings; a more elaborate fudge is
1628        needed. I've used a macro to implement this.
1630    7.  Minor change to pcretest.c to avoid a compiler warning.
1632    8.  Added four artifical Unicode properties to help with an option to make
1633        \s etc use properties (see next item). The new properties are: Xan
1634        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1636    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1637        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1638        this option. Modified pcretest to add /W to test this facility. Added
1639        REG_UCP to make it available via the POSIX interface.
1641    10. Added --line-buffered to pcregrep.
1643    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1644        studied, and the match started with a letter with a code point greater than
1645        127 whose first byte was different to the first byte of the other case of
1646        the letter, the other case of this starting letter was not recognized
1647        (#976).
1649    12. If a pattern that was studied started with a repeated Unicode property
1650        test, for example, \p{Nd}+, there was the theoretical possibility of
1651        setting up an incorrect bitmap of starting bytes, but fortunately it could
1652        not have actually happened in practice until change 8 above was made (it
1653        added property types that matched character-matching opcodes).
1655    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1656        possible starting bytes for non-anchored patterns.
1658    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1659        \R, and also a number of cases that involve Unicode properties, both
1660        explicit and implicit when PCRE_UCP is set.
1662    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1663        input, it could crash or give wrong results if characters with values
1664        greater than 0xc0 were present in the subject string. (Detail: it assumed
1665        UTF-8 input when processing these items.)
1667    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1668        size_t is 64-bit (#991).
1670    17. Added a check for running out of memory when PCRE is compiled with
1671        --disable-stack-for-recursion (#990).
1673    18. If the last data line in a file for pcretest does not have a newline on
1674        the end, a newline was missing in the output.
1676    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1677        less than 128) in its various bitmaps. However, there is a facility for
1678        generating tables according to the current locale when PCRE is compiled. It
1679        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1680        characters, are recognized by isspace() and therefore were getting set in
1681        these tables, and indeed these tables seem to approximate to ISO 8859. This
1682        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1683        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1684        which of course cannot start UTF-8 characters. I have changed the code so
1685        that only real ASCII characters (less than 128) and the correct starting
1686        bytes for UTF-8 encodings are set for characters greater than 127 when in
1687        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1688        altogether.)
1690    20. Added the /T option to pcretest so as to be able to run tests with non-
1691        standard character tables, thus making it possible to include the tests
1692        used for 19 above in the standard set of tests.
1694    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1695        reference to a subpattern the other side of a comment that contains an
1696        opening parenthesis caused either an internal compiling error, or a
1697        reference to the wrong subpattern.
1700    Version 8.02 19-Mar-2010
1701    ------------------------
1703    1.  The Unicode data tables have been updated to Unicode 5.2.0.
1705    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
1706        configured.
1708    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
1709        original author of that file, following a query about its status.
1711    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
1712        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1714    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1715        quantifier applied to a forward-referencing subroutine call, could compile
1716        incorrect code or give the error "internal error: previously-checked
1717        referenced subpattern not found".
1719    6.  Both MS Visual Studio and Symbian OS have problems with initializing
1720        variables to point to external functions. For these systems, therefore,
1721        pcre_malloc etc. are now initialized to local functions that call the
1722        relevant global functions.
1724    7.  There were two entries missing in the vectors called coptable and poptable
1725        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1726        I've fixed the data, and added a kludgy way of testing at compile time that
1727        the lengths are correct (equal to the number of opcodes).
1729    8.  Following on from 7, I added a similar kludge to check the length of the
1730        eint vector in pcreposix.c.
1732    9.  Error texts for pcre_compile() are held as one long string to avoid too
1733        much relocation at load time. To find a text, the string is searched,
1734        counting zeros. There was no check for running off the end of the string,
1735        which could happen if a new error number was added without updating the
1736        string.
1738    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1740    11. \K was not working if it appeared in an atomic group or in a group that
1741        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1742        \K is "not well defined" if used in an assertion. PCRE now accepts it if
1743        the assertion is positive, but not if it is negative.
1745    12. Change 11 fortuitously reduced the size of the stack frame used in the
1746        "match()" function of pcre_exec.c by one pointer. Forthcoming
1747        implementation of support for (*MARK) will need an extra pointer on the
1748        stack; I have reserved it now, so that the stack frame size does not
1749        decrease.
1751    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1752        item in branch that calls a recursion is a subroutine call - as in the
1753        second branch in the above example - was incorrectly given the compile-
1754        time error "recursive call could loop indefinitely" because pcre_compile()
1755        was not correctly checking the subroutine for matching a non-empty string.
1757    14. The checks for overrunning compiling workspace could trigger after an
1758        overrun had occurred. This is a "should never occur" error, but it can be
1759        triggered by pathological patterns such as hundreds of nested parentheses.
1760        The checks now trigger 100 bytes before the end of the workspace.
1762    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1765    Version 8.01 19-Jan-2010
1766    ------------------------
1768    1.  If a pattern contained a conditional subpattern with only one branch (in
1769        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
1770        computed the wrong minimum data length (which is of course zero for such
1771        subpatterns). This could cause incorrect "no match" results.
1773    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1774        the pattern is reset in the first branch, pcre_compile() failed with
1775        "internal error: code overflow at offset...". This happened only when
1776        the reset was to the original external option setting. (An optimization
1777        abstracts leading options settings into an external setting, which was the
1778        cause of this.)
1780    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1781        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1782        assertion pattern did not match (meaning that the assertion was true), it
1783        was incorrectly treated as false if the SKIP had been reached during the
1784        matching. This also applied to assertions used as conditions.
1786    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
1787        assertion subpattern, including such a pattern used as a condition,
1788        unpredictable results occurred, instead of the error return
1791    5.  The C++ GlobalReplace function was not working like Perl for the special
1792        situation when an empty string is matched. It now does the fancy magic
1793        stuff that is necessary.
1795    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1796        removed. (These were left over from very, very early versions of PCRE.)
1798    7.  Some cosmetic changes to the code to make life easier when compiling it
1799        as part of something else:
1801        (a) Change DEBUG to PCRE_DEBUG.
1803        (b) In pcre_compile(), rename the member of the "branch_chain" structure
1804            called "current" as "current_branch", to prevent a collision with the
1805            Linux macro when compiled as a kernel module.
1807        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1808            prevent a collision with the Linux macro when compiled as a kernel
1809            module.
1811    8.  In pcre_compile() there are some checks for integer overflows that used to
1812        cast potentially large values to (double). This has been changed to that
1813        when building, a check for int64_t is made, and if it is found, it is used
1814        instead, thus avoiding the use of floating point arithmetic. (There is no
1815        other use of FP in PCRE.) If int64_t is not found, the fallback is to
1816        double.
1818    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
1819        2005 (difference between two addresses compared to an unsigned value).
1821    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1822        custom one, because of the following reported problem in Windows:
1824          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1825              under Win32.
1826          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1827              therefore missing the function definition.
1828          - The compiler thus generates a "C" signature for the test function.
1829          - The linker fails to find the "C" function.
1830          - PCRE fails to configure if asked to do so against libbz2.
1832    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1833        messages were output:
1835          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1836          rerunning libtoolize, to keep the correct libtool macros in-tree.
1837          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1839        I have done both of these things.
1841    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1842        most of the time, it *can* run out if it is given a pattern that contains a
1843        runaway infinite recursion. I updated the discussion in the pcrestack man
1844        page.
1846    13. Now that we have gone to the x.xx style of version numbers, the minor
1847        version may start with zero. Using 08 or 09 is a bad idea because users
1848        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1849        interpreted as invalid octal numbers. I've updated the previous comment in
1850        configure.ac, and also added a check that gives an error if 08 or 09 are
1851        used.
1853    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1854        causing partial matching to fail when the end of the subject matched \W
1855        in a UTF-8 pattern where \W was quantified with a minimum of 3.
1857    15. There were some discrepancies between the declarations in pcre_internal.h
1858        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1859        their definitions. The declarations used "const uschar *" and the
1860        definitions used USPTR. Even though USPTR is normally defined as "const
1861        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1862        reported that: "This difference in casting confuses some C++ compilers, for
1863        example, SunCC recognizes above declarations as different functions and
1864        generates broken code for hbpcre." I have changed the declarations to use
1865        USPTR.
1867    16. GNU libtool is named differently on some systems. The autogen.sh script now
1868        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1869        (FreeBSD).
1871    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1872        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1873        comment: "Figure out how to create a longlong from a string: strtoll and
1874        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1875        instance, but it only takes 2 args instead of 3!"
1877    18. A subtle bug concerned with back references has been fixed by a change of
1878        specification, with a corresponding code fix. A pattern such as
1879        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1880        refers, was giving matches when it shouldn't. For example, xa=xaaa would
1881        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1882        same bug. Such groups have to be quantified to be useful, or contained
1883        inside another quantified group. (If there's no repetition, the reference
1884        can never match.) The problem arises because, having left the group and
1885        moved on to the rest of the pattern, a later failure that backtracks into
1886        the group uses the captured value from the final iteration of the group
1887        rather than the correct earlier one. I have fixed this in PCRE by forcing
1888        any group that contains a reference to itself to be an atomic group; that
1889        is, there cannot be any backtracking into it once it has completed. This is
1890        similar to recursive and subroutine calls.
1893    Version 8.00 19-Oct-09
1894    ----------------------
1896    1.  The table for translating pcre_compile() error codes into POSIX error codes
1897        was out-of-date, and there was no check on the pcre_compile() error code
1898        being within the table. This could lead to an OK return being given in
1899        error.
1901    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
1902        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1903        in a Windows environment.
1905    3.  The pcregrep --count option prints the count for each file even when it is
1906        zero, as does GNU grep. However, pcregrep was also printing all files when
1907        --files-with-matches was added. Now, when both options are given, it prints
1908        counts only for those files that have at least one match. (GNU grep just
1909        prints the file name in this circumstance, but including the count seems
1910        more useful - otherwise, why use --count?) Also ensured that the
1911        combination -clh just lists non-zero counts, with no names.
1913    4.  The long form of the pcregrep -F option was incorrectly implemented as
1914        --fixed_strings instead of --fixed-strings. This is an incompatible change,
1915        but it seems right to fix it, and I didn't think it was worth preserving
1916        the old behaviour.
1918    5.  The command line items --regex=pattern and --regexp=pattern were not
1919        recognized by pcregrep, which required --regex pattern or --regexp pattern
1920        (with a space rather than an '='). The man page documented the '=' forms,
1921        which are compatible with GNU grep; these now work.
1923    6.  No libpcreposix.pc file was created for pkg-config; there was just
1924        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1926    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1927        when UCP support is not needed, by modifying the Python script that
1928        generates it from Unicode data files. This should not matter if the module
1929        is correctly used as a library, but I received one complaint about 50K of
1930        unwanted data. My guess is that the person linked everything into his
1931        program rather than using a library. Anyway, it does no harm.
1933    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1934        was a minimum greater than 1 for a wide character in a possessive
1935        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1936        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1937        character. Chaos in the form of incorrect output or a compiling loop could
1938        result.
1940    9.  The restrictions on what a pattern can contain when partial matching is
1941        requested for pcre_exec() have been removed. All patterns can now be
1942        partially matched by this function. In addition, if there are at least two
1943        slots in the offset vector, the offset of the earliest inspected character
1944        for the match and the offset of the end of the subject are set in them when
1945        PCRE_ERROR_PARTIAL is returned.
1947    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1948        synonymous with PCRE_PARTIAL, for backwards compatibility, and
1949        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1950        and may be more useful for multi-segment matching.
1952    11. Partial matching with pcre_exec() is now more intuitive. A partial match
1953        used to be given if ever the end of the subject was reached; now it is
1954        given only if matching could not proceed because another character was
1955        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1956        string "Z", which now yields "no match" instead of "partial match". In the
1957        case of pcre_dfa_exec(), "no match" is given if every matching path for the
1958        final character ended with (*FAIL).
1960    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1961        if the pattern had a "must contain" character that was already found in the
1962        earlier partial match, unless partial matching was again requested. For
1963        example, with the pattern /dog.(body)?/, the "must contain" character is
1964        "g". If the first part-match was for the string "dog", restarting with
1965        "sbody" failed. This bug has been fixed.
1967    13. The string returned by pcre_dfa_exec() after a partial match has been
1968        changed so that it starts at the first inspected character rather than the
1969        first character of the match. This makes a difference only if the pattern
1970        starts with a lookbehind assertion or \b or \B (\K is not supported by
1971        pcre_dfa_exec()). It's an incompatible change, but it makes the two
1972        matching functions compatible, and I think it's the right thing to do.
1974    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1975        so that the demonstration program is easily available in environments where
1976        PCRE has not been installed from source.
1978    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1979        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1980        library.
1982    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1983        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1984        is not the first non-POSIX option to be added. Clearly some people find
1985        these options useful.
1987    17. If a caller to the POSIX matching function regexec() passes a non-zero
1988        value for nmatch with a NULL value for pmatch, the value of
1989        nmatch is forced to zero.
1991    18. RunGrepTest did not have a test for the availability of the -u option of
1992        the diff command, as RunTest does. It now checks in the same way as
1993        RunTest, and also checks for the -b option.
1995    19. If an odd number of negated classes containing just a single character
1996        interposed, within parentheses, between a forward reference to a named
1997        subpattern and the definition of the subpattern, compilation crashed with
1998        an internal error, complaining that it could not find the referenced
1999        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
2000        [The bug was that it was starting one character too far in when skipping
2001        over the character class, thus treating the ] as data rather than
2002        terminating the class. This meant it could skip too much.]
2004    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
2005        /g option in pcretest when the pattern contains \K, which makes it possible
2006        to have an empty string match not at the start, even when the pattern is
2007        anchored. Updated pcretest and pcredemo to use this option.
2009    21. If the maximum number of capturing subpatterns in a recursion was greater
2010        than the maximum at the outer level, the higher number was returned, but
2011        with unset values at the outer level. The correct (outer level) value is
2012        now given.
2014    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
2015        PCRE did not set those parentheses (unlike Perl). I have now found a way to
2016        make it do so. The string so far is captured, making this feature
2017        compatible with Perl.
2019    23. The tests have been re-organized, adding tests 11 and 12, to make it
2020        possible to check the Perl 5.10 features against Perl 5.10.
2022    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
2023        pattern matches a fixed length string. PCRE did not allow this; now it
2024        does. Neither allows recursion.
2026    25. I finally figured out how to implement a request to provide the minimum
2027        length of subject string that was needed in order to match a given pattern.
2028        (It was back references and recursion that I had previously got hung up
2029        on.) This code has now been added to pcre_study(); it finds a lower bound
2030        to the length of subject needed. It is not necessarily the greatest lower
2031        bound, but using it to avoid searching strings that are too short does give
2032        some useful speed-ups. The value is available to calling programs via
2033        pcre_fullinfo().
2035    26. While implementing 25, I discovered to my embarrassment that pcretest had
2036        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
2037        study optimizations had never been tested with that matching function.
2038        Oops. What is worse, even when it was passed study data, there was a bug in
2039        pcre_dfa_exec() that meant it never actually used it. Double oops. There
2040        were also very few tests of studied patterns with pcre_dfa_exec().
2042    27. If (?| is used to create subpatterns with duplicate numbers, they are now
2043        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
2044        on the other side of the coin, they are no longer allowed to have different
2045        names, because these cannot be distinguished in PCRE, and this has caused
2046        confusion. (This is a difference from Perl.)
2048    28. When duplicate subpattern names are present (necessarily with different
2049        numbers, as required by 27 above), and a test is made by name in a
2050        conditional pattern, either for a subpattern having been matched, or for
2051        recursion in such a pattern, all the associated numbered subpatterns are
2052        tested, and the overall condition is true if the condition is true for any
2053        one of them. This is the way Perl works, and is also more like the way
2054        testing by number works.
2057    Version 7.9 11-Apr-09
2058    ---------------------
2060    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
2061        (pcretest), all targets were linked against these libraries. This included
2062        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
2063        libraries. This caused unwanted dependencies to be created. This problem
2064        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
2065        pcretest is linked with readline.
2067    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
2068        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
2069        moved outside it again, because FALSE and TRUE are already defined in AIX,
2070        but BOOL is not.
2072    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
2073        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
2075    4.  The pcregrep documentation said spaces were inserted as well as colons (or
2076        hyphens) following file names and line numbers when outputting matching
2077        lines. This is not true; no spaces are inserted. I have also clarified the
2078        wording for the --colour (or --color) option.
2080    5.  In pcregrep, when --colour was used with -o, the list of matching strings
2081        was not coloured; this is different to GNU grep, so I have changed it to be
2082        the same.
2084    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
2085        each matching line was coloured. Now it goes on to look for further matches
2086        of any of the test patterns, which is the same behaviour as GNU grep.
2088    7.  A pattern that could match an empty string could cause pcregrep to loop; it
2089        doesn't make sense to accept an empty string match in pcregrep, so I have
2090        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
2091        seems to be how GNU grep behaves. [But see later change 40 for release
2092        8.33.]
2094    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
2095        start or after a newline", because the conditional assertion was not being
2096        correctly handled. The rule now is that both the assertion and what follows
2097        in the first alternative must satisfy the test.
2099    9.  If auto-callout was enabled in a pattern with a conditional group whose
2100        condition was an assertion, PCRE could crash during matching, both with
2101        pcre_exec() and pcre_dfa_exec().
2103    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
2104        used for matching.
2106    11. Unicode property support in character classes was not working for
2107        characters (bytes) greater than 127 when not in UTF-8 mode.
2109    12. Added the -M command line option to pcretest.
2111    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
2113    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
2115    16. Added comments and documentation about mis-use of no_arg in the C++
2116        wrapper.
2118    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
2119        from Martin Jerabek that uses macro names for all relevant character and
2120        string constants.
2122    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
2123        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
2124        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
2125        these, but not everybody uses configure.
2127    19. A conditional group that had only one branch was not being correctly
2128        recognized as an item that could match an empty string. This meant that an
2129        enclosing group might also not be so recognized, causing infinite looping
2130        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
2131        with the subject "ab", where knowledge that the repeated group can match
2132        nothing is needed in order to break the loop.
2134    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
2135        exec(), but without supplying a callout function, matching went wrong.
2137    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
2138        leak if the size of the offset vector was greater than 30. When the vector
2139        is smaller, the saved offsets during recursion go onto a local stack
2140        vector, but for larger vectors malloc() is used. It was failing to free
2141        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
2142        error, in fact).
2144    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
2145        heapframe that is used only when UTF-8 support is enabled. This caused no
2146        problem, but was untidy.
2148    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
2149        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
2150        included within another project.
2152    24. Steven Van Ingelgem's patches to add more options to the CMake support,
2153        slightly modified by me:
2155          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
2156              not building pcregrep.
2158          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
2159              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
2161    25. Forward references, both numeric and by name, in patterns that made use of
2162        duplicate group numbers, could behave incorrectly or give incorrect errors,
2163        because when scanning forward to find the reference group, PCRE was not
2164        taking into account the duplicate group numbers. A pattern such as
2165        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
2167    26. Changed a few more instances of "const unsigned char *" to USPTR, making
2168        the feature of a custom pointer more persuasive (as requested by a user).
2170    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
2171        pcretest.c, inside #ifndefs, because it seems they are sometimes already
2172        pre-defined.
2174    28. Added support for (*UTF8) at the start of a pattern.
2176    29. Arrange for flags added by the "release type" setting in CMake to be shown
2177        in the configuration summary.
2180    Version 7.8 05-Sep-08
2181    ---------------------
2183    1.  Replaced UCP searching code with optimized version as implemented for Ad
2184        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
2185        stage table and inline lookup instead of a function, giving speed ups of 2
2186        to 5 times on some simple patterns that I tested. Permission was given to
2187        distribute the MultiStage2.py script that generates the tables (it's not in
2188        the tarball, but is in the Subversion repository).
2190    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
2191        scripts.
2193    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
2194        a group with a zero qualifier. The result of the study could be incorrect,
2195        or the function might crash, depending on the pattern.
2197    4.  Caseless matching was not working for non-ASCII characters in back
2198        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
2199        It now works when Unicode Property Support is available.
2201    5.  In pcretest, an escape such as \x{de} in the data was always generating
2202        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
2203        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
2204        truncation.
2206    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
2208    7.  Added two (int) casts to pcregrep when printing the difference of two
2209        pointers, in case they are 64-bit values.
2211    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
2212        test 2 if it fails.
2214    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
2215        and a #define of that name to empty if it is not externally set. This is to
2216        allow users of MSVC to set it if necessary.
2218    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
2219        the convenience functions in the pcre_get.c source file.
2221    11. An option change at the start of a pattern that had top-level alternatives
2222        could cause overwriting and/or a crash. This command provoked a crash in
2223        some environments:
2225          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
2227        This potential security problem was recorded as CVE-2008-2371.
2229    12. For a pattern where the match had to start at the beginning or immediately
2230        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
2231        pcre_dfa_exec() could read past the end of the passed subject if there was
2232        no match. To help with detecting such bugs (e.g. with valgrind), I modified
2233        pcretest so that it places the subject at the end of its malloc-ed buffer.
2235    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
2236        exec() might read past the end of the data buffer in UTF-8 mode.
2238    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
2239        the data contained the byte 0x85 as part of a UTF-8 character within its
2240        first line. This applied both to normal and DFA matching.
2242    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
2243        /^[^d]*?$/8 failed to match "abc".
2245    16. Added a missing copyright notice to pcrecpp_internal.h.
2247    17. Make it more clear in the documentation that values returned from
2248        pcre_exec() in ovector are byte offsets, not character counts.
2250    18. Tidied a few places to stop certain compilers from issuing warnings.
2252    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
2253        supplied by Stefan Weber. I made a further small update for 7.8 because
2254        there is a change of source arrangements: the pcre_searchfuncs.c module is
2255        replaced by pcre_ucd.c.
2258    Version 7.7 07-May-08
2259    ---------------------
2261    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
2262        a string to a long long, pretend we don't even have a long long." This is
2263        done by checking for the strtoq, strtoll, and _strtoi64 functions.
2265    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
2266        pre-7.6 versions, which defined a global no_arg variable instead of putting
2267        it in the RE class. (See also #8 below.)
2269    3.  Remove a line of dead code, identified by coverity and reported by Nuno
2270        Lopes.
2272    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
2274        (1) The include/exclude patterns were being applied to the whole pathnames
2275            of files, instead of just to the final components.
2277        (2) If there was more than one level of directory, the subdirectories were
2278            skipped unless they satisfied the include/exclude conditions. This is
2279            inconsistent with GNU grep (and could even be seen as contrary to the
2280            pcregrep specification - which I improved to make it absolutely clear).
2281            The action now is always to scan all levels of directory, and just
2282            apply the include/exclude patterns to regular files.
2284    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
2285        --exclude_dir in the tests to avoid scanning .svn directories.
2287    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
2288        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
2289        doesn't support NULs in patterns.
2291    7.  Added some missing "const"s to declarations of static tables in
2292        pcre_compile.c and pcre_dfa_exec.c.
2294    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
2295        caused by fix #2  above. (Subsequently also a second patch to fix the
2296        first patch. And a third patch - this was a messy problem.)
2298    9.  Applied Craig's patch to remove the use of push_back().
2300    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
2301        matching function regexec().
2303    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
2304        which, however, unlike Perl's \g{...}, are subroutine calls, not back
2305        references. PCRE supports relative numbers with this syntax (I don't think
2306        Oniguruma does).
2308    12. Previously, a group with a zero repeat such as (...){0} was completely
2309        omitted from the compiled regex. However, this means that if the group
2310        was called as a subroutine from elsewhere in the pattern, things went wrong
2311        (an internal error was given). Such groups are now left in the compiled
2312        pattern, with a new opcode that causes them to be skipped at execution
2313        time.
2315    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
2316        to the way PCRE behaves:
2318        (a) A lone ] character is dis-allowed (Perl treats it as data).
2320        (b) A back reference to an unmatched subpattern matches an empty string
2321            (Perl fails the current match path).
2323        (c) A data ] in a character class must be notated as \] because if the
2324            first data character in a class is ], it defines an empty class. (In
2325            Perl it is not possible to have an empty class.) The empty class []
2326            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
2327            The negative empty class [^] matches any one character, independently
2328            of the DOTALL setting.
2330    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
2331        non-existent subpattern following a character class starting with ']' and
2332        containing () gave an internal compiling error instead of "reference to
2333        non-existent subpattern". Fortunately, when the pattern did exist, the
2334        compiled code was correct. (When scanning forwards to check for the
2335        existence of the subpattern, it was treating the data ']' as terminating
2336        the class, so got the count wrong. When actually compiling, the reference
2337        was subsequently set up correctly.)
2339    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
2340        it was being rejected as not supported by pcre_dfa_exec(), even though
2341        other assertions are supported. I have made pcre_dfa_exec() support
2342        (*FAIL).
2344    16. The implementation of 13c above involved the invention of a new opcode,
2345        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
2346        cannot be changed at match time, I realized I could make a small
2347        improvement to matching performance by compiling OP_ALLANY instead of
2348        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
2349        on the OP_ANY path.
2351    17. Compiling pcretest on Windows with readline support failed without the
2352        following two fixes: (1) Make the unistd.h include conditional on
2353        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
2355    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
2356        ncurses library to be included for pcretest when ReadLine support is
2357        requested, but also to allow for it to be overridden. This patch came from
2358        Daniel Bergström.
2360    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
2361        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
2362        any errors with the current Unicode tables. Thanks to Peter Kankowski for
2363        spotting this.
2366    Version 7.6 28-Jan-08
2367    ---------------------
2369    1.  A character class containing a very large number of characters with
2370        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
2371        overflow.
2373    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
2374        HAVE_LONG_LONG is not defined.
2376    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
2377        bring them up to date and include new features. This patch includes:
2379        - Fixed PH's badly added libz and libbz2 support.
2380        - Fixed a problem with static linking.
2381        - Added pcredemo. [But later removed - see 7 below.]
2382        - Fixed dftables problem and added an option.
2383        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
2384            HAVE_LONG_LONG.
2385        - Added readline support for pcretest.
2386        - Added an listing of the option settings after cmake has run.
2388    4.  A user submitted a patch to Makefile that makes it easy to create
2389        "pcre.dll" under mingw when using Configure/Make. I added stuff to
2390        Makefile.am that cause it to include this special target, without
2391        affecting anything else. Note that the same mingw target plus all
2392        the other distribution libraries and programs are now supported
2393        when configuring with CMake (see 6 below) instead of with
2394        Configure/Make.
2396    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
2397        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
2398        exported in the Windows port". It has not yet been confirmed that the patch
2399        solves the problem, but it does no harm.
2401    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
2402        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
2403        with CMake, and also correct the comment about stack recursion.
2405    7.  Remove the automatic building of pcredemo from the ./configure system and
2406        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
2407        of a program that users should build themselves after PCRE is installed, so
2408        building it automatically is not really right. What is more, it gave
2409        trouble in some build environments.
2411    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
2414    Version 7.5 10-Jan-08
2415    ---------------------
2417    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
2418        values in parens when parsing an RE using the C++ wrapper."
2420    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
2421        Characters greater than 255 were excluded from the class instead of being
2422        included.
2424    3.  The same bug as (2) above applied to negated POSIX classes such as
2425        [:^space:].
2427    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
2428        defined or documented. It seems to have been a typo for PCRE_STATIC, so
2429        I have changed it.
2431    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
2432        first named subpattern) and a construct such as (?&a) would reference the
2433        first named subpattern whose name started with "a" (in other words, the
2434        length check was missing). Both these problems are fixed. "Subpattern name
2435        expected" is now given for (?&) (a zero-length name), and this patch also
2436        makes it give the same error for \k'' (previously it complained that that
2437        was a reference to a non-existent subpattern).
2439    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
2440        this is right because (?- can be followed by option settings as well as by
2441        digits. I have, however, made the messages clearer.
2443    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
2444        than the number used in the conditional) now cause a compile-time error.
2445        This is actually not compatible with Perl, which accepts such patterns, but
2446        treats the conditional as always being FALSE (as PCRE used to), but it
2447        seems to me that giving a diagnostic is better.
2449    8.  Change "alphameric" to the more common word "alphanumeric" in comments
2450        and messages.
2452    9.  Fix two occurrences of "backslash" in comments that should have been
2453        "backspace".
2455    10. Remove two redundant lines of code that can never be obeyed (their function
2456        was moved elsewhere).
2458    11. The program that makes PCRE's Unicode character property table had a bug
2459        which caused it to generate incorrect table entries for sequences of
2460        characters that have the same character type, but are in different scripts.
2461        It amalgamated them into a single range, with the script of the first of
2462        them. In other words, some characters were in the wrong script. There were
2463        thirteen such cases, affecting characters in the following ranges:
2465          U+002b0 - U+002c1
2466          U+0060c - U+0060d
2467          U+0061e - U+00612
2468          U+0064b - U+0065e
2469          U+0074d - U+0076d
2470          U+01800 - U+01805
2471          U+01d00 - U+01d77
2472          U+01d9b - U+01dbf
2473          U+0200b - U+0200f
2474          U+030fc - U+030fe
2475          U+03260 - U+0327f
2476          U+0fb46 - U+0fbb1
2477          U+10450 - U+1049d
2479    12. The -o option (show only the matching part of a line) for pcregrep was not
2480        compatible with GNU grep in that, if there was more than one match in a
2481        line, it showed only the first of them. It now behaves in the same way as
2482        GNU grep.
2484    13. If the -o and -v options were combined for pcregrep, it printed a blank
2485        line for every non-matching line. GNU grep prints nothing, and pcregrep now
2486        does the same. The return code can be used to tell if there were any
2487        non-matching lines.
2489    14. Added --file-offsets and --line-offsets to pcregrep.
2491    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
2492        infinitely looping recursion. The bug was that positive lookaheads were not
2493        being skipped when checking for a possible empty match (negative lookaheads
2494        and both kinds of lookbehind were skipped).
2496    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
2497        inclusion of <windows.h> to before rather than after the definition of
2498        INVALID_FILE_ATTRIBUTES (patch from David Byron).
2500    17. Specifying a possessive quantifier with a specific limit for a Unicode
2501        character property caused pcre_compile() to compile bad code, which led at
2502        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
2503        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
2504        caused the error; without that there was no problem.
2506    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
2508    19. Added --enable-pcretest-libreadline.
2510    20. In pcrecpp.cc, the variable 'count' was incremented twice in
2511        RE::GlobalReplace(). As a result, the number of replacements returned was
2512        double what it should be. I removed one of the increments, but Craig sent a
2513        later patch that removed the other one (the right fix) and added unit tests
2514        that check the return values (which was not done before).
2516    21. Several CMake things:
2518        (1) Arranged that, when cmake is used on Unix, the libraries end up with
2519            the names libpcre and libpcreposix, not just pcre and pcreposix.
2521        (2) The above change means that pcretest and pcregrep are now correctly
2522            linked with the newly-built libraries, not previously installed ones.
2526    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
2527        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
2528        UTF-8 newline character). The key issue is that the pattern starts .*;
2529        this means that the match must be either at the beginning, or after a
2530        newline. The bug was in the code for advancing after a failed match and
2531        checking that the new position followed a newline. It was not taking
2532        account of UTF-8 characters correctly.
2534    23. PCRE was behaving differently from Perl in the way it recognized POSIX
2535        character classes. PCRE was not treating the sequence [:...:] as a
2536        character class unless the ... were all letters. Perl, however, seems to
2537        allow any characters between [: and :], though of course it rejects as
2538        unknown any "names" that contain non-letters, because all the known class
2539        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
2540        for example, whereas PCRE did not - it did not recognize a POSIX character
2541        class. This seemed a bit dangerous, so the code has been changed to be
2542        closer to Perl. The behaviour is not identical to Perl, because PCRE will
2543        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
2544        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
2545        Perl does, and where it didn't before.
2547    24. Rewrite so as to remove the single use of %n from pcregrep because in some
2548        Windows environments %n is disabled by default.
2551    Version 7.4 21-Sep-07
2552    ---------------------
2554    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
2555        means that a class such as [\s] counted as "explicit reference to CR or
2556        LF". That isn't really right - the whole point of the change was to try to
2557        help when there was an actual mention of one of the two characters. So now
2558        the change happens only if \r or \n (or a literal CR or LF) character is
2559        encountered.
2561    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
2562        of both had grown to the point where there were only 3 bits left.
2563        Fortunately, there was spare space in the data structure, and so I have
2564        moved the internal flags into a new 16-bit field to free up more option
2565        bits.
2567    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
2568        but did not set the internal JCHANGED flag - either of these is enough to
2569        control the way the "get" function works - but the PCRE_INFO_JCHANGED
2570        facility is supposed to tell if (?J) was ever used, so now (?J) at the
2571        start sets both bits.
2573    4.  Added options (at build time, compile time, exec time) to change \R from
2574        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
2576    5.  doc/pcresyntax.html was missing from the distribution.
2578    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
2579        compatibility, even though it is no longer used.
2581    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
2582        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
2583        windows.h file is present (where different names are used). [This was
2584        reversed later after testing - see 16 below.]
2586    8.  Changed all #include <config.h> to #include "config.h". There were also
2587        some further <pcre.h> cases that I changed to "pcre.h".
2589    9.  When pcregrep was used with the --colour option, it missed the line ending
2590        sequence off the lines that it output.
2592    10. It was pointed out to me that arrays of string pointers cause lots of
2593        relocations when a shared library is dynamically loaded. A technique of
2594        using a single long string with a table of offsets can drastically reduce
2595        these. I have refactored PCRE in four places to do this. The result is
2596        dramatic:
2598          Originally:                          290
2599          After changing UCP table:            187
2600          After changing error message table:   43
2601          After changing table of "verbs"       36
2602          After changing table of Posix names   22
2604        Thanks to the folks working on Gregex for glib for this insight.
2606    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
2607        unicode-properties was also set.
2609    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
2611    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
2612        checked only for CRLF.
2614    14. Added casts to pcretest.c to avoid compiler warnings.
2616    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
2618    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
2619        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
2620        entirely. This removes changes made in 7 above.
2622    17. The CMake files have been updated, and there is now more information about
2623        building with CMake in the NON-UNIX-USE document.
2626    Version 7.3 28-Aug-07
2627    ---------------------
2629     1. In the rejigging of the build system that eventually resulted in 7.1, the
2630        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
2631        brackets there is not right, since it causes compilers to look for an
2632        installed pcre.h, not the version that is in the source that is being
2633        compiled (which of course may be different). I have changed it back to:
2635          #include "pcre.h"
2637        I have a vague recollection that the change was concerned with compiling in
2638        different directories, but in the new build system, that is taken care of
2639        by the VPATH setting the Makefile.
2641     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
2642        when the subject happened to end in the byte 0x85 (e.g. if the last
2643        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
2644        characters but of course it shouldn't be taken as a newline when it is part
2645        of another character. The bug was that, for an unlimited repeat of . in
2646        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
2647        characters when looking for a newline.
2649     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
2651     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
2652        in debug output.
2654     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
2655        long printing in the pcrecpp unittest when running under MinGW.
2657     6. ESC_K was left out of the EBCDIC table.
2659     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
2660        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
2661        limit also applies to "virtual nesting" when a pattern is recursive, and in
2662        this case 1000 isn't so big. I have been able to remove this limit at the
2663        expense of backing off one optimization in certain circumstances. Normally,
2664        when pcre_exec() would call its internal match() function recursively and
2665        immediately return the result unconditionally, it uses a "tail recursion"
2666        feature to save stack. However, when a subpattern that can match an empty
2667        string has an unlimited repetition quantifier, it no longer makes this
2668        optimization. That gives it a stack frame in which to save the data for
2669        checking that an empty string has been matched. Previously this was taken
2670        from the 1000-entry workspace that had been reserved. So now there is no
2671        explicit limit, but more stack is used.
2673     8. Applied Daniel's patches to solve problems with the import/export magic
2674        syntax that is required for Windows, and which was going wrong for the
2675        pcreposix and pcrecpp parts of the library. These were overlooked when this
2676        problem was solved for the main library.
2678     9. There were some crude static tests to avoid integer overflow when computing
2679        the size of patterns that contain repeated groups with explicit upper
2680        limits. As the maximum quantifier is 65535, the maximum group length was
2681        set at 30,000 so that the product of these two numbers did not overflow a
2682        32-bit integer. However, it turns out that people want to use groups that
2683        are longer than 30,000 bytes (though not repeat them that many times).
2684        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
2685        made it possible to implement the integer overflow checks in a much more
2686        dynamic way, which I have now done. The artificial limitation on group
2687        length has been removed - we now have only the limit on the total length of
2688        the compiled pattern, which depends on the LINK_SIZE setting.
2690    10. Fixed a bug in the documentation for get/copy named substring when
2691        duplicate names are permitted. If none of the named substrings are set, the
2692        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
2693        empty string.
2695    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
2696        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
2697        because the ] is interpreted as the first data character and the
2698        terminating ] is not found. PCRE has been made compatible with Perl in this
2699        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
2700        cause memory overwriting.
2702    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
2703        string has been matched (to stop an infinite loop). It was not recognizing
2704        a conditional subpattern that could match an empty string if that
2705        subpattern was within another subpattern. For example, it looped when
2706        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
2707        condition was not nested. This bug has been fixed.
2709    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
2710        past the start of the subject in the presence of bytes with the top bit
2711        set, for example "\x8aBCD".
2713    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
2714        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
2716    14. Optimized (?!) to (*FAIL).
2718    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
2719        This restricts code points to be within the range 0 to 0x10FFFF, excluding
2720        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
2721        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
2722        does: it's just the validity check that is more restrictive.
2724    16. Inserted checks for integer overflows during escape sequence (backslash)
2725        processing, and also fixed erroneous offset values for syntax errors during
2726        backslash processing.
2728    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
2729        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
2731    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
2732        caused an overrun.
2734    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
2735        something other than just ASCII characters) inside a group that had an
2736        unlimited repeat caused a loop at compile time (while checking to see
2737        whether the group could match an empty string).
2739    20. Debugging a pattern containing \p or \P could cause a crash. For example,
2740        [\P{Any}] did so. (Error in the code for printing property names.)
2742    21. An orphan \E inside a character class could cause a crash.
2744    22. A repeated capturing bracket such as (A)? could cause a wild memory
2745        reference during compilation.
2747    23. There are several functions in pcre_compile() that scan along a compiled
2748        expression for various reasons (e.g. to see if it's fixed length for look
2749        behind). There were bugs in these functions when a repeated \p or \P was
2750        present in the pattern. These operators have additional parameters compared
2751        with \d, etc, and these were not being taken into account when moving along
2752        the compiled data. Specifically:
2754        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
2755            length.
2757        (b) An item such as \pL+ within a repeated group could cause crashes or
2758            loops.
2760        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
2761            "reference to non-existent subpattern" error.
2763        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
2765    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
2766        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
2768    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
2770    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
2771        character were causing crashes (broken optimization).
2773    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
2774        \p or \P) caused a compile-time loop.
2776    28. More problems have arisen in unanchored patterns when CRLF is a valid line
2777        break. For example, the unstudied pattern [\r\n]A does not match the string
2778        "\r\nA" because change 7.0/46 below moves the current point on by two
2779        characters after failing to match at the start. However, the pattern \nA
2780        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
2781        the same is true. There doesn't seem any very clean way out of this, but
2782        what I have chosen to do makes the common cases work: PCRE now takes note
2783        of whether there can be an explicit match for \r or \n anywhere in the
2784        pattern, and if so, 7.0/46 no longer applies. As part of this change,
2785        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
2786        pattern has explicit CR or LF references.
2788    29. Added (*CR) etc for changing newline setting at start of pattern.
2791    Version 7.2 19-Jun-07
2792  ---------------------  ---------------------
2794   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
# Line 21  Version 7.2 01-May-07 Line 2808  Version 7.2 01-May-07
2808      stack recursion. This gives a massive performance boost under BSD, but just      stack recursion. This gives a massive performance boost under BSD, but just
2809      a small improvement under Linux. However, it saves one field in the frame      a small improvement under Linux. However, it saves one field in the frame
2810      in all cases.      in all cases.
2812   6. Added more features from the forthcoming Perl 5.10:   6. Added more features from the forthcoming Perl 5.10:
2814      (a) (?-n) (where n is a string of digits) is a relative subroutine or      (a) (?-n) (where n is a string of digits) is a relative subroutine or
2815          recursion call. It refers to the nth most recently opened parentheses.          recursion call. It refers to the nth most recently opened parentheses.
2817      (b) (?+n) is also a relative subroutine call; it refers to the nth next      (b) (?+n) is also a relative subroutine call; it refers to the nth next
2818          to be opened parentheses.          to be opened parentheses.
2820      (c) Conditions that refer to capturing parentheses can be specified      (c) Conditions that refer to capturing parentheses can be specified
2821          relatively, for example, (?(-2)... or (?(+3)...          relatively, for example, (?(-2)... or (?(+3)...
2823        (d) \K resets the start of the current match so that everything before
2824            is not part of it.
2826        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
2828        (f) \g{name} is another synonym - part of Perl 5.10's unification of
2829            reference syntax.
2831        (g) (?| introduces a group in which the numbering of parentheses in each
2832            alternative starts with the same number.
2834        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
2836     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
2839     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
2840        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
2841        for detecting groups that can match an empty string.
2843     9. A pattern with a very large number of alternatives (more than several
2844        hundred) was running out of internal workspace during the pre-compile
2845        phase, where pcre_compile() figures out how much memory will be needed. A
2846        bit of new cunning has reduced the workspace needed for groups with
2847        alternatives. The 1000-alternative test pattern now uses 12 bytes of
2848        workspace instead of running out of the 4096 that are available.
2850    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
2852    11. Applied patch from Google to remove an optimization that didn't quite work.
2853        The report of the bug said:
2855          pcrecpp::RE("a*").FullMatch("aaa") matches, while
2856          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
2857          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
2859    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
2860        it matched the wrong number of bytes.
2863  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07
2864  ---------------------  ---------------------

Removed from v.167  
changed lines
  Added in v.1494

  ViewVC Help
Powered by ViewVC 1.1.5