On Fri, July 24, 2009 9:35 am, Alexey Zakhlestin 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 projectConstruct your error-handler to "stack" nicely and throw or trigger_error whatever would have happened without it. Then you need not unset/reset the silly thing. -- Some people ask for gifts here. I just want you to buy an Indie CD for yourself: http://cdbaby.com/search/from/lynch -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
