ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 1425 by ph10, Tue Dec 31 17:44:40 2013 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 02-Aug-2011  Version 8.35-RC1 xx-xxxx-201x
5    -----------------------------
7    1.  A new flag is set, when property checks are present in an XCLASS.
8        When this flag is not set, PCRE can perform certain optimizations
9        such as studying these XCLASS-es.
11    2.  The auto-possessification of character sets were improved: a normal
12        and an extended character set can be compared now. Furthermore
13        the JIT compiler optimizes more character set checks.
15    3.  Got rid of some compiler warnings for potentially uninitialized variables
16        that show up only when compiled with -O2.
18    4.  A pattern such as (?=ab\K) that uses \K in an assertion can set the start
19        of a match later then the end of the match. The pcretest program was not
20        handling the case sensibly - it was outputting from the start to the next
21        binary zero. It now reports this situation in a message, and outputs the
22        text from the end to the start.
24    5.  Fast forward search is improved in JIT. Instead of the first three
25        characters, any three characters with fixed position can be searched.
26        Search order: first, last, middle.
28    6.  Improve character range checks in JIT. Characters are read by an inprecise
29        function now, which returns with an unknown value if the character code is
30        above a certain treshold (e.g: 256). The only limitation is that the value
31        must be bigger than the treshold as well. This function is useful, when
32        the characters above the treshold are handled in the same way.
34    7.  The macros RAWUCHAR and RAWUCHARTEST were identical (and the latter was not
35        testing anything, contrary to its name and comment) and were not really
36        fulfilling any useful function, so I have replaced their use by plain code.
37        Similarly for RAWUCHARINC and RAWUCHARINCTEST.
40    Version 8.34 15-December-2013
41    -----------------------------
43    1.  Add pcre[16|32]_jit_free_unused_memory to forcibly free unused JIT
44        executable memory. Patch inspired by Carsten Klein.
46    2.  ./configure --enable-coverage defined SUPPORT_GCOV in config.h, although
47        this macro is never tested and has no effect, because the work to support
48        coverage involves only compiling and linking options and special targets in
49        the Makefile. The comment in config.h implied that defining the macro would
50        enable coverage support, which is totally false. There was also support for
51        setting this macro in the CMake files (my fault, I just copied it from
52        configure). SUPPORT_GCOV has now been removed.
54    3.  Make a small performance improvement in strlen16() and strlen32() in
55        pcretest.
57    4.  Change 36 for 8.33 left some unreachable statements in pcre_exec.c,
58        detected by the Solaris compiler (gcc doesn't seem to be able to diagnose
59        these cases). There was also one in pcretest.c.
61    5.  Cleaned up a "may be uninitialized" compiler warning in pcre_exec.c.
63    6.  In UTF mode, the code for checking whether a group could match an empty
64        string (which is used for indefinitely repeated groups to allow for
65        breaking an infinite loop) was broken when the group contained a repeated
66        negated single-character class with a character that occupied more than one
67        data item and had a minimum repetition of zero (for example, [^\x{100}]* in
68        UTF-8 mode). The effect was undefined: the group might or might not be
69        deemed as matching an empty string, or the program might have crashed.
71    7.  The code for checking whether a group could match an empty string was not
72        recognizing that \h, \H, \v, \V, and \R must match a character.
74    8.  Implemented PCRE_INFO_MATCH_EMPTY, which yields 1 if the pattern can match
75        an empty string. If it can, pcretest shows this in its information output.
77    9.  Fixed two related bugs that applied to Unicode extended grapheme clusters
78        that were repeated with a maximizing qualifier (e.g. \X* or \X{2,5}) when
79        matched by pcre_exec() without using JIT:
81        (a) If the rest of the pattern did not match after a maximal run of
82            grapheme clusters, the code for backing up to try with fewer of them
83            did not always back up over a full grapheme when characters that do not
84            have the modifier quality were involved, e.g. Hangul syllables.
86        (b) If the match point in a subject started with modifier character, and
87            there was no match, the code could incorrectly back up beyond the match
88            point, and potentially beyond the first character in the subject,
89            leading to a segfault or an incorrect match result.
91    10. A conditional group with an assertion condition could lead to PCRE
92        recording an incorrect first data item for a match if no other first data
93        item was recorded. For example, the pattern (?(?=ab)ab) recorded "a" as a
94        first data item, and therefore matched "ca" after "c" instead of at the
95        start.
97    11. Change 40 for 8.33 (allowing pcregrep to find empty strings) showed up a
98        bug that caused the command "echo a | ./pcregrep -M '|a'" to loop.
100    12. The source of pcregrep now includes z/OS-specific code so that it can be
101        compiled for z/OS as part of the special z/OS distribution.
103    13. Added the -T and -TM options to pcretest.
105    14. The code in pcre_compile.c for creating the table of named capturing groups
106        has been refactored. Instead of creating the table dynamically during the
107        actual compiling pass, the information is remembered during the pre-compile
108        pass (on the stack unless there are more than 20 named groups, in which
109        case malloc() is used) and the whole table is created before the actual
110        compile happens. This has simplified the code (it is now nearly 150 lines
111        shorter) and prepared the way for better handling of references to groups
112        with duplicate names.
114    15. A back reference to a named subpattern when there is more than one of the
115        same name now checks them in the order in which they appear in the pattern.
116        The first one that is set is used for the reference. Previously only the
117        first one was inspected. This change makes PCRE more compatible with Perl.
119    16. Unicode character properties were updated from Unicode 6.3.0.
121    17. The compile-time code for auto-possessification has been refactored, based
122        on a patch by Zoltan Herczeg. It now happens after instead of during
123        compilation. The code is cleaner, and more cases are handled. The option
124        PCRE_NO_AUTO_POSSESS is added for testing purposes, and the -O and /O
125        options in pcretest are provided to set it. It can also be set by
126        (*NO_AUTO_POSSESS) at the start of a pattern.
128    18. The character VT has been added to the default ("C" locale) set of
129        characters that match \s and are generally treated as white space,
130        following this same change in Perl 5.18. There is now no difference between
131        "Perl space" and "POSIX space". Whether VT is treated as white space in
132        other locales depends on the locale.
134    19. The code for checking named groups as conditions, either for being set or
135        for being recursed, has been refactored (this is related to 14 and 15
136        above). Processing unduplicated named groups should now be as fast at
137        numerical groups, and processing duplicated groups should be faster than
138        before.
140    20. Two patches to the CMake build system, by Alexander Barkov:
142          (1) Replace the "source" command by "." in CMakeLists.txt because
143              "source" is a bash-ism.
145          (2) Add missing HAVE_STDINT_H and HAVE_INTTYPES_H to config-cmake.h.in;
146              without these the CMake build does not work on Solaris.
148    21. Perl has changed its handling of \8 and \9. If there is no previously
149        encountered capturing group of those numbers, they are treated as the
150        literal characters 8 and 9 instead of a binary zero followed by the
151        literals. PCRE now does the same.
153    22. Following Perl, added \o{} to specify codepoints in octal, making it
154        possible to specify values greater than 0777 and also making them
155        unambiguous.
157    23. Perl now gives an error for missing closing braces after \x{... instead of
158        treating the string as literal. PCRE now does the same.
160    24. RunTest used to grumble if an inappropriate test was selected explicitly,
161        but just skip it when running all tests. This make it awkward to run ranges
162        of tests when one of them was inappropriate. Now it just skips any
163        inappropriate tests, as it always did when running all tests.
165    25. If PCRE_AUTO_CALLOUT and PCRE_UCP were set for a pattern that contained
166        character types such as \d or \w, too many callouts were inserted, and the
167        data that they returned was rubbish.
169    26. In UCP mode, \s was not matching two of the characters that Perl matches,
170        namely NEL (U+0085) and MONGOLIAN VOWEL SEPARATOR (U+180E), though they
171        were matched by \h. The code has now been refactored so that the lists of
172        the horizontal and vertical whitespace characters used for \h and \v (which
173        are defined only in one place) are now also used for \s.
175    27. Add JIT support for the 64 bit TileGX architecture.
176        Patch by Jiong Wang (Tilera Corporation).
178    28. Possessive quantifiers for classes (both explicit and automatically
179        generated) now use special opcodes instead of wrapping in ONCE brackets.
181    29. Whereas an item such as A{4}+ ignored the possessivenes of the quantifier
182        (because it's meaningless), this was not happening when PCRE_CASELESS was
183        set. Not wrong, but inefficient.
185    30. Updated perltest.pl to add /u (force Unicode mode) when /W (use Unicode
186        properties for \w, \d, etc) is present in a test regex. Otherwise if the
187        test contains no characters greater than 255, Perl doesn't realise it
188        should be using Unicode semantics.
190    31. Upgraded the handling of the POSIX classes [:graph:], [:print:], and
191        [:punct:] when PCRE_UCP is set so as to include the same characters as Perl
192        does in Unicode mode.
194    32. Added the "forbid" facility to pcretest so that putting tests into the
195        wrong test files can sometimes be quickly detected.
197    33. There is now a limit (default 250) on the depth of nesting of parentheses.
198        This limit is imposed to control the amount of system stack used at compile
199        time. It can be changed at build time by --with-parens-nest-limit=xxx or
200        the equivalent in CMake.
202    34. Character classes such as [A-\d] or [a-[:digit:]] now cause compile-time
203        errors. Perl warns for these when in warning mode, but PCRE has no facility
204        for giving warnings.
206    35. Change 34 for 8.13 allowed quantifiers on assertions, because Perl does.
207        However, this was not working for (?!) because it is optimized to (*FAIL),
208        for which PCRE does not allow quantifiers. The optimization is now disabled
209        when a quantifier follows (?!). I can't see any use for this, but it makes
210        things uniform.
212    36. Perl no longer allows group names to start with digits, so I have made this
213        change also in PCRE. It simplifies the code a bit.
215    37. In extended mode, Perl ignores spaces before a + that indicates a
216        possessive quantifier. PCRE allowed a space before the quantifier, but not
217        before the possessive +. It now does.
219    38. The use of \K (reset reported match start) within a repeated possessive
220        group such as (a\Kb)*+ was not working.
222    40. Document that the same character tables must be used at compile time and
223        run time, and that the facility to pass tables to pcre_exec() and
224        pcre_dfa_exec() is for use only with saved/restored patterns.
226    41. Applied Jeff Trawick's patch CMakeLists.txt, which "provides two new
227        features for Builds with MSVC:
229        1. Support pcre.rc and/or pcreposix.rc (as is already done for MinGW
230           builds). The .rc files can be used to set FileDescription and many other
231           attributes.
233        2. Add an option (-DINSTALL_MSVC_PDB) to enable installation of .pdb files.
234           This allows higher-level build scripts which want .pdb files to avoid
235           hard-coding the exact files needed."
237    42. Added support for [[:<:]] and [[:>:]] as used in the BSD POSIX library to
238        mean "start of word" and "end of word", respectively, as a transition aid.
240    43. A minimizing repeat of a class containing codepoints greater than 255 in
241        non-UTF 16-bit or 32-bit modes caused an internal error when PCRE was
242        compiled to use the heap for recursion.
244    44. Got rid of some compiler warnings for unused variables when UTF but not UCP
245        is configured.
248    Version 8.33 28-May-2013
249    ------------------------
251    1.  Added 'U' to some constants that are compared to unsigned integers, to
252        avoid compiler signed/unsigned warnings. Added (int) casts to unsigned
253        variables that are added to signed variables, to ensure the result is
254        signed and can be negated.
256    2.  Applied patch by Daniel Richard G for quashing MSVC warnings to the
257        CMake config files.
259    3.  Revise the creation of config.h.generic so that all boolean macros are
260        #undefined, whereas non-boolean macros are #ifndef/#endif-ed. This makes
261        overriding via -D on the command line possible.
263    4.  Changing the definition of the variable "op" in pcre_exec.c from pcre_uchar
264        to unsigned int is reported to make a quite noticeable speed difference in
265        a specific Windows environment. Testing on Linux did also appear to show
266        some benefit (and it is clearly not harmful). Also fixed the definition of
267        Xop which should be unsigned.
269    5.  Related to (4), changing the definition of the intermediate variable cc
270        in repeated character loops from pcre_uchar to pcre_uint32 also gave speed
271        improvements.
273    6.  Fix forward search in JIT when link size is 3 or greater. Also removed some
274        unnecessary spaces.
276    7.  Adjust autogen.sh and configure.ac to lose warnings given by automake 1.12
277        and later.
279    8.  Fix two buffer over read issues in 16 and 32 bit modes. Affects JIT only.
281    9.  Optimizing fast_forward_start_bits in JIT.
283    10. Adding support for callouts in JIT, and fixing some issues revealed
284        during this work. Namely:
286        (a) Unoptimized capturing brackets incorrectly reset on backtrack.
288        (b) Minimum length was not checked before the matching is started.
290    11. The value of capture_last that is passed to callouts was incorrect in some
291        cases when there was a capture on one path that was subsequently abandoned
292        after a backtrack. Also, the capture_last value is now reset after a
293        recursion, since all captures are also reset in this case.
295    12. The interpreter no longer returns the "too many substrings" error in the
296        case when an overflowing capture is in a branch that is subsequently
297        abandoned after a backtrack.
299    13. In the pathological case when an offset vector of size 2 is used, pcretest
300        now prints out the matched string after a yield of 0 or 1.
302    14. Inlining subpatterns in recursions, when certain conditions are fulfilled.
303        Only supported by the JIT compiler at the moment.
305    15. JIT compiler now supports 32 bit Macs thanks to Lawrence Velazquez.
307    16. Partial matches now set offsets[2] to the "bumpalong" value, that is, the
308        offset of the starting point of the matching process, provided the offsets
309        vector is large enough.
311    17. The \A escape now records a lookbehind value of 1, though its execution
312        does not actually inspect the previous character. This is to ensure that,
313        in partial multi-segment matching, at least one character from the old
314        segment is retained when a new segment is processed. Otherwise, if there
315        are no lookbehinds in the pattern, \A might match incorrectly at the start
316        of a new segment.
318    18. Added some #ifdef __VMS code into pcretest.c to help VMS implementations.
320    19. Redefined some pcre_uchar variables in pcre_exec.c as pcre_uint32; this
321        gives some modest performance improvement in 8-bit mode.
323    20. Added the PCRE-specific property \p{Xuc} for matching characters that can
324        be expressed in certain programming languages using Universal Character
325        Names.
327    21. Unicode validation has been updated in the light of Unicode Corrigendum #9,
328        which points out that "non characters" are not "characters that may not
329        appear in Unicode strings" but rather "characters that are reserved for
330        internal use and have only local meaning".
332    22. When a pattern was compiled with automatic callouts (PCRE_AUTO_CALLOUT) and
333        there was a conditional group that depended on an assertion, if the
334        assertion was false, the callout that immediately followed the alternation
335        in the condition was skipped when pcre_exec() was used for matching.
337    23. Allow an explicit callout to be inserted before an assertion that is the
338        condition for a conditional group, for compatibility with automatic
339        callouts, which always insert a callout at this point.
341    24. In 8.31, (*COMMIT) was confined to within a recursive subpattern. Perl also
342        confines (*SKIP) and (*PRUNE) in the same way, and this has now been done.
344    25. (*PRUNE) is now supported by the JIT compiler.
346    26. Fix infinite loop when /(?<=(*SKIP)ac)a/ is matched against aa.
348    27. Fix the case where there are two or more SKIPs with arguments that may be
349        ignored.
351    28. (*SKIP) is now supported by the JIT compiler.
353    29. (*THEN) is now supported by the JIT compiler.
355    30. Update RunTest with additional test selector options.
357    31. The way PCRE handles backtracking verbs has been changed in two ways.
359        (1) Previously, in something like (*COMMIT)(*SKIP), COMMIT would override
360        SKIP. Now, PCRE acts on whichever backtracking verb is reached first by
361        backtracking. In some cases this makes it more Perl-compatible, but Perl's
362        rather obscure rules do not always do the same thing.
364        (2) Previously, backtracking verbs were confined within assertions. This is
365        no longer the case for positive assertions, except for (*ACCEPT). Again,
366        this sometimes improves Perl compatibility, and sometimes does not.
368    32. A number of tests that were in test 2 because Perl did things differently
369        have been moved to test 1, because either Perl or PCRE has changed, and
370        these tests are now compatible.
372    32. Backtracking control verbs are now handled in the same way in JIT and
373        interpreter.
375    33. An opening parenthesis in a MARK/PRUNE/SKIP/THEN name in a pattern that
376        contained a forward subroutine reference caused a compile error.
378    34. Auto-detect and optimize limited repetitions in JIT.
380    35. Implement PCRE_NEVER_UTF to lock out the use of UTF, in particular,
381        blocking (*UTF) etc.
383    36. In the interpreter, maximizing pattern repetitions for characters and
384        character types now use tail recursion, which reduces stack usage.
386    37. The value of the max lookbehind was not correctly preserved if a compiled
387        and saved regex was reloaded on a host of different endianness.
389    38. Implemented (*LIMIT_MATCH) and (*LIMIT_RECURSION). As part of the extension
390        of the compiled pattern block, expand the flags field from 16 to 32 bits
391        because it was almost full.
393    39. Try madvise first before posix_madvise.
395    40. Change 7 for PCRE 7.9 made it impossible for pcregrep to find empty lines
396        with a pattern such as ^$. It has taken 4 years for anybody to notice! The
397        original change locked out all matches of empty strings. This has been
398        changed so that one match of an empty string per line is recognized.
399        Subsequent searches on the same line (for colouring or for --only-matching,
400        for example) do not recognize empty strings.
402    41. Applied a user patch to fix a number of spelling mistakes in comments.
404    42. Data lines longer than 65536 caused pcretest to crash.
406    43. Clarified the data type for length and startoffset arguments for pcre_exec
407        and pcre_dfa_exec in the function-specific man pages, where they were
408        explicitly stated to be in bytes, never having been updated. I also added
409        some clarification to the pcreapi man page.
411    44. A call to pcre_dfa_exec() with an output vector size less than 2 caused
412        a segmentation fault.
415    Version 8.32 30-November-2012
416    -----------------------------
418    1.  Improved JIT compiler optimizations for first character search and single
419        character iterators.
421    2.  Supporting IBM XL C compilers for PPC architectures in the JIT compiler.
422        Patch by Daniel Richard G.
424    3.  Single character iterator optimizations in the JIT compiler.
426    4.  Improved JIT compiler optimizations for character ranges.
428    5.  Rename the "leave" variable names to "quit" to improve WinCE compatibility.
429        Reported by Giuseppe D'Angelo.
431    6.  The PCRE_STARTLINE bit, indicating that a match can occur only at the start
432        of a line, was being set incorrectly in cases where .* appeared inside
433        atomic brackets at the start of a pattern, or where there was a subsequent
434        *PRUNE or *SKIP.
436    7.  Improved instruction cache flush for POWER/PowerPC.
437        Patch by Daniel Richard G.
439    8.  Fixed a number of issues in pcregrep, making it more compatible with GNU
440        grep:
442        (a) There is now no limit to the number of patterns to be matched.
444        (b) An error is given if a pattern is too long.
446        (c) Multiple uses of --exclude, --exclude-dir, --include, and --include-dir
447            are now supported.
449        (d) --exclude-from and --include-from (multiple use) have been added.
451        (e) Exclusions and inclusions now apply to all files and directories, not
452            just to those obtained from scanning a directory recursively.
454        (f) Multiple uses of -f and --file-list are now supported.
456        (g) In a Windows environment, the default for -d has been changed from
457            "read" (the GNU grep default) to "skip", because otherwise the presence
458            of a directory in the file list provokes an error.
460        (h) The documentation has been revised and clarified in places.
462    9.  Improve the matching speed of capturing brackets.
464    10. Changed the meaning of \X so that it now matches a Unicode extended
465        grapheme cluster.
467    11. Patch by Daniel Richard G to the autoconf files to add a macro for sorting
468        out POSIX threads when JIT support is configured.
470    12. Added support for PCRE_STUDY_EXTRA_NEEDED.
472    13. In the POSIX wrapper regcomp() function, setting re_nsub field in the preg
473        structure could go wrong in environments where size_t is not the same size
474        as int.
476    14. Applied user-supplied patch to pcrecpp.cc to allow PCRE_NO_UTF8_CHECK to be
477        set.
479    15. The EBCDIC support had decayed; later updates to the code had included
480        explicit references to (e.g.) \x0a instead of CHAR_LF. There has been a
481        general tidy up of EBCDIC-related issues, and the documentation was also
482        not quite right. There is now a test that can be run on ASCII systems to
483        check some of the EBCDIC-related things (but is it not a full test).
485    16. The new PCRE_STUDY_EXTRA_NEEDED option is now used by pcregrep, resulting
486        in a small tidy to the code.
488    17. Fix JIT tests when UTF is disabled and both 8 and 16 bit mode are enabled.
490    18. If the --only-matching (-o) option in pcregrep is specified multiple
491        times, each one causes appropriate output. For example, -o1 -o2 outputs the
492        substrings matched by the 1st and 2nd capturing parentheses. A separating
493        string can be specified by --om-separator (default empty).
495    19. Improving the first n character searches.
497    20. Turn case lists for horizontal and vertical white space into macros so that
498        they are defined only once.
500    21. This set of changes together give more compatible Unicode case-folding
501        behaviour for characters that have more than one other case when UCP
502        support is available.
504        (a) The Unicode property table now has offsets into a new table of sets of
505            three or more characters that are case-equivalent. The MultiStage2.py
506            script that generates these tables (the pcre_ucd.c file) now scans
507            CaseFolding.txt instead of UnicodeData.txt for character case
508            information.
510        (b) The code for adding characters or ranges of characters to a character
511            class has been abstracted into a generalized function that also handles
512            case-independence. In UTF-mode with UCP support, this uses the new data
513            to handle characters with more than one other case.
515        (c) A bug that is fixed as a result of (b) is that codepoints less than 256
516            whose other case is greater than 256 are now correctly matched
517            caselessly. Previously, the high codepoint matched the low one, but not
518            vice versa.
520        (d) The processing of \h, \H, \v, and \ in character classes now makes use
521            of the new class addition function, using character lists defined as
522            macros alongside the case definitions of 20 above.
524        (e) Caseless back references now work with characters that have more than
525            one other case.
527        (f) General caseless matching of characters with more than one other case
528            is supported.
530    22. Unicode character properties were updated from Unicode 6.2.0
532    23. Improved CMake support under Windows. Patch by Daniel Richard G.
534    24. Add support for 32-bit character strings, and UTF-32
536    25. Major JIT compiler update (code refactoring and bugfixing).
537        Experimental Sparc 32 support is added.
539    26. Applied a modified version of Daniel Richard G's patch to create
540        pcre.h.generic and config.h.generic by "make" instead of in the
541        PrepareRelease script.
543    27. Added a definition for CHAR_NULL (helpful for the z/OS port), and use it in
544        pcre_compile.c when checking for a zero character.
546    28. Introducing a native interface for JIT. Through this interface, the compiled
547        machine code can be directly executed. The purpose of this interface is to
548        provide fast pattern matching, so several sanity checks are not performed.
549        However, feature tests are still performed. The new interface provides
550        1.4x speedup compared to the old one.
552    29. If pcre_exec() or pcre_dfa_exec() was called with a negative value for
553        the subject string length, the error given was PCRE_ERROR_BADOFFSET, which
554        was confusing. There is now a new error PCRE_ERROR_BADLENGTH for this case.
556    30. In 8-bit UTF-8 mode, pcretest failed to give an error for data codepoints
557        greater than 0x7fffffff (which cannot be represented in UTF-8, even under
558        the "old" RFC 2279). Instead, it ended up passing a negative length to
559        pcre_exec().
561    31. Add support for GCC's visibility feature to hide internal functions.
563    32. Running "pcretest -C pcre8" or "pcretest -C pcre16" gave a spurious error
564        "unknown -C option" after outputting 0 or 1.
566    33. There is now support for generating a code coverage report for the test
567        suite in environments where gcc is the compiler and lcov is installed. This
568        is mainly for the benefit of the developers.
570    34. If PCRE is built with --enable-valgrind, certain memory regions are marked
571        unaddressable using valgrind annotations, allowing valgrind to detect
572        invalid memory accesses. This is mainly for the benefit of the developers.
574    25. (*UTF) can now be used to start a pattern in any of the three libraries.
576    26. Give configure error if --enable-cpp but no C++ compiler found.
579    Version 8.31 06-July-2012
580    -------------------------
582    1.  Fixing a wrong JIT test case and some compiler warnings.
584    2.  Removed a bashism from the RunTest script.
586    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
587        to unsigned type, result still unsigned" that was given by an MS compiler
588        on encountering the code "-sizeof(xxx)".
590    4.  Partial matching support is added to the JIT compiler.
592    5.  Fixed several bugs concerned with partial matching of items that consist
593        of more than one character:
595        (a) /^(..)\1/ did not partially match "aba" because checking references was
596            done on an "all or nothing" basis. This also applied to repeated
597            references.
599        (b) \R did not give a hard partial match if \r was found at the end of the
600            subject.
602        (c) \X did not give a hard partial match after matching one or more
603            characters at the end of the subject.
605        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
606            a partial match for the string "\r".
608        (e) When newline was set to CRLF, the metacharacter "." did not recognize
609            a partial match for a CR character at the end of the subject string.
611    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
612        running pcretest, the text "(JIT)" added to the output whenever JIT is
613        actually used to run the match.
615    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
616        or /S+[+] with a digit between 1 and 7.
618    8.  OP_NOT now supports any UTF character not just single-byte ones.
620    9.  (*MARK) control verb is now supported by the JIT compiler.
622    10. The command "./RunTest list" lists the available tests without actually
623        running any of them. (Because I keep forgetting what they all are.)
627    12. Applied a (slightly modified) user-supplied patch that improves performance
628        when the heap is used for recursion (compiled with --disable-stack-for-
629        recursion). Instead of malloc and free for each heap frame each time a
630        logical recursion happens, frames are retained on a chain and re-used where
631        possible. This sometimes gives as much as 30% improvement.
633    13. As documented, (*COMMIT) is now confined to within a recursive subpattern
634        call.
636    14. As documented, (*COMMIT) is now confined to within a positive assertion.
638    15. It is now possible to link pcretest with libedit as an alternative to
639        libreadline.
641    16. (*COMMIT) control verb is now supported by the JIT compiler.
643    17. The Unicode data tables have been updated to Unicode 6.1.0.
645    18. Added --file-list option to pcregrep.
647    19. Added binary file support to pcregrep, including the -a, --binary-files,
648        -I, and --text options.
650    20. The madvise function is renamed for posix_madvise for QNX compatibility
651        reasons. Fixed by Giuseppe D'Angelo.
653    21. Fixed a bug for backward assertions with REVERSE 0 in the JIT compiler.
655    22. Changed the option for creating symbolic links for 16-bit man pages from
656        -s to -sf so that re-installing does not cause issues.
658    23. Support PCRE_NO_START_OPTIMIZE in JIT as (*MARK) support requires it.
660    24. Fixed a very old bug in pcretest that caused errors with restarted DFA
661        matches in certain environments (the workspace was not being correctly
662        retained). Also added to pcre_dfa_exec() a simple plausibility check on
663        some of the workspace data at the beginning of a restart.
665    25. \s*\R was auto-possessifying the \s* when it should not, whereas \S*\R
666        was not doing so when it should - probably a typo introduced by SVN 528
667        (change 8.10/14).
669    26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
670        \w+ when the character tables indicated that \x{c4} was a word character.
671        There were several related cases, all because the tests for doing a table
672        lookup were testing for characters less than 127 instead of 255.
674    27. If a pattern contains capturing parentheses that are not used in a match,
675        their slots in the ovector are set to -1. For those that are higher than
676        any matched groups, this happens at the end of processing. In the case when
677        there were back references that the ovector was too small to contain
678        (causing temporary malloc'd memory to be used during matching), and the
679        highest capturing number was not used, memory off the end of the ovector
680        was incorrectly being set to -1. (It was using the size of the temporary
681        memory instead of the true size.)
683    28. To catch bugs like 27 using valgrind, when pcretest is asked to specify an
684        ovector size, it uses memory at the end of the block that it has got.
686    29. Check for an overlong MARK name and give an error at compile time. The
687        limit is 255 for the 8-bit library and 65535 for the 16-bit library.
689    30. JIT compiler update.
691    31. JIT is now supported on jailbroken iOS devices. Thanks for Ruiger
692        Rill for the patch.
694    32. Put spaces around SLJIT_PRINT_D in the JIT compiler. Required by CXX11.
696    33. Variable renamings in the PCRE-JIT compiler. No functionality change.
698    34. Fixed typos in pcregrep: in two places there was SUPPORT_LIBZ2 instead of
699        SUPPORT_LIBBZ2. This caused a build problem when bzip2 but not gzip (zlib)
700        was enabled.
702    35. Improve JIT code generation for greedy plus quantifier.
704    36. When /((?:a?)*)*c/ or /((?>a?)*)*c/ was matched against "aac", it set group
705        1 to "aa" instead of to an empty string. The bug affected repeated groups
706        that could potentially match an empty string.
708    37. Optimizing single character iterators in JIT.
710    38. Wide characters specified with \uxxxx in JavaScript mode are now subject to
711        the same checks as \x{...} characters in non-JavaScript mode. Specifically,
712        codepoints that are too big for the mode are faulted, and in a UTF mode,
713        disallowed codepoints are also faulted.
715    39. If PCRE was compiled with UTF support, in three places in the DFA
716        matcher there was code that should only have been obeyed in UTF mode, but
717        was being obeyed unconditionally. In 8-bit mode this could cause incorrect
718        processing when bytes with values greater than 127 were present. In 16-bit
719        mode the bug would be provoked by values in the range 0xfc00 to 0xdc00. In
720        both cases the values are those that cannot be the first data item in a UTF
721        character. The three items that might have provoked this were recursions,
722        possessively repeated groups, and atomic groups.
724    40. Ensure that libpcre is explicitly listed in the link commands for pcretest
725        and pcregrep, because some OS require shared objects to be explicitly
726        passed to ld, causing the link step to fail if they are not.
728    41. There were two incorrect #ifdefs in pcre_study.c, meaning that, in 16-bit
729        mode, patterns that started with \h* or \R* might be incorrectly matched.
732    Version 8.30 04-February-2012
733    -----------------------------
735    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
736        name is defined in ctype.h.
738    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
739        only in quite long subpatterns.
741    3.  Removed the function pcre_info(), which has been obsolete and deprecated
742        since it was replaced by pcre_fullinfo() in February 2000.
744    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
745        match a (*MARK), and the match failed at the start of the subject, a
746        reference to memory before the start of the subject could occur. This bug
747        was introduced by fix 17 of release 8.21.
749    5.  A reference to an unset group with zero minimum repetition was giving
750        totally wrong answers (in non-JavaScript-compatibility mode). For example,
751        /(another)?(\1?)test/ matched against "hello world test". This bug was
752        introduced in release 8.13.
754    6.  Add support for 16-bit character strings (a large amount of work involving
755        many changes and refactorings).
757    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
758        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
759        from a file.
761    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
762        rounding is not applied in this particular case).
764    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
765        if they appear, or are escaped, in patterns.
767    10. Get rid of a number of -Wunused-but-set-variable warnings.
769    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
770        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
771        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
772        also returns the mark "x". This bug applied to capturing parentheses,
773        non-capturing parentheses, and atomic parentheses. It also applied to some
774        assertions.
776    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
777        information out of configure.ac instead of relying on pcre.h.generic, which
778        is not stored in the repository.
780    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
781        -lreadline.
783    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
785    15. Applied Graycode's patch to put the top-level frame on the stack rather
786        than the heap when not using the stack for recursion. This gives a
787        performance improvement in many cases when recursion is not deep.
789    16. Experimental code added to "pcretest -C" to output the stack frame size.
792    Version 8.21 12-Dec-2011
793    ------------------------
795    1.  Updating the JIT compiler.
797    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
798        are added as well.
800    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
801        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
802        calling _pcre_jit_exec. Some extra comments are added.
804    4.  (*MARK) settings inside atomic groups that do not contain any capturing
805        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
806        was introduced by change 18 for 8.20.
808    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
809        ECMA-262 standard.
811    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
812        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
813        This bug was probably introduced by change 9 of 8.13.
815    7.  While fixing 6 above, I noticed that a number of other items were being
816        incorrectly rejected as "not fixed length". This arose partly because newer
817        opcodes had not been added to the fixed-length checking code. I have (a)
818        corrected the bug and added tests for these items, and (b) arranged for an
819        error to occur if an unknown opcode is encountered while checking for fixed
820        length instead of just assuming "not fixed length". The items that were
821        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
822        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
823        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
825    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
826        being incorrectly compiled and would have given unpredicatble results.
828    9.  A possessively repeated subpattern with minimum repeat count greater than
829        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
830        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
831        the first (A) could occur when it should not.
833    10. Add a cast and remove a redundant test from the code.
835    11. JIT should use pcre_malloc/pcre_free for allocation.
837    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
838        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
839        is anything other than /usr, -L is still shown).
841    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
843    14. Perl does not support \N without a following name in a [] class; PCRE now
844        also gives an error.
846    15. If a forward reference was repeated with an upper limit of around 2000,
847        it caused the error "internal error: overran compiling workspace". The
848        maximum number of forward references (including repeats) was limited by the
849        internal workspace, and dependent on the LINK_SIZE. The code has been
850        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
851        the default depends on LINK_SIZE. There is a new upper limit (for safety)
852        of around 200,000 forward references. While doing this, I also speeded up
853        the filling in of repeated forward references.
855    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
856        incorrectly expecting the subject to contain another "a" after the start.
858    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
859        in the match, the SKIP should be ignored. This was not happening; instead
860        the SKIP was being treated as NOMATCH. For patterns such as
861        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
862        tested.
864    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
865        now much more compatible with Perl, in particular in cases where the result
866        is a non-match for a non-anchored pattern. For example, if
867        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
868        "m", where previously it did not return a name. A side effect of this
869        change is that for partial matches, the last encountered mark name is
870        returned, as for non matches. A number of tests that were previously not
871        Perl-compatible have been moved into the Perl-compatible test files. The
872        refactoring has had the pleasing side effect of removing one argument from
873        the match() function, thus reducing its stack requirements.
875    19. If the /S+ option was used in pcretest to study a pattern using JIT,
876        subsequent uses of /S (without +) incorrectly behaved like /S+.
878    21. Retrieve executable code size support for the JIT compiler and fixing
879        some warnings.
881    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
882        not work when the shorter character appeared right at the end of the
883        subject string.
885    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
886        systems.
888    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
889        output it when the /M option is used in pcretest.
891    25. The CheckMan script was not being included in the distribution. Also, added
892        an explicit "perl" to run Perl scripts from the PrepareRelease script
893        because this is reportedly needed in Windows.
895    26. If study data was being save in a file and studying had not found a set of
896        "starts with" bytes for the pattern, the data written to the file (though
897        never used) was taken from uninitialized memory and so caused valgrind to
898        complain.
900    27. Updated RunTest.bat as provided by Sheri Pierce.
902    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
904    29. Computation of memory usage for the table of capturing group names was
905        giving an unnecessarily large value.
908    Version 8.20 21-Oct-2011
909    ------------------------
911    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
912        a POSIX class. After further experiments with Perl, which convinced me that
913        Perl has bugs and confusions, a closing square bracket is no longer allowed
914        in a POSIX name. This bug also affected patterns with classes that started
915        with full stops.
917    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
918        captured substring, but while checking the failing first alternative,
919        substring 1 is temporarily captured. If the output vector supplied to
920        pcre_exec() was not big enough for this capture, the yield of the function
921        was still zero ("insufficient space for captured substrings"). This cannot
922        be totally fixed without adding another stack variable, which seems a lot
923        of expense for a edge case. However, I have improved the situation in cases
924        such as /(a)(b)x|abc/ matched against "abc", where the return code
925        indicates that fewer than the maximum number of slots in the ovector have
926        been set.
928    3.  Related to (2) above: when there are more back references in a pattern than
929        slots in the output vector, pcre_exec() uses temporary memory during
930        matching, and copies in the captures as far as possible afterwards. It was
931        using the entire output vector, but this conflicts with the specification
932        that only 2/3 is used for passing back captured substrings. Now it uses
933        only the first 2/3, for compatibility. This is, of course, another edge
934        case.
936    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
937        main code base, and can be used by building with --enable-jit. When this is
938        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
939        runtime --no-jit option is given.
941    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
942        ovector, the return from the function was zero, implying that there were
943        other matches that did not fit. The correct "exactly full" value is now
944        returned.
946    6.  If a subpattern that was called recursively or as a subroutine contained
947        (*PRUNE) or any other control that caused it to give a non-standard return,
948        invalid errors such as "Error -26 (nested recursion at the same subject
949        position)" or even infinite loops could occur.
951    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
952        computing the minimum length on reaching *ACCEPT, and so ended up with the
953        wrong value of 1 rather than 0. Further investigation indicates that
954        computing a minimum subject length in the presence of *ACCEPT is difficult
955        (think back references, subroutine calls), and so I have changed the code
956        so that no minimum is registered for a pattern that contains *ACCEPT.
958    8.  If (*THEN) was present in the first (true) branch of a conditional group,
959        it was not handled as intended. [But see 16 below.]
961    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
962        Sheri Pierce.
964    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
965        the first byte in a match must be "a".
967    11. Change 17 for 8.13 increased the recursion depth for patterns like
968        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
969        pattern contains any instances of (*THEN). If it does not, the old
970        optimizations are restored. It would be nice to do this on a per-group
971        basis, but at the moment that is not feasible.
973    12. In some environments, the output of pcretest -C is CRLF terminated. This
974        broke RunTest's code that checks for the link size. A single white space
975        character after the value is now allowed for.
977    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
978        For "fr", it uses the Windows-specific input and output files.
980    14. If (*THEN) appeared in a group that was called recursively or as a
981        subroutine, it did not work as intended. [But see next item.]
983    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
984        pattern fragments (but not containing any | characters). If A and B are
985        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
986        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
987        D. In other words, Perl considers parentheses that do not contain any |
988        characters to be part of a surrounding alternative, whereas PCRE was
989        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
990        differently. PCRE now behaves in the same way as Perl, except in the case
991        of subroutine/recursion calls such as (?1) which have in any case always
992        been different (but PCRE had them first :-).
994    16. Related to 15 above: Perl does not treat the | in a conditional group as
995        creating alternatives. Such a group is treated in the same way as an
996        ordinary group without any | characters when processing (*THEN). PCRE has
997        been changed to match Perl's behaviour.
999    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
1000        RunGrepTest script failed.
1002    18. Change 22 for version 13 caused atomic groups to use more stack. This is
1003        inevitable for groups that contain captures, but it can lead to a lot of
1004        stack use in large patterns. The old behaviour has been restored for atomic
1005        groups that do not contain any capturing parentheses.
1007    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
1008        suppress the check for a minimum subject length at run time. (If it was
1009        given to pcre_exec() or pcre_dfa_exec() it did work.)
1011    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
1012        fail to work when decoding hex characters in data strings in EBCDIC
1013        environments.
1015    21. It appears that in at least one Mac OS environment, the isxdigit() function
1016        is implemented as a macro that evaluates to its argument more than once,
1017        contravening the C 90 Standard (I haven't checked a later standard). There
1018        was an instance in pcretest which caused it to go wrong when processing
1019        \x{...} escapes in subject strings. The has been rewritten to avoid using
1020        things like p++ in the argument of isxdigit().
1023    Version 8.13 16-Aug-2011
1024  ------------------------  ------------------------
1026  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 98  Version 8.13 02-Aug-2011 Line 1117  Version 8.13 02-Aug-2011
1117      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
1118      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
1119      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
1120      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
1122  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
1123      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 1208  Version 8.13 02-Aug-2011
1208      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
1209      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
1210      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
1211      more like Perl.      more like Perl. (But see 8.20/1 above.)
1213  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
1214      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 1243  Version 8.13 02-Aug-2011
1243      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
1244          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
1246      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
1247          PCRE is built.          PCRE is built.
1249      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 245  Version 8.13 02-Aug-2011 Line 1264  Version 8.13 02-Aug-2011
1264  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
1265      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
1266      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
1268  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
1269      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
1272  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
# Line 900  Version 7.9 11-Apr-09 Line 1919  Version 7.9 11-Apr-09
1919  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
1920      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
1921      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
1922      seems to be how GNU grep behaves.      seems to be how GNU grep behaves. [But see later change 40 for release
1923        8.33.]
1925  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
1926      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 1143  Version 7.7 07-May-08 Line 2163  Version 7.7 07-May-08
2163      containing () gave an internal compiling error instead of "reference to      containing () gave an internal compiling error instead of "reference to
2164      non-existent subpattern". Fortunately, when the pattern did exist, the      non-existent subpattern". Fortunately, when the pattern did exist, the
2165      compiled code was correct. (When scanning forwards to check for the      compiled code was correct. (When scanning forwards to check for the
2166      existencd of the subpattern, it was treating the data ']' as terminating      existence of the subpattern, it was treating the data ']' as terminating
2167      the class, so got the count wrong. When actually compiling, the reference      the class, so got the count wrong. When actually compiling, the reference
2168      was subsequently set up correctly.)      was subsequently set up correctly.)

Removed from v.657  
changed lines
  Added in v.1425

  ViewVC Help
Powered by ViewVC 1.1.5