Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113736
MIME-Version: 1.0
References: <CAF+90c_8Z389ZA2725QDT0bx8sTfaeh4jXRs02E6GZy83pXkVg@mail.gmail.com>
 <CAOWwgpkWMy6VyEPXTsuLUsmSTY1tmmCTqg3HmB6r_uBzFEv=Lg@mail.gmail.com> <20210324103754.2551c075@mcmic-probook.opensides.be>
In-Reply-To: <20210324103754.2551c075@mcmic-probook.opensides.be>
Date: Wed, 24 Mar 2021 10:55:14 +0100
Message-ID: <CAF+90c-LiKPWguA5GSzEo+g_AcCkWfivECGtuxXinPAbe4mfkQ@mail.gmail.com>
To: =?UTF-8?Q?C=C3=B4me_Chilliet?= <come.chilliet@fusiondirectory.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009e47f505be454c44"
Subject: Re: [PHP-DEV] [RFC] Phasing out Serializable
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000009e47f505be454c44
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 24, 2021 at 10:38 AM C=C3=B4me Chilliet <
come.chilliet@fusiondirectory.org> wrote:

> Le Tue, 23 Mar 2021 17:01:40 +0100,
> Nicolas Grekas <nicolas.grekas+php@gmail.com> a =C3=A9crit :
> > Picking up a loose thread:
> > > https://wiki.php.net/rfc/custom_object_serialization introduced a
> > > replacement for Serializable in PHP 7.4, so it's time to think about
> > > deprecating and removing the old mechanism:
> > >
> > > https://wiki.php.net/rfc/phase_out_serializable
> > >
> > > This RFC follows a rather conversative approach. In PHP 8.1 there wil=
l
> be a
> > > deprecation warning if Serializable is implemented without also
> > > implementing __serialize() and __unserialize(). In PHP 9.0, support f=
or
> > > Serializable is dropped internally, and only the interface retained.
> In PHP
> > > 10.0 the interface is dropped as well.
> > >
>
> It is not clear neither in
> https://wiki.php.net/rfc/custom_object_serialization
>  nor in the documentation if it is possible to call parent::__serialize()
> to
>  only add a few fields to serialization.
>
> Is this legal/correct/useful:
>
> public __serialize ( ) : array
> {
>   $data =3D parent::__serialize();
>   $data['specialField'] =3D $data['special']->complicatedStuff();
>   unset($data['special']);
>   return $data;
> }
>
> public __unserialize ( array $data ) : void
> {
>   $data['special'] =3D new SpecialComplicatedThing($data['specialField'])=
;
>   unset($data['specialField']);
>   parent::__unserialize($data);
> }
>

Yes, this is possible.

Regards,
Nikita

--0000000000009e47f505be454c44--