From my prospective, it is more important to remember that
books on style and practices are meant as general guidelines,
they are not laws of nature that always remain true.
Writing programs is too complex an endeavor to conveniently fit
into methods of right an wrong (tm) : after all; how
do you know which of the (possibly conflicting) qualities are important
to me, how do you know my (partially contradictory) goals, and how
do you know my present constrains? You have no way of knowing.
It would be nice to simply follow rules. Does this work,
in each an every case? For rules must work in every case;
otherwise, I cannot stay confident whether this rule
will lead to harm or profit.
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.