> but using POD for this is better than what you have
The debugger perl5db.pl is a good counterexample to this thesis.
It has a big command loop where the users input is read and the documentation for each command is interspersed for each command section.
The documentation will show up in the same order like programmed and must stay at this chronological position.
This makes refactoring the code extremely difficult. Frankly it's a PITA.
I'm a fan of interspersed function docs with POD, but
- only use it for external documentation.
- don't make code position dependend on it
- remember subs can be moved, linear code normally can't
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, 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, 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.
|
|
