Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70526
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADajX4DzpfrsnL30EtcW3Luf0Yx+T=fEMLFOrJT8c6UDiOXZ6g@mail.gmail.com>
References: <CAF+90c9Hxzi_JhyZkyi6Ly9zxWjgFsCBsvgzH7a8n-ce3kPKYw@mail.gmail.com>
	<CADajX4DzpfrsnL30EtcW3Luf0Yx+T=fEMLFOrJT8c6UDiOXZ6g@mail.gmail.com>
Date: Sun, 8 Dec 2013 00:31:41 +0100
Message-ID: <CAF+90c_o7pE5=yeVkDtOYHW++=yF480fXmNWRN7JqTh4b5NQnA@mail.gmail.com>
To: Adam Harvey <aharvey@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b5d42f83c92ac04ecfa2a77
Subject: Re: [PHP-DEV] [VOTE] Allowing use of exceptions in the engine
From: nikita.ppv@gmail.com (Nikita Popov)

--047d7b5d42f83c92ac04ecfa2a77
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 7, 2013 at 10:47 PM, Adam Harvey <aharvey@php.net> wrote:

> On 7 December 2013 04:57, Nikita Popov <nikita.ppv@gmail.com> wrote:
> > I opened the vote on the "Exceptions in the engine" RFC:
> >
> >     https://wiki.php.net/rfc/engine_exceptions#vote
> >
> > The vote has three options, "Yes", "No" and "Yes, without
> > E_RECOVERABLE_ERROR changes". The last option is a version of the
> proposal
> > without BC issues.
> >
> > And regarding the vote: If you are in favor of the proposal in general,
> but
> > want to have it in PHP 6 rather than PHP 5.6, then vote "No" here. If i=
t
> > fails now, someone can revive this once the time for PHP 6 has come.
>
> To be clear: I've voted -1 for exactly this reason, and this reason
> alone. I don't think implementing this piecemeal (without the
> E_RECOVERABLE_ERROR changes) is the right way to go =97 I would prefer
> to have the whole thing as part of a 6.0 release, rather than
> potentially confusing users with a partial implementation.
>

If you're concerned about E_RECOVERABLE_ERROR in particular I should point
out that there are very few recoverable fatals in the engine. Actually, the
only common recoverable error is the typehint violation error. The others
are along the lines of "Instantiation of 'Closure' is not allowed" or
"Closure object cannot have properties" - not something you usually
encounter. For a full list see
http://lxr.php.net/search?q=3DE_RECOVERABLE_ERROR&defs=3D&refs=3D&path=3DZe=
nd&hist=3D&project=3DPHP_TRUNK.
So I don't think that E_RECOVERABLE_ERROR is a particularly large loss in
itself - but the "partial implementation" argument presumably still stands
even without it (won't be able to port all fatal errors at once, after all.=
)

Nikita

--047d7b5d42f83c92ac04ecfa2a77--