There was a thread at
Inline POD vs. EOF POD a while ago about the
joys of inline versus eof POD. While a lot of people seemed
to like inline, my strong sympathies go with the position
put forth by
tye and
Abigail that eof is better for
POD.
In particular I liked Abigail's explanation
of why inline is a problem. To it I can only add the point
that synchronization of POD and code should be far less of
a problem than synchronization of general comments and code.
The POD is about the public interface. Public interfaces
should not be changed as capriciously as code. If you
do change them, you need to track down all of the code that
used the old interface and change that as well. Compared
to that synchronization, modifying the POD is a small
cost.
Comments that need synchronization with code for me go
inline. There your point about distance is relevant. But
I strongly prefer having POD at the end of the file.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.