I agree fully that pod is insufficient for so many things that it is currently being used for. Thanks for raising the issue. My solution would have been different, but I think you've taken a step in the right direction. I hope the next generation of perldoc, has two discrete functions: the first to comment code, the second to provide tutorials, and howtos. I think the code-comments should be reserved largely for notes that help developers -- what is traditionally a "comment" in other language. The latter function should be something that is heavily dependent on community, internet access, and frozen state wiki concepts. Something kind of like a remote repository of texttile documents, that you can pull from, edit and push back to. With cpan being a web interface frontent to it. I'm still thinking about how this should be done, something with XMLRPC, and some VCS voodoo seems to be the way to go.
Evan Carroll
www.EvanCarroll.com
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.