Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104194
MIME-Version: 1.0
References: <CAL=_i_=KCzMg63OPSGfjnb5m2sjK-5XTuCfokGMBwP-RBFH5Ag@mail.gmail.com>
 <2fed98af-3831-1a1c-def8-04793fcc0c6f@birkholz.biz> <CAF+90c-KE6NawSF+8DBrnugUR3Kgo7=9r53Uzgb5d+jBeNYQWQ@mail.gmail.com>
 <2a566239-d205-72f8-fd78-630b7ff01581@birkholz.biz>
In-Reply-To: <2a566239-d205-72f8-fd78-630b7ff01581@birkholz.biz>
Date: Tue, 5 Feb 2019 17:23:27 +0100
Message-ID: <CAFPFaMK-O6sKCo5H_F6h0dG-V070GYYM_Mh-fnyffKd1A=rPXA@mail.gmail.com>
To: Dennis Birkholz <php@dennis.birkholz.biz>
Cc: Nikita Popov <nikita.ppv@gmail.com>, Joe Watkins <krakjoe@php.net>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000052bc8505812808c7"
Subject: Re: [PHP-DEV] RFC Weakrefs
From: george.banyard@gmail.com (Girgias)

--00000000000052bc8505812808c7
Content-Type: text/plain; charset="UTF-8"

On Tue, 5 Feb 2019 at 17:06, Dennis Birkholz <php@dennis.birkholz.biz>
wrote:

> So I would really prefer the WeakReference class would just be
> serializable with all the consequences you outlined. Maybe for PHP 8 we
> will decide to require all classes to be serializable except classes
> that implement the Unserializable interface or something... Or the magic
> __isSerializable() method that can decide this at runtime for the actual
> state of an object without failing hard when trying it.
>
> Greets
> Dennis
>

That on its own would need an RFC AFAIK and I'm not really a fan of this
hypothetical change.
Also it feels kind of backwards imho. Why should I specify that something
is NOT serializable
when serialisation is a behaviour that usually needs special care with?

Also what would happen when someone does the typical thing to prevent
serialization:
public function __sleep() { throw new Exception(); }

Best regards

George P. Banyard

--00000000000052bc8505812808c7--