Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128326
Precedence: bulk
MIME-Version: 1.0
References: <CAJWOiuN8fuejkX1Tj0h=s_Fs2bGEtz-qdMZxRTC1s4at23y=Vw@mail.gmail.com>
 <CANTuiHs0QnVMwh5q1ZLo5gAdASDHdNP99u=Pstsv1LWn3dFSeA@mail.gmail.com>
In-Reply-To: <CANTuiHs0QnVMwh5q1ZLo5gAdASDHdNP99u=Pstsv1LWn3dFSeA@mail.gmail.com>
Date: Thu, 31 Jul 2025 11:41:24 +0500
Message-ID: <CAJWOiuPxtFsCC74X1Z7dpAny5ZESkVZrVNQReR6ttT6OTuPv9A@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Optional Catch Block Body
To: Dmitry Derepko <xepozzd@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c0b048063b33ee89"
From: 91liahim@gmail.com (Mihail Liahimov)

--000000000000c0b048063b33ee89
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, Dmitry

I've been thinking about all these problems. I can't say a definite
decision yet, but I think it will be possible to discuss specific solutions
if the community approves this proposal in principle.

At the moment, I was thinking about a similar syntaxis.:

try {
} catch (ErrorA) catch (ErrorB) {
// some handling
}

or with finally:

try {
} catch (Error) finally {
// ...
}

=D1=87=D1=82, 31 =D0=B8=D1=8E=D0=BB. 2025=E2=80=AF=D0=B3. =D0=B2 11:33, Dmi=
try Derepko <xepozzd@gmail.com>:

> On Thu, Jul 31, 2025 at 7:55=E2=80=AFAM Mihail Liahimov <91liahim@gmail.c=
om>
> wrote:
>
>> Introduction
>>
>> Currently, PHP requires a block body for catch clauses even when the
>> caught exception is not used. This results in unnecessary boilerplate co=
de.
>> This RFC proposes allowing catch clauses without a body when the excepti=
on
>> 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?
>
>
> --
> Best regards,
> Dmitrii Derepko.
> @xepozz
>

--000000000000c0b048063b33ee89
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Dmitry<br><br>I&#39;ve been thinking about all these p=
roblems. I can&#39;t say a definite decision yet, but I think it will be po=
ssible to discuss specific solutions if the community approves this proposa=
l in principle.<br><br>At the moment, I was thinking about a similar syntax=
is.:<br><br>try {<br>} catch (ErrorA) catch (ErrorB) {<br>// some handling<=
br>}<br><br>or with finally:<br><br>try {<br>} catch (Error) finally {<br>/=
/ ...<br>}<br></div><br><div class=3D"gmail_quote gmail_quote_container"><d=
iv dir=3D"ltr" class=3D"gmail_attr">=D1=87=D1=82, 31 =D0=B8=D1=8E=D0=BB. 20=
25=E2=80=AF=D0=B3. =D0=B2 11:33, Dmitry Derepko &lt;<a href=3D"mailto:xepoz=
zd@gmail.com">xepozzd@gmail.com</a>&gt;:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><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" target=3D"_blank">91liahim@gmail.com</a>&gt; wrote:</div></div>=
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n: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 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></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>try {<br>=C2=A0 =C2=A0 // cod=
e that may throw<br>} catch (SomeError)</div><div>=C2=A0finally {}<br></div=
><div><br></div></div><div>Should the error flow into the &quot;finally&quo=
t; construction?=C2=A0</div><div><br></div><div><br></div><span class=3D"gm=
ail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signatu=
re"><div dir=3D"ltr"><div style=3D"color:rgb(34,34,34)">Best regards,</div>=
<div style=3D"color:rgb(34,34,34)"><div dir=3D"ltr"><div dir=3D"ltr">Dmitri=
i Derepko.</div><div><a>@xepozz</a></div></div></div></div></div></div>
</blockquote></div>

--000000000000c0b048063b33ee89--