Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76873
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53FBAD09.1080108@sugarcrm.com>
References: <CAF+90c_M7nKiVLYT0vWaq8wg==Yz0ZZC1V_ke=t71rpWqKPepA@mail.gmail.com>
	<CAF+90c-d6=rSN5Z-cngmEO-bheFF_0JR7iJ4uhFZWVMfRdL2Ug@mail.gmail.com>
	<53FB6D4C.9070705@php.net>
	<CAF+90c8+3Otfw3Mscm8FcNTObHr+_id6bDkLw7DW5xmATgRfkg@mail.gmail.com>
	<53FBAD09.1080108@sugarcrm.com>
Date: Mon, 25 Aug 2014 18:03:12 -0400
Message-ID: <CAHXmDMB5WZWuQugA1UO-xPX9JFWn228+kSk+jwwUuEOKQUbfpA@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, Sebastian Bergmann <sebastian@php.net>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0111d1be66901f05017b5aa1
Subject: Re: [PHP-DEV] Re: [VOTE] Abstract Syntax Tree
From: rican7@gmail.com (Trevor Suarez)

--089e0111d1be66901f05017b5aa1
Content-Type: text/plain; charset=UTF-8

>
> If we're talking the plunge of putting exceptions into the core engine,
> wouldn't it make sense to convert most of the fatal errors (especially
> the "catchable" ones) to exceptions too? Most of them (except for out of
> memory, timeouts and such) don't really require the engine to shut down,
> as it seems... So if we're already saying people will have to deal with
> exceptions in PHP engine anyway, maybe we could make it so that we could
> have unified handling of them?


This is something that Nikita had originally proposed in an RFC (
https://wiki.php.net/rfc/engine_exceptions) but postponed until after 5.6.

I have a feeling we'll be hearing about its resurrection soon enough.

- Trevor

--089e0111d1be66901f05017b5aa1--