One of my favorite goals which appears to sum up several of the more
specific ones stated earlier (simple to state but not so simple to implement):
A program should always gracefully survive even the worst data.
Whether it carries on unperturbed with a warning message in a log, or dies but
clearly spells out why (and does not frag the disk), will depend on the
specific nature of the application. I was reminded of this today while
trying to load a corrupt spreadsheet into Excel (which breaks all the rules 8-( ).
I'd like to be able to assign to an luser
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||