in reply to How to get Pod::Coverage to stop calling my export naked

I never used this module, but after reading the doc I'm irritated...

Did you try to categorize DEBUG as private or also_private?

from Pod::Coverage

Methods Pod::Coverage->new(package => $package) Creates a new Pod::Coverage object. package the name of the package to analyse private an array of regexen which define what symbols are regarded as private (and so need not be documented) ... also_private items are appended to the private list

I agree with educated_foo that Pod::Coverage shouldn't be an installation test, but rather a part of the release/development process.

Cheers Rolf

Replies are listed 'Best First'.
Re^2: How to get Pod::Coverage to stop calling my export naked
by Oberon (Monk) on Feb 06, 2012 at 01:07 UTC

    Thanks for all the suggestions, guys, but I think you misunderstood the problem. The Pod::Coverage problem is not with my module; it's in the module that uses my module. I can't document the constant in my user's POD, I can't make the user declare it private and I can't force them not to use Pod::Coverage. I wouldn't even get very far advising them not to use it: there are all sorts of recommendations out there from very smart people telling them to do it, and Dist::Zilla even includes a Test::Pod::Coverage test in its release tests, if you turn that feature on.

    tye's answer was 100% correct and solved my problem neatly and completely. ++ to him.