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

Diff of /code/trunk/ChangeLog

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

revision 974 by zherczeg, Sat Jun 2 05:56:58 2012 UTC revision 1364 by ph10, Sat Oct 5 15:45:11 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.31  Version 8.34 xx-xxxx-201x
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_POSSESSIFY is added for testing purposes, and the -O and /O
89        options in pcretest are provided to set it.
90    
91    18. The character VT has been added to the set of characters that match \s and
92        are generally treated as white space, following this same change in Perl
93        5.18. There is now no difference between "Perl space" and "POSIX space".
94    
95    
96    Version 8.33 28-May-2013
97    ------------------------
98    
99    1.  Added 'U' to some constants that are compared to unsigned integers, to
100        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
101        variables that are added to signed variables, to ensure the result is
102        signed and can be negated.
103    
104    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
105        CMake config files.
106    
107    3.  Revise the creation of config.h.generic so that all boolean macros are
108        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
109        overriding via -D on the command line possible.
110    
111    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
112        to unsigned int is reported to make a quite noticeable speed difference in
113        a specific Windows environment. Testing on Linux did also appear to show
114        some benefit (and it is clearly not harmful). Also fixed the definition of
115        Xop which should be unsigned.
116    
117    5.  Related to (4), changing the definition of the intermediate variable cc
118        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
119        improvements.
120    
121    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
122        unnecessary spaces.
123    
124    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
125        and later.
126    
127    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
128    
129    9.  Optimizing fast_forward_start_bits in JIT.
130    
131    10. Adding support for callouts in JIT, and fixing some issues revealed
132        during this work. Namely:
133    
134        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
135    
136        (b) Minimum length was not checked before the matching is started.
137    
138    11. The value of capture_last that is passed to callouts was incorrect in some
139        cases when there was a capture on one path that was subsequently abandoned
140        after a backtrack. Also, the capture_last value is now reset after a
141        recursion, since all captures are also reset in this case.
142    
143    12. The interpreter no longer returns the "too many substrings" error in the
144        case when an overflowing capture is in a branch that is subsequently
145        abandoned after a backtrack.
146    
147    13. In the pathological case when an offset vector of size 2 is used, pcretest
148        now prints out the matched string after a yield of 0 or 1.
149    
150    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
151        Only supported by the JIT compiler at the moment.
152    
153    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
154    
155    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
156        offset of the starting point of the matching process, provided the offsets
157        vector is large enough.
158    
159    17. The \A escape now records a lookbehind value of 1, though its execution
160        does not actually inspect the previous character. This is to ensure that,
161        in partial multi-segment matching, at least one character from the old
162        segment is retained when a new segment is processed. Otherwise, if there
163        are no lookbehinds in the pattern, \A might match incorrectly at the start
164        of a new segment.
165    
166    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
167    
168    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
169        gives some modest performance improvement in 8-bit mode.
170    
171    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
172        be expressed in certain programming languages using Universal Character
173        Names.
174    
175    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
176        which points out that "non characters" are not "characters that may not
177        appear in Unicode strings" but rather "characters that are reserved for
178        internal use and have only local meaning".
179    
180    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
181        there was a conditional group that depended on an assertion, if the
182        assertion was false, the callout that immediately followed the alternation
183        in the condition was skipped when pcre_exec() was used for matching.
184    
185    23. Allow an explicit callout to be inserted before an assertion that is the
186        condition for a conditional group, for compatibility with automatic
187        callouts, which always insert a callout at this point.
188    
189    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
190        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
191    
192    25. (*PRUNE) is now supported by the JIT compiler.
193    
194    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
195    
196    27. Fix the case where there are two or more SKIPs with arguments that may be
197        ignored.
198    
199    28. (*SKIP) is now supported by the JIT compiler.
200    
201    29. (*THEN) is now supported by the JIT compiler.
202    
203    30. Update RunTest with additional test selector options.
204    
205    31. The way PCRE handles backtracking verbs has been changed in two ways.
206    
207        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
208        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
209        backtracking. In some cases this makes it more Perl-compatible, but Perl's
210        rather obscure rules do not always do the same thing.
211    
212        (2) Previously, backtracking verbs were confined within assertions. This is
213        no longer the case for positive assertions, except for (*ACCEPT). Again,
214        this sometimes improves Perl compatibility, and sometimes does not.
215    
216    32. A number of tests that were in test 2 because Perl did things differently
217        have been moved to test 1, because either Perl or PCRE has changed, and
218        these tests are now compatible.
219    
220    32. Backtracking control verbs are now handled in the same way in JIT and
221        interpreter.
222    
223    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
224        contained a forward subroutine reference caused a compile error.
225    
226    34. Auto-detect and optimize limited repetitions in JIT.
227    
228    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
229        blocking (*UTF) etc.
230    
231    36. In the interpreter, maximizing pattern repetitions for characters and
232        character types now use tail recursion, which reduces stack usage.
233    
234    37. The value of the max lookbehind was not correctly preserved if a compiled
235        and saved regex was reloaded on a host of different endianness.
236    
237    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
238        of the compiled pattern block, expand the flags field from 16 to 32 bits
239        because it was almost full.
240    
241    39. Try madvise first before posix_madvise.
242    
243    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
244        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
245        original change locked out all matches of empty strings. This has been
246        changed so that one match of an empty string per line is recognized.
247        Subsequent searches on the same line (for colouring or for --only-matching,
248        for example) do not recognize empty strings.
249    
250    41. Applied a user patch to fix a number of spelling mistakes in comments.
251    
252    42. Data lines longer than 65536 caused pcretest to crash.
253    
254    43. Clarified the data type for length and startoffset arguments for pcre_exec
255        and pcre_dfa_exec in the function-specific man pages, where they were
256        explicitly stated to be in bytes, never having been updated. I also added
257        some clarification to the pcreapi man page.
258    
259    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
260        a segmentation fault.
261    
262    
263    Version 8.32 30-November-2012
264  -----------------------------  -----------------------------
265    
266    1.  Improved JIT compiler optimizations for first character search and single
267        character iterators.
268    
269    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
270        Patch by Daniel Richard G.
271    
272    3.  Single character iterator optimizations in the JIT compiler.
273    
274    4.  Improved JIT compiler optimizations for character ranges.
275    
276    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
277        Reported by Giuseppe D'Angelo.
278    
279    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
280        of a line, was being set incorrectly in cases where .* appeared inside
281        atomic brackets at the start of a pattern, or where there was a subsequent
282        *PRUNE or *SKIP.
283    
284    7.  Improved instruction cache flush for POWER/PowerPC.
285        Patch by Daniel Richard G.
286    
287    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
288        grep:
289    
290        (a) There is now no limit to the number of patterns to be matched.
291    
292        (b) An error is given if a pattern is too long.
293    
294        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
295            are now supported.
296    
297        (d) --exclude-from and --include-from (multiple use) have been added.
298    
299        (e) Exclusions and inclusions now apply to all files and directories, not
300            just to those obtained from scanning a directory recursively.
301    
302        (f) Multiple uses of -f and --file-list are now supported.
303    
304        (g) In a Windows environment, the default for -d has been changed from
305            "read" (the GNU grep default) to "skip", because otherwise the presence
306            of a directory in the file list provokes an error.
307    
308        (h) The documentation has been revised and clarified in places.
309    
310    9.  Improve the matching speed of capturing brackets.
311    
312    10. Changed the meaning of \X so that it now matches a Unicode extended
313        grapheme cluster.
314    
315    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
316        out POSIX threads when JIT support is configured.
317    
318    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
319    
320    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
321        structure could go wrong in environments where size_t is not the same size
322        as int.
323    
324    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
325        set.
326    
327    15. The EBCDIC support had decayed; later updates to the code had included
328        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
329        general tidy up of EBCDIC-related issues, and the documentation was also
330        not quite right. There is now a test that can be run on ASCII systems to
331        check some of the EBCDIC-related things (but is it not a full test).
332    
333    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
334        in a small tidy to the code.
335    
336    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
337    
338    18. If the --only-matching (-o) option in pcregrep is specified multiple
339        times, each one causes appropriate output. For example, -o1 -o2 outputs the
340        substrings matched by the 1st and 2nd capturing parentheses. A separating
341        string can be specified by --om-separator (default empty).
342    
343    19. Improving the first n character searches.
344    
345    20. Turn case lists for horizontal and vertical white space into macros so that
346        they are defined only once.
347    
348    21. This set of changes together give more compatible Unicode case-folding
349        behaviour for characters that have more than one other case when UCP
350        support is available.
351    
352        (a) The Unicode property table now has offsets into a new table of sets of
353            three or more characters that are case-equivalent. The MultiStage2.py
354            script that generates these tables (the pcre_ucd.c file) now scans
355            CaseFolding.txt instead of UnicodeData.txt for character case
356            information.
357    
358        (b) The code for adding characters or ranges of characters to a character
359            class has been abstracted into a generalized function that also handles
360            case-independence. In UTF-mode with UCP support, this uses the new data
361            to handle characters with more than one other case.
362    
363        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
364            whose other case is greater than 256 are now correctly matched
365            caselessly. Previously, the high codepoint matched the low one, but not
366            vice versa.
367    
368        (d) The processing of \h, \H, \v, and \ in character classes now makes use
369            of the new class addition function, using character lists defined as
370            macros alongside the case definitions of 20 above.
371    
372        (e) Caseless back references now work with characters that have more than
373            one other case.
374    
375        (f) General caseless matching of characters with more than one other case
376            is supported.
377    
378    22. Unicode character properties were updated from Unicode 6.2.0
379    
380    23. Improved CMake support under Windows. Patch by Daniel Richard G.
381    
382    24. Add support for 32-bit character strings, and UTF-32
383    
384    25. Major JIT compiler update (code refactoring and bugfixing).
385        Experimental Sparc 32 support is added.
386    
387    26. Applied a modified version of Daniel Richard G's patch to create
388        pcre.h.generic and config.h.generic by "make" instead of in the
389        PrepareRelease script.
390    
391    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
392        pcre_compile.c when checking for a zero character.
393    
394    28. Introducing a native interface for JIT. Through this interface, the compiled
395        machine code can be directly executed. The purpose of this interface is to
396        provide fast pattern matching, so several sanity checks are not performed.
397        However, feature tests are still performed. The new interface provides
398        1.4x speedup compared to the old one.
399    
400    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
401        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
402        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
403    
404    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
405        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
406        the "old" RFC 2279). Instead, it ended up passing a negative length to
407        pcre_exec().
408    
409    31. Add support for GCC's visibility feature to hide internal functions.
410    
411    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
412        "unknown -C option" after outputting 0 or 1.
413    
414    33. There is now support for generating a code coverage report for the test
415        suite in environments where gcc is the compiler and lcov is installed. This
416        is mainly for the benefit of the developers.
417    
418    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
419        unaddressable using valgrind annotations, allowing valgrind to detect
420        invalid memory accesses. This is mainly for the benefit of the developers.
421    
422    25. (*UTF) can now be used to start a pattern in any of the three libraries.
423    
424    26. Give configure error if --enable-cpp but no C++ compiler found.
425    
426    
427    Version 8.31 06-July-2012
428    -------------------------
429    
430  1.  Fixing a wrong JIT test case and some compiler warnings.  1.  Fixing a wrong JIT test case and some compiler warnings.
431    
432  2.  Removed a bashism from the RunTest script.  2.  Removed a bashism from the RunTest script.
# Line 95  Version 8.31 Line 518  Version 8.31
518      \w+ when the character tables indicated that \x{c4} was a word character.      \w+ when the character tables indicated that \x{c4} was a word character.
519      There were several related cases, all because the tests for doing a table      There were several related cases, all because the tests for doing a table
520      lookup were testing for characters less than 127 instead of 255.      lookup were testing for characters less than 127 instead of 255.
521    
522  27. If a pattern contains capturing parentheses that are not used in a match,  27. If a pattern contains capturing parentheses that are not used in a match,
523      their slots in the ovector are set to -1. For those that are higher than      their slots in the ovector are set to -1. For those that are higher than
524      any matched groups, this happens at the end of processing. In the case when      any matched groups, this happens at the end of processing. In the case when
525      there were back references that the ovector was too small to contain      there were back references that the ovector was too small to contain
526      (causing temporary malloc'd memory to be used during matching), and the      (causing temporary malloc'd memory to be used during matching), and the
527      highest capturing number was not used, memory off the end of the ovector      highest capturing number was not used, memory off the end of the ovector
528      was incorrectly being set to -1. (It was using the size of the temporary      was incorrectly being set to -1. (It was using the size of the temporary
529      memory instead of the true size.)      memory instead of the true size.)
530    
531  28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an  28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
532      ovector size, it uses memory at the end of the block that it has got.      ovector size, it uses memory at the end of the block that it has got.
533    
534  29. Check for an overlong MARK name and give an error at compile time. The  29. Check for an overlong MARK name and give an error at compile time. The
535      limit is 255 for the 8-bit library and 65535 for the 16-bit library.      limit is 255 for the 8-bit library and 65535 for the 16-bit library.
536    
537  30. JIT compiler update.  30. JIT compiler update.
# Line 120  Version 8.31 Line 543  Version 8.31
543    
544  33. Variable renamings in the PCRE-JIT compiler. No functionality change.  33. Variable renamings in the PCRE-JIT compiler. No functionality change.
545    
546  34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of  34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
547      SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)      SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
548      was enabled.      was enabled.
549    
550  35. Improve JIT code generation for greedy plus quantifier.  35. Improve JIT code generation for greedy plus quantifier.
551    
552    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
553        1 to "aa" instead of to an empty string. The bug affected repeated groups
554        that could potentially match an empty string.
555    
556    37. Optimizing single character iterators in JIT.
557    
558    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
559        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
560        codepoints that are too big for the mode are faulted, and in a UTF mode,
561        disallowed codepoints are also faulted.
562    
563    39. If PCRE was compiled with UTF support, in three places in the DFA
564        matcher there was code that should only have been obeyed in UTF mode, but
565        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
566        processing when bytes with values greater than 127 were present. In 16-bit
567        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
568        both cases the values are those that cannot be the first data item in a UTF
569        character. The three items that might have provoked this were recursions,
570        possessively repeated groups, and atomic groups.
571    
572    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
573        and pcregrep, because some OS require shared objects to be explicitly
574        passed to ld, causing the link step to fail if they are not.
575    
576    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
577        mode, patterns that started with \h* or \R* might be incorrectly matched.
578    
579    
580  Version 8.30 04-February-2012  Version 8.30 04-February-2012
581  -----------------------------  -----------------------------
# Line 1317  Version 7.9 11-Apr-09 Line 1767  Version 7.9 11-Apr-09
1767  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
1768      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
1769      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1770      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1771        8.33.]
1772    
1773  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
1774      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 1560  Version 7.7 07-May-08 Line 2011  Version 7.7 07-May-08
2011      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2012      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2013      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2014      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2015      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2016      was subsequently set up correctly.)      was subsequently set up correctly.)
2017    

Legend:
Removed from v.974  
changed lines
  Added in v.1364

  ViewVC Help
Powered by ViewVC 1.1.5