|There's more than one way to do things|
I chose a very modest goal -- implementing "strict" pragma because "use strict" and "use warnings" are two pragmas which do improve maintainability of Perl scripts. Other new staff mostly don't.
You can be strict/warnings compliant and not benefit
Being in a hurry to automate strict/warnings compliance hints that you just might be missing the point of strict/warnings
The slideshow I linked is very good, its called Program Repair Shop , its about refactoring/strict/warnings
So this is an implicit attempt to push me into "overachiever mode".
No, Its an explicit invitation to answer question #2 yourself,
Chapter 9. Managing Real Programs, Modules, Organizing Code With Modules
I'm boning up right now
Its hard being an archeologist
In reply to Re^3: Perl archeology: Need help in refactoring of old Perl code that does not use strict (hurry up and wait)
by Anonymous Monk