Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84008
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain seld.be designates 209.85.212.176 as permitted sender)
Message-ID: <54F0839C.3010700@seld.be>
Date: Fri, 27 Feb 2015 14:47:56 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAF+90c8nqCBGWpsqdfy+EKekOm3Cw5_zzE_nKeyLK5pzROTueg@mail.gmail.com> <54F07FC7.8050901@php.net>
In-Reply-To: <54F07FC7.8050901@php.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] Exceptions in the engine
From: j.boggiano@seld.be (Jordi Boggiano)

On 27/02/2015 14:31, Sebastian Bergmann wrote:
> Am 23.02.2015 um 19:15 schrieb Nikita Popov:
>> Voting on the engine exceptions RFC, which proposes to convert existing
>> fatal and recoverable fatal errors into exceptions, has opened:
>>
>>      https://wiki.php.net/rfc/engine_exceptions_for_php7#vote
>>
>> The primary vote requires a 2/3 majority, as this is a language change.
>>
>> A second vote will decide whether to use a BaseException based inheritance
>> hierarchy. This vote uses a simple majority.
>
>   I have voted yes on "Allow exceptions in the engine and conversion of
>   existing fatals?" and no on "Introduce and use BaseException?" and
>   would like to elaborate on the latter.
>
>   I am sorry that I was unable to raise this concern earlier (did not
>   really become aware of the RFC before it was put to the vote), but I
>   would prefer the following:
>
>     * Introduce a Throwable interface
>     * Let Exception implement the Throwable interface
>     * Introduce an Error class that implements the Throwable interface
>     * Use Error class as base class for exceptions raised by the engine
>
>   This would be along the lines of what Java does.

+1 on that, and as it seems the BaseException is going to pass, it might 
be good to quickly draft another RFC to amend that part.

It seems people in general favor the fact that catch(Exception $e) does 
not catch those new engine exceptions, but there hopefully would not be 
much resistance against a cleaner scheme than a BaseException class.

Also the Error (and possibly Throwable) class/interface might be put in 
a PHP namespace and then we avoid any potential BC issues, but that's 
perhaps another voting point :)

Cheers