Excellent! Assuming some degree of 'act togetherness', when ready I'll post an article on PM incorporating both suggestions...
--hsm > -----Original Message----- > From: Andy Lester [mailto:[EMAIL PROTECTED] > Sent: Monday, August 16, 2004 8:50 AM > To: [EMAIL PROTECTED] > Cc: Hugh S. Myers; 'Simon Cozens'; [EMAIL PROTECTED] > Subject: Re: Where do people learn how to document a module? > > On Mon, Aug 16, 2004 at 10:26:51AM -0400, Randy W. Sims (ml- > [EMAIL PROTECTED]) wrote: > > Pod::Coverage might be usefull. I think it provides a way to list all > > undocumented subs which in the case of the script you're talking about > > would be all non-private subs. Using it would guarantee that the pod > > generated by your script would rate as 100% covered. > > Further, you can use Test::Pod::Coverage to put that testing in your > test suite for your module, with a simple 4-line script: > > t/pod-coverage.t > > #!perl -T > > use Test::More; > eval "use Test::Pod::Coverage 1.04"; > plan skip_all => "Test::Pod::Coverage 1.04 required for testing POD > coverage" if $@; > all_pod_coverage_ok(); > > That way, you can't add a function without forgetting to write POD for > it: Your test suite will fail without it. > > xoa > > -- > Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
