I hate inline POD. It distracts from the code, and occupies
far too much screen space due to the paragraph oriented
syntax, combined with the low level granularity of the markup
(e.g., try making up a bulleted list of arguments for a
given function - you don't see the function anymore, it's
Personally, I am much in favor of the solution of Lisp
and Python: the docstring. In this approach, the first
comment after the function definition is taken as documentation
for the function. Because of this, code browsers can extract
the documentation for the function easily.
Brainbench MVP for Perl
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||