ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 67 by nigel, Sat Feb 24 21:40:13 2007 UTC revision 83 by nigel, Sat Feb 24 21:41:06 2007 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 6.3 15-Aug-05
5    ---------------------
7     1. The file libpcre.pc.in did not have general read permission in the tarball.
9     2. There were some problems when building without C++ support:
11        (a) If C++ support was not built, "make install" and "make test" still
12            tried to test it.
14        (b) There were problems when the value of CXX was explicitly set. Some
15            changes have been made to try to fix these, and ...
17        (c) --disable-cpp can now be used to explicitly disable C++ support.
19        (d) The use of @CPP_OBJ@ directly caused a blank line preceded by a
20            backslash in a target when C++ was disabled. This confuses some
21            versions of "make", apparently. Using an intermediate variable solves
22            this. (Same for CPP_LOBJ.)
24     3. $(LINK_FOR_BUILD) now includes $(CFLAGS_FOR_BUILD) and $(LINK)
25        (non-Windows) now includes $(CFLAGS) because these flags are sometimes
26        necessary on certain architectures.
28     4. Added a setting of -export-symbols-regex to the link command to remove
29        those symbols that are exported in the C sense, but actually are local
30        within the library, and not documented. Their names all begin with
31        "_pcre_". This is not a perfect job, because (a) we have to except some
32        symbols that pcretest ("illegally") uses, and (b) the facility isn't always
33        available (and never for static libraries). I have made a note to try to
34        find a way round (a) in the future.
37    Version 6.2 01-Aug-05
38    ---------------------
40     1. There was no test for integer overflow of quantifier values. A construction
41        such as {1111111111111111} would give undefined results. What is worse, if
42        a minimum quantifier for a parenthesized subpattern overflowed and became
43        negative, the calculation of the memory size went wrong. This could have
44        led to memory overwriting.
46     2. Building PCRE using VPATH was broken. Hopefully it is now fixed.
48     3. Added "b" to the 2nd argument of fopen() in dftables.c, for non-Unix-like
49        operating environments where this matters.
51     4. Applied Giuseppe Maxia's patch to add additional features for controlling
52        PCRE options from within the C++ wrapper.
54     5. Named capturing subpatterns were not being correctly counted when a pattern
55        was compiled. This caused two problems: (a) If there were more than 100
56        such subpatterns, the calculation of the memory needed for the whole
57        compiled pattern went wrong, leading to an overflow error. (b) Numerical
58        back references of the form \12, where the number was greater than 9, were
59        not recognized as back references, even though there were sufficient
60        previous subpatterns.
62     6. Two minor patches to pcrecpp.cc in order to allow it to compile on older
63        versions of gcc, e.g. 2.95.4.
66    Version 6.1 21-Jun-05
67    ---------------------
69     1. There was one reference to the variable "posix" in pcretest.c that was not
70        surrounded by "#if !defined NOPOSIX".
72     2. Make it possible to compile pcretest without DFA support, UTF8 support, or
73        the cross-check on the old pcre_info() function, for the benefit of the
74        cut-down version of PCRE that is currently imported into Exim.
76     3. A (silly) pattern starting with (?i)(?-i) caused an internal space
77        allocation error. I've done the easy fix, which wastes 2 bytes for sensible
78        patterns that start (?i) but I don't think that matters. The use of (?i) is
79        just an example; this all applies to the other options as well.
81     4. Since libtool seems to echo the compile commands it is issuing, the output
82        from "make" can be reduced a bit by putting "@" in front of each libtool
83        compile command.
85     5. Patch from the folks at Google for configure.in to be a bit more thorough
86        in checking for a suitable C++ installation before trying to compile the
87        C++ stuff. This should fix a reported problem when a compiler was present,
88        but no suitable headers.
90     6. The man pages all had just "PCRE" as their title. I have changed them to
91        be the relevant file name. I have also arranged that these names are
92        retained in the file doc/pcre.txt, which is a concatenation in text format
93        of all the man pages except the little individual ones for each function.
95     7. The NON-UNIX-USE file had not been updated for the different set of source
96        files that come with release 6. I also added a few comments about the C++
97        wrapper.
100    Version 6.0 07-Jun-05
101    ---------------------
103     1. Some minor internal re-organization to help with my DFA experiments.
105     2. Some missing #ifdef SUPPORT_UCP conditionals in pcretest and printint that
106        didn't matter for the library itself when fully configured, but did matter
107        when compiling without UCP support, or within Exim, where the ucp files are
108        not imported.
110     3. Refactoring of the library code to split up the various functions into
111        different source modules. The addition of the new DFA matching code (see
112        below) to a single monolithic source would have made it really too
113        unwieldy, quite apart from causing all the code to be include in a
114        statically linked application, when only some functions are used. This is
115        relevant even without the DFA addition now that patterns can be compiled in
116        one application and matched in another.
118        The downside of splitting up is that there have to be some external
119        functions and data tables that are used internally in different modules of
120        the library but which are not part of the API. These have all had their
121        names changed to start with "_pcre_" so that they are unlikely to clash
122        with other external names.
124     4. Added an alternate matching function, pcre_dfa_exec(), which matches using
125        a different (DFA) algorithm. Although it is slower than the original
126        function, it does have some advantages for certain types of matching
127        problem.
129     5. Upgrades to pcretest in order to test the features of pcre_dfa_exec(),
130        including restarting after a partial match.
132     6. A patch for pcregrep that defines INVALID_FILE_ATTRIBUTES if it is not
133        defined when compiling for Windows was sent to me. I have put it into the
134        code, though I have no means of testing or verifying it.
136     7. Added the pcre_refcount() auxiliary function.
138     8. Added the PCRE_FIRSTLINE option. This constrains an unanchored pattern to
139        match before or at the first newline in the subject string. In pcretest,
140        the /f option on a pattern can be used to set this.
142     9. A repeated \w when used in UTF-8 mode with characters greater than 256
143        would behave wrongly. This has been present in PCRE since release 4.0.
145    10. A number of changes to the pcregrep command:
147        (a) Refactored how -x works; insert ^(...)$ instead of setting
148            PCRE_ANCHORED and checking the length, in preparation for adding
149            something similar for -w.
151        (b) Added the -w (match as a word) option.
153        (c) Refactored the way lines are read and buffered so as to have more
154            than one at a time available.
156        (d) Implemented a pcregrep test script.
158        (e) Added the -M (multiline match) option. This allows patterns to match
159            over several lines of the subject. The buffering ensures that at least
160            8K, or the rest of the document (whichever is the shorter) is available
161            for matching (and similarly the previous 8K for lookbehind assertions).
163        (f) Changed the --help output so that it now says
165              -w, --word-regex(p)
167            instead of two lines, one with "regex" and the other with "regexp"
168            because that confused at least one person since the short forms are the
169            same. (This required a bit of code, as the output is generated
170            automatically from a table. It wasn't just a text change.)
172        (g) -- can be used to terminate pcregrep options if the next thing isn't an
173            option but starts with a hyphen. Could be a pattern or a path name
174            starting with a hyphen, for instance.
176        (h) "-" can be given as a file name to represent stdin.
178        (i) When file names are being printed, "(standard input)" is used for
179            the standard input, for compatibility with GNU grep. Previously
180            "<stdin>" was used.
182        (j) The option --label=xxx can be used to supply a name to be used for
183            stdin when file names are being printed. There is no short form.
185        (k) Re-factored the options decoding logic because we are going to add
186            two more options that take data. Such options can now be given in four
187            different ways, e.g. "-fname", "-f name", "--file=name", "--file name".
189        (l) Added the -A, -B, and -C options for requesting that lines of context
190            around matches be printed.
192        (m) Added the -L option to print the names of files that do not contain
193            any matching lines, that is, the complement of -l.
195        (n) The return code is 2 if any file cannot be opened, but pcregrep does
196            continue to scan other files.
198        (o) The -s option was incorrectly implemented. For compatibility with other
199            greps, it now suppresses the error message for a non-existent or non-
200            accessible file (but not the return code). There is a new option called
201            -q that suppresses the output of matching lines, which was what -s was
202            previously doing.
204        (p) Added --include and --exclude options to specify files for inclusion
205            and exclusion when recursing.
207    11. The Makefile was not using the Autoconf-supported LDFLAGS macro properly.
208        Hopefully, it now does.
210    12. Missing cast in pcre_study().
212    13. Added an "uninstall" target to the makefile.
214    14. Replaced "extern" in the function prototypes in Makefile.in with
215        "PCRE_DATA_SCOPE", which defaults to 'extern' or 'extern "C"' in the Unix
216        world, but is set differently for Windows.
218    15. Added a second compiling function called pcre_compile2(). The only
219        difference is that it has an extra argument, which is a pointer to an
220        integer error code. When there is a compile-time failure, this is set
221        non-zero, in addition to the error test pointer being set to point to an
222        error message. The new argument may be NULL if no error number is required
223        (but then you may as well call pcre_compile(), which is now just a
224        wrapper). This facility is provided because some applications need a
225        numeric error indication, but it has also enabled me to tidy up the way
226        compile-time errors are handled in the POSIX wrapper.
228    16. Added VPATH=.libs to the makefile; this should help when building with one
229        prefix path and installing with another. (Or so I'm told by someone who
230        knows more about this stuff than I do.)
232    17. Added a new option, REG_DOTALL, to the POSIX function regcomp(). This
233        passes PCRE_DOTALL to the pcre_compile() function, making the "." character
234        match everything, including newlines. This is not POSIX-compatible, but
235        somebody wanted the feature. From pcretest it can be activated by using
236        both the P and the s flags.
238    18. AC_PROG_LIBTOOL appeared twice in Makefile.in. Removed one.
240    19. libpcre.pc was being incorrectly installed as executable.
242    20. A couple of places in pcretest check for end-of-line by looking for '\n';
243        it now also looks for '\r' so that it will work unmodified on Windows.
245    21. Added Google's contributed C++ wrapper to the distribution.
247    22. Added some untidy missing memory free() calls in pcretest, to keep
248        Electric Fence happy when testing.
252    Version 5.0 13-Sep-04
253    ---------------------
255     1. Internal change: literal characters are no longer packed up into items
256        containing multiple characters in a single byte-string. Each character
257        is now matched using a separate opcode. However, there may be more than one
258        byte in the character in UTF-8 mode.
260     2. The pcre_callout_block structure has two new fields: pattern_position and
261        next_item_length. These contain the offset in the pattern to the next match
262        item, and its length, respectively.
264     3. The PCRE_AUTO_CALLOUT option for pcre_compile() requests the automatic
265        insertion of callouts before each pattern item. Added the /C option to
266        pcretest to make use of this.
268     4. On the advice of a Windows user, the lines
270          #if defined(_WIN32) || defined(WIN32)
271          _setmode( _fileno( stdout ), 0x8000 );
272          #endif  /* defined(_WIN32) || defined(WIN32) */
274        have been added to the source of pcretest. This apparently does useful
275        magic in relation to line terminators.
277     5. Changed "r" and "w" in the calls to fopen() in pcretest to "rb" and "wb"
278        for the benefit of those environments where the "b" makes a difference.
280     6. The icc compiler has the same options as gcc, but "configure" doesn't seem
281        to know about it. I have put a hack into configure.in that adds in code
282        to set GCC=yes if CC=icc. This seems to end up at a point in the
283        generated configure script that is early enough to affect the setting of
284        compiler options, which is what is needed, but I have no means of testing
285        whether it really works. (The user who reported this had patched the
286        generated configure script, which of course I cannot do.)
288        LATER: After change 22 below (new libtool files), the configure script
289        seems to know about icc (and also ecc). Therefore, I have commented out
290        this hack in configure.in.
292     7. Added support for pkg-config (2 patches were sent in).
294     8. Negated POSIX character classes that used a combination of internal tables
295        were completely broken. These were [[:^alpha:]], [[:^alnum:]], and
296        [[:^ascii]]. Typically, they would match almost any characters. The other
297        POSIX classes were not broken in this way.
299     9. Matching the pattern "\b.*?" against "ab cd", starting at offset 1, failed
300        to find the match, as PCRE was deluded into thinking that the match had to
301        start at the start point or following a newline. The same bug applied to
302        patterns with negative forward assertions or any backward assertions
303        preceding ".*" at the start, unless the pattern required a fixed first
304        character. This was a failing pattern: "(?!.bcd).*". The bug is now fixed.
306    10. In UTF-8 mode, when moving forwards in the subject after a failed match
307        starting at the last subject character, bytes beyond the end of the subject
308        string were read.
310    11. Renamed the variable "class" as "classbits" to make life easier for C++
311        users. (Previously there was a macro definition, but it apparently wasn't
312        enough.)
314    12. Added the new field "tables" to the extra data so that tables can be passed
315        in at exec time, or the internal tables can be re-selected. This allows
316        a compiled regex to be saved and re-used at a later time by a different
317        program that might have everything at different addresses.
319    13. Modified the pcre-config script so that, when run on Solaris, it shows a
320        -R library as well as a -L library.
322    14. The debugging options of pcretest (-d on the command line or D on a
323        pattern) showed incorrect output for anything following an extended class
324        that contained multibyte characters and which was followed by a quantifier.
326    15. Added optional support for general category Unicode character properties
327        via the \p, \P, and \X escapes. Unicode property support implies UTF-8
328        support. It adds about 90K to the size of the library. The meanings of the
329        inbuilt class escapes such as \d and \s have NOT been changed.
331    16. Updated pcredemo.c to include calls to free() to release the memory for the
332        compiled pattern.
334    17. The generated file chartables.c was being created in the source directory
335        instead of in the building directory. This caused the build to fail if the
336        source directory was different from the building directory, and was
337        read-only.
339    18. Added some sample Win commands from Mark Tetrode into the NON-UNIX-USE
340        file. No doubt somebody will tell me if they don't make sense... Also added
341        Dan Mooney's comments about building on OpenVMS.
343    19. Added support for partial matching via the PCRE_PARTIAL option for
344        pcre_exec() and the \P data escape in pcretest.
346    20. Extended pcretest with 3 new pattern features:
348        (i)   A pattern option of the form ">rest-of-line" causes pcretest to
349              write the compiled pattern to the file whose name is "rest-of-line".
350              This is a straight binary dump of the data, with the saved pointer to
351              the character tables forced to be NULL. The study data, if any, is
352              written too. After writing, pcretest reads a new pattern.
354        (ii)  If, instead of a pattern, "<rest-of-line" is given, pcretest reads a
355              compiled pattern from the given file. There must not be any
356              occurrences of "<" in the file name (pretty unlikely); if there are,
357              pcretest will instead treat the initial "<" as a pattern delimiter.
358              After reading in the pattern, pcretest goes on to read data lines as
359              usual.
361        (iii) The F pattern option causes pcretest to flip the bytes in the 32-bit
362              and 16-bit fields in a compiled pattern, to simulate a pattern that
363              was compiled on a host of opposite endianness.
365    21. The pcre-exec() function can now cope with patterns that were compiled on
366        hosts of opposite endianness, with this restriction:
368          As for any compiled expression that is saved and used later, the tables
369          pointer field cannot be preserved; the extra_data field in the arguments
370          to pcre_exec() should be used to pass in a tables address if a value
371          other than the default internal tables were used at compile time.
373    22. Calling pcre_exec() with a negative value of the "ovecsize" parameter is
374        now diagnosed as an error. Previously, most of the time, a negative number
375        would have been treated as zero, but if in addition "ovector" was passed as
376        NULL, a crash could occur.
378    23. Updated the files ltmain.sh, config.sub, config.guess, and aclocal.m4 with
379        new versions from the libtool 1.5 distribution (the last one is a copy of
380        a file called libtool.m4). This seems to have fixed the need to patch
381        "configure" to support Darwin 1.3 (which I used to do). However, I still
382        had to patch ltmain.sh to ensure that ${SED} is set (it isn't on my
383        workstation).
385    24. Changed the PCRE licence to be the more standard "BSD" licence.
388    Version 4.5 01-Dec-03
389    ---------------------
391     1. There has been some re-arrangement of the code for the match() function so
392        that it can be compiled in a version that does not call itself recursively.
393        Instead, it keeps those local variables that need separate instances for
394        each "recursion" in a frame on the heap, and gets/frees frames whenever it
395        needs to "recurse". Keeping track of where control must go is done by means
396        of setjmp/longjmp. The whole thing is implemented by a set of macros that
397        hide most of the details from the main code, and operates only if
398        NO_RECURSE is defined while compiling pcre.c. If PCRE is built using the
399        "configure" mechanism, "--disable-stack-for-recursion" turns on this way of
400        operating.
402        To make it easier for callers to provide specially tailored get/free
403        functions for this usage, two new functions, pcre_stack_malloc, and
404        pcre_stack_free, are used. They are always called in strict stacking order,
405        and the size of block requested is always the same.
407        The PCRE_CONFIG_STACKRECURSE info parameter can be used to find out whether
408        PCRE has been compiled to use the stack or the heap for recursion. The
409        -C option of pcretest uses this to show which version is compiled.
411        A new data escape \S, is added to pcretest; it causes the amounts of store
412        obtained and freed by both kinds of malloc/free at match time to be added
413        to the output.
415     2. Changed the locale test to use "fr_FR" instead of "fr" because that's
416        what's available on my current Linux desktop machine.
418     3. When matching a UTF-8 string, the test for a valid string at the start has
419        been extended. If start_offset is not zero, PCRE now checks that it points
420        to a byte that is the start of a UTF-8 character. If not, it returns
421        PCRE_ERROR_BADUTF8_OFFSET (-11). Note: the whole string is still checked;
422        this is necessary because there may be backward assertions in the pattern.
423        When matching the same subject several times, it may save resources to use
424        PCRE_NO_UTF8_CHECK on all but the first call if the string is long.
426     4. The code for checking the validity of UTF-8 strings has been tightened so
427        that it rejects (a) strings containing 0xfe or 0xff bytes and (b) strings
428        containing "overlong sequences".
430     5. Fixed a bug (appearing twice) that I could not find any way of exploiting!
431        I had written "if ((digitab[*p++] && chtab_digit) == 0)" where the "&&"
432        should have been "&", but it just so happened that all the cases this let
433        through by mistake were picked up later in the function.
435     6. I had used a variable called "isblank" - this is a C99 function, causing
436        some compilers to warn. To avoid this, I renamed it (as "blankclass").
438     7. Cosmetic: (a) only output another newline at the end of pcretest if it is
439        prompting; (b) run "./pcretest /dev/null" at the start of the test script
440        so the version is shown; (c) stop "make test" echoing "./RunTest".
442     8. Added patches from David Burgess to enable PCRE to run on EBCDIC systems.
444     9. The prototype for memmove() for systems that don't have it was using
445        size_t, but the inclusion of the header that defines size_t was later. I've
446        moved the #includes for the C headers earlier to avoid this.
448    10. Added some adjustments to the code to make it easier to compiler on certain
449        special systems:
451          (a) Some "const" qualifiers were missing.
452          (b) Added the macro EXPORT before all exported functions; by default this
453              is defined to be empty.
454          (c) Changed the dftables auxiliary program (that builds chartables.c) so
455              that it reads its output file name as an argument instead of writing
456              to the standard output and assuming this can be redirected.
458    11. In UTF-8 mode, if a recursive reference (e.g. (?1)) followed a character
459        class containing characters with values greater than 255, PCRE compilation
460        went into a loop.
462    12. A recursive reference to a subpattern that was within another subpattern
463        that had a minimum quantifier of zero caused PCRE to crash. For example,
464        (x(y(?2))z)? provoked this bug with a subject that got as far as the
465        recursion. If the recursively-called subpattern itself had a zero repeat,
466        that was OK.
468    13. In pcretest, the buffer for reading a data line was set at 30K, but the
469        buffer into which it was copied (for escape processing) was still set at
470        1024, so long lines caused crashes.
472    14. A pattern such as /[ab]{1,3}+/ failed to compile, giving the error
473        "internal error: code overflow...". This applied to any character class
474        that was followed by a possessive quantifier.
476    15. Modified the Makefile to add libpcre.la as a prerequisite for
477        libpcreposix.la because I was told this is needed for a parallel build to
478        work.
480    16. If a pattern that contained .* following optional items at the start was
481        studied, the wrong optimizing data was generated, leading to matching
482        errors. For example, studying /[ab]*.*c/ concluded, erroneously, that any
483        matching string must start with a or b or c. The correct conclusion for
484        this pattern is that a match can start with any character.
487    Version 4.4 13-Aug-03
488    ---------------------
490     1. In UTF-8 mode, a character class containing characters with values between
491        127 and 255 was not handled correctly if the compiled pattern was studied.
492        In fixing this, I have also improved the studying algorithm for such
493        classes (slightly).
495     2. Three internal functions had redundant arguments passed to them. Removal
496        might give a very teeny performance improvement.
498     3. Documentation bug: the value of the capture_top field in a callout is *one
499        more than* the number of the hightest numbered captured substring.
501     4. The Makefile linked pcretest and pcregrep with -lpcre, which could result
502        in incorrectly linking with a previously installed version. They now link
503        explicitly with libpcre.la.
505     5. configure.in no longer needs to recognize Cygwin specially.
507     6. A problem in pcre.in for Windows platforms is fixed.
509     7. If a pattern was successfully studied, and the -d (or /D) flag was given to
510        pcretest, it used to include the size of the study block as part of its
511        output. Unfortunately, the structure contains a field that has a different
512        size on different hardware architectures. This meant that the tests that
513        showed this size failed. As the block is currently always of a fixed size,
514        this information isn't actually particularly useful in pcretest output, so
515        I have just removed it.
517     8. Three pre-processor statements accidentally did not start in column 1.
518        Sadly, there are *still* compilers around that complain, even though
519        standard C has not required this for well over a decade. Sigh.
521     9. In pcretest, the code for checking callouts passed small integers in the
522        callout_data field, which is a void * field. However, some picky compilers
523        complained about the casts involved for this on 64-bit systems. Now
524        pcretest passes the address of the small integer instead, which should get
525        rid of the warnings.
527    10. By default, when in UTF-8 mode, PCRE now checks for valid UTF-8 strings at
528        both compile and run time, and gives an error if an invalid UTF-8 sequence
529        is found. There is a option for disabling this check in cases where the
530        string is known to be correct and/or the maximum performance is wanted.
532    11. In response to a bug report, I changed one line in Makefile.in from
534            -Wl,--out-implib,.libs/lib@WIN_PREFIX@pcreposix.dll.a \
535        to
536            -Wl,--out-implib,.libs/@WIN_PREFIX@libpcreposix.dll.a \
538        to look similar to other lines, but I have no way of telling whether this
539        is the right thing to do, as I do not use Windows. No doubt I'll get told
540        if it's wrong...
543    Version 4.3 21-May-03
544    ---------------------
546    1. Two instances of @WIN_PREFIX@ omitted from the Windows targets in the
547       Makefile.
549    2. Some refactoring to improve the quality of the code:
551       (i)   The utf8_table... variables are now declared "const".
553       (ii)  The code for \cx, which used the "case flipping" table to upper case
554             lower case letters, now just substracts 32. This is ASCII-specific,
555             but the whole concept of \cx is ASCII-specific, so it seems
556             reasonable.
558       (iii) PCRE was using its character types table to recognize decimal and
559             hexadecimal digits in the pattern. This is silly, because it handles
560             only 0-9, a-f, and A-F, but the character types table is locale-
561             specific, which means strange things might happen. A private
562             table is now used for this - though it costs 256 bytes, a table is
563             much faster than multiple explicit tests. Of course, the standard
564             character types table is still used for matching digits in subject
565             strings against \d.
567       (iv)  Strictly, the identifier ESC_t is reserved by POSIX (all identifiers
568             ending in _t are). So I've renamed it as ESC_tee.
570    3. The first argument for regexec() in the POSIX wrapper should have been
571       defined as "const".
573    4. Changed pcretest to use malloc() for its buffers so that they can be
574       Electric Fenced for debugging.
576    5. There were several places in the code where, in UTF-8 mode, PCRE would try
577       to read one or more bytes before the start of the subject string. Often this
578       had no effect on PCRE's behaviour, but in some circumstances it could
579       provoke a segmentation fault.
581    6. A lookbehind at the start of a pattern in UTF-8 mode could also cause PCRE
582       to try to read one or more bytes before the start of the subject string.
584    7. A lookbehind in a pattern matched in non-UTF-8 mode on a PCRE compiled with
585       UTF-8 support could misbehave in various ways if the subject string
586       contained bytes with the 0x80 bit set and the 0x40 bit unset in a lookbehind
587       area. (PCRE was not checking for the UTF-8 mode flag, and trying to move
588       back over UTF-8 characters.)
591  Version 4.2 14-Apr-03  Version 4.2 14-Apr-03
592  ---------------------  ---------------------

Removed from v.67  
changed lines
  Added in v.83

  ViewVC Help
Powered by ViewVC 1.1.5