Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102587
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
To: Andrea Faulds <ajf@ajf.me>, internals@lists.php.net
References: <04.57.38004.22D38C85@pb1.pair.com>
Message-ID: <5ee4eec2-4910-552a-a3ad-248645fbe037@gmx.de>
Date: Wed, 4 Jul 2018 23:33:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <04.57.38004.22D38C85@pb1.pair.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: [PATCH] Make var_export() output "(object)array(..." instead
 of"stdClass::__set_state(..." for stdClass
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 14.03.2017 at 19:57, Andrea Faulds wrote:

> Since stdClass has no __set_state method, var_export() produces unusable
> output if given an object of that class. I wrote a patch that would make
> var_export() produce a cast to object instead, which could be evaluated
> to get back a stdClass:
> 
> https://github.com/php/php-src/pull/2420
> 
> Any thoughts/comments?
> 
> If you're wondering about whether a __set_state method should be added
> to stdClass, I posted some thoughts in the pull request discussion already.

FTR: If nobody objects, I'll merge this PR into master on 2018-07-12, so
that it goes into PHP 7.3.

See <https://github.com/php/php-src/pull/2420#issuecomment-402561913>.

-- 
Christoph M. Becker