Josh Chamas wrote:
No doubt that use strict will help. That's why all coding projects we start here require them (along with tons of other coding standards). However, since we didn't write this code and as we are not being paid to convert all of it to "use strict", the benefits of it, though understood, are irrelevant.If you call Apache::ASP->Load() on all the files, you can find the errors with UseStrict at compile time, so you do not get errors at runtime. The process of converting over to UseStrict will catch other errors besides the one that started this thread so would be good for the code base to be converted to using.
I zm unsure how I could wind up with a destroyed $Response object when $Request and $Response aren't uned anywhere but in the .asp pages and are never passed into functions or methods in the outlying codebase. So there should be no caching of a $Response object for use after its life has ended.
--
Theo Schlossnagle
Principal Consultant
OmniTI Computer Consulting, Inc. -- http://www.omniti.com/
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
