The only time I get that message is when the file in the message has no pod, but sometimes I have to read the path twice to realize which file is offending.

Phil

I guess what I ought to do then, is go ahead and post this to CPAN, so others can take a look. It seems crazy to post a 400 line module to a web form. I'm afraid my test data is still proprietary data from the group which asked me to write this. Before this gets published for real, I was going to scramble that data for the public. But as this module is designed to interact with web services hosted elsewhere, it takes over 15 minutes to run a test suite with fewer than 60 test cases. Its the data they wanted to see work, but CPAN probbaly deserves a more thoughtful test suite and set of test cases.

-- Hugh

if( $lal && $lol ) { $life++; }

It seems crazy to post a 400 line module to a web form

nothing wrong with that -- you'll find longer around here .. you can edit your OP -- just be sure use <readmore><code> ... </code></readmore> tags

you might even get some code review comments in the process ;)

First, you should skip everything in pod-coverage.t if the user doesn't have Test::Pod::Coverage. Plain and simple, that's primarily for you - no one other than CPAN module contributors is likely to have Test::Pod::Coverage, which of CPAN consumers, is a small percentage. i.e.

use strict;
use warnings;

use Test::More;
eval { use Test::Pod::Coverage qw( no_plan ); };
if( @$ ){
  plan skip_all
    => 'Test::Pod::Coverage required for testing POD coverage';
}
# ...
[download]

Second, everything needs to be documented when testing pod coverage. I forget the details, but I think 95% pod coverage (all public methods, but no private methods) still resulted in a failure last time I ran a pod-coverage.t file on a suite of my recent modules. (And I just checked the docs, no mention of honoring prefixing private methods with underbars.) So I POD'd everything (even though I skip_all'd in my .t file). Every module had everything documented:

=head1 NAME

=head1 SYNOPSIS

=head1 DESCRIPTION

=head2 Methods

=over20

=item new()

=item isValid()

=item getFoo()

=item setFoo()

=item getBar()

=item setBar()

=item _validateBaz

=item _validateFred

=back

=head1 AUTHOR

=head1 BUGS

=head1 ACKNOWLEDGEMENTS

=head1 SEE ALSO

=cut
[download]

s**lil*;  $*=join'',sort split q**;  s;.*;grr; &&s+(.(.)).+$2$1+; $; =
qq-$_-;s,.*,ahc,;$,.=chop for split q,,,reverse;print for($,,$;,$*,$/)
[download]

More than likely your actual pod is invalid. Is your Pod seperate from your code? If not it will be hard to debug, better to put all your Pod at end the of the file. It will be easier to maintain that way.