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: 82921
Status: open
Priority: 0/
Queue: Perl-Critic

People
Owner: Nobody in particular
Requestors: dagolden [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: Deprecated modules are not EvilModules
Module::ProhibitEvilModules complains about p5p deprecated modules. "Deprecation" means "removed from core". There is no implied injunction against continued use from CPAN. See http://perldoc.perl.org/perlpolicy.html#Terminology
Subject: Re: [rt.cpan.org #82921] Deprecated modules are not EvilModules
Date: Wed, 23 Jan 2013 18:55:55 -0800
To: bug-Perl-Critic [...] rt.cpan.org
From: Jeffrey Ryan Thalhammer <jeff [...] imaginative-software.com>
On Jan 23, 2013, at 6:26 PM, David Golden via RT wrote: Show quoted text
> Module::ProhibitEvilModules complains about p5p deprecated modules. > > "Deprecation" means "removed from core". There is no implied injunction > against continued use from CPAN.
Yeah, I'm kinda surprised by that too. I always thought ProhibitEvilModules was a no-op unless you configured the modules that you deemed "evil". But it looks like we decided to make deprecated modules evil too at some point. As you said, deprecation doesn't say anything about a module's fitness. But I suppose some folks might find this to be a useful way to learn if they use any deprecated modules. So this feature should be split out into a separate (non-core) Policy. Or at least the deprecation stuff should be turned off by default. I haven't decided which way to go. Thanks for calling this out. -Jeff