Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103828
MIME-Version: 1.0
References: <CAF+90c-GfwWSJ+LUUYrb6gpZRrwP=XX=hWFD9DL-3xQhBOgp+A@mail.gmail.com>
In-Reply-To: <CAF+90c-GfwWSJ+LUUYrb6gpZRrwP=XX=hWFD9DL-3xQhBOgp+A@mail.gmail.com>
Date: Thu, 24 Jan 2019 15:09:17 +0100
Message-ID: <CADyq6sLq27dT6VRB59ihJhHUanDvwDUnHAdPE6Q6vWXsbYrRfw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>, Nicolas Grekas <nicolas.grekas+php@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000004ec6f7058034c234"
Subject: Re: [PHP-DEV] [RFC] New custom object serialization mechanism
From: ocramius@gmail.com (Marco Pivetta)

--0000000000004ec6f7058034c234
Content-Type: text/plain; charset="UTF-8"

Not really fussed about having another implicit interface for serialization
(via magic methods).

Wouldn't a new interface make this clear, explicit, and make the
deprecation path easier (together with the migration)?

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


On Thu, Jan 24, 2019 at 1:27 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I'd like to propose a new custom object serialization mechanism intended to
> replace the broken Serializable interface:
>
> https://wiki.php.net/rfc/custom_object_serialization
>
> This was already previously discussed in
> https://externals.io/message/98834,
> this just brings it into RFC form. The latest motivation for this is
> https://bugs.php.net/bug.php?id=77302, a compatibility issue in 7.3
> affecting Symfony, caused by Serializable. We can't fix Serializable, but
> we can at least make sure that a working alternative exists.
>
> Regards,
> Nikita
>

--0000000000004ec6f7058034c234--