Re: [VOTE] Allowing use of exceptions in the engine
| From: | Hannes Magnusson | Date: | Mon, 09 Dec 2013 05:14:10 +0000 |
| Subject: | Re: [VOTE] Allowing use of exceptions in the engine | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-70541@lists.php.net to get a copy of this message | ||
On Sat, Dec 7, 2013 at 4:57 AM, Nikita Popov <nikita.ppv@gmail.com> wrote:
> Hi internals!
>
> 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.
>
Wow. This is one of the bigger language changes I have seen proposed to date.
I see the framework guys jumping in on this right away wanting pretty
OO interface of course - but hold your horses a bit.
This is a very fundamental change in the language and a vote should
not be casted lightly.
The recoverable error cases is something I argued when breaking type
hinting was decided to be E_REOCVERABLE_ERROR for reasons that still
baffle me (and depending if its extension code or userland code,
effectively continues current context or not, since internals will
most likely bail out on zpp) - but now we are talking about about
changing something much bigger then that...
If this gets accepted, what is the reason we have these error levels
at all, and shouldn't E_* friends be rewritten into more convenient
logging framework and remove the association with "errors"?
-Hannes