Useless interpolation of literal string at line ...use English qw(-no_match_vars); eval { die 'A horrible death' }; print "Something died\n" if $EVAL_ERROR;
I would have to say that this string was far from useless.confess 'Some error happened because ' . $obj->foo . ' blew up';
If those were double-quotes instead of single-quotes (which they probably were) then the warning was precisely correct.
I would argue that adding return to something like that would be just adding noise.sub mumble_path { join ", " => split '/' => (shift)>get_path }
You certainly can argue! Perl-Critic-Lax is a suite of slightly more forgiving versions of several Policies. Perhaps you could write a new module for it.
Perl::Critic is lenient by default. Normally, it only reports the most severe issues (the relative severities are configurable). However, the web-service is currently configured for maximum strictness. I suppose I should loosen that up a bit. One of these days, I'd like to expose all the Perl::Critic configurations through the web-service, but that's a ways off.
-JeffIn reply to Re^2: Module Announcement: Perl-Critic-1.01
by jthalhammer
in thread Module Announcement: Perl-Critic-1.01
by jthalhammer
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |