Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74978 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54059 invoked from network); 18 Jun 2014 22:22:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jun 2014 22:22:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.91 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.91 smtp91.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.91] ([108.166.43.91:47044] helo=smtp91.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D4/11-46307-A3112A35 for ; Wed, 18 Jun 2014 18:22:51 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp20.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id F1D9F180B3C; Wed, 18 Jun 2014 18:22:47 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp20.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id AE6AE1813FA; Wed, 18 Jun 2014 18:22:47 -0400 (EDT) Message-ID: <53A21137.6010705@sugarcrm.com> Date: Wed, 18 Jun 2014 15:22:47 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Remi Collet , PHP Internals References: <53A1C722.9060501@fedoraproject.org> In-Reply-To: <53A1C722.9060501@fedoraproject.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: Problems with the fix for the BC break introduced in 5.4.29 and 5.5.13 From: smalyshev@sugarcrm.com (Stas Malyshev) 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