Hi Nikita, I very like the idea. Actually, it's a long time desired php feature that many big php users miss. They don't like to show 500 response in any case.
Also +1 for removing ability of silent E_RECOVERABLE_ERROR bypass :) I think that few things may be "improved" 1) I'm not sure if "cacth(Exception $e)" should catch engine and parser exceptions. May be it's better to introduce interface or common parent class "Catchable" and then make Exception, EngineException and ParseException implement it. In case user would like to catch all the error at once they will able to use "catch(Catchable $e)", but cacth(Exception $e) would be 100% compatible. 2) I also think it's not a big problem to keep compatible error messages for uncaught EngineException and ParseException. I'm not sure if that "Uncaught EngineException:" really need. Thanks. Dmitry. On Tue, Oct 7, 2014 at 1:53 AM, Nikita Popov <nikita....@gmail.com> wrote: > Hi internals! > > During the PHP 5.6 development cycle I have proposed an RFC [1] that > suggested the use of exceptions instead of fatal errors in the engine. At > the time the proposal was declined, because the change was judged too > intrusive for a minor version. > > As such I'm re-proposing this RFC for inclusion in PHP 7: > > https://wiki.php.net/rfc/engine_exceptions_for_php7 > > The RFC text is essentially the same as previously, with the primary > difference being that parse errors are now converted to exceptions as well. > This was previously not possible due to limitations in the compiler design. > > Thanks, > Nikita > > [1]: https://wiki.php.net/rfc/engine_exceptions >
