Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129195
Date: Tue, 11 Nov 2025 11:31:15 +0000 (GMT)
To: Larry Garfield <larry@garfieldtech.com>
cc: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] Context Managers
In-Reply-To: <566ce444-0cba-4a72-94e3-64f52b3cf93c@app.fastmail.com>
Message-ID: <82532f65-c944-a854-170f-3b70ce1c552d@php.net>
References: <a087d9fa-112a-4631-9c84-3efae641e0db@app.fastmail.com> <566ce444-0cba-4a72-94e3-64f52b3cf93c@app.fastmail.com>
Precedence: list
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-1658006828-1762860675=:3802"
From: derick@php.net (Derick Rethans)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1658006828-1762860675=:3802
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

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 out=20
of loops (such as foreach) needs to be handled with care.

> 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/hel=
pers.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.

> 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
--8323329-1658006828-1762860675=:3802--