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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.637  
changed lines
  Added in v.1490

  ViewVC Help
Powered by ViewVC 1.1.5