I wrote one a few years back that just dumps a bunch of Pod stubs into a given script (if it has no Pod currently). It's primitive but saves typing. You could do the same in 15 minutes, no doubt. What I might try to do (or maybe someone else as I'm swamped) is do a deeper one that perhaps uses PPI and version and such and only fills out the missing parts alla Perl::Critic's "brutal" recommendations and put it up on the CPAN as a script. Though, adding stubs for subs could actually be seen as a problem. If you did that, your Test::Pod::Coverage tests would pass even though there was really no documentation for the subs, just naked =item listings.
A command line script to do this should allow for things like --inline (versus after __END__), --license, and the other sorts of things that might keep people from using it because it rubbed against the grain of their personal styles.
In reply to Re: Autogenerated Code Docs
by Your Mother
in thread Autogenerated Code Docs
by pileofrogs
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |