Re: An BC issue in unserialize

Hi! > IMHO this isn't something we should change in a 2nd digit release, but on a > major version, even if it wasn't documented. We don't have much option here. Keeping it leads to a remote triggerable segfaults. We've discussed this here just recently. This is a hack that does not work properly with internal classes, and should not work too - the whole reason C: was created is because O: can not work with such classes. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/