Re: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_default_classes.c zend_default_classes.h zend_execute.h zend_execute_API.c
| From: | Derick Rethans | Date: | Fri, 13 Feb 2004 18:28:35 +0000 |
| Subject: | Re: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_default_classes.c zend_default_classes.h zend_execute.h zend_execute_API.c | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-7816@lists.php.net to get a copy of this message | ||
On Fri, 13 Feb 2004, Sterling Hughes wrote:
> > And my point is that I may want to create an exception (sterling's
> > 'InternalException', for example), that I do not want you catching
> > unless you specifically check for it.
>
> Right. Exception heirarchies are nice and all, but sometimes you want
> exceptions to leak through, or be explicitly caught. In-fact, I've
> never encountered a case where this isn't what I want, maybe in a small
> 20 line example, but in large scripts I've almost always designed for
> leakage.
Yeah, i agree with this. From what I understood is that Sterling's new
addition was only there for the lazy people not wanting to implement the
few standard methods. I also see a reason why to allow leaking
exceptions.
Derick