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

Diff of /code/trunk/ChangeLog

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

revision 505 by ph10, Tue Mar 9 16:50:47 2010 UTC revision 1405 by ph10, Mon Nov 25 15:09:21 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.02 01-Mar-2010  Version 8.34 19-November-2013
5    -----------------------------
6    
7    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
8        executable memory. Patch inspired by Carsten Klein.
9    
10    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
11        this macro is never tested and has no effect, because the work to support
12        coverage involves only compiling and linking options and special targets in
13        the Makefile. The comment in config.h implied that defining the macro would
14        enable coverage support, which is totally false. There was also support for
15        setting this macro in the CMake files (my fault, I just copied it from
16        configure). SUPPORT_GCOV has now been removed.
17    
18    3.  Make a small performance improvement in strlen16() and strlen32() in
19        pcretest.
20    
21    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
22        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
23        these cases). There was also one in pcretest.c.
24    
25    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
26    
27    6.  In UTF mode, the code for checking whether a group could match an empty
28        string (which is used for indefinitely repeated groups to allow for
29        breaking an infinite loop) was broken when the group contained a repeated
30        negated single-character class with a character that occupied more than one
31        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
32        UTF-8 mode). The effect was undefined: the group might or might not be
33        deemed as matching an empty string, or the program might have crashed.
34    
35    7.  The code for checking whether a group could match an empty string was not
36        recognizing that \h, \H, \v, \V, and \R must match a character.
37    
38    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
39        an empty string. If it can, pcretest shows this in its information output.
40    
41    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
42        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
43        matched by pcre_exec() without using JIT:
44    
45        (a) If the rest of the pattern did not match after a maximal run of
46            grapheme clusters, the code for backing up to try with fewer of them
47            did not always back up over a full grapheme when characters that do not
48            have the modifier quality were involved, e.g. Hangul syllables.
49    
50        (b) If the match point in a subject started with modifier character, and
51            there was no match, the code could incorrectly back up beyond the match
52            point, and potentially beyond the first character in the subject,
53            leading to a segfault or an incorrect match result.
54    
55    10. A conditional group with an assertion condition could lead to PCRE
56        recording an incorrect first data item for a match if no other first data
57        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
58        first data item, and therefore matched "ca" after "c" instead of at the
59        start.
60    
61    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
62        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
63    
64    12. The source of pcregrep now includes z/OS-specific code so that it can be
65        compiled for z/OS as part of the special z/OS distribution.
66    
67    13. Added the -T and -TM options to pcretest.
68    
69    14. The code in pcre_compile.c for creating the table of named capturing groups
70        has been refactored. Instead of creating the table dynamically during the
71        actual compiling pass, the information is remembered during the pre-compile
72        pass (on the stack unless there are more than 20 named groups, in which
73        case malloc() is used) and the whole table is created before the actual
74        compile happens. This has simplified the code (it is now nearly 150 lines
75        shorter) and prepared the way for better handling of references to groups
76        with duplicate names.
77    
78    15. A back reference to a named subpattern when there is more than one of the
79        same name now checks them in the order in which they appear in the pattern.
80        The first one that is set is used for the reference. Previously only the
81        first one was inspected. This change makes PCRE more compatible with Perl.
82    
83    16. Unicode character properties were updated from Unicode 6.3.0.
84    
85    17. The compile-time code for auto-possessification has been refactored, based
86        on a patch by Zoltan Herczeg. It now happens after instead of during
87        compilation. The code is cleaner, and more cases are handled. The option
88        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
89        options in pcretest are provided to set it. It can also be set by
90        (*NO_AUTO_POSSESS) at the start of a pattern.
91    
92    18. The character VT has been added to the default ("C" locale) set of
93        characters that match \s and are generally treated as white space,
94        following this same change in Perl 5.18. There is now no difference between
95        "Perl space" and "POSIX space". Whether VT is treated as white space in
96        other locales depends on the locale.
97    
98    19. The code for checking named groups as conditions, either for being set or
99        for being recursed, has been refactored (this is related to 14 and 15
100        above). Processing unduplicated named groups should now be as fast at
101        numerical groups, and processing duplicated groups should be faster than
102        before.
103    
104    20. Two patches to the CMake build system, by Alexander Barkov:
105    
106          (1) Replace the "source" command by "." in CMakeLists.txt because
107              "source" is a bash-ism.
108    
109          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
110              without these the CMake build does not work on Solaris.
111    
112    21. Perl has changed its handling of \8 and \9. If there is no previously
113        encountered capturing group of those numbers, they are treated as the
114        literal characters 8 and 9 instead of a binary zero followed by the
115        literals. PCRE now does the same.
116    
117    22. Following Perl, added \o{} to specify codepoints in octal, making it
118        possible to specify values greater than 0777 and also making them
119        unambiguous.
120    
121    23. Perl now gives an error for missing closing braces after \x{... instead of
122        treating the string as literal. PCRE now does the same.
123    
124    24. RunTest used to grumble if an inappropriate test was selected explicitly,
125        but just skip it when running all tests. This make it awkward to run ranges
126        of tests when one of them was inappropriate. Now it just skips any
127        inappropriate tests, as it always did when running all tests.
128    
129    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
130        character types such as \d or \w, too many callouts were inserted, and the
131        data that they returned was rubbish.
132    
133    26. In UCP mode, \s was not matching two of the characters that Perl matches,
134        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
135        were matched by \h. The code has now been refactored so that the lists of
136        the horizontal and vertical whitespace characters used for \h and \v (which
137        are defined only in one place) are now also used for \s.
138    
139    27. Add JIT support for the 64 bit TileGX architecture.
140        Patch by Jiong Wang (Tilera Corporation).
141    
142    28. Possessive quantifiers for classes (both explicit and automatically
143        generated) now use special opcodes instead of wrapping in ONCE brackets.
144    
145    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
146        (because it's meaningless), this was not happening when PCRE_CASELESS was
147        set. Not wrong, but inefficient.
148    
149    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
150        properties for \w, \d, etc) is present in a test regex. Otherwise if the
151        test contains no characters greater than 255, Perl doesn't realise it
152        should be using Unicode semantics.
153    
154    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
155        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
156        does in Unicode mode.
157    
158    32. Added the "forbid" facility to pcretest so that putting tests into the
159        wrong test files can sometimes be quickly detected.
160    
161    33. There is now a limit (default 250) on the depth of nesting of parentheses.
162        This limit is imposed to control the amount of system stack used at compile
163        time. It can be changed at build time by --with-parens-nest-limit=xxx or
164        the equivalent in CMake.
165    
166    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
167        errors. Perl warns for these when in warning mode, but PCRE has no facility
168        for giving warnings.
169    
170    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
171        However, this was not working for (?!) because it is optimized to (*FAIL),
172        for which PCRE does not allow quantifiers. The optimization is now disabled
173        when a quantifier follows (?!). I can't see any use for this, but it makes
174        things uniform.
175    
176    36. Perl no longer allows group names to start with digits, so I have made this
177        change also in PCRE. It simplifies the code a bit.
178    
179    37. In extended mode, Perl ignores spaces before a + that indicates a
180        possessive quantifier. PCRE allowed a space before the quantifier, but not
181        before the possessive +. It now does.
182    
183    38. The use of \K (reset reported match start) within a repeated possessive
184        group such as (a\Kb)*+ was not working.
185    
186    40. Document that the same character tables must be used at compile time and
187        run time, and that the facility to pass tables to pcre_exec() and
188        pcre_dfa_exec() is for use only with saved/restored patterns.
189    
190    
191    Version 8.33 28-May-2013
192    ------------------------
193    
194    1.  Added 'U' to some constants that are compared to unsigned integers, to
195        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
196        variables that are added to signed variables, to ensure the result is
197        signed and can be negated.
198    
199    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
200        CMake config files.
201    
202    3.  Revise the creation of config.h.generic so that all boolean macros are
203        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
204        overriding via -D on the command line possible.
205    
206    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
207        to unsigned int is reported to make a quite noticeable speed difference in
208        a specific Windows environment. Testing on Linux did also appear to show
209        some benefit (and it is clearly not harmful). Also fixed the definition of
210        Xop which should be unsigned.
211    
212    5.  Related to (4), changing the definition of the intermediate variable cc
213        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
214        improvements.
215    
216    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
217        unnecessary spaces.
218    
219    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
220        and later.
221    
222    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
223    
224    9.  Optimizing fast_forward_start_bits in JIT.
225    
226    10. Adding support for callouts in JIT, and fixing some issues revealed
227        during this work. Namely:
228    
229        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
230    
231        (b) Minimum length was not checked before the matching is started.
232    
233    11. The value of capture_last that is passed to callouts was incorrect in some
234        cases when there was a capture on one path that was subsequently abandoned
235        after a backtrack. Also, the capture_last value is now reset after a
236        recursion, since all captures are also reset in this case.
237    
238    12. The interpreter no longer returns the "too many substrings" error in the
239        case when an overflowing capture is in a branch that is subsequently
240        abandoned after a backtrack.
241    
242    13. In the pathological case when an offset vector of size 2 is used, pcretest
243        now prints out the matched string after a yield of 0 or 1.
244    
245    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
246        Only supported by the JIT compiler at the moment.
247    
248    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
249    
250    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
251        offset of the starting point of the matching process, provided the offsets
252        vector is large enough.
253    
254    17. The \A escape now records a lookbehind value of 1, though its execution
255        does not actually inspect the previous character. This is to ensure that,
256        in partial multi-segment matching, at least one character from the old
257        segment is retained when a new segment is processed. Otherwise, if there
258        are no lookbehinds in the pattern, \A might match incorrectly at the start
259        of a new segment.
260    
261    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
262    
263    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
264        gives some modest performance improvement in 8-bit mode.
265    
266    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
267        be expressed in certain programming languages using Universal Character
268        Names.
269    
270    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
271        which points out that "non characters" are not "characters that may not
272        appear in Unicode strings" but rather "characters that are reserved for
273        internal use and have only local meaning".
274    
275    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
276        there was a conditional group that depended on an assertion, if the
277        assertion was false, the callout that immediately followed the alternation
278        in the condition was skipped when pcre_exec() was used for matching.
279    
280    23. Allow an explicit callout to be inserted before an assertion that is the
281        condition for a conditional group, for compatibility with automatic
282        callouts, which always insert a callout at this point.
283    
284    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
285        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
286    
287    25. (*PRUNE) is now supported by the JIT compiler.
288    
289    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
290    
291    27. Fix the case where there are two or more SKIPs with arguments that may be
292        ignored.
293    
294    28. (*SKIP) is now supported by the JIT compiler.
295    
296    29. (*THEN) is now supported by the JIT compiler.
297    
298    30. Update RunTest with additional test selector options.
299    
300    31. The way PCRE handles backtracking verbs has been changed in two ways.
301    
302        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
303        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
304        backtracking. In some cases this makes it more Perl-compatible, but Perl's
305        rather obscure rules do not always do the same thing.
306    
307        (2) Previously, backtracking verbs were confined within assertions. This is
308        no longer the case for positive assertions, except for (*ACCEPT). Again,
309        this sometimes improves Perl compatibility, and sometimes does not.
310    
311    32. A number of tests that were in test 2 because Perl did things differently
312        have been moved to test 1, because either Perl or PCRE has changed, and
313        these tests are now compatible.
314    
315    32. Backtracking control verbs are now handled in the same way in JIT and
316        interpreter.
317    
318    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
319        contained a forward subroutine reference caused a compile error.
320    
321    34. Auto-detect and optimize limited repetitions in JIT.
322    
323    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
324        blocking (*UTF) etc.
325    
326    36. In the interpreter, maximizing pattern repetitions for characters and
327        character types now use tail recursion, which reduces stack usage.
328    
329    37. The value of the max lookbehind was not correctly preserved if a compiled
330        and saved regex was reloaded on a host of different endianness.
331    
332    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
333        of the compiled pattern block, expand the flags field from 16 to 32 bits
334        because it was almost full.
335    
336    39. Try madvise first before posix_madvise.
337    
338    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
339        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
340        original change locked out all matches of empty strings. This has been
341        changed so that one match of an empty string per line is recognized.
342        Subsequent searches on the same line (for colouring or for --only-matching,
343        for example) do not recognize empty strings.
344    
345    41. Applied a user patch to fix a number of spelling mistakes in comments.
346    
347    42. Data lines longer than 65536 caused pcretest to crash.
348    
349    43. Clarified the data type for length and startoffset arguments for pcre_exec
350        and pcre_dfa_exec in the function-specific man pages, where they were
351        explicitly stated to be in bytes, never having been updated. I also added
352        some clarification to the pcreapi man page.
353    
354    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
355        a segmentation fault.
356    
357    
358    Version 8.32 30-November-2012
359    -----------------------------
360    
361    1.  Improved JIT compiler optimizations for first character search and single
362        character iterators.
363    
364    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
365        Patch by Daniel Richard G.
366    
367    3.  Single character iterator optimizations in the JIT compiler.
368    
369    4.  Improved JIT compiler optimizations for character ranges.
370    
371    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
372        Reported by Giuseppe D'Angelo.
373    
374    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
375        of a line, was being set incorrectly in cases where .* appeared inside
376        atomic brackets at the start of a pattern, or where there was a subsequent
377        *PRUNE or *SKIP.
378    
379    7.  Improved instruction cache flush for POWER/PowerPC.
380        Patch by Daniel Richard G.
381    
382    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
383        grep:
384    
385        (a) There is now no limit to the number of patterns to be matched.
386    
387        (b) An error is given if a pattern is too long.
388    
389        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
390            are now supported.
391    
392        (d) --exclude-from and --include-from (multiple use) have been added.
393    
394        (e) Exclusions and inclusions now apply to all files and directories, not
395            just to those obtained from scanning a directory recursively.
396    
397        (f) Multiple uses of -f and --file-list are now supported.
398    
399        (g) In a Windows environment, the default for -d has been changed from
400            "read" (the GNU grep default) to "skip", because otherwise the presence
401            of a directory in the file list provokes an error.
402    
403        (h) The documentation has been revised and clarified in places.
404    
405    9.  Improve the matching speed of capturing brackets.
406    
407    10. Changed the meaning of \X so that it now matches a Unicode extended
408        grapheme cluster.
409    
410    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
411        out POSIX threads when JIT support is configured.
412    
413    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
414    
415    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
416        structure could go wrong in environments where size_t is not the same size
417        as int.
418    
419    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
420        set.
421    
422    15. The EBCDIC support had decayed; later updates to the code had included
423        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
424        general tidy up of EBCDIC-related issues, and the documentation was also
425        not quite right. There is now a test that can be run on ASCII systems to
426        check some of the EBCDIC-related things (but is it not a full test).
427    
428    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
429        in a small tidy to the code.
430    
431    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
432    
433    18. If the --only-matching (-o) option in pcregrep is specified multiple
434        times, each one causes appropriate output. For example, -o1 -o2 outputs the
435        substrings matched by the 1st and 2nd capturing parentheses. A separating
436        string can be specified by --om-separator (default empty).
437    
438    19. Improving the first n character searches.
439    
440    20. Turn case lists for horizontal and vertical white space into macros so that
441        they are defined only once.
442    
443    21. This set of changes together give more compatible Unicode case-folding
444        behaviour for characters that have more than one other case when UCP
445        support is available.
446    
447        (a) The Unicode property table now has offsets into a new table of sets of
448            three or more characters that are case-equivalent. The MultiStage2.py
449            script that generates these tables (the pcre_ucd.c file) now scans
450            CaseFolding.txt instead of UnicodeData.txt for character case
451            information.
452    
453        (b) The code for adding characters or ranges of characters to a character
454            class has been abstracted into a generalized function that also handles
455            case-independence. In UTF-mode with UCP support, this uses the new data
456            to handle characters with more than one other case.
457    
458        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
459            whose other case is greater than 256 are now correctly matched
460            caselessly. Previously, the high codepoint matched the low one, but not
461            vice versa.
462    
463        (d) The processing of \h, \H, \v, and \ in character classes now makes use
464            of the new class addition function, using character lists defined as
465            macros alongside the case definitions of 20 above.
466    
467        (e) Caseless back references now work with characters that have more than
468            one other case.
469    
470        (f) General caseless matching of characters with more than one other case
471            is supported.
472    
473    22. Unicode character properties were updated from Unicode 6.2.0
474    
475    23. Improved CMake support under Windows. Patch by Daniel Richard G.
476    
477    24. Add support for 32-bit character strings, and UTF-32
478    
479    25. Major JIT compiler update (code refactoring and bugfixing).
480        Experimental Sparc 32 support is added.
481    
482    26. Applied a modified version of Daniel Richard G's patch to create
483        pcre.h.generic and config.h.generic by "make" instead of in the
484        PrepareRelease script.
485    
486    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
487        pcre_compile.c when checking for a zero character.
488    
489    28. Introducing a native interface for JIT. Through this interface, the compiled
490        machine code can be directly executed. The purpose of this interface is to
491        provide fast pattern matching, so several sanity checks are not performed.
492        However, feature tests are still performed. The new interface provides
493        1.4x speedup compared to the old one.
494    
495    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
496        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
497        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
498    
499    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
500        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
501        the "old" RFC 2279). Instead, it ended up passing a negative length to
502        pcre_exec().
503    
504    31. Add support for GCC's visibility feature to hide internal functions.
505    
506    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
507        "unknown -C option" after outputting 0 or 1.
508    
509    33. There is now support for generating a code coverage report for the test
510        suite in environments where gcc is the compiler and lcov is installed. This
511        is mainly for the benefit of the developers.
512    
513    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
514        unaddressable using valgrind annotations, allowing valgrind to detect
515        invalid memory accesses. This is mainly for the benefit of the developers.
516    
517    25. (*UTF) can now be used to start a pattern in any of the three libraries.
518    
519    26. Give configure error if --enable-cpp but no C++ compiler found.
520    
521    
522    Version 8.31 06-July-2012
523    -------------------------
524    
525    1.  Fixing a wrong JIT test case and some compiler warnings.
526    
527    2.  Removed a bashism from the RunTest script.
528    
529    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
530        to unsigned type, result still unsigned" that was given by an MS compiler
531        on encountering the code "-sizeof(xxx)".
532    
533    4.  Partial matching support is added to the JIT compiler.
534    
535    5.  Fixed several bugs concerned with partial matching of items that consist
536        of more than one character:
537    
538        (a) /^(..)\1/ did not partially match "aba" because checking references was
539            done on an "all or nothing" basis. This also applied to repeated
540            references.
541    
542        (b) \R did not give a hard partial match if \r was found at the end of the
543            subject.
544    
545        (c) \X did not give a hard partial match after matching one or more
546            characters at the end of the subject.
547    
548        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
549            a partial match for the string "\r".
550    
551        (e) When newline was set to CRLF, the metacharacter "." did not recognize
552            a partial match for a CR character at the end of the subject string.
553    
554    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
555        running pcretest, the text "(JIT)" added to the output whenever JIT is
556        actually used to run the match.
557    
558    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
559        or /S+[+] with a digit between 1 and 7.
560    
561    8.  OP_NOT now supports any UTF character not just single-byte ones.
562    
563    9.  (*MARK) control verb is now supported by the JIT compiler.
564    
565    10. The command "./RunTest list" lists the available tests without actually
566        running any of them. (Because I keep forgetting what they all are.)
567    
568    11. Add PCRE_INFO_MAXLOOKBEHIND.
569    
570    12. Applied a (slightly modified) user-supplied patch that improves performance
571        when the heap is used for recursion (compiled with --disable-stack-for-
572        recursion). Instead of malloc and free for each heap frame each time a
573        logical recursion happens, frames are retained on a chain and re-used where
574        possible. This sometimes gives as much as 30% improvement.
575    
576    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
577        call.
578    
579    14. As documented, (*COMMIT) is now confined to within a positive assertion.
580    
581    15. It is now possible to link pcretest with libedit as an alternative to
582        libreadline.
583    
584    16. (*COMMIT) control verb is now supported by the JIT compiler.
585    
586    17. The Unicode data tables have been updated to Unicode 6.1.0.
587    
588    18. Added --file-list option to pcregrep.
589    
590    19. Added binary file support to pcregrep, including the -a, --binary-files,
591        -I, and --text options.
592    
593    20. The madvise function is renamed for posix_madvise for QNX compatibility
594        reasons. Fixed by Giuseppe D'Angelo.
595    
596    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
597    
598    22. Changed the option for creating symbolic links for 16-bit man pages from
599        -s to -sf so that re-installing does not cause issues.
600    
601    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
602    
603    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
604        matches in certain environments (the workspace was not being correctly
605        retained). Also added to pcre_dfa_exec() a simple plausibility check on
606        some of the workspace data at the beginning of a restart.
607    
608    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
609        was not doing so when it should - probably a typo introduced by SVN 528
610        (change 8.10/14).
611    
612    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
613        \w+ when the character tables indicated that \x{c4} was a word character.
614        There were several related cases, all because the tests for doing a table
615        lookup were testing for characters less than 127 instead of 255.
616    
617    27. If a pattern contains capturing parentheses that are not used in a match,
618        their slots in the ovector are set to -1. For those that are higher than
619        any matched groups, this happens at the end of processing. In the case when
620        there were back references that the ovector was too small to contain
621        (causing temporary malloc'd memory to be used during matching), and the
622        highest capturing number was not used, memory off the end of the ovector
623        was incorrectly being set to -1. (It was using the size of the temporary
624        memory instead of the true size.)
625    
626    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
627        ovector size, it uses memory at the end of the block that it has got.
628    
629    29. Check for an overlong MARK name and give an error at compile time. The
630        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
631    
632    30. JIT compiler update.
633    
634    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
635        Rill for the patch.
636    
637    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
638    
639    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
640    
641    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
642        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
643        was enabled.
644    
645    35. Improve JIT code generation for greedy plus quantifier.
646    
647    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
648        1 to "aa" instead of to an empty string. The bug affected repeated groups
649        that could potentially match an empty string.
650    
651    37. Optimizing single character iterators in JIT.
652    
653    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
654        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
655        codepoints that are too big for the mode are faulted, and in a UTF mode,
656        disallowed codepoints are also faulted.
657    
658    39. If PCRE was compiled with UTF support, in three places in the DFA
659        matcher there was code that should only have been obeyed in UTF mode, but
660        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
661        processing when bytes with values greater than 127 were present. In 16-bit
662        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
663        both cases the values are those that cannot be the first data item in a UTF
664        character. The three items that might have provoked this were recursions,
665        possessively repeated groups, and atomic groups.
666    
667    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
668        and pcregrep, because some OS require shared objects to be explicitly
669        passed to ld, causing the link step to fail if they are not.
670    
671    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
672        mode, patterns that started with \h* or \R* might be incorrectly matched.
673    
674    
675    Version 8.30 04-February-2012
676    -----------------------------
677    
678    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
679        name is defined in ctype.h.
680    
681    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
682        only in quite long subpatterns.
683    
684    3.  Removed the function pcre_info(), which has been obsolete and deprecated
685        since it was replaced by pcre_fullinfo() in February 2000.
686    
687    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
688        match a (*MARK), and the match failed at the start of the subject, a
689        reference to memory before the start of the subject could occur. This bug
690        was introduced by fix 17 of release 8.21.
691    
692    5.  A reference to an unset group with zero minimum repetition was giving
693        totally wrong answers (in non-JavaScript-compatibility mode). For example,
694        /(another)?(\1?)test/ matched against "hello world test". This bug was
695        introduced in release 8.13.
696    
697    6.  Add support for 16-bit character strings (a large amount of work involving
698        many changes and refactorings).
699    
700    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
701        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
702        from a file.
703    
704    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
705        rounding is not applied in this particular case).
706    
707    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
708        if they appear, or are escaped, in patterns.
709    
710    10. Get rid of a number of -Wunused-but-set-variable warnings.
711    
712    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
713        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
714        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
715        also returns the mark "x". This bug applied to capturing parentheses,
716        non-capturing parentheses, and atomic parentheses. It also applied to some
717        assertions.
718    
719    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
720        information out of configure.ac instead of relying on pcre.h.generic, which
721        is not stored in the repository.
722    
723    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
724        -lreadline.
725    
726    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
727    
728    15. Applied Graycode's patch to put the top-level frame on the stack rather
729        than the heap when not using the stack for recursion. This gives a
730        performance improvement in many cases when recursion is not deep.
731    
732    16. Experimental code added to "pcretest -C" to output the stack frame size.
733    
734    
735    Version 8.21 12-Dec-2011
736    ------------------------
737    
738    1.  Updating the JIT compiler.
739    
740    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
741        are added as well.
742    
743    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
744        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
745        calling _pcre_jit_exec. Some extra comments are added.
746    
747    4.  (*MARK) settings inside atomic groups that do not contain any capturing
748        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
749        was introduced by change 18 for 8.20.
750    
751    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
752        ECMA-262 standard.
753    
754    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
755        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
756        This bug was probably introduced by change 9 of 8.13.
757    
758    7.  While fixing 6 above, I noticed that a number of other items were being
759        incorrectly rejected as "not fixed length". This arose partly because newer
760        opcodes had not been added to the fixed-length checking code. I have (a)
761        corrected the bug and added tests for these items, and (b) arranged for an
762        error to occur if an unknown opcode is encountered while checking for fixed
763        length instead of just assuming "not fixed length". The items that were
764        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
765        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
766        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
767    
768    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
769        being incorrectly compiled and would have given unpredicatble results.
770    
771    9.  A possessively repeated subpattern with minimum repeat count greater than
772        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
773        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
774        the first (A) could occur when it should not.
775    
776    10. Add a cast and remove a redundant test from the code.
777    
778    11. JIT should use pcre_malloc/pcre_free for allocation.
779    
780    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
781        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
782        is anything other than /usr, -L is still shown).
783    
784    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
785    
786    14. Perl does not support \N without a following name in a [] class; PCRE now
787        also gives an error.
788    
789    15. If a forward reference was repeated with an upper limit of around 2000,
790        it caused the error "internal error: overran compiling workspace". The
791        maximum number of forward references (including repeats) was limited by the
792        internal workspace, and dependent on the LINK_SIZE. The code has been
793        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
794        the default depends on LINK_SIZE. There is a new upper limit (for safety)
795        of around 200,000 forward references. While doing this, I also speeded up
796        the filling in of repeated forward references.
797    
798    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
799        incorrectly expecting the subject to contain another "a" after the start.
800    
801    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
802        in the match, the SKIP should be ignored. This was not happening; instead
803        the SKIP was being treated as NOMATCH. For patterns such as
804        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
805        tested.
806    
807    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
808        now much more compatible with Perl, in particular in cases where the result
809        is a non-match for a non-anchored pattern. For example, if
810        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
811        "m", where previously it did not return a name. A side effect of this
812        change is that for partial matches, the last encountered mark name is
813        returned, as for non matches. A number of tests that were previously not
814        Perl-compatible have been moved into the Perl-compatible test files. The
815        refactoring has had the pleasing side effect of removing one argument from
816        the match() function, thus reducing its stack requirements.
817    
818    19. If the /S+ option was used in pcretest to study a pattern using JIT,
819        subsequent uses of /S (without +) incorrectly behaved like /S+.
820    
821    21. Retrieve executable code size support for the JIT compiler and fixing
822        some warnings.
823    
824    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
825        not work when the shorter character appeared right at the end of the
826        subject string.
827    
828    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
829        systems.
830    
831    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
832        output it when the /M option is used in pcretest.
833    
834    25. The CheckMan script was not being included in the distribution. Also, added
835        an explicit "perl" to run Perl scripts from the PrepareRelease script
836        because this is reportedly needed in Windows.
837    
838    26. If study data was being save in a file and studying had not found a set of
839        "starts with" bytes for the pattern, the data written to the file (though
840        never used) was taken from uninitialized memory and so caused valgrind to
841        complain.
842    
843    27. Updated RunTest.bat as provided by Sheri Pierce.
844    
845    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
846    
847    29. Computation of memory usage for the table of capturing group names was
848        giving an unnecessarily large value.
849    
850    
851    Version 8.20 21-Oct-2011
852    ------------------------
853    
854    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
855        a POSIX class. After further experiments with Perl, which convinced me that
856        Perl has bugs and confusions, a closing square bracket is no longer allowed
857        in a POSIX name. This bug also affected patterns with classes that started
858        with full stops.
859    
860    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
861        captured substring, but while checking the failing first alternative,
862        substring 1 is temporarily captured. If the output vector supplied to
863        pcre_exec() was not big enough for this capture, the yield of the function
864        was still zero ("insufficient space for captured substrings"). This cannot
865        be totally fixed without adding another stack variable, which seems a lot
866        of expense for a edge case. However, I have improved the situation in cases
867        such as /(a)(b)x|abc/ matched against "abc", where the return code
868        indicates that fewer than the maximum number of slots in the ovector have
869        been set.
870    
871    3.  Related to (2) above: when there are more back references in a pattern than
872        slots in the output vector, pcre_exec() uses temporary memory during
873        matching, and copies in the captures as far as possible afterwards. It was
874        using the entire output vector, but this conflicts with the specification
875        that only 2/3 is used for passing back captured substrings. Now it uses
876        only the first 2/3, for compatibility. This is, of course, another edge
877        case.
878    
879    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
880        main code base, and can be used by building with --enable-jit. When this is
881        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
882        runtime --no-jit option is given.
883    
884    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
885        ovector, the return from the function was zero, implying that there were
886        other matches that did not fit. The correct "exactly full" value is now
887        returned.
888    
889    6.  If a subpattern that was called recursively or as a subroutine contained
890        (*PRUNE) or any other control that caused it to give a non-standard return,
891        invalid errors such as "Error -26 (nested recursion at the same subject
892        position)" or even infinite loops could occur.
893    
894    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
895        computing the minimum length on reaching *ACCEPT, and so ended up with the
896        wrong value of 1 rather than 0. Further investigation indicates that
897        computing a minimum subject length in the presence of *ACCEPT is difficult
898        (think back references, subroutine calls), and so I have changed the code
899        so that no minimum is registered for a pattern that contains *ACCEPT.
900    
901    8.  If (*THEN) was present in the first (true) branch of a conditional group,
902        it was not handled as intended. [But see 16 below.]
903    
904    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
905        Sheri Pierce.
906    
907    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
908        the first byte in a match must be "a".
909    
910    11. Change 17 for 8.13 increased the recursion depth for patterns like
911        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
912        pattern contains any instances of (*THEN). If it does not, the old
913        optimizations are restored. It would be nice to do this on a per-group
914        basis, but at the moment that is not feasible.
915    
916    12. In some environments, the output of pcretest -C is CRLF terminated. This
917        broke RunTest's code that checks for the link size. A single white space
918        character after the value is now allowed for.
919    
920    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
921        For "fr", it uses the Windows-specific input and output files.
922    
923    14. If (*THEN) appeared in a group that was called recursively or as a
924        subroutine, it did not work as intended. [But see next item.]
925    
926    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
927        pattern fragments (but not containing any | characters). If A and B are
928        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
929        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
930        D. In other words, Perl considers parentheses that do not contain any |
931        characters to be part of a surrounding alternative, whereas PCRE was
932        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
933        differently. PCRE now behaves in the same way as Perl, except in the case
934        of subroutine/recursion calls such as (?1) which have in any case always
935        been different (but PCRE had them first :-).
936    
937    16. Related to 15 above: Perl does not treat the | in a conditional group as
938        creating alternatives. Such a group is treated in the same way as an
939        ordinary group without any | characters when processing (*THEN). PCRE has
940        been changed to match Perl's behaviour.
941    
942    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
943        RunGrepTest script failed.
944    
945    18. Change 22 for version 13 caused atomic groups to use more stack. This is
946        inevitable for groups that contain captures, but it can lead to a lot of
947        stack use in large patterns. The old behaviour has been restored for atomic
948        groups that do not contain any capturing parentheses.
949    
950    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
951        suppress the check for a minimum subject length at run time. (If it was
952        given to pcre_exec() or pcre_dfa_exec() it did work.)
953    
954    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
955        fail to work when decoding hex characters in data strings in EBCDIC
956        environments.
957    
958    21. It appears that in at least one Mac OS environment, the isxdigit() function
959        is implemented as a macro that evaluates to its argument more than once,
960        contravening the C 90 Standard (I haven't checked a later standard). There
961        was an instance in pcretest which caused it to go wrong when processing
962        \x{...} escapes in subject strings. The has been rewritten to avoid using
963        things like p++ in the argument of isxdigit().
964    
965    
966    Version 8.13 16-Aug-2011
967    ------------------------
968    
969    1.  The Unicode data tables have been updated to Unicode 6.0.0.
970    
971    2.  Two minor typos in pcre_internal.h have been fixed.
972    
973    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
974        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
975        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
976    
977    4.  There were a number of related bugs in the code for matching backrefences
978        caselessly in UTF-8 mode when codes for the characters concerned were
979        different numbers of bytes. For example, U+023A and U+2C65 are an upper
980        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
981        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
982        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
983        2-byte code at the end of the subject (it thought there wasn't enough data
984        left).
985    
986    5.  Comprehensive information about what went wrong is now returned by
987        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
988        as the output vector has at least 2 elements. The offset of the start of
989        the failing character and a reason code are placed in the vector.
990    
991    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
992        now returned is for the first byte of the failing character, instead of the
993        last byte inspected. This is an incompatible change, but I hope it is small
994        enough not to be a problem. It makes the returned offset consistent with
995        pcre_exec() and pcre_dfa_exec().
996    
997    7.  pcretest now gives a text phrase as well as the error number when
998        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
999        failure, the offset and reason code are output.
1000    
1001    8.  When \R was used with a maximizing quantifier it failed to skip backwards
1002        over a \r\n pair if the subsequent match failed. Instead, it just skipped
1003        back over a single character (\n). This seems wrong (because it treated the
1004        two characters as a single entity when going forwards), conflicts with the
1005        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
1006        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
1007        has been changed.
1008    
1009    9.  Some internal refactoring has changed the processing so that the handling
1010        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
1011        time (the PCRE_DOTALL option was changed this way some time ago: version
1012        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
1013        which was always a bit of a fudge. It also means that there is one less
1014        argument for the match() function, which reduces its stack requirements
1015        slightly. This change also fixes an incompatibility with Perl: the pattern
1016        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
1017    
1018    10. More internal refactoring has drastically reduced the number of recursive
1019        calls to match() for possessively repeated groups such as (abc)++ when
1020        using pcre_exec().
1021    
1022    11. While implementing 10, a number of bugs in the handling of groups were
1023        discovered and fixed:
1024    
1025        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
1026        (a|)*(?1) gave a compile-time internal error.
1027        ((a|)+)+  did not notice that the outer group could match an empty string.
1028        (^a|^)+   was not marked as anchored.
1029        (.*a|.*)+ was not marked as matching at start or after a newline.
1030    
1031    12. Yet more internal refactoring has removed another argument from the match()
1032        function. Special calls to this function are now indicated by setting a
1033        value in a variable in the "match data" data block.
1034    
1035    13. Be more explicit in pcre_study() instead of relying on "default" for
1036        opcodes that mean there is no starting character; this means that when new
1037        ones are added and accidentally left out of pcre_study(), testing should
1038        pick them up.
1039    
1040    14. The -s option of pcretest has been documented for ages as being an old
1041        synonym of -m (show memory usage). I have changed it to mean "force study
1042        for every regex", that is, assume /S for every regex. This is similar to -i
1043        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
1044        using it. It makes it easier to run collections of tests with and without
1045        study enabled, and thereby test pcre_study() more easily. All the standard
1046        tests are now run with and without -s (but some patterns can be marked as
1047        "never study" - see 20 below).
1048    
1049    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
1050        restoration of the capturing data to the outer values was not happening
1051        correctly.
1052    
1053    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
1054        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
1055        pattern had matched an empty string, and so incorrectly returned a no
1056        match.
1057    
1058    17. There was optimizing code for the last branch of non-capturing parentheses,
1059        and also for the obeyed branch of a conditional subexpression, which used
1060        tail recursion to cut down on stack usage. Unfortunately, now that there is
1061        the possibility of (*THEN) occurring in these branches, tail recursion is
1062        no longer possible because the return has to be checked for (*THEN). These
1063        two optimizations have therefore been removed. [But see 8.20/11 above.]
1064    
1065    18. If a pattern containing \R was studied, it was assumed that \R always
1066        matched two bytes, thus causing the minimum subject length to be
1067        incorrectly computed because \R can also match just one byte.
1068    
1069    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
1070        was incorrectly computed.
1071    
1072    20. If /S is present twice on a test pattern in pcretest input, it now
1073        *disables* studying, thereby overriding the use of -s on the command line
1074        (see 14 above). This is necessary for one or two tests to keep the output
1075        identical in both cases.
1076    
1077    21. When (*ACCEPT) was used in an assertion that matched an empty string and
1078        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
1079    
1080    22. When an atomic group that contained a capturing parenthesis was
1081        successfully matched, but the branch in which it appeared failed, the
1082        capturing was not being forgotten if a higher numbered group was later
1083        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
1084        group 1 to "a", when in fact it should be unset. This applied to multi-
1085        branched capturing and non-capturing groups, repeated or not, and also to
1086        positive assertions (capturing in negative assertions does not happen
1087        in PCRE) and also to nested atomic groups.
1088    
1089    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
1090        subject after a captured substring, to make it easier to tell which of a
1091        number of identical substrings has been captured.
1092    
1093    24. The way atomic groups are processed by pcre_exec() has been changed so that
1094        if they are repeated, backtracking one repetition now resets captured
1095        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
1096        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
1097        "aaa". Previously, it would have been "a". As part of this code
1098        refactoring, the way recursive calls are handled has also been changed.
1099    
1100    25. If an assertion condition captured any substrings, they were not passed
1101        back unless some other capturing happened later. For example, if
1102        (?(?=(a))a) was matched against "a", no capturing was returned.
1103    
1104    26. When studying a pattern that contained subroutine calls or assertions,
1105        the code for finding the minimum length of a possible match was handling
1106        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
1107        group 1 called group 2 while simultaneously a separate group 2 called group
1108        1). A stack overflow occurred in this case. I have fixed this by limiting
1109        the recursion depth to 10.
1110    
1111    27. Updated RunTest.bat in the distribution to the version supplied by Tom
1112        Fortmann. This supports explicit test numbers on the command line, and has
1113        argument validation and error reporting.
1114    
1115    28. An instance of \X with an unlimited repeat could fail if at any point the
1116        first character it looked at was a mark character.
1117    
1118    29. Some minor code refactoring concerning Unicode properties and scripts
1119        should reduce the stack requirement of match() slightly.
1120    
1121    30. Added the '=' option to pcretest to check the setting of unused capturing
1122        slots at the end of the pattern, which are documented as being -1, but are
1123        not included in the return count.
1124    
1125    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
1126        compiled something random. Now it gives a compile-time error (as does
1127        Perl).
1128    
1129    32. A *MARK encountered during the processing of a positive assertion is now
1130        recorded and passed back (compatible with Perl).
1131    
1132    33. If --only-matching or --colour was set on a pcregrep call whose pattern
1133        had alternative anchored branches, the search for a second match in a line
1134        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
1135        matched the line "0102" twice. The same bug affected patterns that started
1136        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
1137        twice.
1138    
1139    34. Previously, PCRE did not allow quantification of assertions. However, Perl
1140        does, and because of capturing effects, quantifying parenthesized
1141        assertions may at times be useful. Quantifiers are now allowed for
1142        parenthesized assertions.
1143    
1144    35. A minor code tidy in pcre_compile() when checking options for \R usage.
1145    
1146    36. \g was being checked for fancy things in a character class, when it should
1147        just be a literal "g".
1148    
1149    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
1150        appearance of a nested POSIX class supersedes an apparent external class.
1151        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1152        unescaped square brackets may also appear as part of class names. For
1153        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1154        more like Perl. (But see 8.20/1 above.)
1155    
1156    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1157        was because it thought it was \N{name}, which is not supported).
1158    
1159    39. Add minix to OS list not supporting the -S option in pcretest.
1160    
1161    40. PCRE tries to detect cases of infinite recursion at compile time, but it
1162        cannot analyze patterns in sufficient detail to catch mutual recursions
1163        such as ((?1))((?2)). There is now a runtime test that gives an error if a
1164        subgroup is called recursively as a subpattern for a second time at the
1165        same position in the subject string. In previous releases this might have
1166        been caught by the recursion limit, or it might have run out of stack.
1167    
1168    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
1169        happen only once. PCRE was, however incorrectly giving a compile time error
1170        "recursive call could loop indefinitely" because it cannot analyze the
1171        pattern in sufficient detail. The compile time test no longer happens when
1172        PCRE is compiling a conditional subpattern, but actual runaway loops are
1173        now caught at runtime (see 40 above).
1174    
1175    42. It seems that Perl allows any characters other than a closing parenthesis
1176        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
1177        has been changed to be the same.
1178    
1179    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
1180        as not to get warnings when autogen.sh is called. Also changed
1181        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
1182    
1183    44. To help people who use pcregrep to scan files containing exceedingly long
1184        lines, the following changes have been made:
1185    
1186        (a) The default value of the buffer size parameter has been increased from
1187            8K to 20K. (The actual buffer used is three times this size.)
1188    
1189        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1190            PCRE is built.
1191    
1192        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
1193            to be set at run time.
1194    
1195        (d) Numerical values in pcregrep options can be followed by K or M, for
1196            example --buffer-size=50K.
1197    
1198        (e) If a line being scanned overflows pcregrep's buffer, an error is now
1199            given and the return code is set to 2.
1200    
1201    45. Add a pointer to the latest mark to the callout data block.
1202    
1203    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
1204        partial match of an empty string instead of no match. This was specific to
1205        the use of ".".
1206    
1207    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1208        complete match instead of a partial match. This bug was dependent on both
1209        the PCRE_UTF8 and PCRE_DOTALL options being set.
1210    
1211    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1212        starting byte set, because \b was not being ignored.
1213    
1214    
1215    Version 8.12 15-Jan-2011
1216    ------------------------
1217    
1218    1.  Fixed some typos in the markup of the man pages, and wrote a script that
1219        checks for such things as part of the documentation building process.
1220    
1221    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
1222        --match-limit and --recursion-limit options (added for 8.11). In
1223        particular, this made one of the standard tests fail. (The integer value
1224        went into the wrong half of a long int.)
1225    
1226    3.  If the --colour option was given to pcregrep with -v (invert match), it
1227        did strange things, either producing crazy output, or crashing. It should,
1228        of course, ignore a request for colour when reporting lines that do not
1229        match.
1230    
1231    4.  Another pcregrep bug caused similar problems if --colour was specified with
1232        -M (multiline) and the pattern match finished with a line ending.
1233    
1234    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
1235        matched in multiline mode, the following line was shown as part of the
1236        match. This seems wrong, so I have changed it.
1237    
1238    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
1239        the check for further matches in the same line (so they could be coloured)
1240        to overrun the end of the current line. If another match was found, it was
1241        incorrectly shown (and then shown again when found in the next line).
1242    
1243    7.  If pcregrep was compiled under Windows, there was a reference to the
1244        function pcregrep_exit() before it was defined. I am assuming this was
1245        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
1246        reported by a user. I've moved the definition above the reference.
1247    
1248    
1249    Version 8.11 10-Dec-2010
1250    ------------------------
1251    
1252    1.  (*THEN) was not working properly if there were untried alternatives prior
1253        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
1254        backtracked to try for "b" instead of moving to the next alternative branch
1255        at the same level (in this case, to look for "c"). The Perl documentation
1256        is clear that when (*THEN) is backtracked onto, it goes to the "next
1257        alternative in the innermost enclosing group".
1258    
1259    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
1260        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
1261        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
1262        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
1263        (*THEN).
1264    
1265    3.  If \s appeared in a character class, it removed the VT character from
1266        the class, even if it had been included by some previous item, for example
1267        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
1268        of \s, but is part of the POSIX "space" class.)
1269    
1270    4.  A partial match never returns an empty string (because you can always
1271        match an empty string at the end of the subject); however the checking for
1272        an empty string was starting at the "start of match" point. This has been
1273        changed to the "earliest inspected character" point, because the returned
1274        data for a partial match starts at this character. This means that, for
1275        example, /(?<=abc)def/ gives a partial match for the subject "abc"
1276        (previously it gave "no match").
1277    
1278    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
1279        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
1280        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
1281        has an implication that the given string is incomplete (because a partial
1282        match is preferred over a full match). For this reason, these items now
1283        give a partial match in this situation. [Aside: previously, the one case
1284        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
1285        match rather than a full match, which was wrong by the old rules, but is
1286        now correct.]
1287    
1288    6.  There was a bug in the handling of #-introduced comments, recognized when
1289        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
1290        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
1291        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
1292        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
1293        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
1294        places in pcre_compile().
1295    
1296    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
1297        comments when looking ahead for named forward references to subpatterns,
1298        the only newline sequence it recognized was NL. It now handles newlines
1299        according to the set newline convention.
1300    
1301    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
1302        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
1303        cater for a lack of strerror(). These oversights have been fixed.
1304    
1305    9.  Added --match-limit and --recursion-limit to pcregrep.
1306    
1307    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
1308    
1309    11. When the -o option was used, pcregrep was setting a return code of 1, even
1310        when matches were found, and --line-buffered was not being honoured.
1311    
1312    12. Added an optional parentheses number to the -o and --only-matching options
1313        of pcregrep.
1314    
1315    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
1316        can match an empty string. The code to do it in pcretest and pcredemo
1317        needed fixing:
1318    
1319        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
1320            only one byte after an empty string match just before CRLF (this case
1321            just got forgotten; "any" and "anycrlf" were OK).
1322    
1323        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
1324            mode when an empty string match preceded an ASCII character followed by
1325            a non-ASCII character. (The code for advancing by one character rather
1326            than one byte was nonsense.)
1327    
1328        (c) The pcredemo.c sample program did not have any code at all to handle
1329            the cases when CRLF is a valid newline sequence.
1330    
1331    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
1332        as a starting offset was within the subject string. There is now a new
1333        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
1334        negative or greater than the length of the string. In order to test this,
1335        pcretest is extended to allow the setting of negative starting offsets.
1336    
1337    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
1338        starting offset points to the beginning of a UTF-8 character was
1339        unnecessarily clumsy. I tidied it up.
1340    
1341    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
1342        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
1343    
1344    17. Nobody had reported that the --include_dir option, which was added in
1345        release 7.7 should have been called --include-dir (hyphen, not underscore)
1346        for compatibility with GNU grep. I have changed it to --include-dir, but
1347        left --include_dir as an undocumented synonym, and the same for
1348        --exclude-dir, though that is not available in GNU grep, at least as of
1349        release 2.5.4.
1350    
1351    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
1352        characters from a string of bytes) have been redefined so as not to use
1353        loops, in order to improve performance in some environments. At the same
1354        time, I abstracted some of the common code into auxiliary macros to save
1355        repetition (this should not affect the compiled code).
1356    
1357    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
1358        compile-time error is now given if \c is not followed by an ASCII
1359        character, that is, a byte less than 128. (In EBCDIC mode, the code is
1360        different, and any byte value is allowed.)
1361    
1362    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
1363        START_OPTIMIZE option, which is now allowed at compile time - but just
1364        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
1365        to pcregrep and other applications that have no direct access to PCRE
1366        options. The new /Y option in pcretest sets this option when calling
1367        pcre_compile().
1368    
1369    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
1370        back references. Groups containing recursive back references were forced to
1371        be atomic by that change, but in the case of named groups, the amount of
1372        memory required was incorrectly computed, leading to "Failed: internal
1373        error: code overflow". This has been fixed.
1374    
1375    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
1376        pcretest.c, to avoid build problems in some Borland environments.
1377    
1378    
1379    Version 8.10 25-Jun-2010
1380    ------------------------
1381    
1382    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
1383        THEN.
1384    
1385    2.  (*ACCEPT) was not working when inside an atomic group.
1386    
1387    3.  Inside a character class, \B is treated as a literal by default, but
1388        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
1389        causes the error). The code is unchanged, but I tidied the documentation.
1390    
1391    4.  Inside a character class, PCRE always treated \R and \X as literals,
1392        whereas Perl faults them if its -w option is set. I have changed PCRE so
1393        that it faults them when PCRE_EXTRA is set.
1394    
1395    5.  Added support for \N, which always matches any character other than
1396        newline. (It is the same as "." when PCRE_DOTALL is not set.)
1397    
1398    6.  When compiling pcregrep with newer versions of gcc which may have
1399        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
1400        declared with attribute warn_unused_result" were given. Just casting the
1401        result to (void) does not stop the warnings; a more elaborate fudge is
1402        needed. I've used a macro to implement this.
1403    
1404    7.  Minor change to pcretest.c to avoid a compiler warning.
1405    
1406    8.  Added four artifical Unicode properties to help with an option to make
1407        \s etc use properties (see next item). The new properties are: Xan
1408        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
1409    
1410    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
1411        use Unicode properties. (*UCP) at the start of a pattern can be used to set
1412        this option. Modified pcretest to add /W to test this facility. Added
1413        REG_UCP to make it available via the POSIX interface.
1414    
1415    10. Added --line-buffered to pcregrep.
1416    
1417    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
1418        studied, and the match started with a letter with a code point greater than
1419        127 whose first byte was different to the first byte of the other case of
1420        the letter, the other case of this starting letter was not recognized
1421        (#976).
1422    
1423    12. If a pattern that was studied started with a repeated Unicode property
1424        test, for example, \p{Nd}+, there was the theoretical possibility of
1425        setting up an incorrect bitmap of starting bytes, but fortunately it could
1426        not have actually happened in practice until change 8 above was made (it
1427        added property types that matched character-matching opcodes).
1428    
1429    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
1430        possible starting bytes for non-anchored patterns.
1431    
1432    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
1433        \R, and also a number of cases that involve Unicode properties, both
1434        explicit and implicit when PCRE_UCP is set.
1435    
1436    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
1437        input, it could crash or give wrong results if characters with values
1438        greater than 0xc0 were present in the subject string. (Detail: it assumed
1439        UTF-8 input when processing these items.)
1440    
1441    16. Added a lot of (int) casts to avoid compiler warnings in systems where
1442        size_t is 64-bit (#991).
1443    
1444    17. Added a check for running out of memory when PCRE is compiled with
1445        --disable-stack-for-recursion (#990).
1446    
1447    18. If the last data line in a file for pcretest does not have a newline on
1448        the end, a newline was missing in the output.
1449    
1450    19. The default pcre_chartables.c file recognizes only ASCII characters (values
1451        less than 128) in its various bitmaps. However, there is a facility for
1452        generating tables according to the current locale when PCRE is compiled. It
1453        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
1454        characters, are recognized by isspace() and therefore were getting set in
1455        these tables, and indeed these tables seem to approximate to ISO 8859. This
1456        caused a problem in UTF-8 mode when pcre_study() was used to create a list
1457        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
1458        which of course cannot start UTF-8 characters. I have changed the code so
1459        that only real ASCII characters (less than 128) and the correct starting
1460        bytes for UTF-8 encodings are set for characters greater than 127 when in
1461        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
1462        altogether.)
1463    
1464    20. Added the /T option to pcretest so as to be able to run tests with non-
1465        standard character tables, thus making it possible to include the tests
1466        used for 19 above in the standard set of tests.
1467    
1468    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
1469        reference to a subpattern the other side of a comment that contains an
1470        opening parenthesis caused either an internal compiling error, or a
1471        reference to the wrong subpattern.
1472    
1473    
1474    Version 8.02 19-Mar-2010
1475  ------------------------  ------------------------
1476    
1477  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.
1478    
1479  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
1480      configured.      configured.
1481    
1482  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
1483      original author of that file, following a query about its status.      original author of that file, following a query about its status.
1484    
1485  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
1486      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.
1487    
1488  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
1489      quantifier applied to a forward-referencing subroutine call, could compile      quantifier applied to a forward-referencing subroutine call, could compile
1490      incorrect code or give the error "internal error: previously-checked      incorrect code or give the error "internal error: previously-checked
1491      referenced subpattern not found".      referenced subpattern not found".
1492    
1493  6.  Both MS Visual Studio and Symbian OS have problems with initializing  6.  Both MS Visual Studio and Symbian OS have problems with initializing
1494      variables to point to external functions. For these systems, therefore,      variables to point to external functions. For these systems, therefore,
1495      pcre_malloc etc. are now initialized to local functions that call the      pcre_malloc etc. are now initialized to local functions that call the
1496      relevant global functions.      relevant global functions.
1497    
1498  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
1499      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.
1500      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
1501      the lengths are correct (equal to the number of opcodes).      the lengths are correct (equal to the number of opcodes).
1502    
1503  8.  Following on from 7, I added a similar kludge to check the length of the  8.  Following on from 7, I added a similar kludge to check the length of the
1504      eint vector in pcreposix.c.      eint vector in pcreposix.c.
1505    
1506  9.  Error texts for pcre_compile() are held as one long string to avoid too  9.  Error texts for pcre_compile() are held as one long string to avoid too
1507      much relocation at load time. To find a text, the string is searched,      much relocation at load time. To find a text, the string is searched,
1508      counting zeros. There was no check for running off the end of the string,      counting zeros. There was no check for running off the end of the string,
1509      which could happen if a new error number was added without updating the      which could happen if a new error number was added without updating the
1510      string.      string.
1511    
1512  10. \K gave a compile-time error if it appeared in a lookbehind assersion.  10. \K gave a compile-time error if it appeared in a lookbehind assersion.
1513    
1514  11. \K was not working if it appeared in an atomic group or in a group that  11. \K was not working if it appeared in an atomic group or in a group that
1515      was called as a "subroutine", or in an assertion. Perl 5.11 documents that      was called as a "subroutine", or in an assertion. Perl 5.11 documents that
1516      \K is "not well defined" if used in an assertion. PCRE now accepts it if      \K is "not well defined" if used in an assertion. PCRE now accepts it if
1517      the assertion is positive, but not if it is negative.      the assertion is positive, but not if it is negative.
1518    
1519  12. Change 11 fortuitously reduced the size of the stack frame used in the  12. Change 11 fortuitously reduced the size of the stack frame used in the
1520      "match()" function of pcre_exec.c by one pointer. Forthcoming      "match()" function of pcre_exec.c by one pointer. Forthcoming
1521      implementation of support for (*MARK) will need an extra pointer on the      implementation of support for (*MARK) will need an extra pointer on the
1522      stack; I have reserved it now, so that the stack frame size does not      stack; I have reserved it now, so that the stack frame size does not
1523      decrease.      decrease.
1524    
1525  13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other  13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
1526      item in branch that calls a recursion is a subroutine call - as in the      item in branch that calls a recursion is a subroutine call - as in the
1527      second branch in the above example - was incorrectly given the compile-      second branch in the above example - was incorrectly given the compile-
1528      time error "recursive call could loop indefinitely" because pcre_compile()      time error "recursive call could loop indefinitely" because pcre_compile()
1529      was not correctly checking the subroutine for matching a non-empty string.      was not correctly checking the subroutine for matching a non-empty string.
1530    
1531  14. The checks for overrunning compiling workspace could trigger after an  14. The checks for overrunning compiling workspace could trigger after an
1532      overrun had occurred. This is a "should never occur" error, but it can be      overrun had occurred. This is a "should never occur" error, but it can be
1533      triggered by pathological patterns such as hundreds of nested parentheses.      triggered by pathological patterns such as hundreds of nested parentheses.
1534      The checks now trigger 100 bytes before the end of the workspace.      The checks now trigger 100 bytes before the end of the workspace.
1535    
1536    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
1537    
1538    
1539  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010
# Line 390  Version 7.9 11-Apr-09 Line 1862  Version 7.9 11-Apr-09
1862  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
1863      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
1864      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1865      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1866        8.33.]
1867    
1868  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
1869      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 633  Version 7.7 07-May-08 Line 2106  Version 7.7 07-May-08
2106      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2107      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2108      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2109      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2110      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2111      was subsequently set up correctly.)      was subsequently set up correctly.)
2112    

Legend:
Removed from v.505  
changed lines
  Added in v.1405

  ViewVC Help
Powered by ViewVC 1.1.5