Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68327 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68559 invoked from network); 26 Jul 2013 21:08:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2013 21:08:18 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; 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:53985] helo=smtp91.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F0/8D-25917-145E2F15 for ; Fri, 26 Jul 2013 17:08:18 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id A39031401BD; Fri, 26 Jul 2013 17:08:15 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 1990D1401BB; Fri, 26 Jul 2013 17:08:15 -0400 (EDT) Message-ID: <51F2E53E.1040707@sugarcrm.com> Date: Fri, 26 Jul 2013 14:08:14 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Gustavo Lopes CC: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= , Jakub Zelenka , Nikita Popov , PHP internals list , "nikic@php.net" References: <51F177E7.3020103@sugarcrm.com> <51F182D2.7030007@sugarcrm.com> <1374793278.3605.1436.camel@guybrush> <1374833069.3605.2106.camel@guybrush> <1374838415.3605.2211.camel@guybrush> <1374847163.3605.2377.camel@guybrush> <51F2E393.5090206@nebm.ist.utl.pt> In-Reply-To: <51F2E393.5090206@nebm.ist.utl.pt> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] New handler for retrieving properties when object is serialized From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Yes, this would break extensions. But we never made any promises about > source BC for extensions. In fact, we actually break it for every Actually, we try to preserve source BC for extensions, unless they do some weird things or they go very deep into the implementation details. "Regular" extension generally should not suffer from adding a feature. > Alternatively, could the problem perhaps be mitigated by making > available some utility functions for serializing native types? We could definitely make some parts of serializer API-accessible, or even make serializer as a whole to be more API-friendly, I think it'd be a nice idea if making implementing Serializable would be made easy by reusing serializer code and combining pieces. If now it's hard making it easier definitely a good idea, much better than creating one more API IMHO. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227