more useful options | |
PerlMonks |
Re: <rant>CPAN modules failing to check for write errors</rant>by jepri (Parson) |
on May 29, 2004 at 11:34 UTC ( [id://357450]=note: print w/replies, xml ) | Need Help?? |
I think you have the right of it, but there is no central authority that can force coders to do anything. That's the downside to the whole community coding thing. I think a lot of authors ignore print failures because they program on Unix, and on Unix if you have a valid file handle you can write to it. But checking your opens is pretty poor form, I'll agree. OTOH, I find it pretty annoying when a module throws a die. It means I have to wrap it in an eval rather than just check the return code. If you choose to write an article, why not submit it directly to perl.com or even post it here? I hear a few CPAN authors are members of PerlMonks The CPAN authors I've talked with have been fairly sympathetic to adding additional error checking. I suspect it's a bit of the omniscent author problem - the author knows hir code so well that error messages aren't really needed. It's actually quite hard to write good error messages for people who don't know what your code does. Perhaps it is time to start a new perl meme for CPAN authors :)
In Section
Meditations
|
|