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
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.