/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 622 by ph10, Mon Jul 18 10:46:51 2011 UTC revision 1324 by ph10, Fri May 10 11:40:06 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.13 30-Apr-2011  Version 8.33 28-April-2013
5    --------------------------
6    
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.
11    
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
14    
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.
18    
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.
24    
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.
28    
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
31    
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
34    
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
36    
37    9.  Optimizing fast_forward_start_bits in JIT.
38    
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
41    
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
43    
44        (b) Minimum length was not checked before the matching is started.
45    
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.
50    
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.
54    
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.
57    
58    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
59        Only supported by the JIT compiler at the moment.
60    
61    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
62    
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.
66    
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.
73    
74    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
75    
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.
78    
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.
82    
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".
87    
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.
92    
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.
96    
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.
99    
100    25. (*PRUNE) is now supported by the JIT compiler.
101    
102    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
103    
104    27. Fix the case where there are two or more SKIPs with arguments that may be
105        ignored.
106    
107    28. (*SKIP) is now supported by the JIT compiler.
108    
109    29. (*THEN) is now supported by the JIT compiler.
110    
111    30. Update RunTest with additional test selector options.
112    
113    31. The way PCRE handles backtracking verbs has been changed in two ways.
114    
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.
119    
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.
123    
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.
127    
128    32. Control verbs are handled in the same way in JIT and interpreter.
129    
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.
132    
133    34. Auto-detect and optimize limited repetitions in JIT.
134    
135    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
136        blocking (*UTF) etc.
137    
138    36. In the interpreter, maximizing pattern repetitions for characters and
139        character types now use tail recursion, which reduces stack usage.
140    
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.
143    
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.
147    
148    39. Try madvise first before posix_madvise.
149    
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.
156    
157    
158    Version 8.32 30-November-2012
159    -----------------------------
160    
161    1.  Improved JIT compiler optimizations for first character search and single
162        character iterators.
163    
164    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
165        Patch by Daniel Richard G.
166    
167    3.  Single character iterator optimizations in the JIT compiler.
168    
169    4.  Improved JIT compiler optimizations for character ranges.
170    
171    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
172        Reported by Giuseppe D'Angelo.
173    
174    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
175        of a line, was being set incorrectly in cases where .* appeared inside
176        atomic brackets at the start of a pattern, or where there was a subsequent
177        *PRUNE or *SKIP.
178    
179    7.  Improved instruction cache flush for POWER/PowerPC.
180        Patch by Daniel Richard G.
181    
182    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
183        grep:
184    
185        (a) There is now no limit to the number of patterns to be matched.
186    
187        (b) An error is given if a pattern is too long.
188    
189        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
190            are now supported.
191    
192        (d) --exclude-from and --include-from (multiple use) have been added.
193    
194        (e) Exclusions and inclusions now apply to all files and directories, not
195            just to those obtained from scanning a directory recursively.
196    
197        (f) Multiple uses of -f and --file-list are now supported.
198    
199        (g) In a Windows environment, the default for -d has been changed from
200            "read" (the GNU grep default) to "skip", because otherwise the presence
201            of a directory in the file list provokes an error.
202    
203        (h) The documentation has been revised and clarified in places.
204    
205    9.  Improve the matching speed of capturing brackets.
206    
207    10. Changed the meaning of \X so that it now matches a Unicode extended
208        grapheme cluster.
209    
210    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
211        out POSIX threads when JIT support is configured.
212    
213    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
214    
215    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
216        structure could go wrong in environments where size_t is not the same size
217        as int.
218    
219    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
220        set.
221    
222    15. The EBCDIC support had decayed; later updates to the code had included
223        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
224        general tidy up of EBCDIC-related issues, and the documentation was also
225        not quite right. There is now a test that can be run on ASCII systems to
226        check some of the EBCDIC-related things (but is it not a full test).
227    
228    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
229        in a small tidy to the code.
230    
231    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
232    
233    18. If the --only-matching (-o) option in pcregrep is specified multiple
234        times, each one causes appropriate output. For example, -o1 -o2 outputs the
235        substrings matched by the 1st and 2nd capturing parentheses. A separating
236        string can be specified by --om-separator (default empty).
237    
238    19. Improving the first n character searches.
239    
240    20. Turn case lists for horizontal and vertical white space into macros so that
241        they are defined only once.
242    
243    21. This set of changes together give more compatible Unicode case-folding
244        behaviour for characters that have more than one other case when UCP
245        support is available.
246    
247        (a) The Unicode property table now has offsets into a new table of sets of
248            three or more characters that are case-equivalent. The MultiStage2.py
249            script that generates these tables (the pcre_ucd.c file) now scans
250            CaseFolding.txt instead of UnicodeData.txt for character case
251            information.
252    
253        (b) The code for adding characters or ranges of characters to a character
254            class has been abstracted into a generalized function that also handles
255            case-independence. In UTF-mode with UCP support, this uses the new data
256            to handle characters with more than one other case.
257    
258        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
259            whose other case is greater than 256 are now correctly matched
260            caselessly. Previously, the high codepoint matched the low one, but not
261            vice versa.
262    
263        (d) The processing of \h, \H, \v, and \ in character classes now makes use
264            of the new class addition function, using character lists defined as
265            macros alongside the case definitions of 20 above.
266    
267        (e) Caseless back references now work with characters that have more than
268            one other case.
269    
270        (f) General caseless matching of characters with more than one other case
271            is supported.
272    
273    22. Unicode character properties were updated from Unicode 6.2.0
274    
275    23. Improved CMake support under Windows. Patch by Daniel Richard G.
276    
277    24. Add support for 32-bit character strings, and UTF-32
278    
279    25. Major JIT compiler update (code refactoring and bugfixing).
280        Experimental Sparc 32 support is added.
281    
282    26. Applied a modified version of Daniel Richard G's patch to create
283        pcre.h.generic and config.h.generic by "make" instead of in the
284        PrepareRelease script.
285    
286    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
287        pcre_compile.c when checking for a zero character.
288    
289    28. Introducing a native interface for JIT. Through this interface, the compiled
290        machine code can be directly executed. The purpose of this interface is to
291        provide fast pattern matching, so several sanity checks are not performed.
292        However, feature tests are still performed. The new interface provides
293        1.4x speedup compared to the old one.
294    
295    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
296        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
297        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
298    
299    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
300        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
301        the "old" RFC 2279). Instead, it ended up passing a negative length to
302        pcre_exec().
303    
304    31. Add support for GCC's visibility feature to hide internal functions.
305    
306    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
307        "unknown -C option" after outputting 0 or 1.
308    
309    33. There is now support for generating a code coverage report for the test
310        suite in environments where gcc is the compiler and lcov is installed. This
311        is mainly for the benefit of the developers.
312    
313    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
314        unaddressable using valgrind annotations, allowing valgrind to detect
315        invalid memory accesses. This is mainly for the benefit of the developers.
316    
317    25. (*UTF) can now be used to start a pattern in any of the three libraries.
318    
319    26. Give configure error if --enable-cpp but no C++ compiler found.
320    
321    
322    Version 8.31 06-July-2012
323    -------------------------
324    
325    1.  Fixing a wrong JIT test case and some compiler warnings.
326    
327    2.  Removed a bashism from the RunTest script.
328    
329    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
330        to unsigned type, result still unsigned" that was given by an MS compiler
331        on encountering the code "-sizeof(xxx)".
332    
333    4.  Partial matching support is added to the JIT compiler.
334    
335    5.  Fixed several bugs concerned with partial matching of items that consist
336        of more than one character:
337    
338        (a) /^(..)\1/ did not partially match "aba" because checking references was
339            done on an "all or nothing" basis. This also applied to repeated
340            references.
341    
342        (b) \R did not give a hard partial match if \r was found at the end of the
343            subject.
344    
345        (c) \X did not give a hard partial match after matching one or more
346            characters at the end of the subject.
347    
348        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
349            a partial match for the string "\r".
350    
351        (e) When newline was set to CRLF, the metacharacter "." did not recognize
352            a partial match for a CR character at the end of the subject string.
353    
354    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
355        running pcretest, the text "(JIT)" added to the output whenever JIT is
356        actually used to run the match.
357    
358    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
359        or /S+[+] with a digit between 1 and 7.
360    
361    8.  OP_NOT now supports any UTF character not just single-byte ones.
362    
363    9.  (*MARK) control verb is now supported by the JIT compiler.
364    
365    10. The command "./RunTest list" lists the available tests without actually
366        running any of them. (Because I keep forgetting what they all are.)
367    
368    11. Add PCRE_INFO_MAXLOOKBEHIND.
369    
370    12. Applied a (slightly modified) user-supplied patch that improves performance
371        when the heap is used for recursion (compiled with --disable-stack-for-
372        recursion). Instead of malloc and free for each heap frame each time a
373        logical recursion happens, frames are retained on a chain and re-used where
374        possible. This sometimes gives as much as 30% improvement.
375    
376    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
377        call.
378    
379    14. As documented, (*COMMIT) is now confined to within a positive assertion.
380    
381    15. It is now possible to link pcretest with libedit as an alternative to
382        libreadline.
383    
384    16. (*COMMIT) control verb is now supported by the JIT compiler.
385    
386    17. The Unicode data tables have been updated to Unicode 6.1.0.
387    
388    18. Added --file-list option to pcregrep.
389    
390    19. Added binary file support to pcregrep, including the -a, --binary-files,
391        -I, and --text options.
392    
393    20. The madvise function is renamed for posix_madvise for QNX compatibility
394        reasons. Fixed by Giuseppe D'Angelo.
395    
396    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
397    
398    22. Changed the option for creating symbolic links for 16-bit man pages from
399        -s to -sf so that re-installing does not cause issues.
400    
401    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
402    
403    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
404        matches in certain environments (the workspace was not being correctly
405        retained). Also added to pcre_dfa_exec() a simple plausibility check on
406        some of the workspace data at the beginning of a restart.
407    
408    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
409        was not doing so when it should - probably a typo introduced by SVN 528
410        (change 8.10/14).
411    
412    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
413        \w+ when the character tables indicated that \x{c4} was a word character.
414        There were several related cases, all because the tests for doing a table
415        lookup were testing for characters less than 127 instead of 255.
416    
417    27. If a pattern contains capturing parentheses that are not used in a match,
418        their slots in the ovector are set to -1. For those that are higher than
419        any matched groups, this happens at the end of processing. In the case when
420        there were back references that the ovector was too small to contain
421        (causing temporary malloc'd memory to be used during matching), and the
422        highest capturing number was not used, memory off the end of the ovector
423        was incorrectly being set to -1. (It was using the size of the temporary
424        memory instead of the true size.)
425    
426    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
427        ovector size, it uses memory at the end of the block that it has got.
428    
429    29. Check for an overlong MARK name and give an error at compile time. The
430        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
431    
432    30. JIT compiler update.
433    
434    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
435        Rill for the patch.
436    
437    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
438    
439    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
440    
441    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
442        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
443        was enabled.
444    
445    35. Improve JIT code generation for greedy plus quantifier.
446    
447    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
448        1 to "aa" instead of to an empty string. The bug affected repeated groups
449        that could potentially match an empty string.
450    
451    37. Optimizing single character iterators in JIT.
452    
453    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
454        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
455        codepoints that are too big for the mode are faulted, and in a UTF mode,
456        disallowed codepoints are also faulted.
457    
458    39. If PCRE was compiled with UTF support, in three places in the DFA
459        matcher there was code that should only have been obeyed in UTF mode, but
460        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
461        processing when bytes with values greater than 127 were present. In 16-bit
462        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
463        both cases the values are those that cannot be the first data item in a UTF
464        character. The three items that might have provoked this were recursions,
465        possessively repeated groups, and atomic groups.
466    
467    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
468        and pcregrep, because some OS require shared objects to be explicitly
469        passed to ld, causing the link step to fail if they are not.
470    
471    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
472        mode, patterns that started with \h* or \R* might be incorrectly matched.
473    
474    
475    Version 8.30 04-February-2012
476    -----------------------------
477    
478    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
479        name is defined in ctype.h.
480    
481    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
482        only in quite long subpatterns.
483    
484    3.  Removed the function pcre_info(), which has been obsolete and deprecated
485        since it was replaced by pcre_fullinfo() in February 2000.
486    
487    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
488        match a (*MARK), and the match failed at the start of the subject, a
489        reference to memory before the start of the subject could occur. This bug
490        was introduced by fix 17 of release 8.21.
491    
492    5.  A reference to an unset group with zero minimum repetition was giving
493        totally wrong answers (in non-JavaScript-compatibility mode). For example,
494        /(another)?(\1?)test/ matched against "hello world test". This bug was
495        introduced in release 8.13.
496    
497    6.  Add support for 16-bit character strings (a large amount of work involving
498        many changes and refactorings).
499    
500    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
501        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
502        from a file.
503    
504    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
505        rounding is not applied in this particular case).
506    
507    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
508        if they appear, or are escaped, in patterns.
509    
510    10. Get rid of a number of -Wunused-but-set-variable warnings.
511    
512    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
513        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
514        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
515        also returns the mark "x". This bug applied to capturing parentheses,
516        non-capturing parentheses, and atomic parentheses. It also applied to some
517        assertions.
518    
519    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
520        information out of configure.ac instead of relying on pcre.h.generic, which
521        is not stored in the repository.
522    
523    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
524        -lreadline.
525    
526    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
527    
528    15. Applied Graycode's patch to put the top-level frame on the stack rather
529        than the heap when not using the stack for recursion. This gives a
530        performance improvement in many cases when recursion is not deep.
531    
532    16. Experimental code added to "pcretest -C" to output the stack frame size.
533    
534    
535    Version 8.21 12-Dec-2011
536    ------------------------
537    
538    1.  Updating the JIT compiler.
539    
540    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
541        are added as well.
542    
543    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
544        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
545        calling _pcre_jit_exec. Some extra comments are added.
546    
547    4.  (*MARK) settings inside atomic groups that do not contain any capturing
548        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
549        was introduced by change 18 for 8.20.
550    
551    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
552        ECMA-262 standard.
553    
554    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
555        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
556        This bug was probably introduced by change 9 of 8.13.
557    
558    7.  While fixing 6 above, I noticed that a number of other items were being
559        incorrectly rejected as "not fixed length". This arose partly because newer
560        opcodes had not been added to the fixed-length checking code. I have (a)
561        corrected the bug and added tests for these items, and (b) arranged for an
562        error to occur if an unknown opcode is encountered while checking for fixed
563        length instead of just assuming "not fixed length". The items that were
564        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
565        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
566        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
567    
568    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
569        being incorrectly compiled and would have given unpredicatble results.
570    
571    9.  A possessively repeated subpattern with minimum repeat count greater than
572        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
573        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
574        the first (A) could occur when it should not.
575    
576    10. Add a cast and remove a redundant test from the code.
577    
578    11. JIT should use pcre_malloc/pcre_free for allocation.
579    
580    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
581        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
582        is anything other than /usr, -L is still shown).
583    
584    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
585    
586    14. Perl does not support \N without a following name in a [] class; PCRE now
587        also gives an error.
588    
589    15. If a forward reference was repeated with an upper limit of around 2000,
590        it caused the error "internal error: overran compiling workspace". The
591        maximum number of forward references (including repeats) was limited by the
592        internal workspace, and dependent on the LINK_SIZE. The code has been
593        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
594        the default depends on LINK_SIZE. There is a new upper limit (for safety)
595        of around 200,000 forward references. While doing this, I also speeded up
596        the filling in of repeated forward references.
597    
598    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
599        incorrectly expecting the subject to contain another "a" after the start.
600    
601    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
602        in the match, the SKIP should be ignored. This was not happening; instead
603        the SKIP was being treated as NOMATCH. For patterns such as
604        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
605        tested.
606    
607    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
608        now much more compatible with Perl, in particular in cases where the result
609        is a non-match for a non-anchored pattern. For example, if
610        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
611        "m", where previously it did not return a name. A side effect of this
612        change is that for partial matches, the last encountered mark name is
613        returned, as for non matches. A number of tests that were previously not
614        Perl-compatible have been moved into the Perl-compatible test files. The
615        refactoring has had the pleasing side effect of removing one argument from
616        the match() function, thus reducing its stack requirements.
617    
618    19. If the /S+ option was used in pcretest to study a pattern using JIT,
619        subsequent uses of /S (without +) incorrectly behaved like /S+.
620    
621    21. Retrieve executable code size support for the JIT compiler and fixing
622        some warnings.
623    
624    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
625        not work when the shorter character appeared right at the end of the
626        subject string.
627    
628    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
629        systems.
630    
631    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
632        output it when the /M option is used in pcretest.
633    
634    25. The CheckMan script was not being included in the distribution. Also, added
635        an explicit "perl" to run Perl scripts from the PrepareRelease script
636        because this is reportedly needed in Windows.
637    
638    26. If study data was being save in a file and studying had not found a set of
639        "starts with" bytes for the pattern, the data written to the file (though
640        never used) was taken from uninitialized memory and so caused valgrind to
641        complain.
642    
643    27. Updated RunTest.bat as provided by Sheri Pierce.
644    
645    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
646    
647    29. Computation of memory usage for the table of capturing group names was
648        giving an unnecessarily large value.
649    
650    
651    Version 8.20 21-Oct-2011
652    ------------------------
653    
654    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
655        a POSIX class. After further experiments with Perl, which convinced me that
656        Perl has bugs and confusions, a closing square bracket is no longer allowed
657        in a POSIX name. This bug also affected patterns with classes that started
658        with full stops.
659    
660    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
661        captured substring, but while checking the failing first alternative,
662        substring 1 is temporarily captured. If the output vector supplied to
663        pcre_exec() was not big enough for this capture, the yield of the function
664        was still zero ("insufficient space for captured substrings"). This cannot
665        be totally fixed without adding another stack variable, which seems a lot
666        of expense for a edge case. However, I have improved the situation in cases
667        such as /(a)(b)x|abc/ matched against "abc", where the return code
668        indicates that fewer than the maximum number of slots in the ovector have
669        been set.
670    
671    3.  Related to (2) above: when there are more back references in a pattern than
672        slots in the output vector, pcre_exec() uses temporary memory during
673        matching, and copies in the captures as far as possible afterwards. It was
674        using the entire output vector, but this conflicts with the specification
675        that only 2/3 is used for passing back captured substrings. Now it uses
676        only the first 2/3, for compatibility. This is, of course, another edge
677        case.
678    
679    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
680        main code base, and can be used by building with --enable-jit. When this is
681        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
682        runtime --no-jit option is given.
683    
684    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
685        ovector, the return from the function was zero, implying that there were
686        other matches that did not fit. The correct "exactly full" value is now
687        returned.
688    
689    6.  If a subpattern that was called recursively or as a subroutine contained
690        (*PRUNE) or any other control that caused it to give a non-standard return,
691        invalid errors such as "Error -26 (nested recursion at the same subject
692        position)" or even infinite loops could occur.
693    
694    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
695        computing the minimum length on reaching *ACCEPT, and so ended up with the
696        wrong value of 1 rather than 0. Further investigation indicates that
697        computing a minimum subject length in the presence of *ACCEPT is difficult
698        (think back references, subroutine calls), and so I have changed the code
699        so that no minimum is registered for a pattern that contains *ACCEPT.
700    
701    8.  If (*THEN) was present in the first (true) branch of a conditional group,
702        it was not handled as intended. [But see 16 below.]
703    
704    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
705        Sheri Pierce.
706    
707    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
708        the first byte in a match must be "a".
709    
710    11. Change 17 for 8.13 increased the recursion depth for patterns like
711        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
712        pattern contains any instances of (*THEN). If it does not, the old
713        optimizations are restored. It would be nice to do this on a per-group
714        basis, but at the moment that is not feasible.
715    
716    12. In some environments, the output of pcretest -C is CRLF terminated. This
717        broke RunTest's code that checks for the link size. A single white space
718        character after the value is now allowed for.
719    
720    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
721        For "fr", it uses the Windows-specific input and output files.
722    
723    14. If (*THEN) appeared in a group that was called recursively or as a
724        subroutine, it did not work as intended. [But see next item.]
725    
726    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
727        pattern fragments (but not containing any | characters). If A and B are
728        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
729        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
730        D. In other words, Perl considers parentheses that do not contain any |
731        characters to be part of a surrounding alternative, whereas PCRE was
732        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
733        differently. PCRE now behaves in the same way as Perl, except in the case
734        of subroutine/recursion calls such as (?1) which have in any case always
735        been different (but PCRE had them first :-).
736    
737    16. Related to 15 above: Perl does not treat the | in a conditional group as
738        creating alternatives. Such a group is treated in the same way as an
739        ordinary group without any | characters when processing (*THEN). PCRE has
740        been changed to match Perl's behaviour.
741    
742    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
743        RunGrepTest script failed.
744    
745    18. Change 22 for version 13 caused atomic groups to use more stack. This is
746        inevitable for groups that contain captures, but it can lead to a lot of
747        stack use in large patterns. The old behaviour has been restored for atomic
748        groups that do not contain any capturing parentheses.
749    
750    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
751        suppress the check for a minimum subject length at run time. (If it was
752        given to pcre_exec() or pcre_dfa_exec() it did work.)
753    
754    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
755        fail to work when decoding hex characters in data strings in EBCDIC
756        environments.
757    
758    21. It appears that in at least one Mac OS environment, the isxdigit() function
759        is implemented as a macro that evaluates to its argument more than once,
760        contravening the C 90 Standard (I haven't checked a later standard). There
761        was an instance in pcretest which caused it to go wrong when processing
762        \x{...} escapes in subject strings. The has been rewritten to avoid using
763        things like p++ in the argument of isxdigit().
764    
765    
766    Version 8.13 16-Aug-2011
767  ------------------------  ------------------------
768    
769  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 20  Version 8.13 30-Apr-2011 Line 782  Version 8.13 30-Apr-2011
782      code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a      code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
783      2-byte code at the end of the subject (it thought there wasn't enough data      2-byte code at the end of the subject (it thought there wasn't enough data
784      left).      left).
785    
786  5.  Comprehensive information about what went wrong is now returned by  5.  Comprehensive information about what went wrong is now returned by
787      pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long      pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
788      as the output vector has at least 2 elements. The offset of the start of      as the output vector has at least 2 elements. The offset of the start of
789      the failing character and a reason code are placed in the vector.      the failing character and a reason code are placed in the vector.
790    
791  6.  When the UTF-8 string check fails for pcre_compile(), the offset that is  6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
792      now returned is for the first byte of the failing character, instead of the      now returned is for the first byte of the failing character, instead of the
793      last byte inspected. This is an incompatible change, but I hope it is small      last byte inspected. This is an incompatible change, but I hope it is small
794      enough not to be a problem. It makes the returned offset consistent with      enough not to be a problem. It makes the returned offset consistent with
795      pcre_exec() and pcre_dfa_exec().      pcre_exec() and pcre_dfa_exec().
796    
797  7.  pcretest now gives a text phrase as well as the error number when  7.  pcretest now gives a text phrase as well as the error number when
798      pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check      pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
799      failure, the offset and reason code are output.      failure, the offset and reason code are output.
800    
801  8.  When \R was used with a maximizing quantifier it failed to skip backwards  8.  When \R was used with a maximizing quantifier it failed to skip backwards
802      over a \r\n pair if the subsequent match failed. Instead, it just skipped      over a \r\n pair if the subsequent match failed. Instead, it just skipped
803      back over a single character (\n). This seems wrong (because it treated the      back over a single character (\n). This seems wrong (because it treated the
804      two characters as a single entity when going forwards), conflicts with the      two characters as a single entity when going forwards), conflicts with the
805      documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the      documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
806      behaviour of \R* different to (\R)*, which also seems wrong. The behaviour      behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
807      has been changed.      has been changed.
808    
809  9.  Some internal refactoring has changed the processing so that the handling  9.  Some internal refactoring has changed the processing so that the handling
810      of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile      of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
811      time (the PCRE_DOTALL option was changed this way some time ago: version      time (the PCRE_DOTALL option was changed this way some time ago: version
812      7.7 change 16). This has made it possible to abolish the OP_OPT op code,      7.7 change 16). This has made it possible to abolish the OP_OPT op code,
813      which was always a bit of a fudge. It also means that there is one less      which was always a bit of a fudge. It also means that there is one less
814      argument for the match() function, which reduces its stack requirements      argument for the match() function, which reduces its stack requirements
815      slightly. This change also fixes an incompatibility with Perl: the pattern      slightly. This change also fixes an incompatibility with Perl: the pattern
816      (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.      (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
817    
818  10. More internal refactoring has drastically reduced the number of recursive  10. More internal refactoring has drastically reduced the number of recursive
819      calls to match() for possessively repeated groups such as (abc)++ when      calls to match() for possessively repeated groups such as (abc)++ when
820      using pcre_exec().      using pcre_exec().
821    
822  11. While implementing 10, a number of bugs in the handling of groups were  11. While implementing 10, a number of bugs in the handling of groups were
823      discovered and fixed:      discovered and fixed:
824    
825      (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).      (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
826      (a|)*(?1) gave a compile-time internal error.      (a|)*(?1) gave a compile-time internal error.
827      ((a|)+)+  did not notice that the outer group could match an empty string.      ((a|)+)+  did not notice that the outer group could match an empty string.
828      (^a|^)+   was not marked as anchored.      (^a|^)+   was not marked as anchored.
829      (.*a|.*)+ was not marked as matching at start or after a newline.      (.*a|.*)+ was not marked as matching at start or after a newline.
830    
831  12. Yet more internal refactoring has removed another argument from the match()  12. Yet more internal refactoring has removed another argument from the match()
832      function. Special calls to this function are now indicated by setting a      function. Special calls to this function are now indicated by setting a
833      value in a variable in the "match data" data block.      value in a variable in the "match data" data block.
834    
835  13. Be more explicit in pcre_study() instead of relying on "default" for  13. Be more explicit in pcre_study() instead of relying on "default" for
836      opcodes that mean there is no starting character; this means that when new      opcodes that mean there is no starting character; this means that when new
837      ones are added and accidentally left out of pcre_study(), testing should      ones are added and accidentally left out of pcre_study(), testing should
838      pick them up.      pick them up.
839    
840  14. The -s option of pcretest has been documented for ages as being an old  14. The -s option of pcretest has been documented for ages as being an old
841      synonym of -m (show memory usage). I have changed it to mean "force study      synonym of -m (show memory usage). I have changed it to mean "force study
842      for every regex", that is, assume /S for every regex. This is similar to -i      for every regex", that is, assume /S for every regex. This is similar to -i
843      and -d etc. It's slightly incompatible, but I'm hoping nobody is still      and -d etc. It's slightly incompatible, but I'm hoping nobody is still
844      using it. It makes it easier to run collections of tests with and without      using it. It makes it easier to run collections of tests with and without
845      study enabled, and thereby test pcre_study() more easily. All the standard      study enabled, and thereby test pcre_study() more easily. All the standard
846      tests are now run with and without -s (but some patterns can be marked as      tests are now run with and without -s (but some patterns can be marked as
847      "never study" - see 20 below).      "never study" - see 20 below).
848    
849  15. When (*ACCEPT) was used in a subpattern that was called recursively, the  15. When (*ACCEPT) was used in a subpattern that was called recursively, the
850      restoration of the capturing data to the outer values was not happening      restoration of the capturing data to the outer values was not happening
851      correctly.      correctly.
852    
853  16. If a recursively called subpattern ended with (*ACCEPT) and matched an  16. If a recursively called subpattern ended with (*ACCEPT) and matched an
854      empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole      empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
855      pattern had matched an empty string, and so incorrectly returned a no      pattern had matched an empty string, and so incorrectly returned a no
856      match.      match.
857    
858  17. There was optimizing code for the last branch of non-capturing parentheses,  17. There was optimizing code for the last branch of non-capturing parentheses,
859      and also for the obeyed branch of a conditional subexpression, which used      and also for the obeyed branch of a conditional subexpression, which used
860      tail recursion to cut down on stack usage. Unfortunately, not that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
861      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
862      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
863      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
864    
865  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
866      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
867      incorrectly computed because \R can also match just one byte.      incorrectly computed because \R can also match just one byte.
868    
869  19. If a pattern containing (*ACCEPT) was studied, the minimum subject length  19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
870      was incorrectly computed.      was incorrectly computed.
871    
872  20. If /S is present twice on a test pattern in pcretest input, it *disables*  20. If /S is present twice on a test pattern in pcretest input, it now
873      studying, thereby overriding the use of -s on the command line. This is      *disables* studying, thereby overriding the use of -s on the command line
874      necessary for one or two tests to keep the output identical in both cases.      (see 14 above). This is necessary for one or two tests to keep the output
875        identical in both cases.
876    
877  21. When (*ACCEPT) was used in an assertion that matched an empty string and  21. When (*ACCEPT) was used in an assertion that matched an empty string and
878      PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.      PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
879    
880  22. When an atomic group that contained a capturing parenthesis was  22. When an atomic group that contained a capturing parenthesis was
881      successfully matched, but the branch in which it appeared failed, the      successfully matched, but the branch in which it appeared failed, the
882      capturing was not being forgotten if a higher numbered group was later      capturing was not being forgotten if a higher numbered group was later
883      captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing      captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
884      group 1 to "a", when in fact it should be unset. This applied to multi-      group 1 to "a", when in fact it should be unset. This applied to multi-
885      branched capturing and non-capturing groups, repeated or not, and also to      branched capturing and non-capturing groups, repeated or not, and also to
886      positive assertions (capturing in negative assertions is not well defined      positive assertions (capturing in negative assertions does not happen
887      in PCRE) and also to nested atomic groups.      in PCRE) and also to nested atomic groups.
888    
889  23. Add the ++ qualifier feature to pcretest, to show the remainder of the  23. Add the ++ qualifier feature to pcretest, to show the remainder of the
890      subject after a captured substring (to make it easier to tell which of a      subject after a captured substring, to make it easier to tell which of a
891      number of identical substrings has been captured).      number of identical substrings has been captured.
892    
893  24. The way atomic groups are processed by pcre_exec() has been changed so that  24. The way atomic groups are processed by pcre_exec() has been changed so that
894      if they are repeated, backtracking one repetition now resets captured      if they are repeated, backtracking one repetition now resets captured
895      values correctly. For example, if ((?>(a+)b)+aabab) is matched against      values correctly. For example, if ((?>(a+)b)+aabab) is matched against
896      "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as      "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
897      "aaa". Previously, it would have been "a". As part of this code      "aaa". Previously, it would have been "a". As part of this code
898      refactoring, the way recursive calls are handled has also been changed.      refactoring, the way recursive calls are handled has also been changed.
899    
900  24. If an assertion condition captured any substrings, they were not passed  25. If an assertion condition captured any substrings, they were not passed
901      back unless some other capturing happened later. For example, if      back unless some other capturing happened later. For example, if
902      (?(?=(a))a) was matched against "a", no capturing was returned.      (?(?=(a))a) was matched against "a", no capturing was returned.
903    
904  25. When studying a pattern that contained subroutine calls or assertions,  26. When studying a pattern that contained subroutine calls or assertions,
905      the code for finding the minimum length of a possible match was handling      the code for finding the minimum length of a possible match was handling
906      direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where      direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
907      group 1 called group 2 while simultaneously a separate group 2 called group      group 1 called group 2 while simultaneously a separate group 2 called group
908      1). A stack overflow occurred in this case. I have fixed this by limiting      1). A stack overflow occurred in this case. I have fixed this by limiting
909      the recursion depth to 10.      the recursion depth to 10.
910    
911  26. Updated RunTest.bat in the distribution to the version supplied by Tom  27. Updated RunTest.bat in the distribution to the version supplied by Tom
912      Fortmann. This supports explicit test numbers on the command line, and has      Fortmann. This supports explicit test numbers on the command line, and has
913      argument validation and error reporting.      argument validation and error reporting.
914    
915    28. An instance of \X with an unlimited repeat could fail if at any point the
916        first character it looked at was a mark character.
917    
918    29. Some minor code refactoring concerning Unicode properties and scripts
919        should reduce the stack requirement of match() slightly.
920    
921    30. Added the '=' option to pcretest to check the setting of unused capturing
922        slots at the end of the pattern, which are documented as being -1, but are
923        not included in the return count.
924    
925    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
926        compiled something random. Now it gives a compile-time error (as does
927        Perl).
928    
929    32. A *MARK encountered during the processing of a positive assertion is now
930        recorded and passed back (compatible with Perl).
931    
932    33. If --only-matching or --colour was set on a pcregrep call whose pattern
933        had alternative anchored branches, the search for a second match in a line
934        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
935        matched the line "0102" twice. The same bug affected patterns that started
936        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
937        twice.
938    
939    34. Previously, PCRE did not allow quantification of assertions. However, Perl
940        does, and because of capturing effects, quantifying parenthesized
941        assertions may at times be useful. Quantifiers are now allowed for
942        parenthesized assertions.
943    
944    35. A minor code tidy in pcre_compile() when checking options for \R usage.
945    
946    36. \g was being checked for fancy things in a character class, when it should
947        just be a literal "g".
948    
949    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
950        appearance of a nested POSIX class supersedes an apparent external class.
951        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
952        unescaped square brackets may also appear as part of class names. For
953        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
954        more like Perl. (But see 8.20/1 above.)
955    
956    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
957        was because it thought it was \N{name}, which is not supported).
958    
959    39. Add minix to OS list not supporting the -S option in pcretest.
960    
961    40. PCRE tries to detect cases of infinite recursion at compile time, but it
962        cannot analyze patterns in sufficient detail to catch mutual recursions
963        such as ((?1))((?2)). There is now a runtime test that gives an error if a
964        subgroup is called recursively as a subpattern for a second time at the
965        same position in the subject string. In previous releases this might have
966        been caught by the recursion limit, or it might have run out of stack.
967    
968    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
969        happen only once. PCRE was, however incorrectly giving a compile time error
970        "recursive call could loop indefinitely" because it cannot analyze the
971        pattern in sufficient detail. The compile time test no longer happens when
972        PCRE is compiling a conditional subpattern, but actual runaway loops are
973        now caught at runtime (see 40 above).
974    
975    42. It seems that Perl allows any characters other than a closing parenthesis
976        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
977        has been changed to be the same.
978    
979    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
980        as not to get warnings when autogen.sh is called. Also changed
981        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
982    
983    44. To help people who use pcregrep to scan files containing exceedingly long
984        lines, the following changes have been made:
985    
986        (a) The default value of the buffer size parameter has been increased from
987            8K to 20K. (The actual buffer used is three times this size.)
988    
989        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
990            PCRE is built.
991    
992        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
993            to be set at run time.
994    
995        (d) Numerical values in pcregrep options can be followed by K or M, for
996            example --buffer-size=50K.
997    
998        (e) If a line being scanned overflows pcregrep's buffer, an error is now
999            given and the return code is set to 2.
1000    
1001    45. Add a pointer to the latest mark to the callout data block.
1002    
1003    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1004        partial match of an empty string instead of no match. This was specific to
1005        the use of ".".
1006    
1007    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1008        complete match instead of a partial match. This bug was dependent on both
1009        the PCRE_UTF8 and PCRE_DOTALL options being set.
1010    
1011    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1012        starting byte set, because \b was not being ignored.
1013    
1014    
1015  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
# Line 801  Version 7.9 11-Apr-09 Line 1662  Version 7.9 11-Apr-09
1662  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
1663      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
1664      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1665      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1666        8.33.]
1667    
1668  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
1669      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being

Legend:
Removed from v.622  
changed lines
  Added in v.1324

  ViewVC Help
Powered by ViewVC 1.1.5