Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re^2: Multi-line comments in perl code?

by xdg (Monsignor)
on Jul 14, 2006 at 13:45 UTC ( #561213=note: print w/ replies, xml ) Need Help??


in reply to Re: Multi-line comments in perl code?
in thread Multi-line comments in perl code?

Among other things, POD does not support indentation

Sure it does -- in a Pod format block.

=begin someformat This comment can be indented as much as I want =end someformat =cut

That said, I agree otherwise with your point that Perl doesn't support multi-line comments. Pod can be used for multi-line comments, but Perl and Pod are really two separate languages that can live in the same file. The Perl parser and Pod parsers just choose to pay attention to different languages.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.


Comment on Re^2: Multi-line comments in perl code?
Download Code
Re^3: Multi-line comments in perl code?
by dimar (Curate) on Jul 14, 2006 at 16:24 UTC
    Among other things, POD does not support indentation
    Sure it does -- in a Pod format block.

    Perhaps, but that particular definition of "indentation" is ... shall we say, a lot more 'loose' than the originally intended definition, which can be illustrated as follows:

    =for comment This comment can be indented as much as I want and even more than I want =cut for(0 .. 4){ for(0 .. 3){ for (0 .. 2){ =for comment However, even though "indentation" is supported here, we still have those dangling POD delimiters way back over there. <- <- <- <- Attempting to line them up with the rest of the code produces an error. This is not good because it breaks 'code-folding' in the text editor. It also looks just plain ugly. =cut print "$_\n"; }; }; }; __END__

    Moreover, one has to consider whether the POD in this illustration is even well-formed to begin with. Should this be a format block? Will begin/end work? Is 'for comment' sufficient? Will this mess up the POD documentation? *Way* too much hassle when all you wanted was a *comment*.

      Now I understand what you meant. "Supports" is a vague term. I would have said instead that Pod commands can't be indented, which breaks up the indentation of code around it.

      Personally, I use vim and let it handle my comments for me.

      -xdg

      Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://561213]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (4)
As of 2014-07-31 02:14 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (244 votes), past polls