On 17 May 2015 00:48:07 BST, Levi Morrison <le...@php.net> wrote: >It's also the principle of least astonishment: why isn't TypeException >caught by `catch (Exception $e)`?
This is probably a good argument in favour of "Error" as naming for engine exceptions. If you say "TypeError is not caught by catch (Exception $e)", it seems a lot less surprising. You can even say "a TypeError is Throwable, but it's not an Exception". On a practical level, it's perfectly possible to write a handling function which can process all sorts of different user land exceptions, but wouldn't have a clue what to do about an engine error. Regards, -- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
