X-Git-Url: http://git.vpit.fr/?a=blobdiff_plain;f=lib%2FTest%2FLeaner.pm;h=14cb2421dcfa619328be55b25334f34112c707d5;hb=0a0b6b3837e088a72ac0aabac8644e3360269c13;hp=8a41e4e8ee39c3f6a424d0f929c62bef79c4c5af;hpb=7b053442294016a9ce8e27a3bd424a4a6f829862;p=perl%2Fmodules%2FTest-Leaner.git

diff --git a/lib/Test/Leaner.pm b/lib/Test/Leaner.pm
index 8a41e4e..14cb242 100644
--- a/lib/Test/Leaner.pm
+++ b/lib/Test/Leaner.pm
@@ -45,11 +45,21 @@ L</pass>, L</fail>, L</ok>, L</is>, L</isnt>, L</like>, L</unlike> and L</cmp_ok
 
 =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>).
+
+=item *
+
 L</cmp_ok> throws an exception if the given operator isn't a valid Perl binary operator (except C<'='> and variants).
 It also tests in scalar context, so C<'..'> will be treated as the flip-flop operator and not the range operator.
 
 =item *
 
+L</is_deeply> doesn't guard for memory cycles.
+If the two first arguments present parallel memory cycles, the test may result in an infinite loop.
+
+=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.
 
 =item *
@@ -491,7 +501,9 @@ sub _deep_check {
 
  if ($ry eq 'ARRAY') {
   if ($#$x == $#$y) {
-   _deep_check($x->[$_], $y->[$_]) or return 0 for 0 .. $#$y;
+   # Prevent vivification of deleted elements by fetching the array values.
+   my ($ex, $ey);
+   _deep_check($ex = $x->[$_], $ey = $y->[$_]) or return 0 for 0 .. $#$x;
    return 1;
   }
  } elsif ($ry eq 'HASH') {