Re: type hinting throwing a fatal error
| From: | Andrei Zmievski | Date: | Mon, 22 Aug 2005 21:09:12 +0000 |
| Subject: | Re: type hinting throwing a fatal error | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18279@lists.php.net to get a copy of this message | ||
E_CATCHY catchy enough or you?
-Andrei
On Aug 22, 2005, at 1:02 PM, Derick Rethans wrote:
On Mon, 22 Aug 2005, George Schlossnagle wrote:Right, my current patch allows you do to that for the new "E_CATCHABLE" error. I don't like the name though, so we need to come up with a better one (sorry Zeev :) . Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.phpI'm talking about allowing type hints to be trappable by users, without complicating them with exceptions. I'm proposing a new error level, which behaves like E_ERROR, except it can be caught using a userland error handler, for those cases where the engine/PHP are in a stable state.This sounds good to me. We talked about this briefly a year or so ago, in reference to being able to convert E_ERROR errors to exceptions in an extension.