|There's more than one way to do things|
Re^3: On being 'critical'by sauoq (Abbot)
|on Dec 15, 2006 at 20:50 UTC||Need Help??|
When the boss asked to be compliant with Perl::Critic, s?he was probably (implicitly) asking to follow the lines in PBP, for all the reasons explained in PBP.
Well, even though I once said I expected to never purchase PBP, it seems that I have indirectly done so as I have access to it via my Safari library subscription... So, I took a look at what TheDamian had to say on the subject.
And it really doesn't seem that it applies very well here.
The issue TheDamian raises is essentially that of global variables. From the PBP 10.1:
If that symbol has already been used as a filehandle anywhere else in the same package, executing this open statement will close that previous filehandle and replace it with the newly opened one.But the OP had already fully qualified the package and the handle was named "THELOG" rather than something innocuous like "FILE" or "OUT".
In a private message to bart the other day, I referred to Perl::Critic as a "cargo cult compliance module".
Applying a practice in every situation simply because it is widely accepted as a best practice is not itself a best practice.
"My two cents aren't worth a dime.";