Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67020
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51647536.6030108@sugarcrm.com>
References: <CABBJUpepz+TU-Y6oFkpv9sJ84-Rtf_yrXPN=KpVTMBmK2ZMsFw@mail.gmail.com>
	<51647536.6030108@sugarcrm.com>
Date: Tue, 9 Apr 2013 23:23:14 +0300
Message-ID: <CAGbiJu-qg8d4pdYQyeDTwE=dPPzmSjXZUwqRtz7jOSoYsx3L3Q@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Laruence <laruence@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [PROPOSAL] add a leading backslash to classname when serializing/var_exporting
From: dor.tchizik@gmail.com (Madara Uchiha)

Well, why would you need to serialize an object in one version of PHP,
and unserialize it in another?

On Tue, Apr 9, 2013 at 11:08 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>>     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.
>
> I'm not sure what this has to do with serialize. For var_export it may
> be useful but the use case looks kind of limited. I can't think of a
> common case where such change would be beneficial, and since it's a BC
> break I don't think it is worth it, unless we can find a real use case
> where it is necessary. In the original bug, it says that the user would
> use var_export in different namespace, but why would you need to do this?
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>