Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128344
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: [PHP-DEV] [RFC] Optional Catch Block Body
Date: Thu, 31 Jul 2025 15:46:41 +0200
References: <CAJWOiuN8fuejkX1Tj0h=s_Fs2bGEtz-qdMZxRTC1s4at23y=Vw@mail.gmail.com>
 <095f25f5-695b-46d4-9f31-5d7e7a04ce05@rwec.co.uk>
 <CANS-=peEKJRT0nZeCQPLah-rg0pDd1F1JecvAj95ya0MP8JNPg@mail.gmail.com>
 <a12e42bf-fd60-45c6-a2f6-91308cb0cb32@rwec.co.uk>
To: internals@lists.php.net
In-Reply-To: <a12e42bf-fd60-45c6-a2f6-91308cb0cb32@rwec.co.uk>
Message-ID: <7E01A890-E986-4156-B598-ECD07264C39A@cschneid.com>
From: cschneid@cschneid.com (Christian Schneider)

Am 31.07.2025 um 13:16 schrieb Rowan Tommins [IMSoP] =
<imsop.php@rwec.co.uk>:
> I think an inline syntax like this would be a powerful feature, and a =
potential replacement for the @ operator:
>=20
> $fh =3D null;
> $fh =3D try fopen($filePath, 'w') ignore (FileLockedException);

First of all: I'm wary because partial error handling seems dangerous to =
mel do I know all possible Exception types and which ones should abort =
and which ones should continue? Or will it encourage try ... ignore =
(Exception)? I have to admit that I'm also a sceptic of converting every =
possible info/warning/error to an Exception but that's a different topic =
;-)

If we decide to add something like the above I would very much prefer =
the try ... ignore block to be an expression with value null on error, =
making the first line obsolete. One could still use
	$lines =3D try file($filepath) ignore (FileLockedException) ?? =
[];
if another default value is preferred.

Regards,
- Chris