Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128324
Precedence: bulk
MIME-Version: 1.0
References: <CAJWOiuN8fuejkX1Tj0h=s_Fs2bGEtz-qdMZxRTC1s4at23y=Vw@mail.gmail.com>
In-Reply-To: <CAJWOiuN8fuejkX1Tj0h=s_Fs2bGEtz-qdMZxRTC1s4at23y=Vw@mail.gmail.com>
Date: Thu, 31 Jul 2025 09:33:24 +0300
Message-ID: <CANTuiHs0QnVMwh5q1ZLo5gAdASDHdNP99u=Pstsv1LWn3dFSeA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Optional Catch Block Body
To: Mihail Liahimov <91liahim@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000039fa11063b33d2a6"
From: xepozzd@gmail.com (Dmitry Derepko)

--00000000000039fa11063b33d2a6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 31, 2025 at 7:55=E2=80=AFAM Mihail Liahimov <91liahim@gmail.com=
> wrote:

> Introduction
>
> Currently, PHP requires a block body for catch clauses even when the
> caught exception is not used. This results in unnecessary boilerplate cod=
e.
> This RFC proposes allowing catch clauses without a body when the exceptio=
n
> variable is omitted.
>
> Proposal
>
> Allow the following syntax where the curly braces can be omitted when no
> exception variable is specified and no handling is needed:
>

Hey!

I even tried recently to code it. Looked really good and I thought about
publishing it and creating the RFC.

I have use-cases where I need to try to send a request to a server and
forget about an exception if so:

try { $client->post(...); }

If it fails I'm ok with it.
For sure, there are many pitfalls when you allow users to ignore any
exceptions and errors, but it's up to users, right?

About the proposal:

try {
    // code that may throw
} catch (SomeError);

How can I catch AnotherError?

try {
    // code that may throw
} catch (SomeError)
  catch (AnotherError) { ... }

OR

try {
    // code that may throw
} catch (AnotherError) { ... }
 catch (SomeError);

What about "finally" construction?

try {
    // code that may throw
} catch (SomeError)
 finally {}

Should the error flow into the "finally" construction?


--=20
Best regards,
Dmitrii Derepko.
@xepozz

--00000000000039fa11063b33d2a6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>On Thu, Jul 31, 2025 at 7:55=E2=80=
=AFAM Mihail Liahimov &lt;<a href=3D"mailto:91liahim@gmail.com">91liahim@gm=
ail.com</a>&gt; wrote:</div></div><div class=3D"gmail_quote gmail_quote_con=
tainer"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex"><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 boi=
lerplate code. This RFC proposes allowing catch clauses without a body when=
 the exception variable is omitted.<br><br>Proposal<br><br>Allow the follow=
ing syntax where the curly braces can be omitted when no exception variable=
 is specified and no handling is needed:<br></div>
</blockquote></div><div><br clear=3D"all"></div><div>Hey!</div><div><br></d=
iv><div>I even tried recently to code it. Looked really good and I thought =
about publishing it and creating the RFC.=C2=A0</div><div><br></div><div>I =
have use-cases where I need to try to send a request to a server and forget=
 about an exception if so:</div><div><br></div><div>try { $client-&gt;post(=
...); }</div><div><br></div><div>If it fails I&#39;m ok with it.</div><div>=
For sure, there are many pitfalls when you allow users to ignore any except=
ions and errors, but it&#39;s up to users, right?</div><div><br></div><div>=
About the proposal:</div><div><br></div><div>try {<br>=C2=A0 =C2=A0 // code=
 that may throw<br>} catch (SomeError);<br></div><div><br></div><div>How ca=
n I catch AnotherError?</div><div><br></div><div>try {<br>=C2=A0 =C2=A0 // =
code that may throw<br>} catch (SomeError)</div><div>=C2=A0 catch (AnotherE=
rror) { ... }</div><div><br></div><div>OR</div><div><br></div><div>try {<br=
>=C2=A0 =C2=A0 // code that may throw<br>} catch (AnotherError) { ... }</di=
v><div>=C2=A0catch (SomeError);</div><div><br></div><div>What about &quot;f=
inally&quot; construction?</div><div><div><br class=3D"gmail-Apple-intercha=
nge-newline">try {<br>=C2=A0 =C2=A0 // code that may throw<br>} catch (Some=
Error)</div><div>=C2=A0finally {}<br></div><div><br></div></div><div>Should=
 the error flow into the &quot;finally&quot; construction?=C2=A0</div><div>=
<br></div><div><br></div><span class=3D"gmail_signature_prefix">-- </span><=
br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div style=
=3D"color:rgb(34,34,34)">Best regards,</div><div style=3D"color:rgb(34,34,3=
4)"><div dir=3D"ltr"><div dir=3D"ltr">Dmitrii Derepko.</div><div><a>@xepozz=
</a></div></div></div></div></div></div>

--00000000000039fa11063b33d2a6--