Many will notice that I was clever enough not to suggest
how this might be done. Having looked over the
comments, I agree that POD or some other standard would
be great, however these ideas would all rely on the person entering
the code to do work, and so far few do so. Perhaps they
feel that since it is posted under their name they don't
need further identification.
Ideally I'd still like a simple one line comment as I
suggested originally, which would either be the first line
or follow the #! line if it exists. This would ensure
that all downloaded code would have at least minimal
identification (sufficient to track down additional info). If not, then
fundflow's idea is a good alternative. Since
the Monastery already has this information, why rely on
lazy humans? ;-)
Update: In keeping with my theme of giving credit, my apologies
to BastardOperator for not reading to the end of his
node above where he already mentioned automation.
I blame society for my short attention span!
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, 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, 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.
|
|