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
:-)
--Larry Wall in <1991May31.181659.28817@jpl-devvax.jpl.nasa.gov>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Strictly speaking… (Score:1)
… POD commands are supposed to go in a paragraph of their own, ie. you are supposed to have a blank line above and below every
=fooline.Reply to This
Re: (Score:2)
Is this for technical or conventional reasons? I do recall that there were some older POD parsers that had issues with there not being a newline after the final =cut (yeah, that was real fun to debug), but I don't think that such an artifact is a good reason to disregard jplindstrom's proposal.
Re: (Score:1)
That’s how POD is specified [perl.org]. Interestingly, I see now that
=cutis exempt from this rule, at least insofar as it doesn’t have to be followed by a blank line.(This rule that POD is broken down paragraph-wise for processing is why Perl 5 POD is so terribly verbose for marking up lists, which is why I have stopped using POD as my personal document markup of choice and soon afterwards switched to Markdown, btw. I hear POD6 is going to do this much better.)