I appreciate what you're saying here (and I did read it slowly and carefully :) ). There's another off topic discussion about the need to standardize aspects of communication via refereed journals. In the ACS and APA examples, the reference standards allow anyone (who knows the standards) to easily go and look up the references, and are part of the rules to publish in journals governed by these bodies. (Theoretically, depending on your library, access to materials, you know.) Same thing applies to standardization of communication protocols, etc. Again, these were examples that I had on the top of my head. Perl is great due to TIMTOWTDI, and there is no reason to change it, or to change comments. :)
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|