Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129206
Feedback-ID: i8414410d:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Wed, 12 Nov 2025 09:46:23 -0600
To: "php internals" <internals@lists.php.net>
Message-ID: <4f8f00ce-d734-42a5-ac4d-da4f9ebf14f0@app.fastmail.com>
In-Reply-To: <82532f65-c944-a854-170f-3b70ce1c552d@php.net>
References: <a087d9fa-112a-4631-9c84-3efae641e0db@app.fastmail.com>
 <566ce444-0cba-4a72-94e3-64f52b3cf93c@app.fastmail.com>
 <82532f65-c944-a854-170f-3b70ce1c552d@php.net>
Subject: Re: [PHP-DEV] [RFC] Context Managers
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Nov 11, 2025, at 5:31 AM, Derick Rethans wrote:
> On Wed, 5 Nov 2025, Larry Garfield wrote:
>
>> On Wed, Nov 5, 2025, at 1:38 AM, Deleu wrote:
>>=20
>> > Out of curiosity, what happens if GOTO is used inside a context=20
>> > block to jump away from it?
>>=20
>> That would be a success case, just like break or return.  Basically=20
>> anything other than an exception is a success case.  (That said,=20
>> please don't use Goto. :-) )
>
> I do think you might need special attention to this case, as jumping o=
ut=20
> of loops (such as foreach) needs to be handled with care.

I defer to Arnaud here.

>> And now the big one... also in off-list discussion, Seifeddine noted=20
>> that Laravel already defines a global function named `with`:=20
>> https://github.com/laravel/framework/blob/12.x/src/Illuminate/Support=
/helpers.php#L510
>>=20
>> And since this RFC would require `with` to be a semi-reserved keyword=20
>> at the parser/token level, that creates a conflict.  (This would be=20
>> true even if it was namespaced, although Laravel is definitely Doing=20
>> It Wrong(tm) by using an unnamespaced function.)  Rendering all=20
>> Laravel deployments incompatible with PHP 8.6 until it makes a=20
>> breaking API change would be... not good for the ecosystem.
>
> PHP owns the top level namespace. That's been the going for as long as=
 I=20
> can remember. It was unwise for Laravel to flaunt that rule.

Yes, Laravel is in the wrong here, but AIUI even a namespaced function w=
ould conflict with a soft-reserved keyword.  And regardless, breaking La=
ravel is not a great plan.

>> 1. Java uses a parenthetical block on `try` for similar functionality=20
>> (though without a separate context manager).  That would look like:
>>=20
>> try (new Foo() as $foo) {
>>   // ...
>> }
>> // catch and finally become optional if there is a context.
>
> =E2=80=A6
>
>> 2. Either `use` or `using`.  The semantics here would be identical to=20
>> the current `with` proposal.
>
> IMO, the try syntax is more confusing than another overload of use.
>
> cheers,
> Derick

How about `using`?

--Larry Garfield