Some people seem to like to put Perl::Critic tests into their VCS pre-commit hooks in order to prevent code with violations being checked in. I consider this to be a really bad idea. You should always be able to check your code in, if only for backup purposes. It’s a matter of preserving your code, even if it’s got some stupid PodSpelling violation. You’ve got a production emergency bug fix and you can’t check in because you’ve got a ProhibitEscapedMetacharacters problem? I certainly wouldn’t want that.
Tagsadministration autodie Benchmark bug reporting coding style continuous integration CPAN::Site CPAN module support darkpan DateTime Devel::NYTProf development documentation Exporter ExtUtils::MakeMaker maintenance modern perl modules Moose MyCPAN::App::DPAN MyCPAN::Indexer open source parrot performance perl 5 perl 6 Perl::Critic Pod::Coverage policy development PPI profiling programs rakudo Readonly roles Strawberry Perl syntax Test::Moose Test::Object testing things I like tools twitter upgrading using Perl::Critic xs yapc yapcna2009