Re: Re: Problems with the fix for the BC break introduced in 5.4.29 and 5.5.13

Hi! > My proposal, for a quick solution, trying to be pragmatic and > trying to make the most of php users happy. Is the solution of banning only the internal classes with create_object and their descendants unsatisfactory? > And allow newInstanceWithoutConstructor for internal classes. > (make this unserialize hack used by phpunit and doctrine unneeded) How we can safely make that? For internal classes I'm afraid making them work safely without ctor would be a challenge - after all, all the code expects ctor to run. For user classes at least the engine would throw a fatal error at worst, but for internal classes we'd get segfaults all over the place. I'm not sure how this can be done safely. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227