Re: type hinting throwing a fatal error
| From: | Marcus Boerger | Date: | Mon, 22 Aug 2005 22:31:07 +0000 |
| Subject: | Re: type hinting throwing a fatal error | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18287@lists.php.net to get a copy of this message | ||
Hello George,
Monday, August 22, 2005, 10:10:24 PM, you wrote:
> On Aug 22, 2005, at 4:02 PM, Derick Rethans wrote:
>> On Mon, 22 Aug 2005, George Schlossnagle wrote:
>>
>>
>>>> I'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.
>>>
>>
>> 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 :) .
> My original proposal (at least as I recall it), was to move
> irrecoverable errors to something like
> E_UNRECOVERABLE_ERROR
> or
> E_FATAL
> Leaving current errors as E_ERROR (since most are recoverable, imho)
Exact same here. And i asked for that before, too (w/o answer iirc).
Best regards,
Marcus