Retrofit warnings and severe difficulty. I do not recommend the Big Bang approach, setting warnings (not to mention restrictions) on everything. You will be inundated with warnings to no avail.
You start by turning on warnings about the modules used by scripts (there are some, they are not), instead of applying warnings to everything. Get the purity of the core, and then work on the periphery, one unit at a time. In fact, I would recommend having a simple (Perl) script that just finds a line that does not start with a hash, and adds use warnings;(and possibly use strict;also since you are going to deal with one script at a time), so you can do updates once a script at a time.
, , , , .
"", : . , , "", "".
, , . Perl script, . fix* bin, - , (, , ) , .