Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67016
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mrclay.org from 50.22.11.19 cause and error)
Message-ID: <51641BED.7070501@mrclay.org>
Date: Tue, 09 Apr 2013 09:47:25 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
References: <CABBJUpepz+TU-Y6oFkpv9sJ84-Rtf_yrXPN=KpVTMBmK2ZMsFw@mail.gmail.com>
In-Reply-To: <CABBJUpepz+TU-Y6oFkpv9sJ84-Rtf_yrXPN=KpVTMBmK2ZMsFw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [PROPOSAL] add a leading backslash to classname when
 serializing/var_exporting
From: steve@mrclay.org (Steve Clay)

On 4/8/13 11:28 PM, Laruence wrote:
>      bug is described at #64554

-> https://bugs.php.net/bug.php?id=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.

Short term: Add note to the var_export() docs:

"For full compatibility with namespaces, the representation must be executed within the 
root namespace."


Proposal seems reasonable to me (as Johannes mentioned, serialize should already be OK).

I think we're under no obligation to have serialized forms created in one version work in 
previous versions [1], though FC of already persisted strings are important.

Note this won't solve the problem of existing var_export strings created in past versions. 
(We'll still need some kind of note.)


[1] If an app needs BC of code like \Foo::__set_state(... I would think it'd be easy 
enough to strip away the escapes.


Steve Clay
-- 
http://www.mrclay.org/