Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67787
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.48 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: Mon, 24 Jun 2013 19:20:03 -0400
Message-ID: <CAAyV7nFHkv6EHX2uyoFm8yw4HDryOjgc206X=Y==e6fj3B6sKg@mail.gmail.com>
To: Joost Koehoorn <joost.koehoorn@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf307ca18400717c04dfeea7eb
Subject: Re: [PHP-DEV] Announcing RFC 'Anonymous Catches'
From: ircmaxell@gmail.com (Anthony Ferrara)

--20cf307ca18400717c04dfeea7eb
Content-Type: text/plain; charset=ISO-8859-1

Joost,

First off, let me say welcome and thanks for the contribution!

I have a couple of questions around the intended proposal.

1. How do you plan on handling the case where there are multiple catch
blocks?

    try {
        code();
    } catch {
        doSomething();
    } catch {
        doSomethingElse();
    }

2. You mention as a benefit "Better possibilities for static analysis
tools". Can you elaborate on this? I don't see how this sort of a change
would have any effect (as catch would be the same as the existing `catch
(\Exception $e)`)...

3. What benefit short of not having to type `(\Exception $e)` would this
have? Populating the symbol table is extremely cheap at this stage, because
the variable is already compiled in (so no hash table lookup or anything).

Additionally, I would recommend changing the version target to 5.NEXT
(which would be 5.6 in practice).

As far as my personal feelings, I'd like to get some other commentary first.

Thanks again!!!

Anthony

--20cf307ca18400717c04dfeea7eb--