On Fri, 2004-04-16 at 12:44, Derick Rethans wrote: > I disgree with this behavior too. E_WARNINGs were never supposed to > abort a script, that's what we have E_ERRORs for. (Making E_ERROR an > exception in an OO context is fine, as when it's unhandled it should > abort the script, just like in PHP 4 and all other non-oo extensions).
The problem here is that the errors in question truly are warnings, not show-stopping errors. Unless the engine can support a non-fatal exception, i see no reasonable solution short of completely removing Exceptions from use. I'm not prepared to do that, a failure to open a file is an exception in OO-world and that's what should be there. John -- -=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=- John Coggeshall http://www.coggeshall.org/ The PHP Developer's Handbook http://www.php-handbook.com/ -=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
