Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67808
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <etPan.51c8ce38.54e49eb4.5757@MacBook-Air-van-Joost-Koehoorn.local>
References: <etPan.51c8ce38.54e49eb4.5757@MacBook-Air-van-Joost-Koehoorn.local>
Date: Tue, 25 Jun 2013 17:07:32 +0200
Message-ID: <CAF+90c8Aa0jV7OJkESYW_hfzFkvBQw9KFC_mEST1wrh-EyX=tw@mail.gmail.com>
To: Joost Koehoorn <joost.koehoorn@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b5d46286ba3f804dffbe38f
Subject: Re: [PHP-DEV] Announcing RFC 'Anonymous Catches'
From: nikita.ppv@gmail.com (Nikita Popov)

--047d7b5d46286ba3f804dffbe38f
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 25, 2013 at 12:54 AM, Joost Koehoorn
<joost.koehoorn@gmail.com>wrote:

> Hi all,
>
> I just published an RFC that proposes to add catch-statement without
> needing to specify a variable, and support for fully anonymous catches.
>
> Details can be found at:
>
> https://wiki.php.net/rfc/anonymous_catch
>

No opinion on leaving off $e, but I'm against the generic catch{} statement.

Looking at the Python docs, they don't see particularly fond of the
wildcard-except themselves:

> The last except clause may omit the exception name(s), to serve as a
wildcard. Use this with extreme caution, since it is easy to mask a real
programming error in this way! It can also be used to print an error
message and then re-raise the exception (allowing a caller to handle the
exception as well):

Furthermore a wildcard-catch is bad for forwards compatibility. Right now
all exceptions extend Exception, but this doesn't have to stay so. E.g.
Python has additional exceptions above that for handling stuff like signal
interrupts or die()s and I think it's not unlikely that we will introduce
something like this in PHP too. You normally do *not* want to catch those,
but a wildcard-catch would do this.

Thus I think it's better to stays explicit and keep it at catch(Exception).

Nikita

--047d7b5d46286ba3f804dffbe38f--