If the code compiles, I often just wrap it in
if (0) { ... }. If it doesn't and you're commenting it out temporarily, using the POD style is your best bet; just keep in mind that it will feel a little awkward. If it's commented out longer-term, I would put
# at the beginning of all the lines, as it's less likely to confuse people (including you!) looking at the code later. Hopefully your editor makes
#-ing out a bunch of lines pretty painless; if not I might consider using POD format anyways.
That's just my personal style; I'm sure there are other ways of doing things with their own advantages and disadvantages.
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, details, 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, summary, 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.