Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86262
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.47 as permitted sender)
Message-ID: <5557A542.6020208@gmail.com>
Date: Sat, 16 May 2015 21:14:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Levi Morrison <levim@php.net>, 
 Stanislav Malyshev <smalyshev@gmail.com>
CC: internals <internals@lists.php.net>
References: <CAF+90c8nqCBGWpsqdfy+EKekOm3Cw5_zzE_nKeyLK5pzROTueg@mail.gmail.com>	<54F07FC7.8050901@php.net>	<54F0839C.3010700@seld.be>	<55052FAD.6090608@php.net>	<5505346D.7020700@php.net>	<550DA4EE.2030903@php.net>	<55410973.4010300@php.net>	<55417C64.7000707@gmail.com>	<5541B4D6.9060503@php.net>	<CAMUwpuTQ7pypMGtVvG8Uc058a3EnqTry_ss6ovZMLzg=tHGoJQ@mail.gmail.com>	<55425D7E.6010803@gmail.com>	<FE2BD464-5B2A-482B-9E84-F0CC65B52526@heroku.com>	<554D8F4D.9020903@gmail.com>	<554D90CC.3040607@php.net>	<5552E3EB.5010800@gmail.com>	<5552E494.5070401@php.net>	<CAEZPtU7=6TdFt_px6uVK_LuWQ_tdF-=fKS3S-xrRXxaS9cEvdQ@mail.gmail.com>	<5552FF58.8070807@php.net>	<CAB6YZuxf1a_rEEiuGSaYht=pwGZEunU4Hanr9c8M75pafQmocw@mail.gmail.com>	<CAFMT4NoRdxUeraGn-1VtUSK_sHm5b=yAaVrOCf_vKqHTEUi6qw@mail.gmail.com>	<55575DCF.50801@gmail.com>	<CAFMT4NpKPvRhcR+j22sWurZYnF1QJt-wj2QNsQiTo9NuCnJidg@mail.gmail.com>	<55578C61.3040408@gmail.com> <CAFMT4NohMTz5QqCW_hDQW7bFGgsBQPGKrLS42hmcZmE+OuNaAQ@mail.gmail.com>
In-Reply-To: <CAFMT4NohMTz5QqCW_hDQW7bFGgsBQPGKrLS42hmcZmE+OuNaAQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] Exceptions in the engine
From: rowan.collins@gmail.com (Rowan Collins)

On 16/05/2015 19:44, Levi Morrison wrote:
> On Sat, May 16, 2015 at 12:28 PM, Stanislav Malyshev
> <smalyshev@gmail.com> wrote:
>> Hi!
>>
>>> There's nothing that prevents us from reneging on that by another
>>> vote. If it's a bad decision backed by logical arguments then we can
>> That's a pretty big if, given that your only argument - that it is a BC
>> break - is incorrect, as in fact the set of exceptions caught before and
>> after change is exactly the same, and the only difference is that in the
>> new code, you can *also* catch errors, the option that you didn't have
>> before. Absent that argument, there's no reason to renege.
> You are incorrect. The set of exceptions that `catch (Exception)`
> catches is all exceptions by its definition. By altering it to no
> longer include all exceptions means the semantics of it changed.

Do you agree with these statements?

- There is no exception which a program using "catch ( Exception $e )" 
will catch under PHP 5 but not under PHP 7 (with BaseException/Throwable 
as proposed).
- There is no fatal error which becomes non-fatal for such a program, 
because they will become uncaught EngineExceptions, and failure to catch 
an exception is a fatal error.
- There is no non-fatal error which becomes fatal for such a program, 
because EngineExceptions exist only where there were already fatal errors.

Leaving aside "definitions" and "semantics", where, then, is the BC break?

Regards,

-- 
Rowan Collins
[IMSoP]