Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67845
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.42 as permitted sender)
MIME-Version: 1.0
Sender: patrick.allaert@gmail.com
In-Reply-To: <CAF+90c8Aa0jV7OJkESYW_hfzFkvBQw9KFC_mEST1wrh-EyX=tw@mail.gmail.com>
References: <etPan.51c8ce38.54e49eb4.5757@MacBook-Air-van-Joost-Koehoorn.local>
	<CAF+90c8Aa0jV7OJkESYW_hfzFkvBQw9KFC_mEST1wrh-EyX=tw@mail.gmail.com>
Date: Wed, 26 Jun 2013 08:50:54 +0200
Message-ID: <CACwt+Jfvqb82p-mvyKE+gj+nZfogEztPHZu58cWwy8_kGMaVVA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Joost Koehoorn <joost.koehoorn@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Announcing RFC 'Anonymous Catches'
From: patrickallaert@php.net (Patrick ALLAERT)

2013/6/25 Nikita Popov <nikita.ppv@gmail.com>:
> but I'm against the generic catch{} statement.

I'm sharing Nikita's opinion, with the difference of a bit more
enthusiasm on leaving off the variable as it could make it more
obvious that there is no intention in using the variable, and that no
memory should be kept for it. This might be better than doing:

try {
   [...]
} catch (Exception $ignore) {
    unset($ignore);
}

[...]

However, I see other cases where a variable is technically required
but not used:

abstract class AbstractPrinter {
    abstract public function print($message);
}

class Printer extends AbstractPrinter {
    public function print($message) {
        echo $message;
    }
}

class BlackholePrinter extends AbstractPrinter {
    public function print($message) {
    }
}

In the previous example, $message is not "used" in
BlackholePrinter::print() (as well as in AbstractPrinter::print()).
How do you intend to make that consistent with: catch(Exception) ?

Patrick