Re: Re: #53437
| From: | Etienne Kneuss | Date: | Mon, 10 Jun 2013 12:07:48 +0000 |
| Subject: | Re: Re: #53437 | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-67676@lists.php.net to get a copy of this message | ||
On Mon, Jun 10, 2013 at 1:47 PM, Pierre Joye <pierre.php@gmail.com> wrote:
>
> On Jun 10, 2013 1:24 PM, "Etienne Kneuss" <colder@php.net> wrote:
> >
>
> > So if I understand correctly var_dump now indicates a different type than
> > what accessing the property returns?
> >
> > Even if the change itself does not constitute a big BC break, this
> > behavior is confusing and seems like a big no-no to me.
>
> So a slight change in a debugging function is enough to keep a crash in
> many production code? What do you propose then?
>
You make it sound like there are only those two options :)
I propose we fix the serialization/unserialization crash in a way that does
not affect var_dump.
--
Etienne Kneuss