Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128327
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>
In-Reply-To: <CAJWOiuNw7DycxqabvqZ0z4xKhsZJX4aOE65xXOoFGV9KsNrHEw@mail.gmail.com>
Date: Thu, 31 Jul 2025 08:50:52 +0200
Message-ID: <CAMU7irKWy5hqO65PyLHTSemok6mpx0Q3rR+qzmbeuLWER7x-Fw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Optional Catch Block Body
To: Mihail Liahimov <91liahim@gmail.com>
Cc: Ayesh Karunaratne <ayesh@php.watch>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: alex.daubois+php@gmail.com (Alexandre Daubois)

> Of course, empty catch blocks are bad practice in most cases. But this pa=
rticular proposal is not intended to encourage these bad practices. I'm jus=
t suggesting that you don't have to write an extra boiler plate at the synt=
ax 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.