in reply to Re: On Commenting Out 'use strict;'
in thread On Commenting Out 'use strict;'
That's why a part of best practices should include when to turn off warnings.
If you know a piece of code is going to produce spurious warnings; but not cause any side effects (like the 'uninitialized' that happens all the time); and doing it the correct way gives you complaints from management that it's harder to read you can just add a local $^W immediately before the code.
Harley J Pig
In Section
Meditations