"Imagine if instead of this, you had something like:"The beginning of your reply precisely illustrates why this isn't a great idea for POD - your anchor got mangled entirely and does not (or at least originally didn't) point anywhere.
"And when you mousever the keys, you get a brief explanation of the parameter"
I am not seeing this mouseover effect under SCO... all I get is the "code snippet" gray thing. Can you elaborate what are you referring to?
In any case by "perlish documentation practices" I meant "knows how POD works", not any particular specifics. For example this is how some of the APIs within DBIC are documented (this is the most prevalent, but not consistent throughout style, the project is definitely open to suggestions how to do it better).
TL;DR: I don't think the wording perlish documentation practices is really that far off.
In reply to Re^3: The problem of documenting complex modules.
by ribasushi
in thread The problem of documenting complex modules.
by BrowserUk
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |