ok $exp eq $got or diag explain [$exp, $got];
Yeah, that's not a bad idea.
I don't get much sense from " or diag explain [$exp, $got]" when the variables are Math::MPFR objects:
C:\>perl -MMath::MPFR -MTest::More -e "$got=Math::MPFR->new(2); $exp=
+Math::MPFR->new(2); ok($got != $exp) or diag explain [$exp, $got]; d
+one_testing();"
not ok 1
# Failed test at -e line 1.
# [
# bless( do{\(my $o = 46472664)}, 'Math::MPFR' ),
# bless( do{\(my $o = 46474008)}, 'Math::MPFR' )
# ]
1..1
# Looks like you failed 1 test of 1.
but I could instead use something like or warn "$got == $expected" to provide a more meaningful diagnostic.
There's probably quite a few places in my test scripts where this blow-up could occur, but the blow-up only happens with the overloaded "!=" operator, and then only if the test fails.
Cheers, Rob
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|