I hadn't even noticed it produced a warning. Which was at the very start of the TAP output, while the end of the TAP output indicated that all tests passed.

Test::NoWarnings does the trick, than you :o)
I tried to turn warnings to fatal with

use warnings qw(FATAL all);
as indicated here using FATAL warnings, but it didn't work. It might/could be because of Windows, who doesn't like signals? I'm guessing that FATAL is maybe catching the WARN signal and making it die. But in Windows i found i couldn't catch any signals. It doesn't really matter for me right now : Test::NoWarnings works. Cheers!

PS : the problem was wider than i thought : 1>undef also returns true. Which means that any cmp_ok($got, '<', $expected) statement runs into the same risk / problem.
I'll add this to the first post.


In reply to Re^2: 0==undef, that's annoying. Is it? by mascip
in thread 0==undef, that's annoying. Is it? by mascip

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.