On Thu, 2003-03-27 at 18:04, George Schlossnagle wrote: > On Thursday, March 27, 2003, at 11:58 AM, Andi Gutmans wrote: [...] > I think this can(all) be handled with a custom zend_error_cb anyway (in > an extension - so that it's available only if you want it.) Looks > really simple to implement too.
Well, I can think fo the following disadvantages to that: - Code is less portable (some other user or ISP might not have the fancy --with-cool-oop extension enabled) - Within zend_error, all information is lost about the error context. E.g., if you handle E_ERROR, you will not know if it was an illegal argument, a call to a member function of a non-object or whatever else. You only know it was a fatal error. - Current code relies on the fact that zend_error(E_ERROR, [...]) bails out. If you start throwing around exceptions instead, this will probably end up in a big mess:) Just my 3 cents: Timm -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
