ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 420 by ph10, Wed Aug 12 17:32:27 2009 UTC revision 1364 by ph10, Sat Oct 5 15:45:11 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.00 ??-???-??  Version 8.34 xx-xxxx-201x
5    --------------------------
7    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
8        executable memory. Patch inspired by Carsten Klein.
10    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
11        this macro is never tested and has no effect, because the work to support
12        coverage involves only compiling and linking options and special targets in
13        the Makefile. The comment in config.h implied that defining the macro would
14        enable coverage support, which is totally false. There was also support for
15        setting this macro in the CMake files (my fault, I just copied it from
16        configure). SUPPORT_GCOV has now been removed.
18    3.  Make a small performance improvement in strlen16() and strlen32() in
19        pcretest.
21    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
22        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
23        these cases). There was also one in pcretest.c.
25    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
27    6.  In UTF mode, the code for checking whether a group could match an empty
28        string (which is used for indefinitely repeated groups to allow for
29        breaking an infinite loop) was broken when the group contained a repeated
30        negated single-character class with a character that occupied more than one
31        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
32        UTF-8 mode). The effect was undefined: the group might or might not be
33        deemed as matching an empty string, or the program might have crashed.
35    7.  The code for checking whether a group could match an empty string was not
36        recognizing that \h, \H, \v, \V, and \R must match a character.
38    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
39        an empty string. If it can, pcretest shows this in its information output.
41    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
42        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
43        matched by pcre_exec() without using JIT:
45        (a) If the rest of the pattern did not match after a maximal run of
46            grapheme clusters, the code for backing up to try with fewer of them
47            did not always back up over a full grapheme when characters that do not
48            have the modifier quality were involved, e.g. Hangul syllables.
50        (b) If the match point in a subject started with modifier character, and
51            there was no match, the code could incorrectly back up beyond the match
52            point, and potentially beyond the first character in the subject,
53            leading to a segfault or an incorrect match result.
55    10. A conditional group with an assertion condition could lead to PCRE
56        recording an incorrect first data item for a match if no other first data
57        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
58        first data item, and therefore matched "ca" after "c" instead of at the
59        start.
61    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
62        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
64    12. The source of pcregrep now includes z/OS-specific code so that it can be
65        compiled for z/OS as part of the special z/OS distribution.
67    13. Added the -T and -TM options to pcretest.
69    14. The code in pcre_compile.c for creating the table of named capturing groups
70        has been refactored. Instead of creating the table dynamically during the
71        actual compiling pass, the information is remembered during the pre-compile
72        pass (on the stack unless there are more than 20 named groups, in which
73        case malloc() is used) and the whole table is created before the actual
74        compile happens. This has simplified the code (it is now nearly 150 lines
75        shorter) and prepared the way for better handling of references to groups
76        with duplicate names.
78    15. A back reference to a named subpattern when there is more than one of the
79        same name now checks them in the order in which they appear in the pattern.
80        The first one that is set is used for the reference. Previously only the
81        first one was inspected. This change makes PCRE more compatible with Perl.
83    16. Unicode character properties were updated from Unicode 6.3.0.
85    17. The compile-time code for auto-possessification has been refactored, based
86        on a patch by Zoltan Herczeg. It now happens after instead of during
87        compilation. The code is cleaner, and more cases are handled. The option
88        PCRE_NO_AUTO_POSSESSIFY is added for testing purposes, and the -O and /O
89        options in pcretest are provided to set it.
91    18. The character VT has been added to the set of characters that match \s and
92        are generally treated as white space, following this same change in Perl
93        5.18. There is now no difference between "Perl space" and "POSIX space".
96    Version 8.33 28-May-2013
97    ------------------------
99    1.  Added 'U' to some constants that are compared to unsigned integers, to
100        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
101        variables that are added to signed variables, to ensure the result is
102        signed and can be negated.
104    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
105        CMake config files.
107    3.  Revise the creation of config.h.generic so that all boolean macros are
108        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
109        overriding via -D on the command line possible.
111    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
112        to unsigned int is reported to make a quite noticeable speed difference in
113        a specific Windows environment. Testing on Linux did also appear to show
114        some benefit (and it is clearly not harmful). Also fixed the definition of
115        Xop which should be unsigned.
117    5.  Related to (4), changing the definition of the intermediate variable cc
118        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
119        improvements.
121    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
122        unnecessary spaces.
124    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
125        and later.
127    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
129    9.  Optimizing fast_forward_start_bits in JIT.
131    10. Adding support for callouts in JIT, and fixing some issues revealed
132        during this work. Namely:
134        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
136        (b) Minimum length was not checked before the matching is started.
138    11. The value of capture_last that is passed to callouts was incorrect in some
139        cases when there was a capture on one path that was subsequently abandoned
140        after a backtrack. Also, the capture_last value is now reset after a
141        recursion, since all captures are also reset in this case.
143    12. The interpreter no longer returns the "too many substrings" error in the
144        case when an overflowing capture is in a branch that is subsequently
145        abandoned after a backtrack.
147    13. In the pathological case when an offset vector of size 2 is used, pcretest
148        now prints out the matched string after a yield of 0 or 1.
150    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
151        Only supported by the JIT compiler at the moment.
153    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
155    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
156        offset of the starting point of the matching process, provided the offsets
157        vector is large enough.
159    17. The \A escape now records a lookbehind value of 1, though its execution
160        does not actually inspect the previous character. This is to ensure that,
161        in partial multi-segment matching, at least one character from the old
162        segment is retained when a new segment is processed. Otherwise, if there
163        are no lookbehinds in the pattern, \A might match incorrectly at the start
164        of a new segment.
166    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
168    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
169        gives some modest performance improvement in 8-bit mode.
171    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
172        be expressed in certain programming languages using Universal Character
173        Names.
175    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
176        which points out that "non characters" are not "characters that may not
177        appear in Unicode strings" but rather "characters that are reserved for
178        internal use and have only local meaning".
180    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
181        there was a conditional group that depended on an assertion, if the
182        assertion was false, the callout that immediately followed the alternation
183        in the condition was skipped when pcre_exec() was used for matching.
185    23. Allow an explicit callout to be inserted before an assertion that is the
186        condition for a conditional group, for compatibility with automatic
187        callouts, which always insert a callout at this point.
189    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
190        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
192    25. (*PRUNE) is now supported by the JIT compiler.
194    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
196    27. Fix the case where there are two or more SKIPs with arguments that may be
197        ignored.
199    28. (*SKIP) is now supported by the JIT compiler.
201    29. (*THEN) is now supported by the JIT compiler.
203    30. Update RunTest with additional test selector options.
205    31. The way PCRE handles backtracking verbs has been changed in two ways.
207        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
208        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
209        backtracking. In some cases this makes it more Perl-compatible, but Perl's
210        rather obscure rules do not always do the same thing.
212        (2) Previously, backtracking verbs were confined within assertions. This is
213        no longer the case for positive assertions, except for (*ACCEPT). Again,
214        this sometimes improves Perl compatibility, and sometimes does not.
216    32. A number of tests that were in test 2 because Perl did things differently
217        have been moved to test 1, because either Perl or PCRE has changed, and
218        these tests are now compatible.
220    32. Backtracking control verbs are now handled in the same way in JIT and
221        interpreter.
223    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
224        contained a forward subroutine reference caused a compile error.
226    34. Auto-detect and optimize limited repetitions in JIT.
228    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
229        blocking (*UTF) etc.
231    36. In the interpreter, maximizing pattern repetitions for characters and
232        character types now use tail recursion, which reduces stack usage.
234    37. The value of the max lookbehind was not correctly preserved if a compiled
235        and saved regex was reloaded on a host of different endianness.
237    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
238        of the compiled pattern block, expand the flags field from 16 to 32 bits
239        because it was almost full.
241    39. Try madvise first before posix_madvise.
243    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
244        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
245        original change locked out all matches of empty strings. This has been
246        changed so that one match of an empty string per line is recognized.
247        Subsequent searches on the same line (for colouring or for --only-matching,
248        for example) do not recognize empty strings.
250    41. Applied a user patch to fix a number of spelling mistakes in comments.
252    42. Data lines longer than 65536 caused pcretest to crash.
254    43. Clarified the data type for length and startoffset arguments for pcre_exec
255        and pcre_dfa_exec in the function-specific man pages, where they were
256        explicitly stated to be in bytes, never having been updated. I also added
257        some clarification to the pcreapi man page.
259    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
260        a segmentation fault.
263    Version 8.32 30-November-2012
264    -----------------------------
266    1.  Improved JIT compiler optimizations for first character search and single
267        character iterators.
269    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
270        Patch by Daniel Richard G.
272    3.  Single character iterator optimizations in the JIT compiler.
274    4.  Improved JIT compiler optimizations for character ranges.
276    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
277        Reported by Giuseppe D'Angelo.
279    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
280        of a line, was being set incorrectly in cases where .* appeared inside
281        atomic brackets at the start of a pattern, or where there was a subsequent
282        *PRUNE or *SKIP.
284    7.  Improved instruction cache flush for POWER/PowerPC.
285        Patch by Daniel Richard G.
287    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
288        grep:
290        (a) There is now no limit to the number of patterns to be matched.
292        (b) An error is given if a pattern is too long.
294        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
295            are now supported.
297        (d) --exclude-from and --include-from (multiple use) have been added.
299        (e) Exclusions and inclusions now apply to all files and directories, not
300            just to those obtained from scanning a directory recursively.
302        (f) Multiple uses of -f and --file-list are now supported.
304        (g) In a Windows environment, the default for -d has been changed from
305            "read" (the GNU grep default) to "skip", because otherwise the presence
306            of a directory in the file list provokes an error.
308        (h) The documentation has been revised and clarified in places.
310    9.  Improve the matching speed of capturing brackets.
312    10. Changed the meaning of \X so that it now matches a Unicode extended
313        grapheme cluster.
315    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
316        out POSIX threads when JIT support is configured.
318    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
320    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
321        structure could go wrong in environments where size_t is not the same size
322        as int.
324    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
325        set.
327    15. The EBCDIC support had decayed; later updates to the code had included
328        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
329        general tidy up of EBCDIC-related issues, and the documentation was also
330        not quite right. There is now a test that can be run on ASCII systems to
331        check some of the EBCDIC-related things (but is it not a full test).
333    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
334        in a small tidy to the code.
336    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
338    18. If the --only-matching (-o) option in pcregrep is specified multiple
339        times, each one causes appropriate output. For example, -o1 -o2 outputs the
340        substrings matched by the 1st and 2nd capturing parentheses. A separating
341        string can be specified by --om-separator (default empty).
343    19. Improving the first n character searches.
345    20. Turn case lists for horizontal and vertical white space into macros so that
346        they are defined only once.
348    21. This set of changes together give more compatible Unicode case-folding
349        behaviour for characters that have more than one other case when UCP
350        support is available.
352        (a) The Unicode property table now has offsets into a new table of sets of
353            three or more characters that are case-equivalent. The MultiStage2.py
354            script that generates these tables (the pcre_ucd.c file) now scans
355            CaseFolding.txt instead of UnicodeData.txt for character case
356            information.
358        (b) The code for adding characters or ranges of characters to a character
359            class has been abstracted into a generalized function that also handles
360            case-independence. In UTF-mode with UCP support, this uses the new data
361            to handle characters with more than one other case.
363        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
364            whose other case is greater than 256 are now correctly matched
365            caselessly. Previously, the high codepoint matched the low one, but not
366            vice versa.
368        (d) The processing of \h, \H, \v, and \ in character classes now makes use
369            of the new class addition function, using character lists defined as
370            macros alongside the case definitions of 20 above.
372        (e) Caseless back references now work with characters that have more than
373            one other case.
375        (f) General caseless matching of characters with more than one other case
376            is supported.
378    22. Unicode character properties were updated from Unicode 6.2.0
380    23. Improved CMake support under Windows. Patch by Daniel Richard G.
382    24. Add support for 32-bit character strings, and UTF-32
384    25. Major JIT compiler update (code refactoring and bugfixing).
385        Experimental Sparc 32 support is added.
387    26. Applied a modified version of Daniel Richard G's patch to create
388        pcre.h.generic and config.h.generic by "make" instead of in the
389        PrepareRelease script.
391    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
392        pcre_compile.c when checking for a zero character.
394    28. Introducing a native interface for JIT. Through this interface, the compiled
395        machine code can be directly executed. The purpose of this interface is to
396        provide fast pattern matching, so several sanity checks are not performed.
397        However, feature tests are still performed. The new interface provides
398        1.4x speedup compared to the old one.
400    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
401        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
402        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
404    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
405        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
406        the "old" RFC 2279). Instead, it ended up passing a negative length to
407        pcre_exec().
409    31. Add support for GCC's visibility feature to hide internal functions.
411    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
412        "unknown -C option" after outputting 0 or 1.
414    33. There is now support for generating a code coverage report for the test
415        suite in environments where gcc is the compiler and lcov is installed. This
416        is mainly for the benefit of the developers.
418    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
419        unaddressable using valgrind annotations, allowing valgrind to detect
420        invalid memory accesses. This is mainly for the benefit of the developers.
422    25. (*UTF) can now be used to start a pattern in any of the three libraries.
424    26. Give configure error if --enable-cpp but no C++ compiler found.
427    Version 8.31 06-July-2012
428    -------------------------
430    1.  Fixing a wrong JIT test case and some compiler warnings.
432    2.  Removed a bashism from the RunTest script.
434    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
435        to unsigned type, result still unsigned" that was given by an MS compiler
436        on encountering the code "-sizeof(xxx)".
438    4.  Partial matching support is added to the JIT compiler.
440    5.  Fixed several bugs concerned with partial matching of items that consist
441        of more than one character:
443        (a) /^(..)\1/ did not partially match "aba" because checking references was
444            done on an "all or nothing" basis. This also applied to repeated
445            references.
447        (b) \R did not give a hard partial match if \r was found at the end of the
448            subject.
450        (c) \X did not give a hard partial match after matching one or more
451            characters at the end of the subject.
453        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
454            a partial match for the string "\r".
456        (e) When newline was set to CRLF, the metacharacter "." did not recognize
457            a partial match for a CR character at the end of the subject string.
459    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
460        running pcretest, the text "(JIT)" added to the output whenever JIT is
461        actually used to run the match.
463    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
464        or /S+[+] with a digit between 1 and 7.
466    8.  OP_NOT now supports any UTF character not just single-byte ones.
468    9.  (*MARK) control verb is now supported by the JIT compiler.
470    10. The command "./RunTest list" lists the available tests without actually
471        running any of them. (Because I keep forgetting what they all are.)
475    12. Applied a (slightly modified) user-supplied patch that improves performance
476        when the heap is used for recursion (compiled with --disable-stack-for-
477        recursion). Instead of malloc and free for each heap frame each time a
478        logical recursion happens, frames are retained on a chain and re-used where
479        possible. This sometimes gives as much as 30% improvement.
481    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
482        call.
484    14. As documented, (*COMMIT) is now confined to within a positive assertion.
486    15. It is now possible to link pcretest with libedit as an alternative to
487        libreadline.
489    16. (*COMMIT) control verb is now supported by the JIT compiler.
491    17. The Unicode data tables have been updated to Unicode 6.1.0.
493    18. Added --file-list option to pcregrep.
495    19. Added binary file support to pcregrep, including the -a, --binary-files,
496        -I, and --text options.
498    20. The madvise function is renamed for posix_madvise for QNX compatibility
499        reasons. Fixed by Giuseppe D'Angelo.
501    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
503    22. Changed the option for creating symbolic links for 16-bit man pages from
504        -s to -sf so that re-installing does not cause issues.
506    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
508    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
509        matches in certain environments (the workspace was not being correctly
510        retained). Also added to pcre_dfa_exec() a simple plausibility check on
511        some of the workspace data at the beginning of a restart.
513    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
514        was not doing so when it should - probably a typo introduced by SVN 528
515        (change 8.10/14).
517    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
518        \w+ when the character tables indicated that \x{c4} was a word character.
519        There were several related cases, all because the tests for doing a table
520        lookup were testing for characters less than 127 instead of 255.
522    27. If a pattern contains capturing parentheses that are not used in a match,
523        their slots in the ovector are set to -1. For those that are higher than
524        any matched groups, this happens at the end of processing. In the case when
525        there were back references that the ovector was too small to contain
526        (causing temporary malloc'd memory to be used during matching), and the
527        highest capturing number was not used, memory off the end of the ovector
528        was incorrectly being set to -1. (It was using the size of the temporary
529        memory instead of the true size.)
531    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
532        ovector size, it uses memory at the end of the block that it has got.
534    29. Check for an overlong MARK name and give an error at compile time. The
535        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
537    30. JIT compiler update.
539    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
540        Rill for the patch.
542    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
544    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
546    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
547        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
548        was enabled.
550    35. Improve JIT code generation for greedy plus quantifier.
552    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
553        1 to "aa" instead of to an empty string. The bug affected repeated groups
554        that could potentially match an empty string.
556    37. Optimizing single character iterators in JIT.
558    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
559        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
560        codepoints that are too big for the mode are faulted, and in a UTF mode,
561        disallowed codepoints are also faulted.
563    39. If PCRE was compiled with UTF support, in three places in the DFA
564        matcher there was code that should only have been obeyed in UTF mode, but
565        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
566        processing when bytes with values greater than 127 were present. In 16-bit
567        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
568        both cases the values are those that cannot be the first data item in a UTF
569        character. The three items that might have provoked this were recursions,
570        possessively repeated groups, and atomic groups.
572    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
573        and pcregrep, because some OS require shared objects to be explicitly
574        passed to ld, causing the link step to fail if they are not.
576    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
577        mode, patterns that started with \h* or \R* might be incorrectly matched.
580    Version 8.30 04-February-2012
581    -----------------------------
583    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
584        name is defined in ctype.h.
586    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
587        only in quite long subpatterns.
589    3.  Removed the function pcre_info(), which has been obsolete and deprecated
590        since it was replaced by pcre_fullinfo() in February 2000.
592    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
593        match a (*MARK), and the match failed at the start of the subject, a
594        reference to memory before the start of the subject could occur. This bug
595        was introduced by fix 17 of release 8.21.
597    5.  A reference to an unset group with zero minimum repetition was giving
598        totally wrong answers (in non-JavaScript-compatibility mode). For example,
599        /(another)?(\1?)test/ matched against "hello world test". This bug was
600        introduced in release 8.13.
602    6.  Add support for 16-bit character strings (a large amount of work involving
603        many changes and refactorings).
605    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
606        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
607        from a file.
609    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
610        rounding is not applied in this particular case).
612    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
613        if they appear, or are escaped, in patterns.
615    10. Get rid of a number of -Wunused-but-set-variable warnings.
617    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
618        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
619        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
620        also returns the mark "x". This bug applied to capturing parentheses,
621        non-capturing parentheses, and atomic parentheses. It also applied to some
622        assertions.
624    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
625        information out of configure.ac instead of relying on pcre.h.generic, which
626        is not stored in the repository.
628    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
629        -lreadline.
631    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
633    15. Applied Graycode's patch to put the top-level frame on the stack rather
634        than the heap when not using the stack for recursion. This gives a
635        performance improvement in many cases when recursion is not deep.
637    16. Experimental code added to "pcretest -C" to output the stack frame size.
640    Version 8.21 12-Dec-2011
641    ------------------------
643    1.  Updating the JIT compiler.
645    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
646        are added as well.
648    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
649        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
650        calling _pcre_jit_exec. Some extra comments are added.
652    4.  (*MARK) settings inside atomic groups that do not contain any capturing
653        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
654        was introduced by change 18 for 8.20.
656    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
657        ECMA-262 standard.
659    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
660        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
661        This bug was probably introduced by change 9 of 8.13.
663    7.  While fixing 6 above, I noticed that a number of other items were being
664        incorrectly rejected as "not fixed length". This arose partly because newer
665        opcodes had not been added to the fixed-length checking code. I have (a)
666        corrected the bug and added tests for these items, and (b) arranged for an
667        error to occur if an unknown opcode is encountered while checking for fixed
668        length instead of just assuming "not fixed length". The items that were
669        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
670        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
671        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
673    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
674        being incorrectly compiled and would have given unpredicatble results.
676    9.  A possessively repeated subpattern with minimum repeat count greater than
677        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
678        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
679        the first (A) could occur when it should not.
681    10. Add a cast and remove a redundant test from the code.
683    11. JIT should use pcre_malloc/pcre_free for allocation.
685    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
686        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
687        is anything other than /usr, -L is still shown).
689    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
691    14. Perl does not support \N without a following name in a [] class; PCRE now
692        also gives an error.
694    15. If a forward reference was repeated with an upper limit of around 2000,
695        it caused the error "internal error: overran compiling workspace". The
696        maximum number of forward references (including repeats) was limited by the
697        internal workspace, and dependent on the LINK_SIZE. The code has been
698        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
699        the default depends on LINK_SIZE. There is a new upper limit (for safety)
700        of around 200,000 forward references. While doing this, I also speeded up
701        the filling in of repeated forward references.
703    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
704        incorrectly expecting the subject to contain another "a" after the start.
706    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
707        in the match, the SKIP should be ignored. This was not happening; instead
708        the SKIP was being treated as NOMATCH. For patterns such as
709        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
710        tested.
712    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
713        now much more compatible with Perl, in particular in cases where the result
714        is a non-match for a non-anchored pattern. For example, if
715        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
716        "m", where previously it did not return a name. A side effect of this
717        change is that for partial matches, the last encountered mark name is
718        returned, as for non matches. A number of tests that were previously not
719        Perl-compatible have been moved into the Perl-compatible test files. The
720        refactoring has had the pleasing side effect of removing one argument from
721        the match() function, thus reducing its stack requirements.
723    19. If the /S+ option was used in pcretest to study a pattern using JIT,
724        subsequent uses of /S (without +) incorrectly behaved like /S+.
726    21. Retrieve executable code size support for the JIT compiler and fixing
727        some warnings.
729    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
730        not work when the shorter character appeared right at the end of the
731        subject string.
733    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
734        systems.
736    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
737        output it when the /M option is used in pcretest.
739    25. The CheckMan script was not being included in the distribution. Also, added
740        an explicit "perl" to run Perl scripts from the PrepareRelease script
741        because this is reportedly needed in Windows.
743    26. If study data was being save in a file and studying had not found a set of
744        "starts with" bytes for the pattern, the data written to the file (though
745        never used) was taken from uninitialized memory and so caused valgrind to
746        complain.
748    27. Updated RunTest.bat as provided by Sheri Pierce.
750    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
752    29. Computation of memory usage for the table of capturing group names was
753        giving an unnecessarily large value.
756    Version 8.20 21-Oct-2011
757    ------------------------
759    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
760        a POSIX class. After further experiments with Perl, which convinced me that
761        Perl has bugs and confusions, a closing square bracket is no longer allowed
762        in a POSIX name. This bug also affected patterns with classes that started
763        with full stops.
765    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
766        captured substring, but while checking the failing first alternative,
767        substring 1 is temporarily captured. If the output vector supplied to
768        pcre_exec() was not big enough for this capture, the yield of the function
769        was still zero ("insufficient space for captured substrings"). This cannot
770        be totally fixed without adding another stack variable, which seems a lot
771        of expense for a edge case. However, I have improved the situation in cases
772        such as /(a)(b)x|abc/ matched against "abc", where the return code
773        indicates that fewer than the maximum number of slots in the ovector have
774        been set.
776    3.  Related to (2) above: when there are more back references in a pattern than
777        slots in the output vector, pcre_exec() uses temporary memory during
778        matching, and copies in the captures as far as possible afterwards. It was
779        using the entire output vector, but this conflicts with the specification
780        that only 2/3 is used for passing back captured substrings. Now it uses
781        only the first 2/3, for compatibility. This is, of course, another edge
782        case.
784    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
785        main code base, and can be used by building with --enable-jit. When this is
786        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
787        runtime --no-jit option is given.
789    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
790        ovector, the return from the function was zero, implying that there were
791        other matches that did not fit. The correct "exactly full" value is now
792        returned.
794    6.  If a subpattern that was called recursively or as a subroutine contained
795        (*PRUNE) or any other control that caused it to give a non-standard return,
796        invalid errors such as "Error -26 (nested recursion at the same subject
797        position)" or even infinite loops could occur.
799    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
800        computing the minimum length on reaching *ACCEPT, and so ended up with the
801        wrong value of 1 rather than 0. Further investigation indicates that
802        computing a minimum subject length in the presence of *ACCEPT is difficult
803        (think back references, subroutine calls), and so I have changed the code
804        so that no minimum is registered for a pattern that contains *ACCEPT.
806    8.  If (*THEN) was present in the first (true) branch of a conditional group,
807        it was not handled as intended. [But see 16 below.]
809    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
810        Sheri Pierce.
812    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
813        the first byte in a match must be "a".
815    11. Change 17 for 8.13 increased the recursion depth for patterns like
816        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
817        pattern contains any instances of (*THEN). If it does not, the old
818        optimizations are restored. It would be nice to do this on a per-group
819        basis, but at the moment that is not feasible.
821    12. In some environments, the output of pcretest -C is CRLF terminated. This
822        broke RunTest's code that checks for the link size. A single white space
823        character after the value is now allowed for.
825    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
826        For "fr", it uses the Windows-specific input and output files.
828    14. If (*THEN) appeared in a group that was called recursively or as a
829        subroutine, it did not work as intended. [But see next item.]
831    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
832        pattern fragments (but not containing any | characters). If A and B are
833        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
834        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
835        D. In other words, Perl considers parentheses that do not contain any |
836        characters to be part of a surrounding alternative, whereas PCRE was
837        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
838        differently. PCRE now behaves in the same way as Perl, except in the case
839        of subroutine/recursion calls such as (?1) which have in any case always
840        been different (but PCRE had them first :-).
842    16. Related to 15 above: Perl does not treat the | in a conditional group as
843        creating alternatives. Such a group is treated in the same way as an
844        ordinary group without any | characters when processing (*THEN). PCRE has
845        been changed to match Perl's behaviour.
847    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
848        RunGrepTest script failed.
850    18. Change 22 for version 13 caused atomic groups to use more stack. This is
851        inevitable for groups that contain captures, but it can lead to a lot of
852        stack use in large patterns. The old behaviour has been restored for atomic
853        groups that do not contain any capturing parentheses.
855    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
856        suppress the check for a minimum subject length at run time. (If it was
857        given to pcre_exec() or pcre_dfa_exec() it did work.)
859    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
860        fail to work when decoding hex characters in data strings in EBCDIC
861        environments.
863    21. It appears that in at least one Mac OS environment, the isxdigit() function
864        is implemented as a macro that evaluates to its argument more than once,
865        contravening the C 90 Standard (I haven't checked a later standard). There
866        was an instance in pcretest which caused it to go wrong when processing
867        \x{...} escapes in subject strings. The has been rewritten to avoid using
868        things like p++ in the argument of isxdigit().
871    Version 8.13 16-Aug-2011
872    ------------------------
874    1.  The Unicode data tables have been updated to Unicode 6.0.0.
876    2.  Two minor typos in pcre_internal.h have been fixed.
878    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
879        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
880        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
882    4.  There were a number of related bugs in the code for matching backrefences
883        caselessly in UTF-8 mode when codes for the characters concerned were
884        different numbers of bytes. For example, U+023A and U+2C65 are an upper
885        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
886        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
887        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
888        2-byte code at the end of the subject (it thought there wasn't enough data
889        left).
891    5.  Comprehensive information about what went wrong is now returned by
892        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
893        as the output vector has at least 2 elements. The offset of the start of
894        the failing character and a reason code are placed in the vector.
896    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
897        now returned is for the first byte of the failing character, instead of the
898        last byte inspected. This is an incompatible change, but I hope it is small
899        enough not to be a problem. It makes the returned offset consistent with
900        pcre_exec() and pcre_dfa_exec().
902    7.  pcretest now gives a text phrase as well as the error number when
903        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
904        failure, the offset and reason code are output.
906    8.  When \R was used with a maximizing quantifier it failed to skip backwards
907        over a \r\n pair if the subsequent match failed. Instead, it just skipped
908        back over a single character (\n). This seems wrong (because it treated the
909        two characters as a single entity when going forwards), conflicts with the
910        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
911        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
912        has been changed.
914    9.  Some internal refactoring has changed the processing so that the handling
915        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
916        time (the PCRE_DOTALL option was changed this way some time ago: version
917        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
918        which was always a bit of a fudge. It also means that there is one less
919        argument for the match() function, which reduces its stack requirements
920        slightly. This change also fixes an incompatibility with Perl: the pattern
921        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
923    10. More internal refactoring has drastically reduced the number of recursive
924        calls to match() for possessively repeated groups such as (abc)++ when
925        using pcre_exec().
927    11. While implementing 10, a number of bugs in the handling of groups were
928        discovered and fixed:
930        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
931        (a|)*(?1) gave a compile-time internal error.
932        ((a|)+)+  did not notice that the outer group could match an empty string.
933        (^a|^)+   was not marked as anchored.
934        (.*a|.*)+ was not marked as matching at start or after a newline.
936    12. Yet more internal refactoring has removed another argument from the match()
937        function. Special calls to this function are now indicated by setting a
938        value in a variable in the "match data" data block.
940    13. Be more explicit in pcre_study() instead of relying on "default" for
941        opcodes that mean there is no starting character; this means that when new
942        ones are added and accidentally left out of pcre_study(), testing should
943        pick them up.
945    14. The -s option of pcretest has been documented for ages as being an old
946        synonym of -m (show memory usage). I have changed it to mean "force study
947        for every regex", that is, assume /S for every regex. This is similar to -i
948        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
949        using it. It makes it easier to run collections of tests with and without
950        study enabled, and thereby test pcre_study() more easily. All the standard
951        tests are now run with and without -s (but some patterns can be marked as
952        "never study" - see 20 below).
954    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
955        restoration of the capturing data to the outer values was not happening
956        correctly.
958    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
959        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
960        pattern had matched an empty string, and so incorrectly returned a no
961        match.
963    17. There was optimizing code for the last branch of non-capturing parentheses,
964        and also for the obeyed branch of a conditional subexpression, which used
965        tail recursion to cut down on stack usage. Unfortunately, now that there is
966        the possibility of (*THEN) occurring in these branches, tail recursion is
967        no longer possible because the return has to be checked for (*THEN). These
968        two optimizations have therefore been removed. [But see 8.20/11 above.]
970    18. If a pattern containing \R was studied, it was assumed that \R always
971        matched two bytes, thus causing the minimum subject length to be
972        incorrectly computed because \R can also match just one byte.
974    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
975        was incorrectly computed.
977    20. If /S is present twice on a test pattern in pcretest input, it now
978        *disables* studying, thereby overriding the use of -s on the command line
979        (see 14 above). This is necessary for one or two tests to keep the output
980        identical in both cases.
982    21. When (*ACCEPT) was used in an assertion that matched an empty string and
983        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
985    22. When an atomic group that contained a capturing parenthesis was
986        successfully matched, but the branch in which it appeared failed, the
987        capturing was not being forgotten if a higher numbered group was later
988        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
989        group 1 to "a", when in fact it should be unset. This applied to multi-
990        branched capturing and non-capturing groups, repeated or not, and also to
991        positive assertions (capturing in negative assertions does not happen
992        in PCRE) and also to nested atomic groups.
994    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
995        subject after a captured substring, to make it easier to tell which of a
996        number of identical substrings has been captured.
998    24. The way atomic groups are processed by pcre_exec() has been changed so that
999        if they are repeated, backtracking one repetition now resets captured
1000        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
1001        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
1002        "aaa". Previously, it would have been "a". As part of this code
1003        refactoring, the way recursive calls are handled has also been changed.
1005    25. If an assertion condition captured any substrings, they were not passed
1006        back unless some other capturing happened later. For example, if
1007        (?(?=(a))a) was matched against "a", no capturing was returned.
1009    26. When studying a pattern that contained subroutine calls or assertions,
1010        the code for finding the minimum length of a possible match was handling
1011        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
1012        group 1 called group 2 while simultaneously a separate group 2 called group
1013        1). A stack overflow occurred in this case. I have fixed this by limiting
1014        the recursion depth to 10.
1016    27. Updated RunTest.bat in the distribution to the version supplied by Tom
1017        Fortmann. This supports explicit test numbers on the command line, and has
1018        argument validation and error reporting.
1020    28. An instance of \X with an unlimited repeat could fail if at any point the
1021        first character it looked at was a mark character.
1023    29. Some minor code refactoring concerning Unicode properties and scripts
1024        should reduce the stack requirement of match() slightly.
1026    30. Added the '=' option to pcretest to check the setting of unused capturing
1027        slots at the end of the pattern, which are documented as being -1, but are
1028        not included in the return count.
1030    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
1031        compiled something random. Now it gives a compile-time error (as does
1032        Perl).
1034    32. A *MARK encountered during the processing of a positive assertion is now
1035        recorded and passed back (compatible with Perl).
1037    33. If --only-matching or --colour was set on a pcregrep call whose pattern
1038        had alternative anchored branches, the search for a second match in a line
1039        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
1040        matched the line "0102" twice. The same bug affected patterns that started
1041        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
1042        twice.
1044    34. Previously, PCRE did not allow quantification of assertions. However, Perl
1045        does, and because of capturing effects, quantifying parenthesized
1046        assertions may at times be useful. Quantifiers are now allowed for
1047        parenthesized assertions.
1049    35. A minor code tidy in pcre_compile() when checking options for \R usage.
1051    36. \g was being checked for fancy things in a character class, when it should
1052        just be a literal "g".
1054    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
1055        appearance of a nested POSIX class supersedes an apparent external class.
1056        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1057        unescaped square brackets may also appear as part of class names. For
1058        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1059        more like Perl. (But see 8.20/1 above.)
1061    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1062        was because it thought it was \N{name}, which is not supported).
1064    39. Add minix to OS list not supporting the -S option in pcretest.
1066    40. PCRE tries to detect cases of infinite recursion at compile time, but it
1067        cannot analyze patterns in sufficient detail to catch mutual recursions
1068        such as ((?1))((?2)). There is now a runtime test that gives an error if a
1069        subgroup is called recursively as a subpattern for a second time at the
1070        same position in the subject string. In previous releases this might have
1071        been caught by the recursion limit, or it might have run out of stack.
1073    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
1074        happen only once. PCRE was, however incorrectly giving a compile time error
1075        "recursive call could loop indefinitely" because it cannot analyze the
1076        pattern in sufficient detail. The compile time test no longer happens when
1077        PCRE is compiling a conditional subpattern, but actual runaway loops are
1078        now caught at runtime (see 40 above).
1080    42. It seems that Perl allows any characters other than a closing parenthesis
1081        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
1082        has been changed to be the same.
1084    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
1085        as not to get warnings when autogen.sh is called. Also changed
1086        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
1088    44. To help people who use pcregrep to scan files containing exceedingly long
1089        lines, the following changes have been made:
1091        (a) The default value of the buffer size parameter has been increased from
1092            8K to 20K. (The actual buffer used is three times this size.)
1094        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1095            PCRE is built.
1097        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
1098            to be set at run time.
1100        (d) Numerical values in pcregrep options can be followed by K or M, for
1101            example --buffer-size=50K.
1103        (e) If a line being scanned overflows pcregrep's buffer, an error is now
1104            given and the return code is set to 2.
1106    45. Add a pointer to the latest mark to the callout data block.
1108    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1109        partial match of an empty string instead of no match. This was specific to
1110        the use of ".".
1112    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1113        complete match instead of a partial match. This bug was dependent on both
1114        the PCRE_UTF8 and PCRE_DOTALL options being set.
1116    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1117        starting byte set, because \b was not being ignored.
1120    Version 8.12 15-Jan-2011
1121    ------------------------
1123    1.  Fixed some typos in the markup of the man pages, and wrote a script that
1124        checks for such things as part of the documentation building process.
1126    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
1127        --match-limit and --recursion-limit options (added for 8.11). In
1128        particular, this made one of the standard tests fail. (The integer value
1129        went into the wrong half of a long int.)
1131    3.  If the --colour option was given to pcregrep with -v (invert match), it
1132        did strange things, either producing crazy output, or crashing. It should,
1133        of course, ignore a request for colour when reporting lines that do not
1134        match.
1136    4.  Another pcregrep bug caused similar problems if --colour was specified with
1137        -M (multiline) and the pattern match finished with a line ending.
1139    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
1140        matched in multiline mode, the following line was shown as part of the
1141        match. This seems wrong, so I have changed it.
1143    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
1144        the check for further matches in the same line (so they could be coloured)
1145        to overrun the end of the current line. If another match was found, it was
1146        incorrectly shown (and then shown again when found in the next line).
1148    7.  If pcregrep was compiled under Windows, there was a reference to the
1149        function pcregrep_exit() before it was defined. I am assuming this was
1150        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1151        reported by a user. I've moved the definition above the reference.
1154    Version 8.11 10-Dec-2010
1155    ------------------------
1157    1.  (*THEN) was not working properly if there were untried alternatives prior
1158        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1159        backtracked to try for "b" instead of moving to the next alternative branch
1160        at the same level (in this case, to look for "c"). The Perl documentation
1161        is clear that when (*THEN) is backtracked onto, it goes to the "next
1162        alternative in the innermost enclosing group".
1164    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1165        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
1166        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1167        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1168        (*THEN).
1170    3.  If \s appeared in a character class, it removed the VT character from
1171        the class, even if it had been included by some previous item, for example
1172        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1173        of \s, but is part of the POSIX "space" class.)
1175    4.  A partial match never returns an empty string (because you can always
1176        match an empty string at the end of the subject); however the checking for
1177        an empty string was starting at the "start of match" point. This has been
1178        changed to the "earliest inspected character" point, because the returned
1179        data for a partial match starts at this character. This means that, for
1180        example, /(?<=abc)def/ gives a partial match for the subject "abc"
1181        (previously it gave "no match").
1183    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1184        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1185        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1186        has an implication that the given string is incomplete (because a partial
1187        match is preferred over a full match). For this reason, these items now
1188        give a partial match in this situation. [Aside: previously, the one case
1189        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1190        match rather than a full match, which was wrong by the old rules, but is
1191        now correct.]
1193    6.  There was a bug in the handling of #-introduced comments, recognized when
1194        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1195        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1196        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1197        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1198        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1199        places in pcre_compile().
1201    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1202        comments when looking ahead for named forward references to subpatterns,
1203        the only newline sequence it recognized was NL. It now handles newlines
1204        according to the set newline convention.
1206    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1207        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1208        cater for a lack of strerror(). These oversights have been fixed.
1210    9.  Added --match-limit and --recursion-limit to pcregrep.
1212    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1214    11. When the -o option was used, pcregrep was setting a return code of 1, even
1215        when matches were found, and --line-buffered was not being honoured.
1217    12. Added an optional parentheses number to the -o and --only-matching options
1218        of pcregrep.
1220    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1221        can match an empty string. The code to do it in pcretest and pcredemo
1222        needed fixing:
1224        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1225            only one byte after an empty string match just before CRLF (this case
1226            just got forgotten; "any" and "anycrlf" were OK).
1228        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1229            mode when an empty string match preceded an ASCII character followed by
1230            a non-ASCII character. (The code for advancing by one character rather
1231            than one byte was nonsense.)
1233        (c) The pcredemo.c sample program did not have any code at all to handle
1234            the cases when CRLF is a valid newline sequence.
1236    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1237        as a starting offset was within the subject string. There is now a new
1238        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1239        negative or greater than the length of the string. In order to test this,
1240        pcretest is extended to allow the setting of negative starting offsets.
1242    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1243        starting offset points to the beginning of a UTF-8 character was
1244        unnecessarily clumsy. I tidied it up.
1246    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1247        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1249    17. Nobody had reported that the --include_dir option, which was added in
1250        release 7.7 should have been called --include-dir (hyphen, not underscore)
1251        for compatibility with GNU grep. I have changed it to --include-dir, but
1252        left --include_dir as an undocumented synonym, and the same for
1253        --exclude-dir, though that is not available in GNU grep, at least as of
1254        release 2.5.4.
1256    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1257        characters from a string of bytes) have been redefined so as not to use
1258        loops, in order to improve performance in some environments. At the same
1259        time, I abstracted some of the common code into auxiliary macros to save
1260        repetition (this should not affect the compiled code).
1262    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1263        compile-time error is now given if \c is not followed by an ASCII
1264        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1265        different, and any byte value is allowed.)
1267    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1268        START_OPTIMIZE option, which is now allowed at compile time - but just
1269        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1270        to pcregrep and other applications that have no direct access to PCRE
1271        options. The new /Y option in pcretest sets this option when calling
1272        pcre_compile().
1274    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1275        back references. Groups containing recursive back references were forced to
1276        be atomic by that change, but in the case of named groups, the amount of
1277        memory required was incorrectly computed, leading to "Failed: internal
1278        error: code overflow". This has been fixed.
1280    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1281        pcretest.c, to avoid build problems in some Borland environments.
1284    Version 8.10 25-Jun-2010
1285    ------------------------
1287    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1288        THEN.
1290    2.  (*ACCEPT) was not working when inside an atomic group.
1292    3.  Inside a character class, \B is treated as a literal by default, but
1293        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1294        causes the error). The code is unchanged, but I tidied the documentation.
1296    4.  Inside a character class, PCRE always treated \R and \X as literals,
1297        whereas Perl faults them if its -w option is set. I have changed PCRE so
1298        that it faults them when PCRE_EXTRA is set.
1300    5.  Added support for \N, which always matches any character other than
1301        newline. (It is the same as "." when PCRE_DOTALL is not set.)
1303    6.  When compiling pcregrep with newer versions of gcc which may have
1304        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1305        declared with attribute warn_unused_result" were given. Just casting the
1306        result to (void) does not stop the warnings; a more elaborate fudge is
1307        needed. I've used a macro to implement this.
1309    7.  Minor change to pcretest.c to avoid a compiler warning.
1311    8.  Added four artifical Unicode properties to help with an option to make
1312        \s etc use properties (see next item). The new properties are: Xan
1313        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1315    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1316        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1317        this option. Modified pcretest to add /W to test this facility. Added
1318        REG_UCP to make it available via the POSIX interface.
1320    10. Added --line-buffered to pcregrep.
1322    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1323        studied, and the match started with a letter with a code point greater than
1324        127 whose first byte was different to the first byte of the other case of
1325        the letter, the other case of this starting letter was not recognized
1326        (#976).
1328    12. If a pattern that was studied started with a repeated Unicode property
1329        test, for example, \p{Nd}+, there was the theoretical possibility of
1330        setting up an incorrect bitmap of starting bytes, but fortunately it could
1331        not have actually happened in practice until change 8 above was made (it
1332        added property types that matched character-matching opcodes).
1334    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1335        possible starting bytes for non-anchored patterns.
1337    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1338        \R, and also a number of cases that involve Unicode properties, both
1339        explicit and implicit when PCRE_UCP is set.
1341    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1342        input, it could crash or give wrong results if characters with values
1343        greater than 0xc0 were present in the subject string. (Detail: it assumed
1344        UTF-8 input when processing these items.)
1346    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1347        size_t is 64-bit (#991).
1349    17. Added a check for running out of memory when PCRE is compiled with
1350        --disable-stack-for-recursion (#990).
1352    18. If the last data line in a file for pcretest does not have a newline on
1353        the end, a newline was missing in the output.
1355    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1356        less than 128) in its various bitmaps. However, there is a facility for
1357        generating tables according to the current locale when PCRE is compiled. It
1358        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1359        characters, are recognized by isspace() and therefore were getting set in
1360        these tables, and indeed these tables seem to approximate to ISO 8859. This
1361        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1362        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1363        which of course cannot start UTF-8 characters. I have changed the code so
1364        that only real ASCII characters (less than 128) and the correct starting
1365        bytes for UTF-8 encodings are set for characters greater than 127 when in
1366        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1367        altogether.)
1369    20. Added the /T option to pcretest so as to be able to run tests with non-
1370        standard character tables, thus making it possible to include the tests
1371        used for 19 above in the standard set of tests.
1373    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1374        reference to a subpattern the other side of a comment that contains an
1375        opening parenthesis caused either an internal compiling error, or a
1376        reference to the wrong subpattern.
1379    Version 8.02 19-Mar-2010
1380    ------------------------
1382    1.  The Unicode data tables have been updated to Unicode 5.2.0.
1384    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
1385        configured.
1387    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
1388        original author of that file, following a query about its status.
1390    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
1391        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1393    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1394        quantifier applied to a forward-referencing subroutine call, could compile
1395        incorrect code or give the error "internal error: previously-checked
1396        referenced subpattern not found".
1398    6.  Both MS Visual Studio and Symbian OS have problems with initializing
1399        variables to point to external functions. For these systems, therefore,
1400        pcre_malloc etc. are now initialized to local functions that call the
1401        relevant global functions.
1403    7.  There were two entries missing in the vectors called coptable and poptable
1404        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1405        I've fixed the data, and added a kludgy way of testing at compile time that
1406        the lengths are correct (equal to the number of opcodes).
1408    8.  Following on from 7, I added a similar kludge to check the length of the
1409        eint vector in pcreposix.c.
1411    9.  Error texts for pcre_compile() are held as one long string to avoid too
1412        much relocation at load time. To find a text, the string is searched,
1413        counting zeros. There was no check for running off the end of the string,
1414        which could happen if a new error number was added without updating the
1415        string.
1417    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1419    11. \K was not working if it appeared in an atomic group or in a group that
1420        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1421        \K is "not well defined" if used in an assertion. PCRE now accepts it if
1422        the assertion is positive, but not if it is negative.
1424    12. Change 11 fortuitously reduced the size of the stack frame used in the
1425        "match()" function of pcre_exec.c by one pointer. Forthcoming
1426        implementation of support for (*MARK) will need an extra pointer on the
1427        stack; I have reserved it now, so that the stack frame size does not
1428        decrease.
1430    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1431        item in branch that calls a recursion is a subroutine call - as in the
1432        second branch in the above example - was incorrectly given the compile-
1433        time error "recursive call could loop indefinitely" because pcre_compile()
1434        was not correctly checking the subroutine for matching a non-empty string.
1436    14. The checks for overrunning compiling workspace could trigger after an
1437        overrun had occurred. This is a "should never occur" error, but it can be
1438        triggered by pathological patterns such as hundreds of nested parentheses.
1439        The checks now trigger 100 bytes before the end of the workspace.
1441    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1444    Version 8.01 19-Jan-2010
1445    ------------------------
1447    1.  If a pattern contained a conditional subpattern with only one branch (in
1448        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
1449        computed the wrong minimum data length (which is of course zero for such
1450        subpatterns). This could cause incorrect "no match" results.
1452    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1453        the pattern is reset in the first branch, pcre_compile() failed with
1454        "internal error: code overflow at offset...". This happened only when
1455        the reset was to the original external option setting. (An optimization
1456        abstracts leading options settings into an external setting, which was the
1457        cause of this.)
1459    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1460        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1461        assertion pattern did not match (meaning that the assertion was true), it
1462        was incorrectly treated as false if the SKIP had been reached during the
1463        matching. This also applied to assertions used as conditions.
1465    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
1466        assertion subpattern, including such a pattern used as a condition,
1467        unpredictable results occurred, instead of the error return
1470    5.  The C++ GlobalReplace function was not working like Perl for the special
1471        situation when an empty string is matched. It now does the fancy magic
1472        stuff that is necessary.
1474    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1475        removed. (These were left over from very, very early versions of PCRE.)
1477    7.  Some cosmetic changes to the code to make life easier when compiling it
1478        as part of something else:
1480        (a) Change DEBUG to PCRE_DEBUG.
1482        (b) In pcre_compile(), rename the member of the "branch_chain" structure
1483            called "current" as "current_branch", to prevent a collision with the
1484            Linux macro when compiled as a kernel module.
1486        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1487            prevent a collision with the Linux macro when compiled as a kernel
1488            module.
1490    8.  In pcre_compile() there are some checks for integer overflows that used to
1491        cast potentially large values to (double). This has been changed to that
1492        when building, a check for int64_t is made, and if it is found, it is used
1493        instead, thus avoiding the use of floating point arithmetic. (There is no
1494        other use of FP in PCRE.) If int64_t is not found, the fallback is to
1495        double.
1497    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
1498        2005 (difference between two addresses compared to an unsigned value).
1500    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1501        custom one, because of the following reported problem in Windows:
1503          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1504              under Win32.
1505          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1506              therefore missing the function definition.
1507          - The compiler thus generates a "C" signature for the test function.
1508          - The linker fails to find the "C" function.
1509          - PCRE fails to configure if asked to do so against libbz2.
1511    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1512        messages were output:
1514          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1515          rerunning libtoolize, to keep the correct libtool macros in-tree.
1516          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1518        I have done both of these things.
1520    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1521        most of the time, it *can* run out if it is given a pattern that contains a
1522        runaway infinite recursion. I updated the discussion in the pcrestack man
1523        page.
1525    13. Now that we have gone to the x.xx style of version numbers, the minor
1526        version may start with zero. Using 08 or 09 is a bad idea because users
1527        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1528        interpreted as invalid octal numbers. I've updated the previous comment in
1529        configure.ac, and also added a check that gives an error if 08 or 09 are
1530        used.
1532    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1533        causing partial matching to fail when the end of the subject matched \W
1534        in a UTF-8 pattern where \W was quantified with a minimum of 3.
1536    15. There were some discrepancies between the declarations in pcre_internal.h
1537        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1538        their definitions. The declarations used "const uschar *" and the
1539        definitions used USPTR. Even though USPTR is normally defined as "const
1540        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1541        reported that: "This difference in casting confuses some C++ compilers, for
1542        example, SunCC recognizes above declarations as different functions and
1543        generates broken code for hbpcre." I have changed the declarations to use
1544        USPTR.
1546    16. GNU libtool is named differently on some systems. The autogen.sh script now
1547        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1548        (FreeBSD).
1550    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1551        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1552        comment: "Figure out how to create a longlong from a string: strtoll and
1553        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1554        instance, but it only takes 2 args instead of 3!"
1556    18. A subtle bug concerned with back references has been fixed by a change of
1557        specification, with a corresponding code fix. A pattern such as
1558        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1559        refers, was giving matches when it shouldn't. For example, xa=xaaa would
1560        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1561        same bug. Such groups have to be quantified to be useful, or contained
1562        inside another quantified group. (If there's no repetition, the reference
1563        can never match.) The problem arises because, having left the group and
1564        moved on to the rest of the pattern, a later failure that backtracks into
1565        the group uses the captured value from the final iteration of the group
1566        rather than the correct earlier one. I have fixed this in PCRE by forcing
1567        any group that contains a reference to itself to be an atomic group; that
1568        is, there cannot be any backtracking into it once it has completed. This is
1569        similar to recursive and subroutine calls.
1572    Version 8.00 19-Oct-09
1573  ----------------------  ----------------------
1575  1.  The table for translating pcre_compile() error codes into POSIX error codes  1.  The table for translating pcre_compile() error codes into POSIX error codes
1576      was out-of-date, and there was no check on the pcre_compile() error code      was out-of-date, and there was no check on the pcre_compile() error code
1577      being within the table. This could lead to an OK return being given in      being within the table. This could lead to an OK return being given in
1578      error.      error.
1580  2.  Changed the call to open a subject file in pcregrep from fopen(pathname,  2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
1581      "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests      "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1582      in a Windows environment.      in a Windows environment.
1584  3.  The pcregrep --count option prints the count for each file even when it is  3.  The pcregrep --count option prints the count for each file even when it is
1585      zero, as does GNU grep. However, pcregrep was also printing all files when      zero, as does GNU grep. However, pcregrep was also printing all files when
1586      --files-with-matches was added. Now, when both options are given, it prints      --files-with-matches was added. Now, when both options are given, it prints
1587      counts only for those files that have at least one match. (GNU grep just      counts only for those files that have at least one match. (GNU grep just
1588      prints the file name in this circumstance, but including the count seems      prints the file name in this circumstance, but including the count seems
1589      more useful - otherwise, why use --count?) Also ensured that the      more useful - otherwise, why use --count?) Also ensured that the
1590      combination -clh just lists non-zero counts, with no names.      combination -clh just lists non-zero counts, with no names.
1592    4.  The long form of the pcregrep -F option was incorrectly implemented as
1593        --fixed_strings instead of --fixed-strings. This is an incompatible change,
1594        but it seems right to fix it, and I didn't think it was worth preserving
1595        the old behaviour.
1597    5.  The command line items --regex=pattern and --regexp=pattern were not
1598        recognized by pcregrep, which required --regex pattern or --regexp pattern
1599        (with a space rather than an '='). The man page documented the '=' forms,
1600        which are compatible with GNU grep; these now work.
1602    6.  No libpcreposix.pc file was created for pkg-config; there was just
1603        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1605    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1606        when UCP support is not needed, by modifying the Python script that
1607        generates it from Unicode data files. This should not matter if the module
1608        is correctly used as a library, but I received one complaint about 50K of
1609        unwanted data. My guess is that the person linked everything into his
1610        program rather than using a library. Anyway, it does no harm.
1612    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1613        was a minimum greater than 1 for a wide character in a possessive
1614        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1615        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1616        character. Chaos in the form of incorrect output or a compiling loop could
1617        result.
1619    9.  The restrictions on what a pattern can contain when partial matching is
1620        requested for pcre_exec() have been removed. All patterns can now be
1621        partially matched by this function. In addition, if there are at least two
1622        slots in the offset vector, the offset of the earliest inspected character
1623        for the match and the offset of the end of the subject are set in them when
1624        PCRE_ERROR_PARTIAL is returned.
1626    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1627        synonymous with PCRE_PARTIAL, for backwards compatibility, and
1628        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1629        and may be more useful for multi-segment matching.
1631    11. Partial matching with pcre_exec() is now more intuitive. A partial match
1632        used to be given if ever the end of the subject was reached; now it is
1633        given only if matching could not proceed because another character was
1634        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1635        string "Z", which now yields "no match" instead of "partial match". In the
1636        case of pcre_dfa_exec(), "no match" is given if every matching path for the
1637        final character ended with (*FAIL).
1639    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1640        if the pattern had a "must contain" character that was already found in the
1641        earlier partial match, unless partial matching was again requested. For
1642        example, with the pattern /dog.(body)?/, the "must contain" character is
1643        "g". If the first part-match was for the string "dog", restarting with
1644        "sbody" failed. This bug has been fixed.
1646    13. The string returned by pcre_dfa_exec() after a partial match has been
1647        changed so that it starts at the first inspected character rather than the
1648        first character of the match. This makes a difference only if the pattern
1649        starts with a lookbehind assertion or \b or \B (\K is not supported by
1650        pcre_dfa_exec()). It's an incompatible change, but it makes the two
1651        matching functions compatible, and I think it's the right thing to do.
1653    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1654        so that the demonstration program is easily available in environments where
1655        PCRE has not been installed from source.
1657    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1658        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1659        library.
1661    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1662        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1663        is not the first non-POSIX option to be added. Clearly some people find
1664        these options useful.
1666    17. If a caller to the POSIX matching function regexec() passes a non-zero
1667        value for nmatch with a NULL value for pmatch, the value of
1668        nmatch is forced to zero.
1670    18. RunGrepTest did not have a test for the availability of the -u option of
1671        the diff command, as RunTest does. It now checks in the same way as
1672        RunTest, and also checks for the -b option.
1674    19. If an odd number of negated classes containing just a single character
1675        interposed, within parentheses, between a forward reference to a named
1676        subpattern and the definition of the subpattern, compilation crashed with
1677        an internal error, complaining that it could not find the referenced
1678        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1679        [The bug was that it was starting one character too far in when skipping
1680        over the character class, thus treating the ] as data rather than
1681        terminating the class. This meant it could skip too much.]
1683    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1684        /g option in pcretest when the pattern contains \K, which makes it possible
1685        to have an empty string match not at the start, even when the pattern is
1686        anchored. Updated pcretest and pcredemo to use this option.
1688    21. If the maximum number of capturing subpatterns in a recursion was greater
1689        than the maximum at the outer level, the higher number was returned, but
1690        with unset values at the outer level. The correct (outer level) value is
1691        now given.
1693    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1694        PCRE did not set those parentheses (unlike Perl). I have now found a way to
1695        make it do so. The string so far is captured, making this feature
1696        compatible with Perl.
1698    23. The tests have been re-organized, adding tests 11 and 12, to make it
1699        possible to check the Perl 5.10 features against Perl 5.10.
1701    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1702        pattern matches a fixed length string. PCRE did not allow this; now it
1703        does. Neither allows recursion.
1705    25. I finally figured out how to implement a request to provide the minimum
1706        length of subject string that was needed in order to match a given pattern.
1707        (It was back references and recursion that I had previously got hung up
1708        on.) This code has now been added to pcre_study(); it finds a lower bound
1709        to the length of subject needed. It is not necessarily the greatest lower
1710        bound, but using it to avoid searching strings that are too short does give
1711        some useful speed-ups. The value is available to calling programs via
1712        pcre_fullinfo().
1714    26. While implementing 25, I discovered to my embarrassment that pcretest had
1715        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1716        study optimizations had never been tested with that matching function.
1717        Oops. What is worse, even when it was passed study data, there was a bug in
1718        pcre_dfa_exec() that meant it never actually used it. Double oops. There
1719        were also very few tests of studied patterns with pcre_dfa_exec().
1721    27. If (?| is used to create subpatterns with duplicate numbers, they are now
1722        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1723        on the other side of the coin, they are no longer allowed to have different
1724        names, because these cannot be distinguished in PCRE, and this has caused
1725        confusion. (This is a difference from Perl.)
1727    28. When duplicate subpattern names are present (necessarily with different
1728        numbers, as required by 27 above), and a test is made by name in a
1729        conditional pattern, either for a subpattern having been matched, or for
1730        recursion in such a pattern, all the associated numbered subpatterns are
1731        tested, and the overall condition is true if the condition is true for any
1732        one of them. This is the way Perl works, and is also more like the way
1733        testing by number works.
1736  Version 7.9 11-Apr-09  Version 7.9 11-Apr-09
1737  ---------------------  ---------------------
# Line 56  Version 7.9 11-Apr-09 Line 1767  Version 7.9 11-Apr-09
1767  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
1768      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
1769      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1770      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1771        8.33.]
1773  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1774      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 299  Version 7.7 07-May-08 Line 2011  Version 7.7 07-May-08
2011      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2012      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2013      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2014      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2015      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2016      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.420  
changed lines
  Added in v.1364

  ViewVC Help
Powered by ViewVC 1.1.5