Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129078
Precedence: list
MIME-Version: 1.0
References: <CAFyg4HhrzQrE-q8D6WVkyq9tY+hzR=8rXiXLDPYpNKdYeydrVA@mail.gmail.com>
 <CAMW7n8Bqze3Z7z9ZqSXSwVH4gqLQ3a9xYYSH33hvopOQ9DQChQ@mail.gmail.com> <CAFyg4HjvWDCtfcY8vMYekqpyoLVbXYed=ZMv2X+8UaE--p+QkA@mail.gmail.com>
In-Reply-To: <CAFyg4HjvWDCtfcY8vMYekqpyoLVbXYed=ZMv2X+8UaE--p+QkA@mail.gmail.com>
Date: Wed, 5 Nov 2025 07:27:34 +0200
Message-ID: <CAMW7n8Dz+rbpi1HVhB=hJNevbraQrCqzvyQhev4MsL6NxqRJag@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC][Discussion] use construct (Block Scoping)
To: Seifeddine Gmati <azjezz@carthage.software>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: edmond.ht@gmail.com (Edmond Dantes)

Hello

> A disposal interface has its issues.

Although Arnaud Le Blanc has already covered this topic thoroughly,
I=E2=80=99d like to approach it from a slightly different angle.
Let=E2=80=99s not think of __enter__/__exit__ + RefCount as a problem. Ever=
y
approach has its own purpose. In this case, there is a clear
distinction between Scope logic and __enter__/__exit__ logic. These
are two different concepts, and you cannot and should not try to
satisfy both RefCount and __enter__/__exit__ conditions at the same
time.

The purpose of __enter__/__exit__ is to handle the try-catch-finally
pattern for a resource regardless of the reference count. Therefore,
RefCount is not an issue.
(although PHP can automatically issue a warning when attempting to
call the method while the reference count is greater than one)

If PHP applies unset or __enter__/__exit__ depending on whether an
interface is implemented, it will introduce hidden behavior in the
code, making it harder for developers to understand what is happening.
Compare the two cases:

```php
// I know for sure that Scope implements the interface
// required to be used with "with"
with $scope =3D new Scope() {}

// I have no idea whether the File class implements
// the required interface or not. It=E2=80=99s unclear what will happen in =
the end.
with $file =3D new File("...") {}

```

So, in Python you cannot use arbitrary objects in a with statement,
only those that implement the __enter__ and __exit__ contract.
Therefore, in Python there is no ambiguity in the code. The developer
understands that if `with` is used, it means the object definitely
implements the required interface, otherwise an error will occur. PHP
must guarantee the same behavior.

P.S.
If I=E2=80=99m not mistaken, a recent RFC was proposed about context manage=
rs,
which covers exactly this logic.

---
Ed