I agree. Turns out there's also a website if you want it to do a basic check of your code. It was not kind to me... *sniff*
http://perlcritic.com/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gederberg, Thomas K Sent: Wednesday, September 20, 2006 5:23 PM To: Houston.pm located in Houston, TX. Subject: Re: [pm-h] Upcoming Topics Sounds interesting to me. -----Original Message----- From: G. Wade Johnson [mailto:[EMAIL PROTECTED] Sent: Sunday, September 17, 2006 11:47 AM To: Houston Perl Mongers Subject: [pm-h] Upcoming Topics I've recently been looking at the module Perl::Critic. Although Perl::Critic supports Damian Conway's "Perl Best Practices" out of the box. It also supports the ability to add policies of your own. Is anyone interested in a talk about using Perl::Critic to improve adherence to coding standards? I'm looking at modifying the Perl::Critic policies for all of the modules that I work on to see if it will actually improve my code. G. Wade -- It's easier to port a shell than a shell script. -- Larry Wall _______________________________________________ Houston mailing list [email protected] http://mail.pm.org/mailman/listinfo/houston Website: http://houston.pm.org/
