ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 341 by ph10, Sat Apr 19 16:41:04 2008 UTC revision 1260 by ph10, Wed Feb 27 15:41:22 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.7 05-Mar-08  Version 8.33 xx-xxxx-201x
5    -------------------------
7    1.  Added 'U' to some constants that are compared to unsigned integers, to
8        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
9        variables that are added to signed variables, to ensure the result is
10        signed and can be negated.
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
15    3.  Revise the creation of config.h.generic so that all boolean macros are
16        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
17        overriding via -D on the command line possible.
19    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
20        to unsigned int is reported to make a quite noticeable speed difference in
21        a specific Windows environment. Testing on Linux did also appear to show
22        some benefit (and it is clearly not harmful). Also fixed the definition of
23        Xop which should be unsigned.
25    5.  Related to (4), changing the definition of the intermediate variable cc
26        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
27        improvements.
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
37    9.  Optimizing fast_forward_start_bits in JIT.
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
44        (b) Minimum length was not checked before the matching is started.
46    11. The value of capture_last that is passed to callouts was incorrect in some
47        cases when there was a capture on one path that was subsequently abandoned
48        after a backtrack. Also, the capture_last value is now reset after a
49        recursion, since all captures are also reset in this case.
51    12. The interpreter no longer returns the "too many substrings" error in the
52        case when an overflowing capture is in a branch that is subsequently
53        abandoned after a backtrack.
55    13. In the pathological case when an offset vector of size 2 is used, pcretest
56        now prints out the matched string after a yield of 0 or 1.
58    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
59        Only supported by the JIT compiler at the moment.
61    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
63    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
64        offset of the starting point of the matching process, provided the offsets
65        vector is large enough.
67    17. The \A escape now records a lookbehind value of 1, though its execution
68        does not actually inspect the previous character. This is to ensure that,
69        in partial multi-segment matching, at least one character from the old
70        segment is retained when a new segment is processed. Otherwise, if there
71        are no lookbehinds in the pattern, \A might match incorrectly at the start
72        of a new segment.
74    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
76    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
77        gives some modest performance improvement in 8-bit mode.
79    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
80        be expressed in certain programming languages using Universal Character
81        Names.
84    Version 8.32 30-November-2012
85    -----------------------------
87    1.  Improved JIT compiler optimizations for first character search and single
88        character iterators.
90    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
91        Patch by Daniel Richard G.
93    3.  Single character iterator optimizations in the JIT compiler.
95    4.  Improved JIT compiler optimizations for character ranges.
97    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
98        Reported by Giuseppe D'Angelo.
100    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
101        of a line, was being set incorrectly in cases where .* appeared inside
102        atomic brackets at the start of a pattern, or where there was a subsequent
103        *PRUNE or *SKIP.
105    7.  Improved instruction cache flush for POWER/PowerPC.
106        Patch by Daniel Richard G.
108    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
109        grep:
111        (a) There is now no limit to the number of patterns to be matched.
113        (b) An error is given if a pattern is too long.
115        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
116            are now supported.
118        (d) --exclude-from and --include-from (multiple use) have been added.
120        (e) Exclusions and inclusions now apply to all files and directories, not
121            just to those obtained from scanning a directory recursively.
123        (f) Multiple uses of -f and --file-list are now supported.
125        (g) In a Windows environment, the default for -d has been changed from
126            "read" (the GNU grep default) to "skip", because otherwise the presence
127            of a directory in the file list provokes an error.
129        (h) The documentation has been revised and clarified in places.
131    9.  Improve the matching speed of capturing brackets.
133    10. Changed the meaning of \X so that it now matches a Unicode extended
134        grapheme cluster.
136    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
137        out POSIX threads when JIT support is configured.
139    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
141    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
142        structure could go wrong in environments where size_t is not the same size
143        as int.
145    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
146        set.
148    15. The EBCDIC support had decayed; later updates to the code had included
149        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
150        general tidy up of EBCDIC-related issues, and the documentation was also
151        not quite right. There is now a test that can be run on ASCII systems to
152        check some of the EBCDIC-related things (but is it not a full test).
154    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
155        in a small tidy to the code.
157    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
159    18. If the --only-matching (-o) option in pcregrep is specified multiple
160        times, each one causes appropriate output. For example, -o1 -o2 outputs the
161        substrings matched by the 1st and 2nd capturing parentheses. A separating
162        string can be specified by --om-separator (default empty).
164    19. Improving the first n character searches.
166    20. Turn case lists for horizontal and vertical white space into macros so that
167        they are defined only once.
169    21. This set of changes together give more compatible Unicode case-folding
170        behaviour for characters that have more than one other case when UCP
171        support is available.
173        (a) The Unicode property table now has offsets into a new table of sets of
174            three or more characters that are case-equivalent. The MultiStage2.py
175            script that generates these tables (the pcre_ucd.c file) now scans
176            CaseFolding.txt instead of UnicodeData.txt for character case
177            information.
179        (b) The code for adding characters or ranges of characters to a character
180            class has been abstracted into a generalized function that also handles
181            case-independence. In UTF-mode with UCP support, this uses the new data
182            to handle characters with more than one other case.
184        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
185            whose other case is greater than 256 are now correctly matched
186            caselessly. Previously, the high codepoint matched the low one, but not
187            vice versa.
189        (d) The processing of \h, \H, \v, and \ in character classes now makes use
190            of the new class addition function, using character lists defined as
191            macros alongside the case definitions of 20 above.
193        (e) Caseless back references now work with characters that have more than
194            one other case.
196        (f) General caseless matching of characters with more than one other case
197            is supported.
199    22. Unicode character properties were updated from Unicode 6.2.0
201    23. Improved CMake support under Windows. Patch by Daniel Richard G.
203    24. Add support for 32-bit character strings, and UTF-32
205    25. Major JIT compiler update (code refactoring and bugfixing).
206        Experimental Sparc 32 support is added.
208    26. Applied a modified version of Daniel Richard G's patch to create
209        pcre.h.generic and config.h.generic by "make" instead of in the
210        PrepareRelease script.
212    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
213        pcre_compile.c when checking for a zero character.
215    28. Introducing a native interface for JIT. Through this interface, the compiled
216        machine code can be directly executed. The purpose of this interface is to
217        provide fast pattern matching, so several sanity checks are not performed.
218        However, feature tests are still performed. The new interface provides
219        1.4x speedup compared to the old one.
221    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
222        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
223        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
225    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
226        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
227        the "old" RFC 2279). Instead, it ended up passing a negative length to
228        pcre_exec().
230    31. Add support for GCC's visibility feature to hide internal functions.
232    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
233        "unknown -C option" after outputting 0 or 1.
235    33. There is now support for generating a code coverage report for the test
236        suite in environments where gcc is the compiler and lcov is installed. This
237        is mainly for the benefit of the developers.
239    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
240        unaddressable using valgrind annotations, allowing valgrind to detect
241        invalid memory accesses. This is mainly for the benefit of the developers.
243    25. (*UTF) can now be used to start a pattern in any of the three libraries.
245    26. Give configure error if --enable-cpp but no C++ compiler found.
248    Version 8.31 06-July-2012
249    -------------------------
251    1.  Fixing a wrong JIT test case and some compiler warnings.
253    2.  Removed a bashism from the RunTest script.
255    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
256        to unsigned type, result still unsigned" that was given by an MS compiler
257        on encountering the code "-sizeof(xxx)".
259    4.  Partial matching support is added to the JIT compiler.
261    5.  Fixed several bugs concerned with partial matching of items that consist
262        of more than one character:
264        (a) /^(..)\1/ did not partially match "aba" because checking references was
265            done on an "all or nothing" basis. This also applied to repeated
266            references.
268        (b) \R did not give a hard partial match if \r was found at the end of the
269            subject.
271        (c) \X did not give a hard partial match after matching one or more
272            characters at the end of the subject.
274        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
275            a partial match for the string "\r".
277        (e) When newline was set to CRLF, the metacharacter "." did not recognize
278            a partial match for a CR character at the end of the subject string.
280    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
281        running pcretest, the text "(JIT)" added to the output whenever JIT is
282        actually used to run the match.
284    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
285        or /S+[+] with a digit between 1 and 7.
287    8.  OP_NOT now supports any UTF character not just single-byte ones.
289    9.  (*MARK) control verb is now supported by the JIT compiler.
291    10. The command "./RunTest list" lists the available tests without actually
292        running any of them. (Because I keep forgetting what they all are.)
296    12. Applied a (slightly modified) user-supplied patch that improves performance
297        when the heap is used for recursion (compiled with --disable-stack-for-
298        recursion). Instead of malloc and free for each heap frame each time a
299        logical recursion happens, frames are retained on a chain and re-used where
300        possible. This sometimes gives as much as 30% improvement.
302    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
303        call.
305    14. As documented, (*COMMIT) is now confined to within a positive assertion.
307    15. It is now possible to link pcretest with libedit as an alternative to
308        libreadline.
310    16. (*COMMIT) control verb is now supported by the JIT compiler.
312    17. The Unicode data tables have been updated to Unicode 6.1.0.
314    18. Added --file-list option to pcregrep.
316    19. Added binary file support to pcregrep, including the -a, --binary-files,
317        -I, and --text options.
319    20. The madvise function is renamed for posix_madvise for QNX compatibility
320        reasons. Fixed by Giuseppe D'Angelo.
322    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
324    22. Changed the option for creating symbolic links for 16-bit man pages from
325        -s to -sf so that re-installing does not cause issues.
327    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
329    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
330        matches in certain environments (the workspace was not being correctly
331        retained). Also added to pcre_dfa_exec() a simple plausibility check on
332        some of the workspace data at the beginning of a restart.
334    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
335        was not doing so when it should - probably a typo introduced by SVN 528
336        (change 8.10/14).
338    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
339        \w+ when the character tables indicated that \x{c4} was a word character.
340        There were several related cases, all because the tests for doing a table
341        lookup were testing for characters less than 127 instead of 255.
343    27. If a pattern contains capturing parentheses that are not used in a match,
344        their slots in the ovector are set to -1. For those that are higher than
345        any matched groups, this happens at the end of processing. In the case when
346        there were back references that the ovector was too small to contain
347        (causing temporary malloc'd memory to be used during matching), and the
348        highest capturing number was not used, memory off the end of the ovector
349        was incorrectly being set to -1. (It was using the size of the temporary
350        memory instead of the true size.)
352    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
353        ovector size, it uses memory at the end of the block that it has got.
355    29. Check for an overlong MARK name and give an error at compile time. The
356        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
358    30. JIT compiler update.
360    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
361        Rill for the patch.
363    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
365    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
367    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
368        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
369        was enabled.
371    35. Improve JIT code generation for greedy plus quantifier.
373    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
374        1 to "aa" instead of to an empty string. The bug affected repeated groups
375        that could potentially match an empty string.
377    37. Optimizing single character iterators in JIT.
379    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
380        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
381        codepoints that are too big for the mode are faulted, and in a UTF mode,
382        disallowed codepoints are also faulted.
384    39. If PCRE was compiled with UTF support, in three places in the DFA
385        matcher there was code that should only have been obeyed in UTF mode, but
386        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
387        processing when bytes with values greater than 127 were present. In 16-bit
388        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
389        both cases the values are those that cannot be the first data item in a UTF
390        character. The three items that might have provoked this were recursions,
391        possessively repeated groups, and atomic groups.
393    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
394        and pcregrep, because some OS require shared objects to be explicitly
395        passed to ld, causing the link step to fail if they are not.
397    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
398        mode, patterns that started with \h* or \R* might be incorrectly matched.
401    Version 8.30 04-February-2012
402    -----------------------------
404    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
405        name is defined in ctype.h.
407    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
408        only in quite long subpatterns.
410    3.  Removed the function pcre_info(), which has been obsolete and deprecated
411        since it was replaced by pcre_fullinfo() in February 2000.
413    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
414        match a (*MARK), and the match failed at the start of the subject, a
415        reference to memory before the start of the subject could occur. This bug
416        was introduced by fix 17 of release 8.21.
418    5.  A reference to an unset group with zero minimum repetition was giving
419        totally wrong answers (in non-JavaScript-compatibility mode). For example,
420        /(another)?(\1?)test/ matched against "hello world test". This bug was
421        introduced in release 8.13.
423    6.  Add support for 16-bit character strings (a large amount of work involving
424        many changes and refactorings).
426    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
427        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
428        from a file.
430    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
431        rounding is not applied in this particular case).
433    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
434        if they appear, or are escaped, in patterns.
436    10. Get rid of a number of -Wunused-but-set-variable warnings.
438    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
439        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
440        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
441        also returns the mark "x". This bug applied to capturing parentheses,
442        non-capturing parentheses, and atomic parentheses. It also applied to some
443        assertions.
445    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
446        information out of configure.ac instead of relying on pcre.h.generic, which
447        is not stored in the repository.
449    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
450        -lreadline.
452    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
454    15. Applied Graycode's patch to put the top-level frame on the stack rather
455        than the heap when not using the stack for recursion. This gives a
456        performance improvement in many cases when recursion is not deep.
458    16. Experimental code added to "pcretest -C" to output the stack frame size.
461    Version 8.21 12-Dec-2011
462    ------------------------
464    1.  Updating the JIT compiler.
466    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
467        are added as well.
469    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
470        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
471        calling _pcre_jit_exec. Some extra comments are added.
473    4.  (*MARK) settings inside atomic groups that do not contain any capturing
474        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
475        was introduced by change 18 for 8.20.
477    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
478        ECMA-262 standard.
480    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
481        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
482        This bug was probably introduced by change 9 of 8.13.
484    7.  While fixing 6 above, I noticed that a number of other items were being
485        incorrectly rejected as "not fixed length". This arose partly because newer
486        opcodes had not been added to the fixed-length checking code. I have (a)
487        corrected the bug and added tests for these items, and (b) arranged for an
488        error to occur if an unknown opcode is encountered while checking for fixed
489        length instead of just assuming "not fixed length". The items that were
490        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
491        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
492        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
494    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
495        being incorrectly compiled and would have given unpredicatble results.
497    9.  A possessively repeated subpattern with minimum repeat count greater than
498        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
499        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
500        the first (A) could occur when it should not.
502    10. Add a cast and remove a redundant test from the code.
504    11. JIT should use pcre_malloc/pcre_free for allocation.
506    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
507        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
508        is anything other than /usr, -L is still shown).
510    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
512    14. Perl does not support \N without a following name in a [] class; PCRE now
513        also gives an error.
515    15. If a forward reference was repeated with an upper limit of around 2000,
516        it caused the error "internal error: overran compiling workspace". The
517        maximum number of forward references (including repeats) was limited by the
518        internal workspace, and dependent on the LINK_SIZE. The code has been
519        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
520        the default depends on LINK_SIZE. There is a new upper limit (for safety)
521        of around 200,000 forward references. While doing this, I also speeded up
522        the filling in of repeated forward references.
524    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
525        incorrectly expecting the subject to contain another "a" after the start.
527    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
528        in the match, the SKIP should be ignored. This was not happening; instead
529        the SKIP was being treated as NOMATCH. For patterns such as
530        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
531        tested.
533    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
534        now much more compatible with Perl, in particular in cases where the result
535        is a non-match for a non-anchored pattern. For example, if
536        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
537        "m", where previously it did not return a name. A side effect of this
538        change is that for partial matches, the last encountered mark name is
539        returned, as for non matches. A number of tests that were previously not
540        Perl-compatible have been moved into the Perl-compatible test files. The
541        refactoring has had the pleasing side effect of removing one argument from
542        the match() function, thus reducing its stack requirements.
544    19. If the /S+ option was used in pcretest to study a pattern using JIT,
545        subsequent uses of /S (without +) incorrectly behaved like /S+.
547    21. Retrieve executable code size support for the JIT compiler and fixing
548        some warnings.
550    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
551        not work when the shorter character appeared right at the end of the
552        subject string.
554    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
555        systems.
557    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
558        output it when the /M option is used in pcretest.
560    25. The CheckMan script was not being included in the distribution. Also, added
561        an explicit "perl" to run Perl scripts from the PrepareRelease script
562        because this is reportedly needed in Windows.
564    26. If study data was being save in a file and studying had not found a set of
565        "starts with" bytes for the pattern, the data written to the file (though
566        never used) was taken from uninitialized memory and so caused valgrind to
567        complain.
569    27. Updated RunTest.bat as provided by Sheri Pierce.
571    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
573    29. Computation of memory usage for the table of capturing group names was
574        giving an unnecessarily large value.
577    Version 8.20 21-Oct-2011
578    ------------------------
580    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
581        a POSIX class. After further experiments with Perl, which convinced me that
582        Perl has bugs and confusions, a closing square bracket is no longer allowed
583        in a POSIX name. This bug also affected patterns with classes that started
584        with full stops.
586    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
587        captured substring, but while checking the failing first alternative,
588        substring 1 is temporarily captured. If the output vector supplied to
589        pcre_exec() was not big enough for this capture, the yield of the function
590        was still zero ("insufficient space for captured substrings"). This cannot
591        be totally fixed without adding another stack variable, which seems a lot
592        of expense for a edge case. However, I have improved the situation in cases
593        such as /(a)(b)x|abc/ matched against "abc", where the return code
594        indicates that fewer than the maximum number of slots in the ovector have
595        been set.
597    3.  Related to (2) above: when there are more back references in a pattern than
598        slots in the output vector, pcre_exec() uses temporary memory during
599        matching, and copies in the captures as far as possible afterwards. It was
600        using the entire output vector, but this conflicts with the specification
601        that only 2/3 is used for passing back captured substrings. Now it uses
602        only the first 2/3, for compatibility. This is, of course, another edge
603        case.
605    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
606        main code base, and can be used by building with --enable-jit. When this is
607        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
608        runtime --no-jit option is given.
610    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
611        ovector, the return from the function was zero, implying that there were
612        other matches that did not fit. The correct "exactly full" value is now
613        returned.
615    6.  If a subpattern that was called recursively or as a subroutine contained
616        (*PRUNE) or any other control that caused it to give a non-standard return,
617        invalid errors such as "Error -26 (nested recursion at the same subject
618        position)" or even infinite loops could occur.
620    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
621        computing the minimum length on reaching *ACCEPT, and so ended up with the
622        wrong value of 1 rather than 0. Further investigation indicates that
623        computing a minimum subject length in the presence of *ACCEPT is difficult
624        (think back references, subroutine calls), and so I have changed the code
625        so that no minimum is registered for a pattern that contains *ACCEPT.
627    8.  If (*THEN) was present in the first (true) branch of a conditional group,
628        it was not handled as intended. [But see 16 below.]
630    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
631        Sheri Pierce.
633    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
634        the first byte in a match must be "a".
636    11. Change 17 for 8.13 increased the recursion depth for patterns like
637        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
638        pattern contains any instances of (*THEN). If it does not, the old
639        optimizations are restored. It would be nice to do this on a per-group
640        basis, but at the moment that is not feasible.
642    12. In some environments, the output of pcretest -C is CRLF terminated. This
643        broke RunTest's code that checks for the link size. A single white space
644        character after the value is now allowed for.
646    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
647        For "fr", it uses the Windows-specific input and output files.
649    14. If (*THEN) appeared in a group that was called recursively or as a
650        subroutine, it did not work as intended. [But see next item.]
652    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
653        pattern fragments (but not containing any | characters). If A and B are
654        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
655        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
656        D. In other words, Perl considers parentheses that do not contain any |
657        characters to be part of a surrounding alternative, whereas PCRE was
658        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
659        differently. PCRE now behaves in the same way as Perl, except in the case
660        of subroutine/recursion calls such as (?1) which have in any case always
661        been different (but PCRE had them first :-).
663    16. Related to 15 above: Perl does not treat the | in a conditional group as
664        creating alternatives. Such a group is treated in the same way as an
665        ordinary group without any | characters when processing (*THEN). PCRE has
666        been changed to match Perl's behaviour.
668    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
669        RunGrepTest script failed.
671    18. Change 22 for version 13 caused atomic groups to use more stack. This is
672        inevitable for groups that contain captures, but it can lead to a lot of
673        stack use in large patterns. The old behaviour has been restored for atomic
674        groups that do not contain any capturing parentheses.
676    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
677        suppress the check for a minimum subject length at run time. (If it was
678        given to pcre_exec() or pcre_dfa_exec() it did work.)
680    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
681        fail to work when decoding hex characters in data strings in EBCDIC
682        environments.
684    21. It appears that in at least one Mac OS environment, the isxdigit() function
685        is implemented as a macro that evaluates to its argument more than once,
686        contravening the C 90 Standard (I haven't checked a later standard). There
687        was an instance in pcretest which caused it to go wrong when processing
688        \x{...} escapes in subject strings. The has been rewritten to avoid using
689        things like p++ in the argument of isxdigit().
692    Version 8.13 16-Aug-2011
693    ------------------------
695    1.  The Unicode data tables have been updated to Unicode 6.0.0.
697    2.  Two minor typos in pcre_internal.h have been fixed.
699    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
700        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
701        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
703    4.  There were a number of related bugs in the code for matching backrefences
704        caselessly in UTF-8 mode when codes for the characters concerned were
705        different numbers of bytes. For example, U+023A and U+2C65 are an upper
706        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
707        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
708        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
709        2-byte code at the end of the subject (it thought there wasn't enough data
710        left).
712    5.  Comprehensive information about what went wrong is now returned by
713        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
714        as the output vector has at least 2 elements. The offset of the start of
715        the failing character and a reason code are placed in the vector.
717    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
718        now returned is for the first byte of the failing character, instead of the
719        last byte inspected. This is an incompatible change, but I hope it is small
720        enough not to be a problem. It makes the returned offset consistent with
721        pcre_exec() and pcre_dfa_exec().
723    7.  pcretest now gives a text phrase as well as the error number when
724        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
725        failure, the offset and reason code are output.
727    8.  When \R was used with a maximizing quantifier it failed to skip backwards
728        over a \r\n pair if the subsequent match failed. Instead, it just skipped
729        back over a single character (\n). This seems wrong (because it treated the
730        two characters as a single entity when going forwards), conflicts with the
731        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
732        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
733        has been changed.
735    9.  Some internal refactoring has changed the processing so that the handling
736        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
737        time (the PCRE_DOTALL option was changed this way some time ago: version
738        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
739        which was always a bit of a fudge. It also means that there is one less
740        argument for the match() function, which reduces its stack requirements
741        slightly. This change also fixes an incompatibility with Perl: the pattern
742        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
744    10. More internal refactoring has drastically reduced the number of recursive
745        calls to match() for possessively repeated groups such as (abc)++ when
746        using pcre_exec().
748    11. While implementing 10, a number of bugs in the handling of groups were
749        discovered and fixed:
751        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
752        (a|)*(?1) gave a compile-time internal error.
753        ((a|)+)+  did not notice that the outer group could match an empty string.
754        (^a|^)+   was not marked as anchored.
755        (.*a|.*)+ was not marked as matching at start or after a newline.
757    12. Yet more internal refactoring has removed another argument from the match()
758        function. Special calls to this function are now indicated by setting a
759        value in a variable in the "match data" data block.
761    13. Be more explicit in pcre_study() instead of relying on "default" for
762        opcodes that mean there is no starting character; this means that when new
763        ones are added and accidentally left out of pcre_study(), testing should
764        pick them up.
766    14. The -s option of pcretest has been documented for ages as being an old
767        synonym of -m (show memory usage). I have changed it to mean "force study
768        for every regex", that is, assume /S for every regex. This is similar to -i
769        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
770        using it. It makes it easier to run collections of tests with and without
771        study enabled, and thereby test pcre_study() more easily. All the standard
772        tests are now run with and without -s (but some patterns can be marked as
773        "never study" - see 20 below).
775    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
776        restoration of the capturing data to the outer values was not happening
777        correctly.
779    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
780        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
781        pattern had matched an empty string, and so incorrectly returned a no
782        match.
784    17. There was optimizing code for the last branch of non-capturing parentheses,
785        and also for the obeyed branch of a conditional subexpression, which used
786        tail recursion to cut down on stack usage. Unfortunately, now that there is
787        the possibility of (*THEN) occurring in these branches, tail recursion is
788        no longer possible because the return has to be checked for (*THEN). These
789        two optimizations have therefore been removed. [But see 8.20/11 above.]
791    18. If a pattern containing \R was studied, it was assumed that \R always
792        matched two bytes, thus causing the minimum subject length to be
793        incorrectly computed because \R can also match just one byte.
795    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
796        was incorrectly computed.
798    20. If /S is present twice on a test pattern in pcretest input, it now
799        *disables* studying, thereby overriding the use of -s on the command line
800        (see 14 above). This is necessary for one or two tests to keep the output
801        identical in both cases.
803    21. When (*ACCEPT) was used in an assertion that matched an empty string and
804        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
806    22. When an atomic group that contained a capturing parenthesis was
807        successfully matched, but the branch in which it appeared failed, the
808        capturing was not being forgotten if a higher numbered group was later
809        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
810        group 1 to "a", when in fact it should be unset. This applied to multi-
811        branched capturing and non-capturing groups, repeated or not, and also to
812        positive assertions (capturing in negative assertions does not happen
813        in PCRE) and also to nested atomic groups.
815    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
816        subject after a captured substring, to make it easier to tell which of a
817        number of identical substrings has been captured.
819    24. The way atomic groups are processed by pcre_exec() has been changed so that
820        if they are repeated, backtracking one repetition now resets captured
821        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
822        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
823        "aaa". Previously, it would have been "a". As part of this code
824        refactoring, the way recursive calls are handled has also been changed.
826    25. If an assertion condition captured any substrings, they were not passed
827        back unless some other capturing happened later. For example, if
828        (?(?=(a))a) was matched against "a", no capturing was returned.
830    26. When studying a pattern that contained subroutine calls or assertions,
831        the code for finding the minimum length of a possible match was handling
832        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
833        group 1 called group 2 while simultaneously a separate group 2 called group
834        1). A stack overflow occurred in this case. I have fixed this by limiting
835        the recursion depth to 10.
837    27. Updated RunTest.bat in the distribution to the version supplied by Tom
838        Fortmann. This supports explicit test numbers on the command line, and has
839        argument validation and error reporting.
841    28. An instance of \X with an unlimited repeat could fail if at any point the
842        first character it looked at was a mark character.
844    29. Some minor code refactoring concerning Unicode properties and scripts
845        should reduce the stack requirement of match() slightly.
847    30. Added the '=' option to pcretest to check the setting of unused capturing
848        slots at the end of the pattern, which are documented as being -1, but are
849        not included in the return count.
851    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
852        compiled something random. Now it gives a compile-time error (as does
853        Perl).
855    32. A *MARK encountered during the processing of a positive assertion is now
856        recorded and passed back (compatible with Perl).
858    33. If --only-matching or --colour was set on a pcregrep call whose pattern
859        had alternative anchored branches, the search for a second match in a line
860        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
861        matched the line "0102" twice. The same bug affected patterns that started
862        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
863        twice.
865    34. Previously, PCRE did not allow quantification of assertions. However, Perl
866        does, and because of capturing effects, quantifying parenthesized
867        assertions may at times be useful. Quantifiers are now allowed for
868        parenthesized assertions.
870    35. A minor code tidy in pcre_compile() when checking options for \R usage.
872    36. \g was being checked for fancy things in a character class, when it should
873        just be a literal "g".
875    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
876        appearance of a nested POSIX class supersedes an apparent external class.
877        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
878        unescaped square brackets may also appear as part of class names. For
879        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
880        more like Perl. (But see 8.20/1 above.)
882    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
883        was because it thought it was \N{name}, which is not supported).
885    39. Add minix to OS list not supporting the -S option in pcretest.
887    40. PCRE tries to detect cases of infinite recursion at compile time, but it
888        cannot analyze patterns in sufficient detail to catch mutual recursions
889        such as ((?1))((?2)). There is now a runtime test that gives an error if a
890        subgroup is called recursively as a subpattern for a second time at the
891        same position in the subject string. In previous releases this might have
892        been caught by the recursion limit, or it might have run out of stack.
894    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
895        happen only once. PCRE was, however incorrectly giving a compile time error
896        "recursive call could loop indefinitely" because it cannot analyze the
897        pattern in sufficient detail. The compile time test no longer happens when
898        PCRE is compiling a conditional subpattern, but actual runaway loops are
899        now caught at runtime (see 40 above).
901    42. It seems that Perl allows any characters other than a closing parenthesis
902        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
903        has been changed to be the same.
905    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
906        as not to get warnings when autogen.sh is called. Also changed
907        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
909    44. To help people who use pcregrep to scan files containing exceedingly long
910        lines, the following changes have been made:
912        (a) The default value of the buffer size parameter has been increased from
913            8K to 20K. (The actual buffer used is three times this size.)
915        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
916            PCRE is built.
918        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
919            to be set at run time.
921        (d) Numerical values in pcregrep options can be followed by K or M, for
922            example --buffer-size=50K.
924        (e) If a line being scanned overflows pcregrep's buffer, an error is now
925            given and the return code is set to 2.
927    45. Add a pointer to the latest mark to the callout data block.
929    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
930        partial match of an empty string instead of no match. This was specific to
931        the use of ".".
933    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
934        complete match instead of a partial match. This bug was dependent on both
935        the PCRE_UTF8 and PCRE_DOTALL options being set.
937    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
938        starting byte set, because \b was not being ignored.
941    Version 8.12 15-Jan-2011
942    ------------------------
944    1.  Fixed some typos in the markup of the man pages, and wrote a script that
945        checks for such things as part of the documentation building process.
947    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
948        --match-limit and --recursion-limit options (added for 8.11). In
949        particular, this made one of the standard tests fail. (The integer value
950        went into the wrong half of a long int.)
952    3.  If the --colour option was given to pcregrep with -v (invert match), it
953        did strange things, either producing crazy output, or crashing. It should,
954        of course, ignore a request for colour when reporting lines that do not
955        match.
957    4.  Another pcregrep bug caused similar problems if --colour was specified with
958        -M (multiline) and the pattern match finished with a line ending.
960    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
961        matched in multiline mode, the following line was shown as part of the
962        match. This seems wrong, so I have changed it.
964    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
965        the check for further matches in the same line (so they could be coloured)
966        to overrun the end of the current line. If another match was found, it was
967        incorrectly shown (and then shown again when found in the next line).
969    7.  If pcregrep was compiled under Windows, there was a reference to the
970        function pcregrep_exit() before it was defined. I am assuming this was
971        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
972        reported by a user. I've moved the definition above the reference.
975    Version 8.11 10-Dec-2010
976    ------------------------
978    1.  (*THEN) was not working properly if there were untried alternatives prior
979        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
980        backtracked to try for "b" instead of moving to the next alternative branch
981        at the same level (in this case, to look for "c"). The Perl documentation
982        is clear that when (*THEN) is backtracked onto, it goes to the "next
983        alternative in the innermost enclosing group".
985    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
986        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
987        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
988        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
989        (*THEN).
991    3.  If \s appeared in a character class, it removed the VT character from
992        the class, even if it had been included by some previous item, for example
993        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
994        of \s, but is part of the POSIX "space" class.)
996    4.  A partial match never returns an empty string (because you can always
997        match an empty string at the end of the subject); however the checking for
998        an empty string was starting at the "start of match" point. This has been
999        changed to the "earliest inspected character" point, because the returned
1000        data for a partial match starts at this character. This means that, for
1001        example, /(?<=abc)def/ gives a partial match for the subject "abc"
1002        (previously it gave "no match").
1004    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1005        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1006        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1007        has an implication that the given string is incomplete (because a partial
1008        match is preferred over a full match). For this reason, these items now
1009        give a partial match in this situation. [Aside: previously, the one case
1010        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1011        match rather than a full match, which was wrong by the old rules, but is
1012        now correct.]
1014    6.  There was a bug in the handling of #-introduced comments, recognized when
1015        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1016        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1017        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1018        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1019        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1020        places in pcre_compile().
1022    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1023        comments when looking ahead for named forward references to subpatterns,
1024        the only newline sequence it recognized was NL. It now handles newlines
1025        according to the set newline convention.
1027    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1028        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1029        cater for a lack of strerror(). These oversights have been fixed.
1031    9.  Added --match-limit and --recursion-limit to pcregrep.
1033    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1035    11. When the -o option was used, pcregrep was setting a return code of 1, even
1036        when matches were found, and --line-buffered was not being honoured.
1038    12. Added an optional parentheses number to the -o and --only-matching options
1039        of pcregrep.
1041    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1042        can match an empty string. The code to do it in pcretest and pcredemo
1043        needed fixing:
1045        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1046            only one byte after an empty string match just before CRLF (this case
1047            just got forgotten; "any" and "anycrlf" were OK).
1049        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1050            mode when an empty string match preceded an ASCII character followed by
1051            a non-ASCII character. (The code for advancing by one character rather
1052            than one byte was nonsense.)
1054        (c) The pcredemo.c sample program did not have any code at all to handle
1055            the cases when CRLF is a valid newline sequence.
1057    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1058        as a starting offset was within the subject string. There is now a new
1059        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1060        negative or greater than the length of the string. In order to test this,
1061        pcretest is extended to allow the setting of negative starting offsets.
1063    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1064        starting offset points to the beginning of a UTF-8 character was
1065        unnecessarily clumsy. I tidied it up.
1067    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1068        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1070    17. Nobody had reported that the --include_dir option, which was added in
1071        release 7.7 should have been called --include-dir (hyphen, not underscore)
1072        for compatibility with GNU grep. I have changed it to --include-dir, but
1073        left --include_dir as an undocumented synonym, and the same for
1074        --exclude-dir, though that is not available in GNU grep, at least as of
1075        release 2.5.4.
1077    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1078        characters from a string of bytes) have been redefined so as not to use
1079        loops, in order to improve performance in some environments. At the same
1080        time, I abstracted some of the common code into auxiliary macros to save
1081        repetition (this should not affect the compiled code).
1083    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1084        compile-time error is now given if \c is not followed by an ASCII
1085        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1086        different, and any byte value is allowed.)
1088    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1089        START_OPTIMIZE option, which is now allowed at compile time - but just
1090        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1091        to pcregrep and other applications that have no direct access to PCRE
1092        options. The new /Y option in pcretest sets this option when calling
1093        pcre_compile().
1095    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1096        back references. Groups containing recursive back references were forced to
1097        be atomic by that change, but in the case of named groups, the amount of
1098        memory required was incorrectly computed, leading to "Failed: internal
1099        error: code overflow". This has been fixed.
1101    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1102        pcretest.c, to avoid build problems in some Borland environments.
1105    Version 8.10 25-Jun-2010
1106    ------------------------
1108    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1109        THEN.
1111    2.  (*ACCEPT) was not working when inside an atomic group.
1113    3.  Inside a character class, \B is treated as a literal by default, but
1114        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1115        causes the error). The code is unchanged, but I tidied the documentation.
1117    4.  Inside a character class, PCRE always treated \R and \X as literals,
1118        whereas Perl faults them if its -w option is set. I have changed PCRE so
1119        that it faults them when PCRE_EXTRA is set.
1121    5.  Added support for \N, which always matches any character other than
1122        newline. (It is the same as "." when PCRE_DOTALL is not set.)
1124    6.  When compiling pcregrep with newer versions of gcc which may have
1125        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1126        declared with attribute warn_unused_result" were given. Just casting the
1127        result to (void) does not stop the warnings; a more elaborate fudge is
1128        needed. I've used a macro to implement this.
1130    7.  Minor change to pcretest.c to avoid a compiler warning.
1132    8.  Added four artifical Unicode properties to help with an option to make
1133        \s etc use properties (see next item). The new properties are: Xan
1134        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1136    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1137        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1138        this option. Modified pcretest to add /W to test this facility. Added
1139        REG_UCP to make it available via the POSIX interface.
1141    10. Added --line-buffered to pcregrep.
1143    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1144        studied, and the match started with a letter with a code point greater than
1145        127 whose first byte was different to the first byte of the other case of
1146        the letter, the other case of this starting letter was not recognized
1147        (#976).
1149    12. If a pattern that was studied started with a repeated Unicode property
1150        test, for example, \p{Nd}+, there was the theoretical possibility of
1151        setting up an incorrect bitmap of starting bytes, but fortunately it could
1152        not have actually happened in practice until change 8 above was made (it
1153        added property types that matched character-matching opcodes).
1155    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1156        possible starting bytes for non-anchored patterns.
1158    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1159        \R, and also a number of cases that involve Unicode properties, both
1160        explicit and implicit when PCRE_UCP is set.
1162    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1163        input, it could crash or give wrong results if characters with values
1164        greater than 0xc0 were present in the subject string. (Detail: it assumed
1165        UTF-8 input when processing these items.)
1167    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1168        size_t is 64-bit (#991).
1170    17. Added a check for running out of memory when PCRE is compiled with
1171        --disable-stack-for-recursion (#990).
1173    18. If the last data line in a file for pcretest does not have a newline on
1174        the end, a newline was missing in the output.
1176    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1177        less than 128) in its various bitmaps. However, there is a facility for
1178        generating tables according to the current locale when PCRE is compiled. It
1179        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1180        characters, are recognized by isspace() and therefore were getting set in
1181        these tables, and indeed these tables seem to approximate to ISO 8859. This
1182        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1183        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1184        which of course cannot start UTF-8 characters. I have changed the code so
1185        that only real ASCII characters (less than 128) and the correct starting
1186        bytes for UTF-8 encodings are set for characters greater than 127 when in
1187        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1188        altogether.)
1190    20. Added the /T option to pcretest so as to be able to run tests with non-
1191        standard character tables, thus making it possible to include the tests
1192        used for 19 above in the standard set of tests.
1194    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1195        reference to a subpattern the other side of a comment that contains an
1196        opening parenthesis caused either an internal compiling error, or a
1197        reference to the wrong subpattern.
1200    Version 8.02 19-Mar-2010
1201    ------------------------
1203    1.  The Unicode data tables have been updated to Unicode 5.2.0.
1205    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
1206        configured.
1208    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
1209        original author of that file, following a query about its status.
1211    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
1212        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1214    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1215        quantifier applied to a forward-referencing subroutine call, could compile
1216        incorrect code or give the error "internal error: previously-checked
1217        referenced subpattern not found".
1219    6.  Both MS Visual Studio and Symbian OS have problems with initializing
1220        variables to point to external functions. For these systems, therefore,
1221        pcre_malloc etc. are now initialized to local functions that call the
1222        relevant global functions.
1224    7.  There were two entries missing in the vectors called coptable and poptable
1225        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1226        I've fixed the data, and added a kludgy way of testing at compile time that
1227        the lengths are correct (equal to the number of opcodes).
1229    8.  Following on from 7, I added a similar kludge to check the length of the
1230        eint vector in pcreposix.c.
1232    9.  Error texts for pcre_compile() are held as one long string to avoid too
1233        much relocation at load time. To find a text, the string is searched,
1234        counting zeros. There was no check for running off the end of the string,
1235        which could happen if a new error number was added without updating the
1236        string.
1238    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1240    11. \K was not working if it appeared in an atomic group or in a group that
1241        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1242        \K is "not well defined" if used in an assertion. PCRE now accepts it if
1243        the assertion is positive, but not if it is negative.
1245    12. Change 11 fortuitously reduced the size of the stack frame used in the
1246        "match()" function of pcre_exec.c by one pointer. Forthcoming
1247        implementation of support for (*MARK) will need an extra pointer on the
1248        stack; I have reserved it now, so that the stack frame size does not
1249        decrease.
1251    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1252        item in branch that calls a recursion is a subroutine call - as in the
1253        second branch in the above example - was incorrectly given the compile-
1254        time error "recursive call could loop indefinitely" because pcre_compile()
1255        was not correctly checking the subroutine for matching a non-empty string.
1257    14. The checks for overrunning compiling workspace could trigger after an
1258        overrun had occurred. This is a "should never occur" error, but it can be
1259        triggered by pathological patterns such as hundreds of nested parentheses.
1260        The checks now trigger 100 bytes before the end of the workspace.
1262    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1265    Version 8.01 19-Jan-2010
1266    ------------------------
1268    1.  If a pattern contained a conditional subpattern with only one branch (in
1269        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
1270        computed the wrong minimum data length (which is of course zero for such
1271        subpatterns). This could cause incorrect "no match" results.
1273    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
1274        the pattern is reset in the first branch, pcre_compile() failed with
1275        "internal error: code overflow at offset...". This happened only when
1276        the reset was to the original external option setting. (An optimization
1277        abstracts leading options settings into an external setting, which was the
1278        cause of this.)
1280    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
1281        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
1282        assertion pattern did not match (meaning that the assertion was true), it
1283        was incorrectly treated as false if the SKIP had been reached during the
1284        matching. This also applied to assertions used as conditions.
1286    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
1287        assertion subpattern, including such a pattern used as a condition,
1288        unpredictable results occurred, instead of the error return
1291    5.  The C++ GlobalReplace function was not working like Perl for the special
1292        situation when an empty string is matched. It now does the fancy magic
1293        stuff that is necessary.
1295    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
1296        removed. (These were left over from very, very early versions of PCRE.)
1298    7.  Some cosmetic changes to the code to make life easier when compiling it
1299        as part of something else:
1301        (a) Change DEBUG to PCRE_DEBUG.
1303        (b) In pcre_compile(), rename the member of the "branch_chain" structure
1304            called "current" as "current_branch", to prevent a collision with the
1305            Linux macro when compiled as a kernel module.
1307        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
1308            prevent a collision with the Linux macro when compiled as a kernel
1309            module.
1311    8.  In pcre_compile() there are some checks for integer overflows that used to
1312        cast potentially large values to (double). This has been changed to that
1313        when building, a check for int64_t is made, and if it is found, it is used
1314        instead, thus avoiding the use of floating point arithmetic. (There is no
1315        other use of FP in PCRE.) If int64_t is not found, the fallback is to
1316        double.
1318    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
1319        2005 (difference between two addresses compared to an unsigned value).
1321    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
1322        custom one, because of the following reported problem in Windows:
1324          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
1325              under Win32.
1326          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
1327              therefore missing the function definition.
1328          - The compiler thus generates a "C" signature for the test function.
1329          - The linker fails to find the "C" function.
1330          - PCRE fails to configure if asked to do so against libbz2.
1332    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
1333        messages were output:
1335          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
1336          rerunning libtoolize, to keep the correct libtool macros in-tree.
1337          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
1339        I have done both of these things.
1341    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
1342        most of the time, it *can* run out if it is given a pattern that contains a
1343        runaway infinite recursion. I updated the discussion in the pcrestack man
1344        page.
1346    13. Now that we have gone to the x.xx style of version numbers, the minor
1347        version may start with zero. Using 08 or 09 is a bad idea because users
1348        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
1349        interpreted as invalid octal numbers. I've updated the previous comment in
1350        configure.ac, and also added a check that gives an error if 08 or 09 are
1351        used.
1353    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
1354        causing partial matching to fail when the end of the subject matched \W
1355        in a UTF-8 pattern where \W was quantified with a minimum of 3.
1357    15. There were some discrepancies between the declarations in pcre_internal.h
1358        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
1359        their definitions. The declarations used "const uschar *" and the
1360        definitions used USPTR. Even though USPTR is normally defined as "const
1361        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
1362        reported that: "This difference in casting confuses some C++ compilers, for
1363        example, SunCC recognizes above declarations as different functions and
1364        generates broken code for hbpcre." I have changed the declarations to use
1365        USPTR.
1367    16. GNU libtool is named differently on some systems. The autogen.sh script now
1368        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
1369        (FreeBSD).
1371    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
1372        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
1373        comment: "Figure out how to create a longlong from a string: strtoll and
1374        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
1375        instance, but it only takes 2 args instead of 3!"
1377    18. A subtle bug concerned with back references has been fixed by a change of
1378        specification, with a corresponding code fix. A pattern such as
1379        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
1380        refers, was giving matches when it shouldn't. For example, xa=xaaa would
1381        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
1382        same bug. Such groups have to be quantified to be useful, or contained
1383        inside another quantified group. (If there's no repetition, the reference
1384        can never match.) The problem arises because, having left the group and
1385        moved on to the rest of the pattern, a later failure that backtracks into
1386        the group uses the captured value from the final iteration of the group
1387        rather than the correct earlier one. I have fixed this in PCRE by forcing
1388        any group that contains a reference to itself to be an atomic group; that
1389        is, there cannot be any backtracking into it once it has completed. This is
1390        similar to recursive and subroutine calls.
1393    Version 8.00 19-Oct-09
1394    ----------------------
1396    1.  The table for translating pcre_compile() error codes into POSIX error codes
1397        was out-of-date, and there was no check on the pcre_compile() error code
1398        being within the table. This could lead to an OK return being given in
1399        error.
1401    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
1402        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
1403        in a Windows environment.
1405    3.  The pcregrep --count option prints the count for each file even when it is
1406        zero, as does GNU grep. However, pcregrep was also printing all files when
1407        --files-with-matches was added. Now, when both options are given, it prints
1408        counts only for those files that have at least one match. (GNU grep just
1409        prints the file name in this circumstance, but including the count seems
1410        more useful - otherwise, why use --count?) Also ensured that the
1411        combination -clh just lists non-zero counts, with no names.
1413    4.  The long form of the pcregrep -F option was incorrectly implemented as
1414        --fixed_strings instead of --fixed-strings. This is an incompatible change,
1415        but it seems right to fix it, and I didn't think it was worth preserving
1416        the old behaviour.
1418    5.  The command line items --regex=pattern and --regexp=pattern were not
1419        recognized by pcregrep, which required --regex pattern or --regexp pattern
1420        (with a space rather than an '='). The man page documented the '=' forms,
1421        which are compatible with GNU grep; these now work.
1423    6.  No libpcreposix.pc file was created for pkg-config; there was just
1424        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
1426    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
1427        when UCP support is not needed, by modifying the Python script that
1428        generates it from Unicode data files. This should not matter if the module
1429        is correctly used as a library, but I received one complaint about 50K of
1430        unwanted data. My guess is that the person linked everything into his
1431        program rather than using a library. Anyway, it does no harm.
1433    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
1434        was a minimum greater than 1 for a wide character in a possessive
1435        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
1436        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
1437        character. Chaos in the form of incorrect output or a compiling loop could
1438        result.
1440    9.  The restrictions on what a pattern can contain when partial matching is
1441        requested for pcre_exec() have been removed. All patterns can now be
1442        partially matched by this function. In addition, if there are at least two
1443        slots in the offset vector, the offset of the earliest inspected character
1444        for the match and the offset of the end of the subject are set in them when
1445        PCRE_ERROR_PARTIAL is returned.
1447    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
1448        synonymous with PCRE_PARTIAL, for backwards compatibility, and
1449        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
1450        and may be more useful for multi-segment matching.
1452    11. Partial matching with pcre_exec() is now more intuitive. A partial match
1453        used to be given if ever the end of the subject was reached; now it is
1454        given only if matching could not proceed because another character was
1455        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
1456        string "Z", which now yields "no match" instead of "partial match". In the
1457        case of pcre_dfa_exec(), "no match" is given if every matching path for the
1458        final character ended with (*FAIL).
1460    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
1461        if the pattern had a "must contain" character that was already found in the
1462        earlier partial match, unless partial matching was again requested. For
1463        example, with the pattern /dog.(body)?/, the "must contain" character is
1464        "g". If the first part-match was for the string "dog", restarting with
1465        "sbody" failed. This bug has been fixed.
1467    13. The string returned by pcre_dfa_exec() after a partial match has been
1468        changed so that it starts at the first inspected character rather than the
1469        first character of the match. This makes a difference only if the pattern
1470        starts with a lookbehind assertion or \b or \B (\K is not supported by
1471        pcre_dfa_exec()). It's an incompatible change, but it makes the two
1472        matching functions compatible, and I think it's the right thing to do.
1474    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
1475        so that the demonstration program is easily available in environments where
1476        PCRE has not been installed from source.
1478    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
1479        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
1480        library.
1482    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
1483        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
1484        is not the first non-POSIX option to be added. Clearly some people find
1485        these options useful.
1487    17. If a caller to the POSIX matching function regexec() passes a non-zero
1488        value for nmatch with a NULL value for pmatch, the value of
1489        nmatch is forced to zero.
1491    18. RunGrepTest did not have a test for the availability of the -u option of
1492        the diff command, as RunTest does. It now checks in the same way as
1493        RunTest, and also checks for the -b option.
1495    19. If an odd number of negated classes containing just a single character
1496        interposed, within parentheses, between a forward reference to a named
1497        subpattern and the definition of the subpattern, compilation crashed with
1498        an internal error, complaining that it could not find the referenced
1499        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
1500        [The bug was that it was starting one character too far in when skipping
1501        over the character class, thus treating the ] as data rather than
1502        terminating the class. This meant it could skip too much.]
1504    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
1505        /g option in pcretest when the pattern contains \K, which makes it possible
1506        to have an empty string match not at the start, even when the pattern is
1507        anchored. Updated pcretest and pcredemo to use this option.
1509    21. If the maximum number of capturing subpatterns in a recursion was greater
1510        than the maximum at the outer level, the higher number was returned, but
1511        with unset values at the outer level. The correct (outer level) value is
1512        now given.
1514    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
1515        PCRE did not set those parentheses (unlike Perl). I have now found a way to
1516        make it do so. The string so far is captured, making this feature
1517        compatible with Perl.
1519    23. The tests have been re-organized, adding tests 11 and 12, to make it
1520        possible to check the Perl 5.10 features against Perl 5.10.
1522    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
1523        pattern matches a fixed length string. PCRE did not allow this; now it
1524        does. Neither allows recursion.
1526    25. I finally figured out how to implement a request to provide the minimum
1527        length of subject string that was needed in order to match a given pattern.
1528        (It was back references and recursion that I had previously got hung up
1529        on.) This code has now been added to pcre_study(); it finds a lower bound
1530        to the length of subject needed. It is not necessarily the greatest lower
1531        bound, but using it to avoid searching strings that are too short does give
1532        some useful speed-ups. The value is available to calling programs via
1533        pcre_fullinfo().
1535    26. While implementing 25, I discovered to my embarrassment that pcretest had
1536        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
1537        study optimizations had never been tested with that matching function.
1538        Oops. What is worse, even when it was passed study data, there was a bug in
1539        pcre_dfa_exec() that meant it never actually used it. Double oops. There
1540        were also very few tests of studied patterns with pcre_dfa_exec().
1542    27. If (?| is used to create subpatterns with duplicate numbers, they are now
1543        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
1544        on the other side of the coin, they are no longer allowed to have different
1545        names, because these cannot be distinguished in PCRE, and this has caused
1546        confusion. (This is a difference from Perl.)
1548    28. When duplicate subpattern names are present (necessarily with different
1549        numbers, as required by 27 above), and a test is made by name in a
1550        conditional pattern, either for a subpattern having been matched, or for
1551        recursion in such a pattern, all the associated numbered subpatterns are
1552        tested, and the overall condition is true if the condition is true for any
1553        one of them. This is the way Perl works, and is also more like the way
1554        testing by number works.
1557    Version 7.9 11-Apr-09
1558    ---------------------
1560    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
1561        (pcretest), all targets were linked against these libraries. This included
1562        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
1563        libraries. This caused unwanted dependencies to be created. This problem
1564        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
1565        pcretest is linked with readline.
1567    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
1568        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
1569        moved outside it again, because FALSE and TRUE are already defined in AIX,
1570        but BOOL is not.
1572    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
1573        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
1575    4.  The pcregrep documentation said spaces were inserted as well as colons (or
1576        hyphens) following file names and line numbers when outputting matching
1577        lines. This is not true; no spaces are inserted. I have also clarified the
1578        wording for the --colour (or --color) option.
1580    5.  In pcregrep, when --colour was used with -o, the list of matching strings
1581        was not coloured; this is different to GNU grep, so I have changed it to be
1582        the same.
1584    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
1585        each matching line was coloured. Now it goes on to look for further matches
1586        of any of the test patterns, which is the same behaviour as GNU grep.
1588    7.  A pattern that could match an empty string could cause pcregrep to loop; it
1589        doesn't make sense to accept an empty string match in pcregrep, so I have
1590        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1591        seems to be how GNU grep behaves.
1593    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1594        start or after a newline", because the conditional assertion was not being
1595        correctly handled. The rule now is that both the assertion and what follows
1596        in the first alternative must satisfy the test.
1598    9.  If auto-callout was enabled in a pattern with a conditional group whose
1599        condition was an assertion, PCRE could crash during matching, both with
1600        pcre_exec() and pcre_dfa_exec().
1602    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
1603        used for matching.
1605    11. Unicode property support in character classes was not working for
1606        characters (bytes) greater than 127 when not in UTF-8 mode.
1608    12. Added the -M command line option to pcretest.
1610    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
1612    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
1614    16. Added comments and documentation about mis-use of no_arg in the C++
1615        wrapper.
1617    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
1618        from Martin Jerabek that uses macro names for all relevant character and
1619        string constants.
1621    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
1622        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
1623        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
1624        these, but not everybody uses configure.
1626    19. A conditional group that had only one branch was not being correctly
1627        recognized as an item that could match an empty string. This meant that an
1628        enclosing group might also not be so recognized, causing infinite looping
1629        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
1630        with the subject "ab", where knowledge that the repeated group can match
1631        nothing is needed in order to break the loop.
1633    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
1634        exec(), but without supplying a callout function, matching went wrong.
1636    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
1637        leak if the size of the offset vector was greater than 30. When the vector
1638        is smaller, the saved offsets during recursion go onto a local stack
1639        vector, but for larger vectors malloc() is used. It was failing to free
1640        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
1641        error, in fact).
1643    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
1644        heapframe that is used only when UTF-8 support is enabled. This caused no
1645        problem, but was untidy.
1647    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
1648        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
1649        included within another project.
1651    24. Steven Van Ingelgem's patches to add more options to the CMake support,
1652        slightly modified by me:
1654          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
1655              not building pcregrep.
1657          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
1658              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
1660    25. Forward references, both numeric and by name, in patterns that made use of
1661        duplicate group numbers, could behave incorrectly or give incorrect errors,
1662        because when scanning forward to find the reference group, PCRE was not
1663        taking into account the duplicate group numbers. A pattern such as
1664        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
1666    26. Changed a few more instances of "const unsigned char *" to USPTR, making
1667        the feature of a custom pointer more persuasive (as requested by a user).
1669    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
1670        pcretest.c, inside #ifndefs, because it seems they are sometimes already
1671        pre-defined.
1673    28. Added support for (*UTF8) at the start of a pattern.
1675    29. Arrange for flags added by the "release type" setting in CMake to be shown
1676        in the configuration summary.
1679    Version 7.8 05-Sep-08
1680    ---------------------
1682    1.  Replaced UCP searching code with optimized version as implemented for Ad
1683        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
1684        stage table and inline lookup instead of a function, giving speed ups of 2
1685        to 5 times on some simple patterns that I tested. Permission was given to
1686        distribute the MultiStage2.py script that generates the tables (it's not in
1687        the tarball, but is in the Subversion repository).
1689    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
1690        scripts.
1692    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
1693        a group with a zero qualifier. The result of the study could be incorrect,
1694        or the function might crash, depending on the pattern.
1696    4.  Caseless matching was not working for non-ASCII characters in back
1697        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
1698        It now works when Unicode Property Support is available.
1700    5.  In pcretest, an escape such as \x{de} in the data was always generating
1701        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
1702        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
1703        truncation.
1705    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
1707    7.  Added two (int) casts to pcregrep when printing the difference of two
1708        pointers, in case they are 64-bit values.
1710    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
1711        test 2 if it fails.
1713    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
1714        and a #define of that name to empty if it is not externally set. This is to
1715        allow users of MSVC to set it if necessary.
1717    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
1718        the convenience functions in the pcre_get.c source file.
1720    11. An option change at the start of a pattern that had top-level alternatives
1721        could cause overwriting and/or a crash. This command provoked a crash in
1722        some environments:
1724          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
1726        This potential security problem was recorded as CVE-2008-2371.
1728    12. For a pattern where the match had to start at the beginning or immediately
1729        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
1730        pcre_dfa_exec() could read past the end of the passed subject if there was
1731        no match. To help with detecting such bugs (e.g. with valgrind), I modified
1732        pcretest so that it places the subject at the end of its malloc-ed buffer.
1734    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
1735        exec() might read past the end of the data buffer in UTF-8 mode.
1737    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
1738        the data contained the byte 0x85 as part of a UTF-8 character within its
1739        first line. This applied both to normal and DFA matching.
1741    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
1742        /^[^d]*?$/8 failed to match "abc".
1744    16. Added a missing copyright notice to pcrecpp_internal.h.
1746    17. Make it more clear in the documentation that values returned from
1747        pcre_exec() in ovector are byte offsets, not character counts.
1749    18. Tidied a few places to stop certain compilers from issuing warnings.
1751    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
1752        supplied by Stefan Weber. I made a further small update for 7.8 because
1753        there is a change of source arrangements: the pcre_searchfuncs.c module is
1754        replaced by pcre_ucd.c.
1757    Version 7.7 07-May-08
1758  ---------------------  ---------------------
1760  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
1761      a string to a long long, pretend we don't even have a long long." This is      a string to a long long, pretend we don't even have a long long." This is
1762      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
1764  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
1765      pre-7.6 versions, which defined a global no_arg variable instead of putting      pre-7.6 versions, which defined a global no_arg variable instead of putting
1766      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
1768  3.  Remove a line of dead code, identified by coverity and reported by Nuno  3.  Remove a line of dead code, identified by coverity and reported by Nuno
1769      Lopes.      Lopes.
1771  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
1773      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
1774          of files, instead of just to the final components.          of files, instead of just to the final components.
1776      (2) If there was more than one level of directory, the subdirectories were      (2) If there was more than one level of directory, the subdirectories were
1777          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
1778          inconsistent with GNU grep (and could even be seen as contrary to the          inconsistent with GNU grep (and could even be seen as contrary to the
1779          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
1780          The action now is always to scan all levels of directory, and just          The action now is always to scan all levels of directory, and just
1781          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
1783  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
1784      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
1786  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
1787      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
1788      doesn't support NULs in patterns.      doesn't support NULs in patterns.
1790  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
1791      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
1793  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
1794      caused by fix #2  above. (Subsequently also a second patch to fix the      caused by fix #2  above. (Subsequently also a second patch to fix the
1795      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
1797  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
1799  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
1800      matching function regexec().      matching function regexec().
1802  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',  11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
1803      which, however, unlike Perl's \g{...}, are subroutine calls, not back      which, however, unlike Perl's \g{...}, are subroutine calls, not back
1804      references. PCRE supports relative numbers with this syntax (I don't think      references. PCRE supports relative numbers with this syntax (I don't think
1805      Oniguruma does).      Oniguruma does).
1807  12. Previously, a group with a zero repeat such as (...){0} was completely  12. Previously, a group with a zero repeat such as (...){0} was completely
1808      omitted from the compiled regex. However, this means that if the group      omitted from the compiled regex. However, this means that if the group
1809      was called as a subroutine from elsewhere in the pattern, things went wrong      was called as a subroutine from elsewhere in the pattern, things went wrong
1810      (an internal error was given). Such groups are now left in the compiled      (an internal error was given). Such groups are now left in the compiled
1811      pattern, with a new opcode that causes them to be skipped at execution      pattern, with a new opcode that causes them to be skipped at execution
1812      time.      time.
1814  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes  13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
1815      to the way PCRE behaves:      to the way PCRE behaves:
1817      (a) A lone ] character is dis-allowed (Perl treats it as data).      (a) A lone ] character is dis-allowed (Perl treats it as data).
1819      (b) A back reference to an unmatched subpattern matches an empty string      (b) A back reference to an unmatched subpattern matches an empty string
1820          (Perl fails the current match path).          (Perl fails the current match path).
1822      (c) A data ] in a character class must be notated as \] because if the      (c) A data ] in a character class must be notated as \] because if the
1823          first data character in a class is ], it defines an empty class. (In          first data character in a class is ], it defines an empty class. (In
1824          Perl it is not possible to have an empty class.) The empty class []          Perl it is not possible to have an empty class.) The empty class []
1825          never matches; it forces failure and is equivalent to (*FAIL) or (?!).          never matches; it forces failure and is equivalent to (*FAIL) or (?!).
1826          The negative empty class [^] matches any one character, independently          The negative empty class [^] matches any one character, independently
1827          of the DOTALL setting.          of the DOTALL setting.
1829  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a  14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
1830      non-existent subpattern following a character class starting with ']' and      non-existent subpattern following a character class starting with ']' and
1831      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
1832      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
1833      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
1834      existencd of the subpattern, it was treating the data ']' as terminating      existencd of the subpattern, it was treating the data ']' as terminating
1835      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
1836      was subsequently set up correctly.)      was subsequently set up correctly.)
1838  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;  15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1839      it was being rejected as not supported by pcre_dfa_exec(), even though      it was being rejected as not supported by pcre_dfa_exec(), even though
1840      other assertions are supported. I have made pcre_dfa_exec() support      other assertions are supported. I have made pcre_dfa_exec() support
1841      (*FAIL).      (*FAIL).
1843    16. The implementation of 13c above involved the invention of a new opcode,
1844        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1845        cannot be changed at match time, I realized I could make a small
1846        improvement to matching performance by compiling OP_ALLANY instead of
1847        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1848        on the OP_ANY path.
1850    17. Compiling pcretest on Windows with readline support failed without the
1851        following two fixes: (1) Make the unistd.h include conditional on
1852        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1854    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1855        ncurses library to be included for pcretest when ReadLine support is
1856        requested, but also to allow for it to be overridden. This patch came from
1857        Daniel Bergström.
1859    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1860        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1861        any errors with the current Unicode tables. Thanks to Peter Kankowski for
1862        spotting this.
1865  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08

Removed from v.341  
changed lines
  Added in v.1260

  ViewVC Help
Powered by ViewVC 1.1.5