Rasmus Lerdorf schrieb: > [...] > What do we do with code like this? If you follow it through it is > essentially doing: > > 3 = "banana"; This is obviously totally wrong and has to be noted as wrong, hence E_NOTICE. Since it can be dealt with without rendering the script unexecutable raising a fatal error in PHP5 is wrong => switch that to E_NOTICE, too. But the problem for a lot of people using PHP applications simply is that they had perfectly running code and they weren't getting any notices at all. Now they still have working code but this one error in code they haven't written is throwing notices at them like hell. The quick answer is "deactivate error reporting for production systems", but this is not a real solution for the PHP 4.x platform. People _using_ foreign code expect to get consistent behaviour from their applications. So the report level for this should be configurable for the 4.x branch with silence as default. AllOLLi ____________ "The good news is: The whiskey works." [Lost in Translation] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
