Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104491
MIME-Version: 1.0
Date: Thu, 21 Feb 2019 16:27:40 +0100
Message-ID: <CAKg-N=XODDd=eU=E8cXG=uKayn5AETNH_FLnOCWOVXPM-PWkqg@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000001017d30582691e7b"
Subject: Optional catch binding
From: franssen.roland@gmail.com (Roland Franssen)

--0000000000001017d30582691e7b
Content-Type: text/plain; charset="UTF-8"

Hi Internals,

I'd like to propose an idea to allow catching exceptions by type only, or
globally, by any type.

In case the "$e" variable or the exception type is redundant, it doesn't
need to be specified:

try {
    x();
} catch (\Throwable) {
    // ...
}

try {
    x();
} catch {
    // ...
}

Example in the wild that could benefit from this:
https://github.com/symfony/symfony/blob/5a3e8942032c1a49496fe8db61828707b45442f9/src/Symfony/Component/Config/Definition/ArrayNode.php#L247
($e
variable is redundant).

Allthough global exception catching might not be a good practice per se, I
don't see a real reason to forbid it. However, these are 2 independent
features that can be voted for I guess.

For now, I'm aiming to get rid of "unused variable $e".

Thoughts?

See also
-
https://nitayneeman.com/posts/a-taste-from-ecmascript-2019/#optional-catch-binding
- https://en.cppreference.com/w/cpp/language/try_catch

Cheers,
Roland Franssen

PS: 3rd attempt, sorry if im spamming somehow

--0000000000001017d30582691e7b--