Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Almost all of my modules are written with inline POD because I believe it’s very important for the documentation to be next to the code, but if you’ve worked on a codebase for any length of time, that POD quickly becomes annoying. The following will fold your POD out of the way

    … so what you’re saying is it’s so important for POD to be next to the code that you want a way to make it go away so that it will be less annoying that it’s there. I see. :-)

    Personally I prefer P

    • I also prefer the it at the end. I think inline Pod is annoying and it also creates an overhead in the parser. We had mixed Pod in my previous $job. Some were inline some were after the __END__ I wish adding them after __END__ was in the coding standards :) But, anyway there are far more annoying things in the actual code of other people other than Pod...