The Problems of Perl: The Future of Bugzilla

[Christopher Hicks]

On Thu, May 10, 2007 at 04:55:42PM +0200, Guillaume Rousse wrote:
> Establish a standard perltidy configuration file. And use a dedicated
> framework to impose your prefered style, such as Perl::Critic.

Definitely a good plan for any perl project.

> I recommand reading 'Perl Best Practices',
> by D. Conway, for instance. Or even joining some perl conference to
> present bugzilla, and discuss those issues directly with people.

Damian Conway consitently exceeds my expectations and Perl Best Practices is a great example.  I've been using Perl for 15 years or so, I teach perl classes, and all of the code we develop for clients is in Perl.  We've had a Perl Style Guide internally for five or six years.  And I still learned a lot from Perl Best Practices.  I can't say that I agree with every bit of it and there are small parts of it that we note in our style guide as being in disagreement with Perl Best Practices, but the rest of the book is so self evidently a good idea its hard not to recommend it for anyone writing a script larger than 10 lines.

Mr. Rousse deserves an ovation for his patience and directness in addressing what is a very suprising attitude from one of the core devs on one of the preeminent Perl applications in the world.  Thanks Guillaume.

-- 
</chris>

"The problem with troubleshooting is that trouble shoots back!"