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

People
Owner: Nobody in particular
Requestors: user42 [...] zip.com.au
Cc:
AdminCc:

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



Subject: ProhibitLvalueSubstr vs highest_explicit_perl_version
Date: Tue, 06 Jul 2010 10:33:56 +1000
To: bug-Perl-Critic [...] rt.cpan.org
From: Kevin Ryde <user42 [...] zip.com.au>
I had some code with a "use 5.004" and thought ProhibitLvalueSubstr might have an option like when_perlver_allows=yes which would tell it to report only when the highest_explicit_perl_version() is new enough that 4-arg substr is in fact available (ie. 5.005). Such an option would sort of mean you don't want to up an explicit minimum version, but do want to hear about lvalue substrs lurking in code already declaring itself for new enough perl. If there's no explicit "use 5.x" then I'd be happy for it to report, effectively treating no declared version as if it meant something more or less recent.
Committed as SVN revision 4075. To be consistent with the three other policies that are sensitive to Perl version, there is no option to control whether documents are skipped if they specify a sufficiently old version of Perl, it just happens.