Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115903
Date: Tue, 31 Aug 2021 16:16:08 +0200
To: internals@lists.php.net
Message-ID: <20210831161608.1e994d57@mcmic-probook.opensides.be>
In-Reply-To: <20210831155642.1779f22f@mcmic-probook.opensides.be>
References: <20210831155642.1779f22f@mcmic-probook.opensides.be>
Organization: FusionDirectory
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Resources and object resources
From: come.chilliet@fusiondirectory.org (=?UTF-8?B?Q8O0bWU=?= Chilliet)

Le Tue, 31 Aug 2021 15:56:42 +0200,
C=C3=B4me Chilliet <come.chilliet@fusiondirectory.org> a =C3=A9crit :
> It seems to be consistent accross versions: https://3v4l.org/BHtAh
>=20
> But what will happen when LDAP connections are turned into objects in 8.1?
> Will they also become int(0) upon serialization or will they behave in an
> other way? I could not find a case of resource that became an object and =
is
> allowed on 3v4l to test this. There is no LDAP or CURL in there.

Quick followup on this, I found a case that can be tested on 3v4l:
https://3v4l.org/EKFP0

-> Fatal error: Uncaught Exception: Serialization of 'XMLParser' is not all=
owed
in /in/EKFP0:13

So it seems objects of this kind throw when serialized (I hope they all do
that). It is not clear to me how that behaves with session, will it throw as
soon as affected to $_SESSION, or at the end of the request?

https://www.php.net/manual/en/class.xmlparser.php -> does fully opaque impl=
ies
non serializable?