The nuclear power plant software looks like it is written in VB, but it might be MFC. That, along with Flash and Crystal Reports. I hope you feel confident about that!

BOOM !!!!!!!!!!!!!!!!!

For the necessity of testing, I was thinking of the earlier example of the failover of a full nfs filesystem to a new one. That seems like a fair amount of code, and if I wrote it, I would need to test it.

Ah yes - I see what you mean. For really critical things I can't see any way round it - generally I assume that any failure from a print is serious enough to switch fs and log whatever was in $!. As you say, it's vitally important that the error handling code does get run before it goes live :)

Thanks for the info on File::Slurp - I'll have to check it out. No doubt there are modules with good I/O handling on CPAN but I couldnt tell you off hand - another thing to add to my todo list :)

So I'm going to go off, do a bit more research, and hopefully come back to the monastery with an article and maybe some code for review. Give me a few days and I'll be back :)


In reply to Re: Re: Re: Re: <rant>CPAN modules failing to check for write errors</rant> by Anonymous Monk
in thread <rant>CPAN modules failing to check for write errors</rant> by Anonymous Monk

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.