Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80701
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.212.173 cause and error)
MIME-Version: 1.0
In-Reply-To: <CALKiJKqsUPDN23c7DrpQrhXJD-RU1W4ZNq1h0Lotgrcm+JgUKA@mail.gmail.com>
References: <CA+kxMuQcfMY00k+WtnNUppD7N9PMQsx356h1XTy1X8px1m0MBw@mail.gmail.com>
	<003201d0326b$6fd27f60$4f777e20$@tekwire.net>
	<23490588-0131-4B0F-A7AA-C9C8C766626C@ajf.me>
	<CALKiJKqsUPDN23c7DrpQrhXJD-RU1W4ZNq1h0Lotgrcm+JgUKA@mail.gmail.com>
Date: Sat, 17 Jan 2015 16:19:11 +0000
Message-ID: <CA+kxMuQHkvetuPASEt0AP1fkMmdVHewGqkMjVqs=mvrGA-nTLw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: Andrea Faulds <ajf@ajf.me>, francois@tekwire.net, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Class constructor behaviour
From: danack@basereality.com (Dan Ackroyd)

On 17 January 2015 at 16:04, Rowan Collins <rowan.collins@gmail.com> wrote:
> The difference is that AFAIK all the exceptions returned by OOP extensions right now are of classes specific to that extension, whereas this would be a global engine-thrown exception.

Sorry - I wasn't clear. I didn't mean they should throw generic
exceptions; they definitely should throw exceptions specific to the
code being called. To a very large part these exceptions already
exist:

The intl extension has: http://php.net/manual/en/class.intlexception.php
The reflection extension has:
http://php.net/manual/en/class.reflectionexception.php

For the intl extension, these are already in use in some places, if
the user has set "intl.use_exceptions".

This is why I think most, if not all, of the work would need to be
done before an RFC could be voted on - it's one of those cases where
people could disagree with details of the RFC, even if they agreed in
the general idea.

cheers
Dan