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.
Wayback Machine
- June 2012 (1)
- February 2010 (1)
- December 2009 (2)
- November 2009 (3)
- August 2009 (1)
- July 2009 (3)
- June 2009 (7)
- May 2009 (4)
- April 2009 (1)
- March 2009 (1)
- February 2009 (3)
- January 2009 (2)
- October 2008 (2)
- September 2008 (4)
- May 2008 (1)
- March 2008 (1)
- September 2007 (2)
Tags
administration 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