Re: use strict

[talexb]

In maintenance programming, one of the first rules I can think of is "Make the smallest possible change that's going to fix the bug or add the feature." So adding something like use strict, while an excellent idea, may cause undesirable side effects, either the same warning messages appearing a thousand times an hour in the error log, or a failure to compile, resulting in the customer seeing an Internal Server Error. Sad face.

I'm all for using strict when working on new development, but adding that to something in production needs to be used sparingly.