|Think about Loose Coupling|
Re^3: Things every perl programmer should know? (disabled warnings)by Aristotle (Chancellor)
|on Jun 04, 2003 at 23:17 UTC||Need Help??|
For me, it's:
because that sodding warning has never caught anything for me that strict wouldn't have trapped sooner. The kicker is that fixing it requires jumping through very silly hoops to make it go away. ($foo = $foo = 1; anyone?) As for uninitialized - well, I don't get a warning on
I admit it's sometimes a little awkward to code around the uninitialized warning, but usually something like adding a || 0 or || '' or such does the trick just fine. And that kind of thing isn't silly, in fact I think it's clearer in intent in that I document via code that I explicitly expect undefs there.
Makeshifts last the longest.