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.
  • So what kind of differences did you notice between the two? Do they give conflicting or compelmentary results? Do you have any thoughts on how these types of modules should work. As the author of Perl::Critic, I'm just curious to see what other people think. Thanks for your feedback. -Jeff
    • Well I should do a more thorough analysis, recommending any of the two :)

      Anyway I see the two modules having to different scopes.

      Where Perl::Critic is focused on the well defined set of best practices from the book 'Perl Best Practices', Module::CheckStyle is more general - and can be configured into applying a check for any styleguide, which makes it more interesting in conjunction with for example a company coding guideline, perhaps even PerlStyle. I actually asked Claes to let the module implement PerlStyle as it's default configuration.

      And as I see the scope of Module::CheckStyle it could possibly also implement the Perl best practive as laid out by Damian Conway.

      But as always there is room for both modules :)