ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 498 by ph10, Wed Mar 3 19:29:38 2010 UTC revision 1334 by ph10, Wed May 15 16:53:18 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.02 01-Mar-2010  Version 8.33 28-April-2013
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.
83    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
84        which points out that "non characters" are not "characters that may not
85        appear in Unicode strings" but rather "characters that are reserved for
86        internal use and have only local meaning".
88    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
89        there was a conditional group that depended on an assertion, if the
90        assertion was false, the callout that immediately followed the alternation
91        in the condition was skipped when pcre_exec() was used for matching.
93    23. Allow an explicit callout to be inserted before an assertion that is the
94        condition for a conditional group, for compatibility with automatic
95        callouts, which always insert a callout at this point.
97    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
98        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
100    25. (*PRUNE) is now supported by the JIT compiler.
102    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
104    27. Fix the case where there are two or more SKIPs with arguments that may be
105        ignored.
107    28. (*SKIP) is now supported by the JIT compiler.
109    29. (*THEN) is now supported by the JIT compiler.
111    30. Update RunTest with additional test selector options.
113    31. The way PCRE handles backtracking verbs has been changed in two ways.
115        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
116        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
117        backtracking. In some cases this makes it more Perl-compatible, but Perl's
118        rather obscure rules do not always do the same thing.
120        (2) Previously, backtracking verbs were confined within assertions. This is
121        no longer the case for positive assertions, except for (*ACCEPT). Again,
122        this sometimes improves Perl compatibility, and sometimes does not.
124    32. A number of tests that were in test 2 because Perl did things differently
125        have been moved to test 1, because either Perl or PCRE has changed, and
126        these tests are now compatible.
128    32. Control verbs are handled in the same way in JIT and interpreter.
130    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
131        contained a forward subroutine reference caused a compile error.
133    34. Auto-detect and optimize limited repetitions in JIT.
135    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
136        blocking (*UTF) etc.
138    36. In the interpreter, maximizing pattern repetitions for characters and
139        character types now use tail recursion, which reduces stack usage.
141    37. The value of the max lookbehind was not correctly preserved if a compiled
142        and saved regex was reloaded on a host of different endianness.
144    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
145        of the compiled pattern block, expand the flags field from 16 to 32 bits
146        because it was almost full.
148    39. Try madvise first before posix_madvise.
150    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
151        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
152        original change locked out all matches of empty strings. This has been
153        changed so that one match of an empty string per line is recognized.
154        Subsequent searches on the same line (for colouring or for --only-matching,
155        for example) do not recognize empty strings.
157    41. Applied a user patch to fix a number of spelling mistakes in comments.
159    42. Data lines longer than 65536 caused pcretest to crash.
161    43. Clarified the data type for length and startoffset arguments for pcre_exec
162        and pcre_dfa_exec in the function-specific man pages, where they were
163        explicitly stated to be in bytes, never having been updated. I also added
164        some clarification to the pcreapi man page.
166    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
167        a segmentation fault.
170    Version 8.32 30-November-2012
171    -----------------------------
173    1.  Improved JIT compiler optimizations for first character search and single
174        character iterators.
176    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
177        Patch by Daniel Richard G.
179    3.  Single character iterator optimizations in the JIT compiler.
181    4.  Improved JIT compiler optimizations for character ranges.
183    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
184        Reported by Giuseppe D'Angelo.
186    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
187        of a line, was being set incorrectly in cases where .* appeared inside
188        atomic brackets at the start of a pattern, or where there was a subsequent
189        *PRUNE or *SKIP.
191    7.  Improved instruction cache flush for POWER/PowerPC.
192        Patch by Daniel Richard G.
194    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
195        grep:
197        (a) There is now no limit to the number of patterns to be matched.
199        (b) An error is given if a pattern is too long.
201        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
202            are now supported.
204        (d) --exclude-from and --include-from (multiple use) have been added.
206        (e) Exclusions and inclusions now apply to all files and directories, not
207            just to those obtained from scanning a directory recursively.
209        (f) Multiple uses of -f and --file-list are now supported.
211        (g) In a Windows environment, the default for -d has been changed from
212            "read" (the GNU grep default) to "skip", because otherwise the presence
213            of a directory in the file list provokes an error.
215        (h) The documentation has been revised and clarified in places.
217    9.  Improve the matching speed of capturing brackets.
219    10. Changed the meaning of \X so that it now matches a Unicode extended
220        grapheme cluster.
222    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
223        out POSIX threads when JIT support is configured.
225    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
227    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
228        structure could go wrong in environments where size_t is not the same size
229        as int.
231    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
232        set.
234    15. The EBCDIC support had decayed; later updates to the code had included
235        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
236        general tidy up of EBCDIC-related issues, and the documentation was also
237        not quite right. There is now a test that can be run on ASCII systems to
238        check some of the EBCDIC-related things (but is it not a full test).
240    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
241        in a small tidy to the code.
243    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
245    18. If the --only-matching (-o) option in pcregrep is specified multiple
246        times, each one causes appropriate output. For example, -o1 -o2 outputs the
247        substrings matched by the 1st and 2nd capturing parentheses. A separating
248        string can be specified by --om-separator (default empty).
250    19. Improving the first n character searches.
252    20. Turn case lists for horizontal and vertical white space into macros so that
253        they are defined only once.
255    21. This set of changes together give more compatible Unicode case-folding
256        behaviour for characters that have more than one other case when UCP
257        support is available.
259        (a) The Unicode property table now has offsets into a new table of sets of
260            three or more characters that are case-equivalent. The MultiStage2.py
261            script that generates these tables (the pcre_ucd.c file) now scans
262            CaseFolding.txt instead of UnicodeData.txt for character case
263            information.
265        (b) The code for adding characters or ranges of characters to a character
266            class has been abstracted into a generalized function that also handles
267            case-independence. In UTF-mode with UCP support, this uses the new data
268            to handle characters with more than one other case.
270        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
271            whose other case is greater than 256 are now correctly matched
272            caselessly. Previously, the high codepoint matched the low one, but not
273            vice versa.
275        (d) The processing of \h, \H, \v, and \ in character classes now makes use
276            of the new class addition function, using character lists defined as
277            macros alongside the case definitions of 20 above.
279        (e) Caseless back references now work with characters that have more than
280            one other case.
282        (f) General caseless matching of characters with more than one other case
283            is supported.
285    22. Unicode character properties were updated from Unicode 6.2.0
287    23. Improved CMake support under Windows. Patch by Daniel Richard G.
289    24. Add support for 32-bit character strings, and UTF-32
291    25. Major JIT compiler update (code refactoring and bugfixing).
292        Experimental Sparc 32 support is added.
294    26. Applied a modified version of Daniel Richard G's patch to create
295        pcre.h.generic and config.h.generic by "make" instead of in the
296        PrepareRelease script.
298    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
299        pcre_compile.c when checking for a zero character.
301    28. Introducing a native interface for JIT. Through this interface, the compiled
302        machine code can be directly executed. The purpose of this interface is to
303        provide fast pattern matching, so several sanity checks are not performed.
304        However, feature tests are still performed. The new interface provides
305        1.4x speedup compared to the old one.
307    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
308        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
309        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
311    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
312        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
313        the "old" RFC 2279). Instead, it ended up passing a negative length to
314        pcre_exec().
316    31. Add support for GCC's visibility feature to hide internal functions.
318    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
319        "unknown -C option" after outputting 0 or 1.
321    33. There is now support for generating a code coverage report for the test
322        suite in environments where gcc is the compiler and lcov is installed. This
323        is mainly for the benefit of the developers.
325    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
326        unaddressable using valgrind annotations, allowing valgrind to detect
327        invalid memory accesses. This is mainly for the benefit of the developers.
329    25. (*UTF) can now be used to start a pattern in any of the three libraries.
331    26. Give configure error if --enable-cpp but no C++ compiler found.
334    Version 8.31 06-July-2012
335    -------------------------
337    1.  Fixing a wrong JIT test case and some compiler warnings.
339    2.  Removed a bashism from the RunTest script.
341    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
342        to unsigned type, result still unsigned" that was given by an MS compiler
343        on encountering the code "-sizeof(xxx)".
345    4.  Partial matching support is added to the JIT compiler.
347    5.  Fixed several bugs concerned with partial matching of items that consist
348        of more than one character:
350        (a) /^(..)\1/ did not partially match "aba" because checking references was
351            done on an "all or nothing" basis. This also applied to repeated
352            references.
354        (b) \R did not give a hard partial match if \r was found at the end of the
355            subject.
357        (c) \X did not give a hard partial match after matching one or more
358            characters at the end of the subject.
360        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
361            a partial match for the string "\r".
363        (e) When newline was set to CRLF, the metacharacter "." did not recognize
364            a partial match for a CR character at the end of the subject string.
366    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
367        running pcretest, the text "(JIT)" added to the output whenever JIT is
368        actually used to run the match.
370    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
371        or /S+[+] with a digit between 1 and 7.
373    8.  OP_NOT now supports any UTF character not just single-byte ones.
375    9.  (*MARK) control verb is now supported by the JIT compiler.
377    10. The command "./RunTest list" lists the available tests without actually
378        running any of them. (Because I keep forgetting what they all are.)
382    12. Applied a (slightly modified) user-supplied patch that improves performance
383        when the heap is used for recursion (compiled with --disable-stack-for-
384        recursion). Instead of malloc and free for each heap frame each time a
385        logical recursion happens, frames are retained on a chain and re-used where
386        possible. This sometimes gives as much as 30% improvement.
388    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
389        call.
391    14. As documented, (*COMMIT) is now confined to within a positive assertion.
393    15. It is now possible to link pcretest with libedit as an alternative to
394        libreadline.
396    16. (*COMMIT) control verb is now supported by the JIT compiler.
398    17. The Unicode data tables have been updated to Unicode 6.1.0.
400    18. Added --file-list option to pcregrep.
402    19. Added binary file support to pcregrep, including the -a, --binary-files,
403        -I, and --text options.
405    20. The madvise function is renamed for posix_madvise for QNX compatibility
406        reasons. Fixed by Giuseppe D'Angelo.
408    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
410    22. Changed the option for creating symbolic links for 16-bit man pages from
411        -s to -sf so that re-installing does not cause issues.
413    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
415    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
416        matches in certain environments (the workspace was not being correctly
417        retained). Also added to pcre_dfa_exec() a simple plausibility check on
418        some of the workspace data at the beginning of a restart.
420    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
421        was not doing so when it should - probably a typo introduced by SVN 528
422        (change 8.10/14).
424    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
425        \w+ when the character tables indicated that \x{c4} was a word character.
426        There were several related cases, all because the tests for doing a table
427        lookup were testing for characters less than 127 instead of 255.
429    27. If a pattern contains capturing parentheses that are not used in a match,
430        their slots in the ovector are set to -1. For those that are higher than
431        any matched groups, this happens at the end of processing. In the case when
432        there were back references that the ovector was too small to contain
433        (causing temporary malloc'd memory to be used during matching), and the
434        highest capturing number was not used, memory off the end of the ovector
435        was incorrectly being set to -1. (It was using the size of the temporary
436        memory instead of the true size.)
438    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
439        ovector size, it uses memory at the end of the block that it has got.
441    29. Check for an overlong MARK name and give an error at compile time. The
442        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
444    30. JIT compiler update.
446    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
447        Rill for the patch.
449    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
451    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
453    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
454        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
455        was enabled.
457    35. Improve JIT code generation for greedy plus quantifier.
459    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
460        1 to "aa" instead of to an empty string. The bug affected repeated groups
461        that could potentially match an empty string.
463    37. Optimizing single character iterators in JIT.
465    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
466        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
467        codepoints that are too big for the mode are faulted, and in a UTF mode,
468        disallowed codepoints are also faulted.
470    39. If PCRE was compiled with UTF support, in three places in the DFA
471        matcher there was code that should only have been obeyed in UTF mode, but
472        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
473        processing when bytes with values greater than 127 were present. In 16-bit
474        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
475        both cases the values are those that cannot be the first data item in a UTF
476        character. The three items that might have provoked this were recursions,
477        possessively repeated groups, and atomic groups.
479    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
480        and pcregrep, because some OS require shared objects to be explicitly
481        passed to ld, causing the link step to fail if they are not.
483    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
484        mode, patterns that started with \h* or \R* might be incorrectly matched.
487    Version 8.30 04-February-2012
488    -----------------------------
490    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
491        name is defined in ctype.h.
493    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
494        only in quite long subpatterns.
496    3.  Removed the function pcre_info(), which has been obsolete and deprecated
497        since it was replaced by pcre_fullinfo() in February 2000.
499    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
500        match a (*MARK), and the match failed at the start of the subject, a
501        reference to memory before the start of the subject could occur. This bug
502        was introduced by fix 17 of release 8.21.
504    5.  A reference to an unset group with zero minimum repetition was giving
505        totally wrong answers (in non-JavaScript-compatibility mode). For example,
506        /(another)?(\1?)test/ matched against "hello world test". This bug was
507        introduced in release 8.13.
509    6.  Add support for 16-bit character strings (a large amount of work involving
510        many changes and refactorings).
512    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
513        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
514        from a file.
516    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
517        rounding is not applied in this particular case).
519    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
520        if they appear, or are escaped, in patterns.
522    10. Get rid of a number of -Wunused-but-set-variable warnings.
524    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
525        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
526        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
527        also returns the mark "x". This bug applied to capturing parentheses,
528        non-capturing parentheses, and atomic parentheses. It also applied to some
529        assertions.
531    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
532        information out of configure.ac instead of relying on pcre.h.generic, which
533        is not stored in the repository.
535    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
536        -lreadline.
538    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
540    15. Applied Graycode's patch to put the top-level frame on the stack rather
541        than the heap when not using the stack for recursion. This gives a
542        performance improvement in many cases when recursion is not deep.
544    16. Experimental code added to "pcretest -C" to output the stack frame size.
547    Version 8.21 12-Dec-2011
548    ------------------------
550    1.  Updating the JIT compiler.
552    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
553        are added as well.
555    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
556        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
557        calling _pcre_jit_exec. Some extra comments are added.
559    4.  (*MARK) settings inside atomic groups that do not contain any capturing
560        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
561        was introduced by change 18 for 8.20.
563    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
564        ECMA-262 standard.
566    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
567        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
568        This bug was probably introduced by change 9 of 8.13.
570    7.  While fixing 6 above, I noticed that a number of other items were being
571        incorrectly rejected as "not fixed length". This arose partly because newer
572        opcodes had not been added to the fixed-length checking code. I have (a)
573        corrected the bug and added tests for these items, and (b) arranged for an
574        error to occur if an unknown opcode is encountered while checking for fixed
575        length instead of just assuming "not fixed length". The items that were
576        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
577        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
578        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
580    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
581        being incorrectly compiled and would have given unpredicatble results.
583    9.  A possessively repeated subpattern with minimum repeat count greater than
584        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
585        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
586        the first (A) could occur when it should not.
588    10. Add a cast and remove a redundant test from the code.
590    11. JIT should use pcre_malloc/pcre_free for allocation.
592    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
593        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
594        is anything other than /usr, -L is still shown).
596    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
598    14. Perl does not support \N without a following name in a [] class; PCRE now
599        also gives an error.
601    15. If a forward reference was repeated with an upper limit of around 2000,
602        it caused the error "internal error: overran compiling workspace". The
603        maximum number of forward references (including repeats) was limited by the
604        internal workspace, and dependent on the LINK_SIZE. The code has been
605        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
606        the default depends on LINK_SIZE. There is a new upper limit (for safety)
607        of around 200,000 forward references. While doing this, I also speeded up
608        the filling in of repeated forward references.
610    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
611        incorrectly expecting the subject to contain another "a" after the start.
613    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
614        in the match, the SKIP should be ignored. This was not happening; instead
615        the SKIP was being treated as NOMATCH. For patterns such as
616        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
617        tested.
619    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
620        now much more compatible with Perl, in particular in cases where the result
621        is a non-match for a non-anchored pattern. For example, if
622        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
623        "m", where previously it did not return a name. A side effect of this
624        change is that for partial matches, the last encountered mark name is
625        returned, as for non matches. A number of tests that were previously not
626        Perl-compatible have been moved into the Perl-compatible test files. The
627        refactoring has had the pleasing side effect of removing one argument from
628        the match() function, thus reducing its stack requirements.
630    19. If the /S+ option was used in pcretest to study a pattern using JIT,
631        subsequent uses of /S (without +) incorrectly behaved like /S+.
633    21. Retrieve executable code size support for the JIT compiler and fixing
634        some warnings.
636    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
637        not work when the shorter character appeared right at the end of the
638        subject string.
640    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
641        systems.
643    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
644        output it when the /M option is used in pcretest.
646    25. The CheckMan script was not being included in the distribution. Also, added
647        an explicit "perl" to run Perl scripts from the PrepareRelease script
648        because this is reportedly needed in Windows.
650    26. If study data was being save in a file and studying had not found a set of
651        "starts with" bytes for the pattern, the data written to the file (though
652        never used) was taken from uninitialized memory and so caused valgrind to
653        complain.
655    27. Updated RunTest.bat as provided by Sheri Pierce.
657    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
659    29. Computation of memory usage for the table of capturing group names was
660        giving an unnecessarily large value.
663    Version 8.20 21-Oct-2011
664    ------------------------
666    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
667        a POSIX class. After further experiments with Perl, which convinced me that
668        Perl has bugs and confusions, a closing square bracket is no longer allowed
669        in a POSIX name. This bug also affected patterns with classes that started
670        with full stops.
672    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
673        captured substring, but while checking the failing first alternative,
674        substring 1 is temporarily captured. If the output vector supplied to
675        pcre_exec() was not big enough for this capture, the yield of the function
676        was still zero ("insufficient space for captured substrings"). This cannot
677        be totally fixed without adding another stack variable, which seems a lot
678        of expense for a edge case. However, I have improved the situation in cases
679        such as /(a)(b)x|abc/ matched against "abc", where the return code
680        indicates that fewer than the maximum number of slots in the ovector have
681        been set.
683    3.  Related to (2) above: when there are more back references in a pattern than
684        slots in the output vector, pcre_exec() uses temporary memory during
685        matching, and copies in the captures as far as possible afterwards. It was
686        using the entire output vector, but this conflicts with the specification
687        that only 2/3 is used for passing back captured substrings. Now it uses
688        only the first 2/3, for compatibility. This is, of course, another edge
689        case.
691    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
692        main code base, and can be used by building with --enable-jit. When this is
693        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
694        runtime --no-jit option is given.
696    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
697        ovector, the return from the function was zero, implying that there were
698        other matches that did not fit. The correct "exactly full" value is now
699        returned.
701    6.  If a subpattern that was called recursively or as a subroutine contained
702        (*PRUNE) or any other control that caused it to give a non-standard return,
703        invalid errors such as "Error -26 (nested recursion at the same subject
704        position)" or even infinite loops could occur.
706    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
707        computing the minimum length on reaching *ACCEPT, and so ended up with the
708        wrong value of 1 rather than 0. Further investigation indicates that
709        computing a minimum subject length in the presence of *ACCEPT is difficult
710        (think back references, subroutine calls), and so I have changed the code
711        so that no minimum is registered for a pattern that contains *ACCEPT.
713    8.  If (*THEN) was present in the first (true) branch of a conditional group,
714        it was not handled as intended. [But see 16 below.]
716    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
717        Sheri Pierce.
719    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
720        the first byte in a match must be "a".
722    11. Change 17 for 8.13 increased the recursion depth for patterns like
723        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
724        pattern contains any instances of (*THEN). If it does not, the old
725        optimizations are restored. It would be nice to do this on a per-group
726        basis, but at the moment that is not feasible.
728    12. In some environments, the output of pcretest -C is CRLF terminated. This
729        broke RunTest's code that checks for the link size. A single white space
730        character after the value is now allowed for.
732    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
733        For "fr", it uses the Windows-specific input and output files.
735    14. If (*THEN) appeared in a group that was called recursively or as a
736        subroutine, it did not work as intended. [But see next item.]
738    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
739        pattern fragments (but not containing any | characters). If A and B are
740        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
741        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
742        D. In other words, Perl considers parentheses that do not contain any |
743        characters to be part of a surrounding alternative, whereas PCRE was
744        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
745        differently. PCRE now behaves in the same way as Perl, except in the case
746        of subroutine/recursion calls such as (?1) which have in any case always
747        been different (but PCRE had them first :-).
749    16. Related to 15 above: Perl does not treat the | in a conditional group as
750        creating alternatives. Such a group is treated in the same way as an
751        ordinary group without any | characters when processing (*THEN). PCRE has
752        been changed to match Perl's behaviour.
754    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
755        RunGrepTest script failed.
757    18. Change 22 for version 13 caused atomic groups to use more stack. This is
758        inevitable for groups that contain captures, but it can lead to a lot of
759        stack use in large patterns. The old behaviour has been restored for atomic
760        groups that do not contain any capturing parentheses.
762    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
763        suppress the check for a minimum subject length at run time. (If it was
764        given to pcre_exec() or pcre_dfa_exec() it did work.)
766    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
767        fail to work when decoding hex characters in data strings in EBCDIC
768        environments.
770    21. It appears that in at least one Mac OS environment, the isxdigit() function
771        is implemented as a macro that evaluates to its argument more than once,
772        contravening the C 90 Standard (I haven't checked a later standard). There
773        was an instance in pcretest which caused it to go wrong when processing
774        \x{...} escapes in subject strings. The has been rewritten to avoid using
775        things like p++ in the argument of isxdigit().
778    Version 8.13 16-Aug-2011
779    ------------------------
781    1.  The Unicode data tables have been updated to Unicode 6.0.0.
783    2.  Two minor typos in pcre_internal.h have been fixed.
785    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
786        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
787        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
789    4.  There were a number of related bugs in the code for matching backrefences
790        caselessly in UTF-8 mode when codes for the characters concerned were
791        different numbers of bytes. For example, U+023A and U+2C65 are an upper
792        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
793        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
794        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
795        2-byte code at the end of the subject (it thought there wasn't enough data
796        left).
798    5.  Comprehensive information about what went wrong is now returned by
799        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
800        as the output vector has at least 2 elements. The offset of the start of
801        the failing character and a reason code are placed in the vector.
803    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
804        now returned is for the first byte of the failing character, instead of the
805        last byte inspected. This is an incompatible change, but I hope it is small
806        enough not to be a problem. It makes the returned offset consistent with
807        pcre_exec() and pcre_dfa_exec().
809    7.  pcretest now gives a text phrase as well as the error number when
810        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
811        failure, the offset and reason code are output.
813    8.  When \R was used with a maximizing quantifier it failed to skip backwards
814        over a \r\n pair if the subsequent match failed. Instead, it just skipped
815        back over a single character (\n). This seems wrong (because it treated the
816        two characters as a single entity when going forwards), conflicts with the
817        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
818        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
819        has been changed.
821    9.  Some internal refactoring has changed the processing so that the handling
822        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
823        time (the PCRE_DOTALL option was changed this way some time ago: version
824        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
825        which was always a bit of a fudge. It also means that there is one less
826        argument for the match() function, which reduces its stack requirements
827        slightly. This change also fixes an incompatibility with Perl: the pattern
828        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
830    10. More internal refactoring has drastically reduced the number of recursive
831        calls to match() for possessively repeated groups such as (abc)++ when
832        using pcre_exec().
834    11. While implementing 10, a number of bugs in the handling of groups were
835        discovered and fixed:
837        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
838        (a|)*(?1) gave a compile-time internal error.
839        ((a|)+)+  did not notice that the outer group could match an empty string.
840        (^a|^)+   was not marked as anchored.
841        (.*a|.*)+ was not marked as matching at start or after a newline.
843    12. Yet more internal refactoring has removed another argument from the match()
844        function. Special calls to this function are now indicated by setting a
845        value in a variable in the "match data" data block.
847    13. Be more explicit in pcre_study() instead of relying on "default" for
848        opcodes that mean there is no starting character; this means that when new
849        ones are added and accidentally left out of pcre_study(), testing should
850        pick them up.
852    14. The -s option of pcretest has been documented for ages as being an old
853        synonym of -m (show memory usage). I have changed it to mean "force study
854        for every regex", that is, assume /S for every regex. This is similar to -i
855        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
856        using it. It makes it easier to run collections of tests with and without
857        study enabled, and thereby test pcre_study() more easily. All the standard
858        tests are now run with and without -s (but some patterns can be marked as
859        "never study" - see 20 below).
861    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
862        restoration of the capturing data to the outer values was not happening
863        correctly.
865    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
866        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
867        pattern had matched an empty string, and so incorrectly returned a no
868        match.
870    17. There was optimizing code for the last branch of non-capturing parentheses,
871        and also for the obeyed branch of a conditional subexpression, which used
872        tail recursion to cut down on stack usage. Unfortunately, now that there is
873        the possibility of (*THEN) occurring in these branches, tail recursion is
874        no longer possible because the return has to be checked for (*THEN). These
875        two optimizations have therefore been removed. [But see 8.20/11 above.]
877    18. If a pattern containing \R was studied, it was assumed that \R always
878        matched two bytes, thus causing the minimum subject length to be
879        incorrectly computed because \R can also match just one byte.
881    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
882        was incorrectly computed.
884    20. If /S is present twice on a test pattern in pcretest input, it now
885        *disables* studying, thereby overriding the use of -s on the command line
886        (see 14 above). This is necessary for one or two tests to keep the output
887        identical in both cases.
889    21. When (*ACCEPT) was used in an assertion that matched an empty string and
890        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
892    22. When an atomic group that contained a capturing parenthesis was
893        successfully matched, but the branch in which it appeared failed, the
894        capturing was not being forgotten if a higher numbered group was later
895        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
896        group 1 to "a", when in fact it should be unset. This applied to multi-
897        branched capturing and non-capturing groups, repeated or not, and also to
898        positive assertions (capturing in negative assertions does not happen
899        in PCRE) and also to nested atomic groups.
901    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
902        subject after a captured substring, to make it easier to tell which of a
903        number of identical substrings has been captured.
905    24. The way atomic groups are processed by pcre_exec() has been changed so that
906        if they are repeated, backtracking one repetition now resets captured
907        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
908        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
909        "aaa". Previously, it would have been "a". As part of this code
910        refactoring, the way recursive calls are handled has also been changed.
912    25. If an assertion condition captured any substrings, they were not passed
913        back unless some other capturing happened later. For example, if
914        (?(?=(a))a) was matched against "a", no capturing was returned.
916    26. When studying a pattern that contained subroutine calls or assertions,
917        the code for finding the minimum length of a possible match was handling
918        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
919        group 1 called group 2 while simultaneously a separate group 2 called group
920        1). A stack overflow occurred in this case. I have fixed this by limiting
921        the recursion depth to 10.
923    27. Updated RunTest.bat in the distribution to the version supplied by Tom
924        Fortmann. This supports explicit test numbers on the command line, and has
925        argument validation and error reporting.
927    28. An instance of \X with an unlimited repeat could fail if at any point the
928        first character it looked at was a mark character.
930    29. Some minor code refactoring concerning Unicode properties and scripts
931        should reduce the stack requirement of match() slightly.
933    30. Added the '=' option to pcretest to check the setting of unused capturing
934        slots at the end of the pattern, which are documented as being -1, but are
935        not included in the return count.
937    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
938        compiled something random. Now it gives a compile-time error (as does
939        Perl).
941    32. A *MARK encountered during the processing of a positive assertion is now
942        recorded and passed back (compatible with Perl).
944    33. If --only-matching or --colour was set on a pcregrep call whose pattern
945        had alternative anchored branches, the search for a second match in a line
946        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
947        matched the line "0102" twice. The same bug affected patterns that started
948        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
949        twice.
951    34. Previously, PCRE did not allow quantification of assertions. However, Perl
952        does, and because of capturing effects, quantifying parenthesized
953        assertions may at times be useful. Quantifiers are now allowed for
954        parenthesized assertions.
956    35. A minor code tidy in pcre_compile() when checking options for \R usage.
958    36. \g was being checked for fancy things in a character class, when it should
959        just be a literal "g".
961    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
962        appearance of a nested POSIX class supersedes an apparent external class.
963        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
964        unescaped square brackets may also appear as part of class names. For
965        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
966        more like Perl. (But see 8.20/1 above.)
968    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
969        was because it thought it was \N{name}, which is not supported).
971    39. Add minix to OS list not supporting the -S option in pcretest.
973    40. PCRE tries to detect cases of infinite recursion at compile time, but it
974        cannot analyze patterns in sufficient detail to catch mutual recursions
975        such as ((?1))((?2)). There is now a runtime test that gives an error if a
976        subgroup is called recursively as a subpattern for a second time at the
977        same position in the subject string. In previous releases this might have
978        been caught by the recursion limit, or it might have run out of stack.
980    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
981        happen only once. PCRE was, however incorrectly giving a compile time error
982        "recursive call could loop indefinitely" because it cannot analyze the
983        pattern in sufficient detail. The compile time test no longer happens when
984        PCRE is compiling a conditional subpattern, but actual runaway loops are
985        now caught at runtime (see 40 above).
987    42. It seems that Perl allows any characters other than a closing parenthesis
988        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
989        has been changed to be the same.
991    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
992        as not to get warnings when autogen.sh is called. Also changed
993        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
995    44. To help people who use pcregrep to scan files containing exceedingly long
996        lines, the following changes have been made:
998        (a) The default value of the buffer size parameter has been increased from
999            8K to 20K. (The actual buffer used is three times this size.)
1001        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1002            PCRE is built.
1004        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
1005            to be set at run time.
1007        (d) Numerical values in pcregrep options can be followed by K or M, for
1008            example --buffer-size=50K.
1010        (e) If a line being scanned overflows pcregrep's buffer, an error is now
1011            given and the return code is set to 2.
1013    45. Add a pointer to the latest mark to the callout data block.
1015    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1016        partial match of an empty string instead of no match. This was specific to
1017        the use of ".".
1019    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1020        complete match instead of a partial match. This bug was dependent on both
1021        the PCRE_UTF8 and PCRE_DOTALL options being set.
1023    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1024        starting byte set, because \b was not being ignored.
1027    Version 8.12 15-Jan-2011
1028    ------------------------
1030    1.  Fixed some typos in the markup of the man pages, and wrote a script that
1031        checks for such things as part of the documentation building process.
1033    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
1034        --match-limit and --recursion-limit options (added for 8.11). In
1035        particular, this made one of the standard tests fail. (The integer value
1036        went into the wrong half of a long int.)
1038    3.  If the --colour option was given to pcregrep with -v (invert match), it
1039        did strange things, either producing crazy output, or crashing. It should,
1040        of course, ignore a request for colour when reporting lines that do not
1041        match.
1043    4.  Another pcregrep bug caused similar problems if --colour was specified with
1044        -M (multiline) and the pattern match finished with a line ending.
1046    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
1047        matched in multiline mode, the following line was shown as part of the
1048        match. This seems wrong, so I have changed it.
1050    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
1051        the check for further matches in the same line (so they could be coloured)
1052        to overrun the end of the current line. If another match was found, it was
1053        incorrectly shown (and then shown again when found in the next line).
1055    7.  If pcregrep was compiled under Windows, there was a reference to the
1056        function pcregrep_exit() before it was defined. I am assuming this was
1057        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1058        reported by a user. I've moved the definition above the reference.
1061    Version 8.11 10-Dec-2010
1062    ------------------------
1064    1.  (*THEN) was not working properly if there were untried alternatives prior
1065        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1066        backtracked to try for "b" instead of moving to the next alternative branch
1067        at the same level (in this case, to look for "c"). The Perl documentation
1068        is clear that when (*THEN) is backtracked onto, it goes to the "next
1069        alternative in the innermost enclosing group".
1071    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1072        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
1073        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1074        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1075        (*THEN).
1077    3.  If \s appeared in a character class, it removed the VT character from
1078        the class, even if it had been included by some previous item, for example
1079        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1080        of \s, but is part of the POSIX "space" class.)
1082    4.  A partial match never returns an empty string (because you can always
1083        match an empty string at the end of the subject); however the checking for
1084        an empty string was starting at the "start of match" point. This has been
1085        changed to the "earliest inspected character" point, because the returned
1086        data for a partial match starts at this character. This means that, for
1087        example, /(?<=abc)def/ gives a partial match for the subject "abc"
1088        (previously it gave "no match").
1090    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1091        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1092        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1093        has an implication that the given string is incomplete (because a partial
1094        match is preferred over a full match). For this reason, these items now
1095        give a partial match in this situation. [Aside: previously, the one case
1096        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1097        match rather than a full match, which was wrong by the old rules, but is
1098        now correct.]
1100    6.  There was a bug in the handling of #-introduced comments, recognized when
1101        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1102        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1103        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1104        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1105        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1106        places in pcre_compile().
1108    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1109        comments when looking ahead for named forward references to subpatterns,
1110        the only newline sequence it recognized was NL. It now handles newlines
1111        according to the set newline convention.
1113    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1114        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1115        cater for a lack of strerror(). These oversights have been fixed.
1117    9.  Added --match-limit and --recursion-limit to pcregrep.
1119    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1121    11. When the -o option was used, pcregrep was setting a return code of 1, even
1122        when matches were found, and --line-buffered was not being honoured.
1124    12. Added an optional parentheses number to the -o and --only-matching options
1125        of pcregrep.
1127    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1128        can match an empty string. The code to do it in pcretest and pcredemo
1129        needed fixing:
1131        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1132            only one byte after an empty string match just before CRLF (this case
1133            just got forgotten; "any" and "anycrlf" were OK).
1135        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1136            mode when an empty string match preceded an ASCII character followed by
1137            a non-ASCII character. (The code for advancing by one character rather
1138            than one byte was nonsense.)
1140        (c) The pcredemo.c sample program did not have any code at all to handle
1141            the cases when CRLF is a valid newline sequence.
1143    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1144        as a starting offset was within the subject string. There is now a new
1145        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1146        negative or greater than the length of the string. In order to test this,
1147        pcretest is extended to allow the setting of negative starting offsets.
1149    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1150        starting offset points to the beginning of a UTF-8 character was
1151        unnecessarily clumsy. I tidied it up.
1153    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1154        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1156    17. Nobody had reported that the --include_dir option, which was added in
1157        release 7.7 should have been called --include-dir (hyphen, not underscore)
1158        for compatibility with GNU grep. I have changed it to --include-dir, but
1159        left --include_dir as an undocumented synonym, and the same for
1160        --exclude-dir, though that is not available in GNU grep, at least as of
1161        release 2.5.4.
1163    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1164        characters from a string of bytes) have been redefined so as not to use
1165        loops, in order to improve performance in some environments. At the same
1166        time, I abstracted some of the common code into auxiliary macros to save
1167        repetition (this should not affect the compiled code).
1169    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1170        compile-time error is now given if \c is not followed by an ASCII
1171        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1172        different, and any byte value is allowed.)
1174    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1175        START_OPTIMIZE option, which is now allowed at compile time - but just
1176        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1177        to pcregrep and other applications that have no direct access to PCRE
1178        options. The new /Y option in pcretest sets this option when calling
1179        pcre_compile().
1181    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1182        back references. Groups containing recursive back references were forced to
1183        be atomic by that change, but in the case of named groups, the amount of
1184        memory required was incorrectly computed, leading to "Failed: internal
1185        error: code overflow". This has been fixed.
1187    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1188        pcretest.c, to avoid build problems in some Borland environments.
1191    Version 8.10 25-Jun-2010
1192    ------------------------
1194    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1195        THEN.
1197    2.  (*ACCEPT) was not working when inside an atomic group.
1199    3.  Inside a character class, \B is treated as a literal by default, but
1200        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1201        causes the error). The code is unchanged, but I tidied the documentation.
1203    4.  Inside a character class, PCRE always treated \R and \X as literals,
1204        whereas Perl faults them if its -w option is set. I have changed PCRE so
1205        that it faults them when PCRE_EXTRA is set.
1207    5.  Added support for \N, which always matches any character other than
1208        newline. (It is the same as "." when PCRE_DOTALL is not set.)
1210    6.  When compiling pcregrep with newer versions of gcc which may have
1211        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1212        declared with attribute warn_unused_result" were given. Just casting the
1213        result to (void) does not stop the warnings; a more elaborate fudge is
1214        needed. I've used a macro to implement this.
1216    7.  Minor change to pcretest.c to avoid a compiler warning.
1218    8.  Added four artifical Unicode properties to help with an option to make
1219        \s etc use properties (see next item). The new properties are: Xan
1220        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1222    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1223        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1224        this option. Modified pcretest to add /W to test this facility. Added
1225        REG_UCP to make it available via the POSIX interface.
1227    10. Added --line-buffered to pcregrep.
1229    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1230        studied, and the match started with a letter with a code point greater than
1231        127 whose first byte was different to the first byte of the other case of
1232        the letter, the other case of this starting letter was not recognized
1233        (#976).
1235    12. If a pattern that was studied started with a repeated Unicode property
1236        test, for example, \p{Nd}+, there was the theoretical possibility of
1237        setting up an incorrect bitmap of starting bytes, but fortunately it could
1238        not have actually happened in practice until change 8 above was made (it
1239        added property types that matched character-matching opcodes).
1241    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1242        possible starting bytes for non-anchored patterns.
1244    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1245        \R, and also a number of cases that involve Unicode properties, both
1246        explicit and implicit when PCRE_UCP is set.
1248    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1249        input, it could crash or give wrong results if characters with values
1250        greater than 0xc0 were present in the subject string. (Detail: it assumed
1251        UTF-8 input when processing these items.)
1253    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1254        size_t is 64-bit (#991).
1256    17. Added a check for running out of memory when PCRE is compiled with
1257        --disable-stack-for-recursion (#990).
1259    18. If the last data line in a file for pcretest does not have a newline on
1260        the end, a newline was missing in the output.
1262    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1263        less than 128) in its various bitmaps. However, there is a facility for
1264        generating tables according to the current locale when PCRE is compiled. It
1265        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1266        characters, are recognized by isspace() and therefore were getting set in
1267        these tables, and indeed these tables seem to approximate to ISO 8859. This
1268        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1269        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1270        which of course cannot start UTF-8 characters. I have changed the code so
1271        that only real ASCII characters (less than 128) and the correct starting
1272        bytes for UTF-8 encodings are set for characters greater than 127 when in
1273        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1274        altogether.)
1276    20. Added the /T option to pcretest so as to be able to run tests with non-
1277        standard character tables, thus making it possible to include the tests
1278        used for 19 above in the standard set of tests.
1280    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1281        reference to a subpattern the other side of a comment that contains an
1282        opening parenthesis caused either an internal compiling error, or a
1283        reference to the wrong subpattern.
1286    Version 8.02 19-Mar-2010
1287  ------------------------  ------------------------
1289  1.  The Unicode data tables have been updated to Unicode 5.2.0.  1.  The Unicode data tables have been updated to Unicode 5.2.0.
1291  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
1292      configured.      configured.
1294  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
1295      original author of that file, following a query about its status.      original author of that file, following a query about its status.
1297  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
1298      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
1300  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1301      quantifier applied to a forward-referencing subroutine call, could compile      quantifier applied to a forward-referencing subroutine call, could compile
1302      incorrect code or give the error "internal error: previously-checked      incorrect code or give the error "internal error: previously-checked
1303      referenced subpattern not found".      referenced subpattern not found".
1305  6.  Both MS Visual Studio and Symbian OS have problems with initializing  6.  Both MS Visual Studio and Symbian OS have problems with initializing
1306      variables to point to external functions. For these systems, therefore,      variables to point to external functions. For these systems, therefore,
1307      pcre_malloc etc. are now initialized to local functions that call the      pcre_malloc etc. are now initialized to local functions that call the
1308      relevant global functions.      relevant global functions.
1310  7.  There were two entries missing in the vectors called coptable and poptable  7.  There were two entries missing in the vectors called coptable and poptable
1311      in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.      in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
1312      I've fixed the data, and added a kludgy way of testing at compile time that      I've fixed the data, and added a kludgy way of testing at compile time that
1313      the lengths are correct (equal to the number of opcodes).      the lengths are correct (equal to the number of opcodes).
1315    8.  Following on from 7, I added a similar kludge to check the length of the
1316        eint vector in pcreposix.c.
1318    9.  Error texts for pcre_compile() are held as one long string to avoid too
1319        much relocation at load time. To find a text, the string is searched,
1320        counting zeros. There was no check for running off the end of the string,
1321        which could happen if a new error number was added without updating the
1322        string.
1324    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1326    11. \K was not working if it appeared in an atomic group or in a group that
1327        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1328        \K is "not well defined" if used in an assertion. PCRE now accepts it if
1329        the assertion is positive, but not if it is negative.
1331    12. Change 11 fortuitously reduced the size of the stack frame used in the
1332        "match()" function of pcre_exec.c by one pointer. Forthcoming
1333        implementation of support for (*MARK) will need an extra pointer on the
1334        stack; I have reserved it now, so that the stack frame size does not
1335        decrease.
1337    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1338        item in branch that calls a recursion is a subroutine call - as in the
1339        second branch in the above example - was incorrectly given the compile-
1340        time error "recursive call could loop indefinitely" because pcre_compile()
1341        was not correctly checking the subroutine for matching a non-empty string.
1343    14. The checks for overrunning compiling workspace could trigger after an
1344        overrun had occurred. This is a "should never occur" error, but it can be
1345        triggered by pathological patterns such as hundreds of nested parentheses.
1346        The checks now trigger 100 bytes before the end of the workspace.
1348    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1351  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
# Line 357  Version 7.9 11-Apr-09 Line 1674  Version 7.9 11-Apr-09
1674  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
1675      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
1676      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1677      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1678        8.33.]
1680  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
1681      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
# Line 600  Version 7.7 07-May-08 Line 1918  Version 7.7 07-May-08
1918      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
1919      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
1920      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
1921      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
1922      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
1923      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.498  
changed lines
  Added in v.1334

  ViewVC Help
Powered by ViewVC 1.1.5