Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69879
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.172 as permitted sender)
Message-ID: <526BD9F5.9040309@gmail.com>
Date: Sat, 26 Oct 2013 16:04:21 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAF+90c8OgW4Nonaz+HQn+gi4r+AdaEMXsTxCAhn=WO-+aQQsZQ@mail.gmail.com> <52699FB5.20300@garfieldtech.com> <526A6BCC.3060502@php.net> <526AC472.8060607@sugarcrm.com> <526AC950.7020605@php.net> <526BB309.4030106@gmail.com> <526BD0FB.1020809@php.net>
In-Reply-To: <526BD0FB.1020809@php.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine
From: rowan.collins@gmail.com (Rowan Collins)

On 26/10/2013 15:26, Joe Watkins wrote:
> They _should_ exist as a boundary, a last resort, if at all, but when 
> they do exist they are no such boundary or last resort, they are 
> normal catch blocks because the core throws the base Exception ... I'm 
> just making the observation that it's not a very good idea to do that, 
> doesn't take a lot to fix, has no bc issues and sets the right kind of 
> standard.

Right, I'm agreed that throw statements should be as specific as 
possible, both in core/extensions and in userland.

But you seemed to link that somehow to catch(Exception) blocks, which 
are an entirely different topic, and have valid use cases, since they 
mean "catch everything descended from this class" not "catch things with 
this exact class".

Regards the engine throwing exceptions, it's the catch side of things 
which is most relevant.

-- 
Rowan Collins
[IMSoP]