Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128328
Precedence: bulk
MIME-Version: 1.0
References: <CAJWOiuN8fuejkX1Tj0h=s_Fs2bGEtz-qdMZxRTC1s4at23y=Vw@mail.gmail.com>
 <CANLbj-pe0cyqaQkf2k2_XH+Ybj9Gy11-=M=eqxgaQsF62GJAeQ@mail.gmail.com>
 <CAJWOiuNw7DycxqabvqZ0z4xKhsZJX4aOE65xXOoFGV9KsNrHEw@mail.gmail.com> <CAMU7irKWy5hqO65PyLHTSemok6mpx0Q3rR+qzmbeuLWER7x-Fw@mail.gmail.com>
In-Reply-To: <CAMU7irKWy5hqO65PyLHTSemok6mpx0Q3rR+qzmbeuLWER7x-Fw@mail.gmail.com>
Date: Thu, 31 Jul 2025 12:02:42 +0500
Message-ID: <CAJWOiuP7xBdtqx50SFZgN3-7uvPhW9WH=VV=FXVjOFSPMFEDvw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Optional Catch Block Body
To: Alexandre Daubois <alex.daubois+php@gmail.com>
Cc: Ayesh Karunaratne <ayesh@php.watch>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f07054063b343a93"
From: 91liahim@gmail.com (Mihail Liahimov)

--000000000000f07054063b343a93
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello, Alexandre.

I've heard your concerns, but I don't think this proposal will encourage
other developers to ignore exceptions more often. Basically, even now,
nothing can stop a developer from ignoring exceptions. He can simply leave
the body of the capture block empty. And in this RFC is proposed just to
allow not to write extra brackets {}.

If we talk from the point of view of bad practices and applicability, then
the same nullsafe operator may encourage developers to check for null less
often. And this leads to problems, I personally observed this.

It seems to me that the issue of bad and good practices should be the
responsibility of developers. A programming language is just a tool. And
there are many ways in which it can be "badly" applied.

=D1=87=D1=82, 31 =D0=B8=D1=8E=D0=BB. 2025=E2=80=AF=D0=B3. =D0=B2 11:51, Ale=
xandre Daubois <alex.daubois+php@gmail.com>:

> > 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.
>
> From what I can tell, it's very rare to have empty catch blocks, and
> even more being done rightfully. I'd be very suspicious if I came
> across such code.
>
> I think the extra boilerplate is actually a good thing, showing the
> explicit intent to not catch the error. I get that the proposal is not
> intended to encourage such a thing, but I agree with Ayesh: it would
> definitely will.
>

--000000000000f07054063b343a93
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hello, Alexandre.<br><br>I&#39;ve heard y=
our concerns, but I don&#39;t think this proposal will encourage other deve=
lopers to ignore exceptions more often. Basically, even now, nothing can st=
op a developer from ignoring exceptions. He can simply leave the body of th=
e capture block empty. And in this RFC is proposed just to allow not to wri=
te extra brackets {}.<br><br>If we talk from the point of view of bad pract=
ices and applicability, then the same nullsafe operator may encourage devel=
opers to check for null less often. And this leads to problems, I personall=
y observed this.<br><br>It seems to me that the issue of bad and good pract=
ices should be the responsibility of developers. A programming language is =
just a tool. And there are many ways in which it can be &quot;badly&quot; a=
pplied.<br></div><br><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:51, Alexandre Daubois &lt;<a href=3D"mailto:alex=
.daubois%2Bphp@gmail.com">alex.daubois+php@gmail.com</a>&gt;:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">&gt; Of course, empty catch b=
locks are bad practice in most cases. But this particular proposal is not i=
ntended to encourage these bad practices. I&#39;m just suggesting that you =
don&#39;t have to write an extra boiler plate at the syntax level in situat=
ions where it&#39;s necessary.<br>
<br>
From what I can tell, it&#39;s very rare to have empty catch blocks, and<br=
>
even more being done rightfully. I&#39;d be very suspicious if I came<br>
across such code.<br>
<br>
I think the extra boilerplate is actually a good thing, showing the<br>
explicit intent to not catch the error. I get that the proposal is not<br>
intended to encourage such a thing, but I agree with Ayesh: it would<br>
definitely will.<br>
</blockquote></div></div>

--000000000000f07054063b343a93--