I do not agree with Postel: "be conservative" in what you accept, too. Otherwise you have just made a too-generalized promise to anyone who shows up that, somehow, you will do the right thing with anything they offer. My point being that I could never "desk check" YOUR code, unless I could somehow comb the universe to discover each and every call. The "correct" operation of this code as written depends on the "correctness" of every possible caller – and could offer no assistance at all in detecting that a bug existed in any of them. Of course, "realizing that a bug exists" is always the first hurdle, and "determining where it is" is the second. Maybe i would rewrite Postel's rule as: "be suspicious as hell, because if you don't catch the CALLER'S bug, no one will."
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.