On Fri, Jul 24, 2009 at 16:35, Alexey Zakhlestin<indey...@gmail.com> wrote:
> On Fri, Jul 24, 2009 at 6:29 PM, Hannes
> Magnusson<hannes.magnus...@gmail.com> wrote:
>> On Fri, Jul 24, 2009 at 15:43, Ben Scholzen 'DASPRiD'<m...@dasprids.de>
>> wrote:
>>> To you both, this is especially, for library code like Zend Framework.
>>> The library cannot expect the user to have the error handle set, so it
>>> would have to replace the error handler before every line which it wants
>>> to try {} and reset it after the catch. This is not really a clean
>>> solution, at it can occur pretty often.
>>
>> Why do you have to replace it?
>
> because in case of a library, there is a "third-party" called "user".
> User might have his own opinion on error-handlers. And then, there's
> even worse case, when there are 2 or three libraries mixed in the
> single project
No. The RFC says it should throw Exception. There is no need for other
error handlers in that case.
If you want multiple error handlers then create RFC for error handler stacking.
-Hannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
