Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26874 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16735 invoked by uid 1010); 9 Dec 2006 19:56:19 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 16720 invoked from network); 9 Dec 2006 19:56:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Dec 2006 19:56:19 -0000 Authentication-Results: pb1.pair.com header.from=ceo@l-i-e.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=ceo@l-i-e.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain l-i-e.com from 67.139.134.202 cause and error) X-PHP-List-Original-Sender: ceo@l-i-e.com X-Host-Fingerprint: 67.139.134.202 o2.hostbaby.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from [67.139.134.202] ([67.139.134.202:1190] helo=o2.hostbaby.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AE/F4-50161-D941B754 for ; Sat, 09 Dec 2006 14:55:44 -0500 Received: (qmail 50899 invoked by uid 98); 9 Dec 2006 19:55:09 -0000 Received: from 127.0.0.1 by o2.hostbaby.com (envelope-from , uid 1013) with qmail-scanner-1.25 (clamdscan: 0.88.4/2311. Clear:RC:1(127.0.0.1):. Processed in 0.07235 secs); 09 Dec 2006 19:55:09 -0000 X-Qmail-Scanner-Mail-From: ceo@l-i-e.com via o2.hostbaby.com X-Qmail-Scanner: 1.25 (Clear:RC:1(127.0.0.1):. Processed in 0.07235 secs) Received: from unknown (HELO l-i-e.com) (127.0.0.1) by localhost with SMTP; 9 Dec 2006 19:55:09 -0000 Received: from 209.254.223.2 (SquirrelMail authenticated user ceo@l-i-e.com) by www.l-i-e.com with HTTP; Sat, 9 Dec 2006 13:55:09 -0600 (CST) Message-ID: <61679.209.254.223.2.1165694109.squirrel@www.l-i-e.com> In-Reply-To: <79.1E.13900.F8038754@pb1.pair.com> References: <0c60b01d19ec7e242ade31e29120ee27@gravitonic.com> <4577FC87.7090109@hardened-php.net> <79.1E.13900.F8038754@pb1.pair.com> Date: Sat, 9 Dec 2006 13:55:09 -0600 (CST) To: "Zeev Suraski" Cc: "Stefan Esser" , internals@lists.php.net Reply-To: ceo@l-i-e.com User-Agent: Hostbaby Webmail MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: [PHP-DEV] PHP 5.2: Serialization patch From: ceo@l-i-e.com ("Richard Lynch") On Thu, December 7, 2006 9:17 am, Zeev Suraski wrote: > At 13:35 07/12/2006, Stefan Esser wrote: >>Guys, >> >>why can't you simply introduce a new variable type for serialized >>strings like uppercase S: >>There is absolutely no need for breaking backward compatibility. > > I can't think of a single reason not to use a new type like you > suggest. > > Can anybody think of any drawbacks? Somebody MIGHT have written their own unserializer/serializer which made incorrect assumptions about the internal format, such as 's' being the same as 'S'... So, perhaps, just to be consistent with the data I *think* appears in serialized form, 'u' for 'unicode' would maybe be better than 'S' I confess I have no idea what is actually inside of serialized data, and could be WAY off base, but I stretched far enough to come up with something that could go wrong, because that's the kind of paranoid guy I am. :-) -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?