Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69851
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c8OgW4Nonaz+HQn+gi4r+AdaEMXsTxCAhn=WO-+aQQsZQ@mail.gmail.com>
References: <CAF+90c8OgW4Nonaz+HQn+gi4r+AdaEMXsTxCAhn=WO-+aQQsZQ@mail.gmail.com>
Date: Thu, 24 Oct 2013 21:35:31 +0200
Message-ID: <CAEZPtU5Zcy2pkMVREaowR9ZtVvud63sGXdRAM7CBWMw7JZH=dg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine
From: pierre.php@gmail.com (Pierre Joye)

On Thu, Oct 24, 2013 at 7:41 PM, Nikita Popov <nikita.ppv@gmail.com> wrote:
> Hi internals!
>
> I'd like to propose an RFC, which allows the use of exceptions within the
> engine and also allows changing existing fatal errors to exceptions:
>
>     https://wiki.php.net/rfc/engine_exceptions
>
> This topic has been cropping up in the discussions for several of the
> recent RFCs and I think the time has come to consider moving away from
> fatal errors.
>
> Thoughts?

I like the idea, well done!

I understand that this RFC refers to the engine only, however I think
many exts may follow this path too. We should consider about naming
conventions for the extensions as well.

Another point, I'm wondering if 5.x is the right time to introduce
exceptions in core.

-- 
Pierre

@pierrejoye | http://www.libgd.org