Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70520
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.45 as permitted sender)
MIME-Version: 1.0
Date: Sat, 7 Dec 2013 13:57:45 +0100
Message-ID: <CAF+90c9Hxzi_JhyZkyi6Ly9zxWjgFsCBsvgzH7a8n-ce3kPKYw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e015388481ba3f304ecf14f48
Subject: [VOTE] Allowing use of exceptions in the engine
From: nikita.ppv@gmail.com (Nikita Popov)

--089e015388481ba3f304ecf14f48
Content-Type: text/plain; charset=ISO-8859-1

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.

Some further notes:
 * I will not be including something like BaseException. Introducing it for
this purpose seems like bad design and will be very hard to get rid of in
the future. As the proposal (without recoverable errors) does not break BC
[1] even without it, I don't see a reason to introduce it.
 * Some people suggest to use different subclasses of EngineException for
different error types. I'm not against that, but I think it's okay to do
that in a separate proposal, if someone can come up with a good selection
of exception classes. It's much easier (and does not break BC) to add
subclassing later, than to add suboptimal subclass types now and try to fix
something like the SPL exception mess later.
 * The suggested uncaught exception error message change is just a bit of
cosmetics (and not directly related to this proposal), so I'd like to do
that separately.

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 it
fails now, someone can revive this once the time for PHP 6 has come.

Thanks,
Nikita

[1]: We don't have a formal definition for this, but it seems to be general
consensus that relaxing error conditions does not constitute a backwards
compatibility break.

--089e015388481ba3f304ecf14f48--