Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86257
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.173 as permitted sender)
Message-ID: <55579575.6060409@gmail.com>
Date: Sat, 16 May 2015 12:07:33 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Levi Morrison <levim@php.net>
CC: Rowan Collins <rowan.collins@gmail.com>, 
 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
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] Exceptions in the engine
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> You are incorrect. The set of exceptions that `catch (Exception)` 
> catches is all exceptions by its definition. By altering it to no

There's no such definition. It's invented to serve your point, which
makes it circular logic. catch(Exception) catches everything that
descends from Exception. It is true that throwables that do not descend
from Exception did not exist before, however their exact semantics was
implemented as engine errors, so nothing changed in that regard.
catch(Exception) did not catch parse errors, it still doesn't.

> longer include all exceptions means the semantics of it changed.

No, it doesn't mean that. It catches every exception descended from
class Exception as it did before. Nobody guaranteed you - and if fact it
never were true - that there are no other situations which can lead to
early exit from the code and that catch(Exception) can't catch. It is
still the case. Before, these things were implemented as "errors", now
some of them are implemented as exceptions. That's an implementation
detail, semantic hasn't changed - except for the fact that you can now
catch more of them is you wanted.

-- 
Stas Malyshev
smalyshev@gmail.com