Re: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_default_classes.c zend_default_classes.h zend_execute.h zend_execute_API.c
| From: | George Schlossnagle | Date: | Sat, 14 Feb 2004 15:44:02 +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 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-7823@lists.php.net to get a copy of this message | ||
On Feb 14, 2004, at 8:08 AM, Zeev Suraski wrote:
At 19:50 13/02/2004, Sterling Hughes wrote:Because you want it to be catchable by someone who is looking for it. GeorgeRight. 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.My experience is a bit of the opposite, and the truth is somewhere in the middle I guess. But anyway, if you want to error out, why not just do that? Why go through the mess of coming up with an exception that will propagate through God knows how many checks and hopefully won't be caught?