I vote for using
#s as I've stated
elsewhere under the heading no pod & code.
Personally I find the desire or need to temporarily
comment out
fair sized blocks of
code is a warning of impending danger or difficulty.
And usually these style of comments are meant to be
temporary. Often the trouble is so imminent that it
has already arrived.
Requiring commented code to be compilable seems like a
feature to me. But I know what you mean.
Quick update: The following is not what Abigail
said. Abigail pointed out that you can't comment the
entire BEGIN block this way. You can't. You
can't comment out any other subroutine definition either.
Or forward sub declaration.
And you can comment out code in a begin block. Viz:
#!/usr/bin/perl
use strict;
use warnings;
BEGIN { use constant COMMENT => 0; }
BEGIN {
if ( COMMENT ){
print "silence\n";
}
print "noise\n";
}
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.