The change wasn't actually to make Tidy throw exceptions, but rather to throw errors instead of exceptions (until recently, Tidy would throw exceptions in either OO or procedural contexts).
Although I could change Tidy to not throw exceptions, I am inclinded to leave it as is (maybe change the error code from E_ERROR to E_WARNING). It's really bothersome to me to think of these new PHP 5 OO extensions being released without throwing exceptions. There is a lot of debate as we know about when exceptions should be thrown, but I haven't heard anyone flat out say exceptions in the OO context is bad. Thus, my hope is that we can roll RC2 and re-visit this issue to come up with a long-term exceptions standard. If for some reason we can't agree to throw exceptions internally, I've got no problem reverting back to no exceptions in Tidy. John -----Original Message----- From: Andi Gutmans [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 13, 2004 11:39 AM To: [EMAIL PROTECTED] Subject: [PHP-DEV] RC2RC1 Guys, I want to roll RC2RC1. There are three major changes I think we should get out of the door ASAP: - zend.ze1_compatibility_mode fix. - MT-safe crash bug. - studlyCaps changes. The only important issue I see is John's change of tiny to throw exceptions. As there's no way we will finalize our policy on exceptions, it might be the best to roll it back and release RC2. I think the fixes are too important to let them linger for too long. John, what says you? Andi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
