IMHO, the difference, I think, between professional publications and Perl programming is that the professional associations don't have a culture that states "TMTOWTDI". But that is precisely what makes this question interesting to me:
- Since any comment style that the reader can comprehend is "acceptable", we are clearly straining at gnats. This is ok, because the camel is on my desk, not in my coffee cup. :)
- If we all agree that this is a preference issue, the problem is equivalent to "What style is easiest to understand?" And, reading your preferences provides me with useful information about what people like/dislike.
Having said this, perhaps I need to initiate a poll...
-papidave
-
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.
|
