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!
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.
For example, I was thinking
about writing a little test system to see how a
module such as File::Slurp handles
a full filesystem. Perhaps I could write something
like File::Slurp::Failover, which would do the clever
nfs failover trick.
By the way, File::Slurp has some
options for error handling. Perhaps it could
be used as an example of a good way to handle
I/O errors. Or is there a better example of a
module that has good I/O error handling?
It should work perfectly the first time! - toma
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.