"be consistent" | |
PerlMonks |
Re^6: Comment blocks & private methods (update: indentation)by LanX (Saint) |
on Dec 12, 2014 at 17:15 UTC ( [id://1110195]=note: print w/replies, xml ) | Need Help?? |
I like the empty =for solution b/c it's concise (only four letters¹) and backwards compatible and you can easily extend it by adding a format. Though as long as it's not documented some pod-parser might fail if no format is given. I think Larry might not like them cause /* ... */ might be easily overlooked and therfore people tend to indent the text in between. > (when you get used to POD containing useless code, you may ignore perfectly useful documentation embeded in the code) POD is rarely interspersed like in literal programming, and personally I never tend to ignore it more then comments. Take a look into perl5db.pl as an example.
Cheers Rolf (addicted to the Perl Programming Language and ☆☆☆☆ :) ¹) With Python needing 3 doublequotes """ this seems a compatative solution.
updateThough POD fails if you need to adjust to surrounding indentation. There is a reason why one should always look up older discussions. ;)
In Section
Seekers of Perl Wisdom
|
|