note jthalhammer <em>The magic punctuatinon it is talking about is $@ without which I could not really catch exceptions</em> <code> use English qw(-no_match_vars); eval { die 'A horrible death' }; print "Something died\n" if $EVAL_ERROR; </code> <em>Useless interpolation of literal string at line ... <br/> I don't even get that one because the line in question is basically something like this: <code> confess 'Some error happened because ' . $obj->foo . ' blew up'; </code> I would have to say that this string was far from useless. </em> <p> If those were double-quotes instead of single-quotes (which they probably were) then the warning was precisely correct. </p> <code> sub mumble_path { join ", " => split '/' => (shift)>get_path } </code> <em> I would argue that adding return to something like that would be just adding noise. </em> <p> You certainly can argue! [dist://Perl-Critic-Lax] is a suite of slightly more forgiving versions of several Policies. Perhaps you could write a new module for it. </p> <p> 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. </p> -Jeff 596691 596706