Re: Exceptions and a real example: Tidy
| From: | Sterling Hughes | Date: | Fri, 16 Apr 2004 22:20:30 +0000 |
| Subject: | Re: Exceptions and a real example: Tidy | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-9298@lists.php.net to get a copy of this message | ||
Tidy's current error handling scheme is totally messed up - every single thing in the extension should be an E_WARNING by PHP standards. Its RC2, and this stuff has worked for a long time, breaking it now is counterproductive and annoying.
John, if you insist on messing up the error handling in the tidy extension, which is a serious thing, why not move it to pecl where you have full control over such things without bothering the rest of the release..?
-Sterling
On Apr 16, 2004, at 9:44 AM, Derick Rethans wrote:
On Fri, 16 Apr 2004, Christian Schneider wrote:John Coggeshall wrote:I disgree with this behavior too. E_WARNINGs were never supposed to abort a script, that's what we have E_ERRORs for. (Making E_ERROR an exception in an OO context is fine, as when it's unhandled it should abort the script, just like in PHP 4 and all other non-oo extensions). Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.phpthe best compromise I can reach without discarding exceptions entirely, which I believe is even more wrong for OO code.I disagree. I lost track over the last couple of days, what is everyone else's view on this?