Re: Re: cvs: pear-core /PEAR
| From: | Lukas Smith | Date: | Mon, 06 Sep 2004 16:21:46 +0000 |
| Subject: | Re: Re: cvs: pear-core /PEAR | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev php.pear.core |
| Request: | Send a blank email to pear-dev+get-33249@lists.php.net to get a copy of this message | ||
Lukas Smith wrote:
Well, kinda reminds me of the PEAR_Errors gets upgraded to PEAR_Exception thing we discussed a while back in order to make it possible to support Exceptions within PHP4 compatible code. Anyways seems like the same thing to me, but I am not going to argue over it.On a related note: Davey's idea on being able to resume inside the exception handler was shot down on internals@. If we would call our own method to throw any exception we could of course control how and when things get thrown or if at all. This would solve my big gripe that sometimes I want quick and dirty and would therefore like to disable all or selection of exceptions entirely (especially for packages written by rather exception trigger happy people). So to me this backtrace argument is a showstopper for alot of things that would make exceptions alot less painful for those of us who are a bit worried about what exceptions could do to their code. regards, LukasShowstopper in the sense that it effectively killed off the "Exceptions within PHP4 compatible code" idea.seems like more and more this fact is becoming a show stopper (as it already was for the turn pear_errors into exceptions on demand php4/php5 compatibility thing). maybe its time we address this?How is it a showstopper?