On 8 Jun 2007, at 01:14, Joshua ben Jore wrote:
On 6/7/07, Eric Wilhelm <[EMAIL PROTECTED]> wrote:
I've never seen the benefit of pod after __END__. IMO, your code and
docs should follow the same order/groupings. That, and you have to
It has two benefits. Separating code from pod prevents it from being
wholely unreadable without syntax highlighting. I ran into this face
first once while trying to read CPAN code or something similar through
a browser. I ended up mistaking code in pod for real code and mostly
it was pretty unpleasant.
[snip]
I'll be annoying and just go with "it depends"!
If I have a whole bunch of public subroutines that I can have in a
reasonable order for reading I'll inline the POD. I find it helps to
have it nearby. That Knuth bloke and his literate programming wasn't
completely nuts in my opinion :-)
When I have a bunch of private subroutines, or the sensible code
order doesn't match the sensible reading order, I'll stick it all at
the end.
Sometimes I'll switch back and forth a few times as I refactor.
Adrian