X-Git-Url: http://git.vpit.fr/?a=blobdiff_plain;f=README;h=c123f9791edf7a4b1331551141f792be49c986f5;hb=acae07cb4264d1039a86aa31854cca2ce37382f1;hp=6a1b258ff8a11f31ad06e755b48be94453a71ad4;hpb=f6f6b610f4471652428707ae0203563eae291669;p=perl%2Fmodules%2FTest-Valgrind.git

diff --git a/README b/README
index 6a1b258..c123f97 100644
--- a/README
+++ b/README
@@ -2,7 +2,7 @@ NAME
     Test::Valgrind - Test Perl code through valgrind.
 
 VERSION
-    Version 0.051
+    Version 0.07
 
 SYNOPSIS
         use Test::More;
@@ -77,20 +77,23 @@ CAVEATS
     You can't use this module to test code given by the "-e" command-line
     switch.
 
-    Results will most likely be better if your perl is built with debugging
+    Perl 5.8 is notorious for leaking like there's no tomorrow, so the
+    suppressions are very likely not to be very accurate on it. Anyhow,
+    results will most likely be better if your perl is built with debugging
     enabled. Using the latest valgrind available will also help.
 
     This module is not really secure. It's definitely not taint safe. That
     shouldn't be a problem for test files.
 
-    If your tests output to STDERR, everything will be eaten in the process.
-    In particular, running this module against test files will obliterate
-    their original test results.
+    What your tests output to STDOUT is eaten unless you pass the "diag"
+    option, in which case it will be reprinted as diagnostics. STDERR is
+    kept untouched.
 
 DEPENDENCIES
     Valgrind 3.1.0 (<http://valgrind.org>).
 
-    Carp, POSIX (core modules since perl 5) and Test::More (since 5.6.2).
+    Carp, Fcntl, POSIX (core modules since perl 5) and Test::Builder (since
+    5.6.2).
 
     Perl::Destruct::Level.