|Subject:||"no critic" for pod after __END__|
|Date:||Thu, 08 Jul 2010 08:07:02 +1000|
|To:||bug-Perl-Critic [...] rt.cpan.org|
|From:||Kevin Ryde <user42 [...] zip.com.au>|
Foo.pm below critiqued as "perlcritic -1 Foo.pm" gets violation (among several others), Pod NAME does not match the package declaration at line 5, column 1. (no explanation). (Severity: 1) where I hoped the "no critic" directive in Foo.pm would suppress that policy. It seems to suppress successfully if the __END__ is removed, but I hoped it would be possible to put pod after __END__ and still affect pod policies on it. I don't mind if the no critic directive has to come before __END__ to be seen, though you'd be tempted to grep them out after an __END__ too.
## no critic (RequirePackageMatchesPodName) __END__ =head1 NAME Bar - wrong module name here!