Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I don't have any sympathy for the "uses_test_nowarnings" metric (mainly because it promotes Test::NoWarnings to a universal best practice to be used -- and abused -- everywhere). That happened before with Test::Pod and Test::PodCoverage and their corresponding metrics. On the other hand, to make sure that your code is free from warnings you don't know about is a good idea. But there's code that needs it and others that don't -- just like it happens with "use warnings" or "use strict".

    But you're certainl

    • Something better could be done with Module::Install and other similar developer-helper modules (which at least will let you update the embedded dependency at a later date without much suffering).

      Refusing to add unnecessary complexity which only serves to toggle one bit in a Kwalitee index is a sure sign of Actual Quality. This is one case where Kwalitee is very much at odds with Quality.