Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103504
To: internals@lists.php.net
References: <a47689bc-33a5-b3c0-d2c0-802809f26b2c@php.net>
Message-ID: <072f23be-24bc-c05b-d908-f689980623c6@gmx.de>
Date: Mon, 26 Nov 2018 11:51:59 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <a47689bc-33a5-b3c0-d2c0-802809f26b2c@php.net>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: Built-in classes that cannot be serialized
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 26.11.2018 at 10:27, Sebastian Bergmann wrote:

> The following classes register zend_class_serialize_deny: Closure, COM,
> DOTNET, Generator, HashContext, Reflection, ReflectionClass,
> ReflectionClassConstant, ReflectionExtension, ReflectionException,
> ReflectionFunction, ReflectionFunctionAbstract, ReflectionGenerator,
> ReflectionMethod, ReflectionNamedType, ReflectionObject,
> ReflectionParameter, ReflectionProperty, ReflectionRype,
> ReflectionZendExtension, SimpleXmlElement, SplFileInfo, Variant.
> 
> Are these all the built-in classes that cannot be serialized?

Well, the com_dotnet classes have only been made unserializable very
recently, due to bug #77177, so I can imagine that there are more
classes.  Particularly, the database related classes come to mind.  For
instance, it's currently possible to serialize SQLite3 instances, albeit
that makes no sense ("O:7:"SQLite3":0:{}").

> Would it be possible to implement ReflectionClass::isSerializable() that
> returns false when the class is a) built-in and b) has
> zend_class_serialize_deny registered?

I presume that this could easily be implemented, but if the method
returns TRUE for all other cases, it would be misleading since classes
may unconditionally throw in __sleep().

-- 
Christoph M. Becker