Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82657
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c8NAROuCDgRajF4AN2oTc4fzmxTjtVC_OAQH=ZFm5N9Uw@mail.gmail.com>
References: <CAF+90c-7w1fLqmffYvPRhmtt8rzESEpSmW8vfMD-YfLt1mG_8w@mail.gmail.com>
	<CAF+90c8NAROuCDgRajF4AN2oTc4fzmxTjtVC_OAQH=ZFm5N9Uw@mail.gmail.com>
Date: Sat, 14 Feb 2015 07:55:10 +0700
Message-ID: <CAEZPtU6WdS-kiJUWpT_HzxyYTDMWm9t5+mayM0tsHQ4V20f5Yg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1296827c1d8050f01ce29
Subject: Re: [PHP-DEV] Re: [RFC] Exceptions in the engine
From: pierre.php@gmail.com (Pierre Joye)

--001a11c1296827c1d8050f01ce29
Content-Type: text/plain; charset=UTF-8

Could you revive it in a new thread please? :)
On Feb 13, 2015 3:25 PM, "Nikita Popov" <nikita.ppv@gmail.com> wrote:

> On Mon, Oct 6, 2014 at 11:53 PM, Nikita Popov <nikita.ppv@gmail.com>
> wrote:
>
> > Hi internals!
> >
> > During the PHP 5.6 development cycle I have proposed an RFC [1] that
> > suggested the use of exceptions instead of fatal errors in the engine. At
> > the time the proposal was declined, because the change was judged too
> > intrusive for a minor version.
> >
> > As such I'm re-proposing this RFC for inclusion in PHP 7:
> >
> >     https://wiki.php.net/rfc/engine_exceptions_for_php7
> >
> > The RFC text is essentially the same as previously, with the primary
> > difference being that parse errors are now converted to exceptions as
> well.
> > This was previously not possible due to limitations in the compiler
> design.
> >
> > Thanks,
> > Nikita
> >
> >   [1]: https://wiki.php.net/rfc/engine_exceptions
> >
>
> Feature freeze is not so far away now, so I'd like to bring this RFC up
> again and proceed to voting shortly. There are two primary open questions:
>
>  * Subclassing: Should there be more specific subclasses of EngineException
> for particular errors?
>  * Superclassing: Should EngineException inherit from Exception (and as
> such be subject to catch(Exception)) or should we introduce some kind of
> special super-class that is not caught by default (like
> Catchable/Throwable)?
>
> I don't think we can implement a high-quality subclassing scheme in a
> timeframe for PHP 7, as such I would suggest to postpone this (if we
> actually want to do it) to a later point in time. We can introduce
> subclasses without BC issues in a minor version.
>
> The question of whether EngineException should inherit from Exception is
> something we do have to consider now. Personally I prefer not introducing
> any special exception types that aren't caught by default. I think that
> would only make sense for errors that could occur literally everywhere
> (like memory limit or timeout), but these are not handled by this RFC for
> technical reasons. If someone has a strong opinion on this, I might make it
> a voting option.
>
> Commentary on these, and also any other relevant points is very welcome!
>
> Thanks,
> Nikita
>
> PS: The patch attached to the RFC is very outdated. I plan to only update
> it to current master once the RFC passes (if it does), as I already had to
> practically rewrite it a few times.
>

--001a11c1296827c1d8050f01ce29--