Another POD typo

[perl/modules/Test-Leaner.git] / lib / Test / Leaner.pm

diff --git a/lib/Test/Leaner.pm b/lib/Test/Leaner.pm
index 3881656a12072c805d26a254e09d5de8d38b1069..8a09c2948cfb004a9865010dd2e5f431218497c1 100644 (file)
--- a/lib/Test/Leaner.pm
+++ b/lib/Test/Leaner.pm
@@ -10,11 +10,11 @@ Test::Leaner - A slimmer Test::More for when you favor performance over complete
 
 =head1 VERSION
 
-Version 0.01
+Version 0.02
 
 =cut
 
-our $VERSION = '0.01';
+our $VERSION = '0.02';
 
 =head1 SYNOPSIS
 
@@ -41,12 +41,12 @@ However, L</ok> honors C<'bool'> overloading, L</is> and L</is_deeply> honor C<'
 
 =item *
 
-L</pass>, L</fail>, L</ok>, L</is>, L</isnt>, L</like>, L</unlike> and L</cmp_ok> are all guaranteed to return the truth value of the test.
+L</pass>, L</fail>, L</ok>, L</is>, L</isnt>, L</like>, L</unlike>, L</cmp_ok> and L</is_deeply> are all guaranteed to return the truth value of the test.
 
 =item *
 
 L</like> and L</unlike> don't special case regular expressions that are passed as C<'/.../'> strings.
-A string regexp argument is always treated as a the source of the regexp, making C<like $text, $rx> and C<like $text, qr[$rx]> equivalent to each other and to C<cmp_ok $text, '=~', $rx> (and likewise for C<unlike>).
+A string regexp argument is always treated as the source of the regexp, making C<like $text, $rx> and C<like $text, qr[$rx]> equivalent to each other and to C<cmp_ok $text, '=~', $rx> (and likewise for C<unlike>).
 
 =item *
 
@@ -61,6 +61,7 @@ If the two first arguments present parallel memory cycles, the test may result i
 =item *
 
 The tests don't output any kind of default diagnostic in case of failure ; the rationale being that if you have a large number of tests and a lot of them are failing, then you don't want to be flooded by diagnostics.
+Moreover, this allows a much faster variant of L</is_deeply>.
 
 =item *
 
@@ -120,7 +121,7 @@ our @EXPORT = qw<
 =head2 C<PERL_TEST_LEANER_USES_TEST_MORE>
 
 If this environment variable is set, L<Test::Leaner> will replace its functions by those from L<Test::More>.
-Moreover, the symbols that are imported you C<use Test::Leaner> will be those from L<Test::More>, but you can still only import the symbols originally defined in L<Test::Leaner> (hence the functions from L<Test::More> that are not implemented in L<Test::Leaner> will not be imported).
+Moreover, the symbols that are imported when you C<use Test::Leaner> will be those from L<Test::More>, but you can still only import the symbols originally defined in L<Test::Leaner> (hence the functions from L<Test::More> that are not implemented in L<Test::Leaner> will not be imported).
 If your version of L<Test::More> is too old and doesn't have some symbols (like L</note> or L</done_testing>), they will be replaced in L<Test::Leaner> by croaking stubs.
 
 This may be useful if your L<Test::Leaner>-based test script fails and you want extra diagnostics.
@@ -179,6 +180,7 @@ if ($ENV{PERL_TEST_LEANER_USES_TEST_MORE}) {
 
  my $import = sub {
   shift;
+
   my @imports = &_handle_import_args;
   @imports = @EXPORT unless @imports;
   my @test_more_imports;
@@ -191,7 +193,10 @@ if ($ENV{PERL_TEST_LEANER_USES_TEST_MORE}) {
     *{$pkg."::$_"} = $leaner_stash->{$_};
    }
   }
+
   my $test_more_import = 'Test::More'->can('import');
+  return unless $test_more_import;
+
   @_ = (
    'Test::More',
    @_,
@@ -201,6 +206,7 @@ if ($ENV{PERL_TEST_LEANER_USES_TEST_MORE}) {
    lock $plan if THREADSAFE;
    push @_, 'no_diag' if $no_diag;
   }
+
   goto $test_more_import;
  };