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
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!use warnings qw(FATAL all);
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
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |