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: 52570
Status: resolved
Priority: 0/
Queue: Perl-Critic
People
Owner: Nobody in particular
Requestors: GLEACH [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 1.105
Fixed in: (no value)

History Show all quoted text
  Tue Dec 08 14:17:51 2009 GLEACH [...] cpan.org - Ticket created
Subject: stopwords not found
If '=begin stopwords ... =end stopwords' is at the end of the file, perlcritic does not discover them. Unfortunately Pod::Usage craps out if they are not at the end.
  Tue Jan 19 22:47:28 2010 wyant [...] cpan.org - Correspondence added
On Tue Dec 08 14:17:51 2009, GLEACH wrote: Show quoted text
> If '=begin stopwords ... =end stopwords' is at the end of the file, > perlcritic does not discover them. Unfortunately Pod::Usage craps out if > they are not at the end.
This does not look to me like a Perl::Critic bug. The documentation for Perl::Critic::Policy::Documentation::PodSpelling 1.105 says "To add exceptions on a module-by-module basis, add 'stopwords' as described in Pod::Spell." The documentation for Pod::Spell says that stopwords take effect _after_ they are specified, so stopwords defined at the end of the file do nothing. I am also unable to make Pod::Usage 1.36 "crap out" by putting stop words above the bottom of the POD. If you can reproduce your Pod::Usage problem with the current version of Pod::Usage in a reasonably short script, you might want to report a bug in Pod::Usage. If you want Pod::Spell to recognize stopwords before they are specified, you might try submitting an enhancement request to Pod::Spelling.
  Tue Jan 19 22:47:32 2010 The RT System itself - Status changed from 'new' to 'open'
  Wed Jan 20 09:09:52 2010 GLEACH [...] cpan.org - Correspondence added
On Tue Jan 19 22:47:28 2010, WYANT wrote: Show quoted text
> On Tue Dec 08 14:17:51 2009, GLEACH wrote:
> > If '=begin stopwords ... =end stopwords' is at the end of the file, > > perlcritic does not discover them. Unfortunately Pod::Usage craps out if > > they are not at the end.
> > This does not look to me like a Perl::Critic bug. The documentation for > Perl::Critic::Policy::Documentation::PodSpelling 1.105 says "To add > exceptions on a module-by-module basis, add 'stopwords' as described in > Pod::Spell." The documentation for Pod::Spell says that stopwords take > effect _after_ they are specified, so stopwords defined at the end of > the file do nothing. > > I am also unable to make Pod::Usage 1.36 "crap out" by putting stop > words above the bottom of the POD. > > If you can reproduce your Pod::Usage problem with the current version of > Pod::Usage in a reasonably short script, you might want to report a bug > in Pod::Usage. If you want Pod::Spell to recognize stopwords before they > are specified, you might try submitting an enhancement request to > Pod::Spelling.
I'll report it to Pod::Usage. Thanks for the info, and sorry for the bother.
  Thu Jan 21 22:29:37 2010 wyant [...] cpan.org - Correspondence added
On Wed Jan 20 09:09:52 2010, GLEACH wrote: Show quoted text
> > I'll report it to Pod::Usage. Thanks for the info, and sorry for the
bother. Sorry in turn for taking so long to respond. Good luck with Pod::Usage.
  Wed Jul 11 04:00:21 2012 thaljef [...] cpan.org - Correspondence added
Since this problem seems to lie outside of Perl::Critic, I'm marking this ticket as "rejected". -- Jeffrey Thalhammer Imaginative Software Systems www.imaginative-software.com
  Wed Jul 11 04:00:23 2012 thaljef [...] cpan.org - Status changed from 'open' to 'resolved'