Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

The most significant Perl::Critic release in a long while.

Journal written by elliot (8136) and posted by brian_d_foy on 2009.01.01 19:26   Printer-friendly
Perl::Critic 1.094 is on its way to a CPAN mirror near you. There are a number of changes in it, but there's one in particular that I want to point out. A new policy called Miscellanea::ProhibitUselessNoCritic.

Adam Kennedy wrote a journal entry where he mentioned "the expense of having to maintain ## no critic entries permanently". This inspired the creation of the new policy.

One of the problems with Perl::Critic is that you may, over time, end up with policy disabling comments scattered across your code that no longer apply, making the code harder to understand. This policy will complain about any ## no critic that doesn't actually disable any policies. You then know that you can remove those comments, making your code cleaner and congratulating yourself for solving whatever issue that caused you to put it there in the first place.

Related Stories

The Quest for Perfect Tools 4 comments [+]

Both Gabor and Herbert have been discussing what they see as desirable in an editor.

I think most of the specifics of what this tool should do or that tool should do are largely irrelevant, because as a user interface we're facing what is fundamentally an "Open Problem".

What we can do, however, is identify the underlying effects that we need to achieve in the creation of tools for wide audiences, and then refer back to effects when looking at individual features.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Unfamiliar with implementation and performance details, upon reading about ProhibitUselessNoCritic I was immediately reminded of an old idea I had for "no strict": warn (if warnings are enabled) if the code doesn't eval anything and is strict compliant.

  • Perl::Critic is maturing and getting better, it is becoming unavoidable as a tool in the toolbox.

    Thanks for all the work and effort.