Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84006
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 93.190.64.238 as permitted sender)
Message-ID: <54F07FC7.8050901@php.net>
Date: Fri, 27 Feb 2015 15:31:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; 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>
In-Reply-To: <CAF+90c8nqCBGWpsqdfy+EKekOm3Cw5_zzE_nKeyLK5pzROTueg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [VOTE] Exceptions in the engine
From: sebastian@php.net (Sebastian Bergmann)

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.