Re: exceptions instead of errors

> The reason i did not allow E_ERROR is the fact that i knew some few errors > which leave an unstable engine state. > > So perhaps a new error code isn't such a bad idea as i first thought. But > it makes > only sense when we change some codes which are aren't really E_ERROR and > that would be another BC issuue since it would also affect non exception code. > OR we convert the new error code into its original E_ERROR code before spitting > it out as a normal error. That's basically what I was suggesting. Having something like E_EXCEPTION would provide a nice separation and roll-in to converting all "acceptable" E_ERRORs into exception-throwing mechanisms. Of course, the idea here still would be uncaught exceptions would still cause an E_ERROR via a default catching mechanism. John > marcus > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- -~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~- John Coggeshall john at coggeshall dot org http://www.coggeshall.org/ -~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~--~=~-