Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68324 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48592 invoked from network); 26 Jul 2013 17:16:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2013 17:16:04 -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:60326] helo=smtp91.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 79/1A-25917-2DEA2F15 for ; Fri, 26 Jul 2013 13:16:02 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 140D0140144; Fri, 26 Jul 2013 13:16:00 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id AAEB8140139; Fri, 26 Jul 2013 13:15:59 -0400 (EDT) Message-ID: <51F2AEC4.3000603@sugarcrm.com> Date: Fri, 26 Jul 2013 10:15:48 -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: Jakub Zelenka CC: PHP internals list References: <51F177E7.3020103@sugarcrm.com> <51F182D2.7030007@sugarcrm.com> <1374793278.3605.1436.camel@guybrush> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] New handler for retrieving properties when object is serialized From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > This is a bit painful to generate and then parse (unserialize) string if > you do it in C... Especially if you need only add few properties that > will contain data for serialization. In that case Serailizable is a bit > overkill... > > And for my use case (DateTime serialization) it would be BC as well. > Different format (Serializable always generate Custom string). I think given that we already have not one, but two interfaces for dealing with serialization (__sleep and Serializable), adding a third one that does essentially the same but with a little difference would be really too much. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227