Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69859
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.28 cause and error)
Message-ID: <52699FB5.20300@garfieldtech.com>
Date: Thu, 24 Oct 2013 17:31:17 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; 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>
In-Reply-To: <CAF+90c8OgW4Nonaz+HQn+gi4r+AdaEMXsTxCAhn=WO-+aQQsZQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine
From: larry@garfieldtech.com (Larry Garfield)

On 10/24/13 12:41 PM, 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

As a PHP user-space developer I love this idea.  However, I share the 
concern of others here that it could result in BC unpleasantness, even 
if limited to the E_FATAL and E_RECOVERABLE_FATAL use cases.  I don't 
know off hand how various versions of Drupal would handle this.

--Larry Garfield