Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Perl-Critic CPAN distribution.

Report information
The Basics
Id: 59268
Status: resolved
Priority: 0/
Queue: Perl-Critic

People
Owner: Nobody in particular
Requestors: rjray [...] blackperl.com
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in:
  • 1.108
  • 1.109
  • 1.111
Fixed in:
  • 1.110_001
  • 1.112_001
  • 1.112_002
  • 1.113



Subject: Documentation::RequirePodSections should not complain until the first line of POD
Currently, because of the "whole-document" nature of this policy, its complaints are reported at line 1 of the document, even if your POD doesn't start until after __END__ long past line 1. This forces any per-file disabling via "## no critic" to be the first line in the file. This might not be feasible if the file is a script that needs a #! line to be first, nor is is useful if more than one policy "demands" that its no-critic be on line 1. It would be more useful if this policy could react to no-critic directives that simply appear before the first line of POD. Currently, the only alternative is to globally disable the policy entirely, which is a shame if you actually use it but just need the occasional exception. -- """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" Randy J. Ray Silicon Valley Scale Modelers: http://www.svsm.org rjray@blackperl.com randy.j.ray@gmail.com
Patch submitted as SVN revision 3881. The '## no critic' will be effective anywhere before the first '=head1' POD. Be aware of a restriction in Perl::Critic -- it does not recognize ANY '## no critic' annotations after __END__ (or __DATA__, for that matter).