Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69852
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 198.187.29.239 as permitted sender)
Message-ID: <5269777D.1000708@ajf.me>
Date: Thu, 24 Oct 2013 20:39:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:25.0) Gecko/20100101 Thunderbird/25.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAF+90c8OgW4Nonaz+HQn+gi4r+AdaEMXsTxCAhn=WO-+aQQsZQ@mail.gmail.com>
In-Reply-To: <CAF+90c8OgW4Nonaz+HQn+gi4r+AdaEMXsTxCAhn=WO-+aQQsZQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine
From: ajf@ajf.me (Andrea Faulds)

On 24/10/2013 18:41, Nikita Popov 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?
>
> Thanks,
> Nikita
>

I love this proposal! Errors are a very dated way of handling errors, 
and there are a lot of fatal errors which are unnecessarily fatal. This 
would mean many could stop being fatal and start being exceptions, which 
is great news.

-- 
Andrea Faulds
http://ajf.me/