Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125727
Message-ID: <92135a49-84c4-42ac-9c98-9d83e33f4c51@gmx.de>
Date: Wed, 2 Oct 2024 13:31:02 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] Change Directory class to behave like an opaque
 object
Content-Language: de-DE
To: "Gina P. Banyard" <internals@gpb.moe>,
 Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
References: <2VnM6xycBpzqzDnAZKWS4zxCSUjvoKywJRiBzTcGhS8axaFS7QwbGNQtjkovo1jQi1XLiEGGTi3KfQfWoxUT527U_-6IGO3092BZdW436q0=@gpb.moe>
 <3ab9db77462c5f49c7c4a977098ba4677deb363f.camel@ageofdream.com>
 <ZkeezQs79B9mZpTWi3KHmLdYsFcxNCgqvdeuSRYG-S1_WMXghAVivIUtxIIT0t9LmgDvGx-zlOtZxV_c5BXHNH9dnZ43_wEJqOTab0YIaOc=@gpb.moe>
 <680c10a5523288e4b1df2760e6e03da61a1ac6c5.camel@ageofdream.com>
 <c7ec5fa1-6fc2-4253-ac8b-61e4462e294f@app.fastmail.com>
 <892124c704f6e18abe2d6c85f6e207ed516d4ed1.camel@ageofdream.com>
 <bf9e4589-b874-4ca7-95cf-c7a88f3aeec6@app.fastmail.com>
 <0VZtrSDTuGwRkGGWFc_2yiAbJa69FBZ1dvn1xfi7dr5KpuGs-Xuo8xH-2WPOwzj-4KB-y0wrfg3t5QXEpx6TvSM0FVYpPfY7jD8efFweGLk=@gpb.moe>
In-Reply-To: <0VZtrSDTuGwRkGGWFc_2yiAbJa69FBZ1dvn1xfi7dr5KpuGs-Xuo8xH-2WPOwzj-4KB-y0wrfg3t5QXEpx6TvSM0FVYpPfY7jD8efFweGLk=@gpb.moe>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
UI-OutboundReport: notjunk:1;M01:P0:n1QbSsCPGjs=;txjS4z8STJerc8nx6KrQtY8ePVw
 Urq9YJWW5EXW3Mkm22ssT0C6QKYGZ3f5bA2HJgguDeZ4VCkkgpyrVfC3vTW8fnVtVbr7eAVna
 hbB7gwA4Jb+UZ/o67pnBFVbseog5+EIQMfr/B2k5k8LhnKxAW2KUqfN82UhnSMov+o7sWhKrx
 adfr+bBjnr1FGj+gpwUvOmiKul9tfwmVZM2uHF2PeKaL0zOlxn9r/zuqJtQkKKFLFmF3OBDkD
 STsGXRwwqomT3MpwZzXMMktbBvBkExhRq/jjufak7flqhlZyP0Z4HQ6R+W23HMy4IJCPWeKRL
 MWvw0l1QgBT341j6jOGQ84KUw2SNingOotx5zKiZ5iVcvC0oO1/bC5B6MXAbgg8JliN555fUe
 EHGsedXyUpIqBFNArZTFteN+p31twsjT0H006MzYl7ZIA1xhahtIL5vsGbER6oRd/V7Xi1MXN
 0iLgGv/6shIzaPeOBM93r5cNH133/bHo3uSX2fy6WU9NfTYILoifPEzEqSFgHHjrqB63iNx3o
 pC9q0guV05V1Pdd/Dy0/IzQekcCu6pJHgiaY4MCsl39RntaxNvlnchDk+sGMJm5avkSOohQre
 mUtLBkyL6RuehBTrHc15KDOeyrTVcWWXX+l1VluvWtxoaaTpQT+NQ/xAEDUSoaVyMefcC/Kfs
 PxUsuUGPFLMJ7nwiO7br2IPiTqMiMSBvktFVtSjbr4ebUMocBw4g8rVIrwzqGGntYc5QzHFu1
 AS2rHJ8z3pJ0omfWpgLcyv65feOIZXljjIAjVBOT/5vWlDwKorJLv2MomGJgWFq8nvz80y2fk
 3osSDGYwf/imbsgkFnE4DyvA==
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 02.10.2024 at 12:55, Gina P. Banyard wrote:

> On Wednesday, 2 October 2024 at 00:32, Larry Garfield <larry@garfieldtec=
h.com> wrote:
>
>> I have no strong opinions on this RFC as I've not paid close attention =
to it, but "we can't introduce an unnamespaced class, that's a BC break" i=
s simply not true, and not consistent with how Internals and the stdlib ar=
e and have been developed.
>
> This is not a new class, it is a class that has existed since the PHP 4 =
days.

Plus it is not part of some rarely used extension, but rather of
ext/standard, so it is always available, and nobody had been able to
declare a userland class Directory (https://3v4l.org/dUOq0).

> Arguably, if this would be a new class, that argument would have more me=
rit.

Right.

> But changing the name of class that is 20+ years old and could have been=
 used in type declarations since possibly PHP 5.0 is a non-starter IMHO.

I agree, although one could pursue the RFC process.  This would be a
completely different RFC, though.

Christoph