Is there any reason to use printf instead of warn for diagnostics?
If I use
warn then it gets output to the screen every time it gets executed in
make test - creating a deluge of noise to sift through.
If I use
printf then I can quietly fiddle about with pieces of code and see what's going on, and then not be slugged with the deluge if I run
make test.
To that extent, it's working perfectly ... the only problem is that TAP::Harness likes to give me misleading messages that I don't really understand.
It's just a practice I engage in as a convenience thing during debugging, and such
printf statements are not something that I'll (intentionally ;-) include in a CPAN release.
I don't regard this TAP::Harness behaviour as a big issue ... but I'm a little curious about it.
Cheers,
Rob
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.