On 7/12/05, Chuck Hagenbuch <[EMAIL PROTECTED]> wrote:
> Yes, they could turn off warnings. But since the code has always run
> cleanly beforehand, they don't think to do that.
It's definitely not the cleanest solution, but for those of you who
want to have a "quick fix" which will hide the problem until you have
time to fix it properly, use the following at the top of a common
file:
if(!defined('E_STRICT')) {
define('E_STRICT', 2048);
}
error_reporting(error_reporting() & ~E_NOTICE & ~E_STRICT);
Never depend on a user to do something for you that you can do
yourself. If you feel notice reporting should be off on a production
level script, then turn them off, and make it easy and documented for
them to turn it back on if they want it, not expect them to know how
to disable them theirself automatically.
--
---------------------------
Jeremy Johnstone
http://www.jeremyjohnstone.com
[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
