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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.360  
changed lines
  Added in v.1408

  ViewVC Help
Powered by ViewVC 1.1.5