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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.69  
changed lines
  Added in v.85

  ViewVC Help
Powered by ViewVC 1.1.5