Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128325
Precedence: bulk
MIME-Version: 1.0
References: <CAJWOiuN8fuejkX1Tj0h=s_Fs2bGEtz-qdMZxRTC1s4at23y=Vw@mail.gmail.com>
 <CANLbj-pe0cyqaQkf2k2_XH+Ybj9Gy11-=M=eqxgaQsF62GJAeQ@mail.gmail.com>
In-Reply-To: <CANLbj-pe0cyqaQkf2k2_XH+Ybj9Gy11-=M=eqxgaQsF62GJAeQ@mail.gmail.com>
Date: Thu, 31 Jul 2025 11:35:53 +0500
Message-ID: <CAJWOiuNw7DycxqabvqZ0z4xKhsZJX4aOE65xXOoFGV9KsNrHEw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Optional Catch Block Body
To: Ayesh Karunaratne <ayesh@php.watch>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000075af0063b33dbb6"
From: 91liahim@gmail.com (Mihail Liahimov)

--000000000000075af0063b33dbb6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey, Ayesh! Thank you for noticing an important point.

Of course, empty catch blocks are bad practice in most cases. But this
particular proposal is not intended to encourage these bad practices. I'm
just suggesting that you don't have to write an extra boiler plate at the
syntax level in situations where it's necessary.

=D1=87=D1=82, 31 =D0=B8=D1=8E=D0=BB. 2025=E2=80=AF=D0=B3. =D0=B2 11:21, Aye=
sh Karunaratne <ayesh@php.watch>:

> > Motivation
> >
> > Reduced Boilerplate: Eliminates unnecessary empty blocks when exception=
s
> only need to be caught and ignored.
> > Improved Readability: Makes the code more concise and focuses on the
> important parts.
> >
>
> Empty `catch` blocks are a code-smell. If the `try` block is not ready
> to handle the exception, it should let the exception bubble up; not
> silence it. I think we should not encourage this further.
>

--000000000000075af0063b33dbb6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hey, Ayesh!=C2=A0Thank you for noticing an important point=
.<br><br>Of course, empty catch blocks are bad practice in most cases. But =
this particular proposal is not intended to encourage these bad practices. =
I&#39;m just suggesting that you don&#39;t have to write an extra boiler pl=
ate at the syntax level in situations where it&#39;s necessary.<br></div><b=
r><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=
=3D"gmail_attr">=D1=87=D1=82, 31 =D0=B8=D1=8E=D0=BB. 2025=E2=80=AF=D0=B3. =
=D0=B2 11:21, Ayesh Karunaratne &lt;ayesh@php.watch&gt;:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">&gt; Motivation<br>
&gt;<br>
&gt; Reduced Boilerplate: Eliminates unnecessary empty blocks when exceptio=
ns only need to be caught and ignored.<br>
&gt; Improved Readability: Makes the code more concise and focuses on the i=
mportant parts.<br>
&gt;<br>
<br>
Empty `catch` blocks are a code-smell. If the `try` block is not ready<br>
to handle the exception, it should let the exception bubble up; not<br>
silence it. I think we should not encourage this further.<br>
</blockquote></div>

--000000000000075af0063b33dbb6--