Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68317 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8333 invoked from network); 26 Jul 2013 10:04:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2013 10:04:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:48029] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 78/13-25917-1C942F15 for ; Fri, 26 Jul 2013 06:04:50 -0400 Received: from [192.168.2.20] (ppp-93-104-4-146.dynamic.mnet-online.de [93.104.4.146]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 4759F65F37; Fri, 26 Jul 2013 12:04:46 +0200 (CEST) To: Jakub Zelenka Cc: Stas Malyshev , Nikita Popov , PHP internals list , "nikic@php.net" In-Reply-To: References: <51F177E7.3020103@sugarcrm.com> <51F182D2.7030007@sugarcrm.com> <1374793278.3605.1436.camel@guybrush> Content-Type: text/plain; charset="UTF-8" Date: Fri, 26 Jul 2013 12:04:29 +0200 Message-ID: <1374833069.3605.2106.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] New handler for retrieving properties when object is serialized From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Fri, 2013-07-26 at 10:38 +0100, Jakub Zelenka wrote: > 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... So rather change the engine, which affects way more things and add yet another serialisation hook making it even more confusing what to use? > > > And for my use case (DateTime serialization) it would be BC as well. > Different format (Serializable always generate Custom string). > You're solution also depends on an API break and also changes the way the objects behave during serialization/unserialization. Doesn't convince me. johannes