Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128321
Message-ID: <26D77653-F0F6-4156-ADBA-86D9955C45B8@nicksdot.dev>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_C3F2C93F-DEF8-419D-A466-5EA29AFC38D4"
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: Re: [PHP-DEV] [RFC] Optional Catch Block Body
Date: Thu, 31 Jul 2025 12:43:34 +0700
In-Reply-To: <CAJWOiuN8fuejkX1Tj0h=s_Fs2bGEtz-qdMZxRTC1s4at23y=Vw@mail.gmail.com>
Cc: PHP internals <internals@lists.php.net>
To: Mihail Liahimov <91liahim@gmail.com>
References: <CAJWOiuN8fuejkX1Tj0h=s_Fs2bGEtz-qdMZxRTC1s4at23y=Vw@mail.gmail.com>
From: php@nicksdot.dev (Nick)


--Apple-Mail=_C3F2C93F-DEF8-419D-A466-5EA29AFC38D4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 31. Jul 2025, at 11:53, Mihail Liahimov <91liahim@gmail.com> wrote:
>=20
> Introduction
>=20
> Currently, PHP requires a block body for catch clauses even when the =
caught exception is not used. This results in unnecessary boilerplate =
code. This RFC proposes allowing catch clauses without a body when the =
exception variable is omitted.
>=20
> Proposal
>=20
> Allow the following syntax where the curly braces can be omitted when =
no exception variable is specified and no handling is needed:
>=20
> try {
>     // code that may throw
> } catch (SomeError);
>=20
> This would be equivalent to:
>=20
> try {
>     // code that may throw
> } catch (SomeError) {}
>=20
> Motivation
>=20
> Reduced Boilerplate: Eliminates unnecessary empty blocks when =
exceptions only need to be caught and ignored.
> Improved Readability: Makes the code more concise and focuses on the =
important parts.
>=20
> Backward Incompatible Changes
>=20
> None. This is purely an additive change to the syntax.
>=20

Hey Mihail,

Why would the `catch (SomeError)` still be required if it isn=E2=80=99t =
used?

Cheers,
Nick=

--Apple-Mail=_C3F2C93F-DEF8-419D-A466-5EA29AFC38D4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><br =
id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote =
type=3D"cite"><div>On 31. Jul 2025, at 11:53, Mihail Liahimov =
&lt;91liahim@gmail.com&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div =
dir=3D"ltr">Introduction<br><br>Currently, PHP requires a block body for =
catch clauses even when the caught exception is not used. This results =
in unnecessary boilerplate code. This RFC proposes allowing catch =
clauses without a body when the exception variable is =
omitted.<br><br>Proposal<br><br>Allow the following syntax where the =
curly braces can be omitted when no exception variable is specified and =
no handling is needed:<br><br>try {<br>&nbsp; &nbsp; // code that may =
throw<br>} catch (SomeError);<br><br>This would be equivalent =
to:<br><br>try {<br>&nbsp; &nbsp; // code that may throw<br>} catch =
(SomeError) {}<br><br>Motivation<br><br>Reduced Boilerplate: Eliminates =
unnecessary empty blocks when exceptions only need to be caught and =
ignored.<br>Improved Readability: Makes the code more concise and =
focuses on the important parts.<br><br>Backward Incompatible =
Changes<br><br>None. This is purely an additive change to the =
syntax.<br><br></div>
</div></blockquote></div><br><div>Hey =
Mihail,</div><div><br></div><div>Why would the `catch (SomeError)` still =
be required if it isn=E2=80=99t =
used?</div><div><br></div><div><b>Cheers,</b></div><div>Nick</div></body><=
/html>=

--Apple-Mail=_C3F2C93F-DEF8-419D-A466-5EA29AFC38D4--