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

Diff of /code/trunk/ChangeLog

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

revision 746 by ph10, Tue Nov 15 15:07:02 2011 UTC revision 1248 by ph10, Wed Feb 13 17:36:38 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.21  Version 8.33 xx-xxxx-201x
5  ------------  -------------------------
6    
7    1.  Added 'U' to some constants that are compared to unsigned integers, to
8        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
9        variables that are added to signed variables, to ensure the result is
10        signed and can be negated.
11    
12    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
13        CMake config files.
14    
15    3.  Revise the creation of config.h.generic so that all boolean macros are
16        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
17        overriding via -D on the command line possible.
18    
19    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
20        to unsigned int is reported to make a quite noticeable speed difference in
21        a specific Windows environment. Testing on Linux did also appear to show
22        some benefit (and it is clearly not harmful). Also fixed the definition of
23        Xop which should be unsigned.
24    
25    5.  Related to (4), changing the definition of the intermediate variable cc
26        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
27        improvements.
28    
29    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
30        unnecessary spaces.
31    
32    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
33        and later.
34    
35    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
36    
37    9.  Optimizing fast_forward_start_bits in JIT.
38    
39    10. Adding experimental support for callouts in JIT, and fixing some
40        issues revealed during this work. Namely:
41    
42        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
43    
44        (b) Minimum length was not checked before the matching is started.
45    
46        WARNING: Callouts are not release ready! <- this line needs to be removed when it is.
47    
48    11. The value of capture_last that is passed to callouts was incorrect in some
49        cases when there was a capture on one path that was subsequently abandoned
50        after a backtrack. Also, the capture_last value is now reset after a
51        recursion, since all captures are also reset in this case.
52    
53    12. The interpreter no longer returns the "too many substrings" error in the
54        case when an overflowing capture is in a branch that is subsequently
55        abandoned after a backtrack.
56    
57    13. In the pathological case when an offset vector of size 2 is used, pcretest
58        now prints out the matched string after a yield of 0 or 1.
59    
60    
61    Version 8.32 30-November-2012
62    -----------------------------
63    
64    1.  Improved JIT compiler optimizations for first character search and single
65        character iterators.
66    
67    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
68        Patch by Daniel Richard G.
69    
70    3.  Single character iterator optimizations in the JIT compiler.
71    
72    4.  Improved JIT compiler optimizations for character ranges.
73    
74    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
75        Reported by Giuseppe D'Angelo.
76    
77    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
78        of a line, was being set incorrectly in cases where .* appeared inside
79        atomic brackets at the start of a pattern, or where there was a subsequent
80        *PRUNE or *SKIP.
81    
82    7.  Improved instruction cache flush for POWER/PowerPC.
83        Patch by Daniel Richard G.
84    
85    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
86        grep:
87    
88        (a) There is now no limit to the number of patterns to be matched.
89    
90        (b) An error is given if a pattern is too long.
91    
92        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
93            are now supported.
94    
95        (d) --exclude-from and --include-from (multiple use) have been added.
96    
97        (e) Exclusions and inclusions now apply to all files and directories, not
98            just to those obtained from scanning a directory recursively.
99    
100        (f) Multiple uses of -f and --file-list are now supported.
101    
102        (g) In a Windows environment, the default for -d has been changed from
103            "read" (the GNU grep default) to "skip", because otherwise the presence
104            of a directory in the file list provokes an error.
105    
106        (h) The documentation has been revised and clarified in places.
107    
108    9.  Improve the matching speed of capturing brackets.
109    
110    10. Changed the meaning of \X so that it now matches a Unicode extended
111        grapheme cluster.
112    
113    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
114        out POSIX threads when JIT support is configured.
115    
116    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
117    
118    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
119        structure could go wrong in environments where size_t is not the same size
120        as int.
121    
122    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
123        set.
124    
125    15. The EBCDIC support had decayed; later updates to the code had included
126        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
127        general tidy up of EBCDIC-related issues, and the documentation was also
128        not quite right. There is now a test that can be run on ASCII systems to
129        check some of the EBCDIC-related things (but is it not a full test).
130    
131    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
132        in a small tidy to the code.
133    
134    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
135    
136    18. If the --only-matching (-o) option in pcregrep is specified multiple
137        times, each one causes appropriate output. For example, -o1 -o2 outputs the
138        substrings matched by the 1st and 2nd capturing parentheses. A separating
139        string can be specified by --om-separator (default empty).
140    
141    19. Improving the first n character searches.
142    
143    20. Turn case lists for horizontal and vertical white space into macros so that
144        they are defined only once.
145    
146    21. This set of changes together give more compatible Unicode case-folding
147        behaviour for characters that have more than one other case when UCP
148        support is available.
149    
150        (a) The Unicode property table now has offsets into a new table of sets of
151            three or more characters that are case-equivalent. The MultiStage2.py
152            script that generates these tables (the pcre_ucd.c file) now scans
153            CaseFolding.txt instead of UnicodeData.txt for character case
154            information.
155    
156        (b) The code for adding characters or ranges of characters to a character
157            class has been abstracted into a generalized function that also handles
158            case-independence. In UTF-mode with UCP support, this uses the new data
159            to handle characters with more than one other case.
160    
161        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
162            whose other case is greater than 256 are now correctly matched
163            caselessly. Previously, the high codepoint matched the low one, but not
164            vice versa.
165    
166        (d) The processing of \h, \H, \v, and \ in character classes now makes use
167            of the new class addition function, using character lists defined as
168            macros alongside the case definitions of 20 above.
169    
170        (e) Caseless back references now work with characters that have more than
171            one other case.
172    
173        (f) General caseless matching of characters with more than one other case
174            is supported.
175    
176    22. Unicode character properties were updated from Unicode 6.2.0
177    
178    23. Improved CMake support under Windows. Patch by Daniel Richard G.
179    
180    24. Add support for 32-bit character strings, and UTF-32
181    
182    25. Major JIT compiler update (code refactoring and bugfixing).
183        Experimental Sparc 32 support is added.
184    
185    26. Applied a modified version of Daniel Richard G's patch to create
186        pcre.h.generic and config.h.generic by "make" instead of in the
187        PrepareRelease script.
188    
189    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
190        pcre_compile.c when checking for a zero character.
191    
192    28. Introducing a native interface for JIT. Through this interface, the compiled
193        machine code can be directly executed. The purpose of this interface is to
194        provide fast pattern matching, so several sanity checks are not performed.
195        However, feature tests are still performed. The new interface provides
196        1.4x speedup compared to the old one.
197    
198    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
199        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
200        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
201    
202    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
203        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
204        the "old" RFC 2279). Instead, it ended up passing a negative length to
205        pcre_exec().
206    
207    31. Add support for GCC's visibility feature to hide internal functions.
208    
209    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
210        "unknown -C option" after outputting 0 or 1.
211    
212    33. There is now support for generating a code coverage report for the test
213        suite in environments where gcc is the compiler and lcov is installed. This
214        is mainly for the benefit of the developers.
215    
216    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
217        unaddressable using valgrind annotations, allowing valgrind to detect
218        invalid memory accesses. This is mainly for the benefit of the developers.
219    
220    25. (*UTF) can now be used to start a pattern in any of the three libraries.
221    
222    26. Give configure error if --enable-cpp but no C++ compiler found.
223    
224    
225    Version 8.31 06-July-2012
226    -------------------------
227    
228    1.  Fixing a wrong JIT test case and some compiler warnings.
229    
230    2.  Removed a bashism from the RunTest script.
231    
232    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
233        to unsigned type, result still unsigned" that was given by an MS compiler
234        on encountering the code "-sizeof(xxx)".
235    
236    4.  Partial matching support is added to the JIT compiler.
237    
238    5.  Fixed several bugs concerned with partial matching of items that consist
239        of more than one character:
240    
241        (a) /^(..)\1/ did not partially match "aba" because checking references was
242            done on an "all or nothing" basis. This also applied to repeated
243            references.
244    
245        (b) \R did not give a hard partial match if \r was found at the end of the
246            subject.
247    
248        (c) \X did not give a hard partial match after matching one or more
249            characters at the end of the subject.
250    
251        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
252            a partial match for the string "\r".
253    
254        (e) When newline was set to CRLF, the metacharacter "." did not recognize
255            a partial match for a CR character at the end of the subject string.
256    
257    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
258        running pcretest, the text "(JIT)" added to the output whenever JIT is
259        actually used to run the match.
260    
261    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
262        or /S+[+] with a digit between 1 and 7.
263    
264    8.  OP_NOT now supports any UTF character not just single-byte ones.
265    
266    9.  (*MARK) control verb is now supported by the JIT compiler.
267    
268    10. The command "./RunTest list" lists the available tests without actually
269        running any of them. (Because I keep forgetting what they all are.)
270    
271    11. Add PCRE_INFO_MAXLOOKBEHIND.
272    
273    12. Applied a (slightly modified) user-supplied patch that improves performance
274        when the heap is used for recursion (compiled with --disable-stack-for-
275        recursion). Instead of malloc and free for each heap frame each time a
276        logical recursion happens, frames are retained on a chain and re-used where
277        possible. This sometimes gives as much as 30% improvement.
278    
279    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
280        call.
281    
282    14. As documented, (*COMMIT) is now confined to within a positive assertion.
283    
284    15. It is now possible to link pcretest with libedit as an alternative to
285        libreadline.
286    
287    16. (*COMMIT) control verb is now supported by the JIT compiler.
288    
289    17. The Unicode data tables have been updated to Unicode 6.1.0.
290    
291    18. Added --file-list option to pcregrep.
292    
293    19. Added binary file support to pcregrep, including the -a, --binary-files,
294        -I, and --text options.
295    
296    20. The madvise function is renamed for posix_madvise for QNX compatibility
297        reasons. Fixed by Giuseppe D'Angelo.
298    
299    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
300    
301    22. Changed the option for creating symbolic links for 16-bit man pages from
302        -s to -sf so that re-installing does not cause issues.
303    
304    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
305    
306    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
307        matches in certain environments (the workspace was not being correctly
308        retained). Also added to pcre_dfa_exec() a simple plausibility check on
309        some of the workspace data at the beginning of a restart.
310    
311    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
312        was not doing so when it should - probably a typo introduced by SVN 528
313        (change 8.10/14).
314    
315    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
316        \w+ when the character tables indicated that \x{c4} was a word character.
317        There were several related cases, all because the tests for doing a table
318        lookup were testing for characters less than 127 instead of 255.
319    
320    27. If a pattern contains capturing parentheses that are not used in a match,
321        their slots in the ovector are set to -1. For those that are higher than
322        any matched groups, this happens at the end of processing. In the case when
323        there were back references that the ovector was too small to contain
324        (causing temporary malloc'd memory to be used during matching), and the
325        highest capturing number was not used, memory off the end of the ovector
326        was incorrectly being set to -1. (It was using the size of the temporary
327        memory instead of the true size.)
328    
329    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
330        ovector size, it uses memory at the end of the block that it has got.
331    
332    29. Check for an overlong MARK name and give an error at compile time. The
333        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
334    
335    30. JIT compiler update.
336    
337    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
338        Rill for the patch.
339    
340    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
341    
342    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
343    
344    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
345        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
346        was enabled.
347    
348    35. Improve JIT code generation for greedy plus quantifier.
349    
350    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
351        1 to "aa" instead of to an empty string. The bug affected repeated groups
352        that could potentially match an empty string.
353    
354    37. Optimizing single character iterators in JIT.
355    
356    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
357        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
358        codepoints that are too big for the mode are faulted, and in a UTF mode,
359        disallowed codepoints are also faulted.
360    
361    39. If PCRE was compiled with UTF support, in three places in the DFA
362        matcher there was code that should only have been obeyed in UTF mode, but
363        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
364        processing when bytes with values greater than 127 were present. In 16-bit
365        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
366        both cases the values are those that cannot be the first data item in a UTF
367        character. The three items that might have provoked this were recursions,
368        possessively repeated groups, and atomic groups.
369    
370    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
371        and pcregrep, because some OS require shared objects to be explicitly
372        passed to ld, causing the link step to fail if they are not.
373    
374    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
375        mode, patterns that started with \h* or \R* might be incorrectly matched.
376    
377    
378    Version 8.30 04-February-2012
379    -----------------------------
380    
381    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
382        name is defined in ctype.h.
383    
384    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
385        only in quite long subpatterns.
386    
387    3.  Removed the function pcre_info(), which has been obsolete and deprecated
388        since it was replaced by pcre_fullinfo() in February 2000.
389    
390    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
391        match a (*MARK), and the match failed at the start of the subject, a
392        reference to memory before the start of the subject could occur. This bug
393        was introduced by fix 17 of release 8.21.
394    
395    5.  A reference to an unset group with zero minimum repetition was giving
396        totally wrong answers (in non-JavaScript-compatibility mode). For example,
397        /(another)?(\1?)test/ matched against "hello world test". This bug was
398        introduced in release 8.13.
399    
400    6.  Add support for 16-bit character strings (a large amount of work involving
401        many changes and refactorings).
402    
403    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
404        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
405        from a file.
406    
407    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
408        rounding is not applied in this particular case).
409    
410    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
411        if they appear, or are escaped, in patterns.
412    
413    10. Get rid of a number of -Wunused-but-set-variable warnings.
414    
415    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
416        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
417        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
418        also returns the mark "x". This bug applied to capturing parentheses,
419        non-capturing parentheses, and atomic parentheses. It also applied to some
420        assertions.
421    
422    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
423        information out of configure.ac instead of relying on pcre.h.generic, which
424        is not stored in the repository.
425    
426    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
427        -lreadline.
428    
429    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
430    
431    15. Applied Graycode's patch to put the top-level frame on the stack rather
432        than the heap when not using the stack for recursion. This gives a
433        performance improvement in many cases when recursion is not deep.
434    
435    16. Experimental code added to "pcretest -C" to output the stack frame size.
436    
437    
438    Version 8.21 12-Dec-2011
439    ------------------------
440    
441  1.  Updating the JIT compiler.  1.  Updating the JIT compiler.
442    
# Line 13  Version 8.21 Line 447  Version 8.21
447      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before      PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
448      calling _pcre_jit_exec. Some extra comments are added.      calling _pcre_jit_exec. Some extra comments are added.
449    
450  4.  Mark settings inside atomic groups that do not contain any capturing  4.  (*MARK) settings inside atomic groups that do not contain any capturing
451      parentheses, for example, (?>a(*:m)), were not being passed out. This bug      parentheses, for example, (?>a(*:m)), were not being passed out. This bug
452      was introduced by change 18 for 8.20.      was introduced by change 18 for 8.20.
453    
# Line 22  Version 8.21 Line 456  Version 8.21
456    
457  6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were  6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
458      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.      erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
459      This bug was probably introduced by change 9 of 8.13.      This bug was probably introduced by change 9 of 8.13.
460    
461    7.  While fixing 6 above, I noticed that a number of other items were being
462        incorrectly rejected as "not fixed length". This arose partly because newer
463        opcodes had not been added to the fixed-length checking code. I have (a)
464        corrected the bug and added tests for these items, and (b) arranged for an
465        error to occur if an unknown opcode is encountered while checking for fixed
466        length instead of just assuming "not fixed length". The items that were
467        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
468        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
469        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
470    
471    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
472        being incorrectly compiled and would have given unpredicatble results.
473    
474    9.  A possessively repeated subpattern with minimum repeat count greater than
475        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
476        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
477        the first (A) could occur when it should not.
478    
479    10. Add a cast and remove a redundant test from the code.
480    
481    11. JIT should use pcre_malloc/pcre_free for allocation.
482    
483    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
484        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
485        is anything other than /usr, -L is still shown).
486    
487    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
488    
489    14. Perl does not support \N without a following name in a [] class; PCRE now
490        also gives an error.
491    
492    15. If a forward reference was repeated with an upper limit of around 2000,
493        it caused the error "internal error: overran compiling workspace". The
494        maximum number of forward references (including repeats) was limited by the
495        internal workspace, and dependent on the LINK_SIZE. The code has been
496        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
497        the default depends on LINK_SIZE. There is a new upper limit (for safety)
498        of around 200,000 forward references. While doing this, I also speeded up
499        the filling in of repeated forward references.
500    
501    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
502        incorrectly expecting the subject to contain another "a" after the start.
503    
504    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
505        in the match, the SKIP should be ignored. This was not happening; instead
506        the SKIP was being treated as NOMATCH. For patterns such as
507        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
508        tested.
509    
510    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
511        now much more compatible with Perl, in particular in cases where the result
512        is a non-match for a non-anchored pattern. For example, if
513        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
514        "m", where previously it did not return a name. A side effect of this
515        change is that for partial matches, the last encountered mark name is
516        returned, as for non matches. A number of tests that were previously not
517        Perl-compatible have been moved into the Perl-compatible test files. The
518        refactoring has had the pleasing side effect of removing one argument from
519        the match() function, thus reducing its stack requirements.
520    
521    19. If the /S+ option was used in pcretest to study a pattern using JIT,
522        subsequent uses of /S (without +) incorrectly behaved like /S+.
523    
524    21. Retrieve executable code size support for the JIT compiler and fixing
525        some warnings.
526    
527    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
528        not work when the shorter character appeared right at the end of the
529        subject string.
530    
531    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
532        systems.
533    
534    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
535        output it when the /M option is used in pcretest.
536    
537    25. The CheckMan script was not being included in the distribution. Also, added
538        an explicit "perl" to run Perl scripts from the PrepareRelease script
539        because this is reportedly needed in Windows.
540    
541    26. If study data was being save in a file and studying had not found a set of
542        "starts with" bytes for the pattern, the data written to the file (though
543        never used) was taken from uninitialized memory and so caused valgrind to
544        complain.
545    
546    27. Updated RunTest.bat as provided by Sheri Pierce.
547    
548    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
549    
550    29. Computation of memory usage for the table of capturing group names was
551        giving an unnecessarily large value.
552    
553    
554  Version 8.20 21-Oct-2011  Version 8.20 21-Oct-2011

Legend:
Removed from v.746  
changed lines
  Added in v.1248

  ViewVC Help
Powered by ViewVC 1.1.5