Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125670
Date: Tue, 24 Sep 2024 17:25:44 +0000
To: Christian Schneider <cschneid@cschneid.com>
Cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] Change Directory class to behave like an opaque object
Message-ID: <K6XMvPafLWFFTu_Y9zQgYNPfARY_HVNKdIel9Ot0Qk_iNtH7lfeVOoVBsxF8Bgt-3tahNPaudogzHcSRz2QbK6E4XLm9QDUuSS9DTm8RP3w=@gpb.moe>
In-Reply-To: <2FB7E806-05B9-4493-AFF3-42A494F0D9CC@cschneid.com>
References: <2VnM6xycBpzqzDnAZKWS4zxCSUjvoKywJRiBzTcGhS8axaFS7QwbGNQtjkovo1jQi1XLiEGGTi3KfQfWoxUT527U_-6IGO3092BZdW436q0=@gpb.moe> <2FB7E806-05B9-4493-AFF3-42A494F0D9CC@cschneid.com>
Feedback-ID: 96993444:user:proton
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: internals@gpb.moe ("Gina P. Banyard")

On Tuesday, 24 September 2024 at 14:34, Christian Schneider <cschneid@cschn=
eid.com> wrote:

> Am 14.09.2024 um 17:33 schrieb Gina P. Banyard internals@gpb.moe:
>=20
> > I came across the Directory class while doing some code exploration of =
ext/standard.
> > This class is effectively an opaque object for Directory resources, how=
ever it doesn't behave like one, as it has existed since PHP 4.
> >=20
> > As such, I am proposing an RFC to turn this class into an opaque object=
.
> >=20
> > RFC: https://wiki.php.net/rfc/directory-opaque-object
>=20
>=20
> While I understand the other proposed changes (although I'm always a bit =
wary about the wish to make more and more things final) I was wondering why=
 you would prevent cloning?
> What are the possible downsides in allowing people to get a clone of a Di=
rectory object?

Mainly because the current behaviour doesn't do a proper clone.
It still shares a common directory resource with the original object meanin=
g that there is spooky action at a distance even thought cloning is meant t=
o prevent this.

Best regards,

Gina P. Banyard