Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67012
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Laruence <laruence@php.net>
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <CABBJUpepz+TU-Y6oFkpv9sJ84-Rtf_yrXPN=KpVTMBmK2ZMsFw@mail.gmail.com>
References:
	 <CABBJUpepz+TU-Y6oFkpv9sJ84-Rtf_yrXPN=KpVTMBmK2ZMsFw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 09 Apr 2013 10:19:27 +0200
Message-ID: <1365495567.2171.34.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [PROPOSAL] add a leading backslash to classname when
 serializing/var_exporting
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Tue, 2013-04-09 at 11:28 +0800, Laruence wrote:
> Hey:
> 
>     bug is described at #64554
> 
>     I proposal to add a leading backslash to all classnames (not only ns
> names, since no harm, consistent and make sense) when doing serialize,
> var_export etc.
> 
>    what do you think?

This breaks compatibility with serialization with <=5.2.

Right now, when using no namespaces, you can serialiaze things in
5.6-dev and unserialize in older versions.

In the bug I also don't see a need for doing this in serialize.
unserialize should know those are fully qualified.

var_export is a bit more nifty. I see a similar compatibility issue as
with serialize but also the use case ...

johannes