Hi! > The issue is that a warning wouldn't destroy that object. That object will > occasionally segfault PHP. E_ERROR is the simplest solution which doesn't > change the behavior of the normal operations.
Can't we just reset the object data to some known "zero" state? Having E_ERROR in a function that is not supposed to normally bail out is not a good thing - especially unserialize which may deal with external data. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php