Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69863
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.54 as permitted sender)
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6932F8AC-430B-4B6F-9DA2-EC4481F480BA"; protocol="application/pgp-signature"; micalg=pgp-sha512
In-Reply-To: <CAF+90c8OgW4Nonaz+HQn+gi4r+AdaEMXsTxCAhn=WO-+aQQsZQ@mail.gmail.com>
Date: Fri, 25 Oct 2013 13:59:11 +0400
Cc: PHP internals <internals@lists.php.net>
Message-ID: <48695B62-3224-4A31-965D-EFFC9BD4F4D0@gmail.com>
References: <CAF+90c8OgW4Nonaz+HQn+gi4r+AdaEMXsTxCAhn=WO-+aQQsZQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine
From: indeyets@gmail.com (Alexey Zakhlestin)

--Apple-Mail=_6932F8AC-430B-4B6F-9DA2-EC4481F480BA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On 24 =D0=BE=D0=BA=D1=82. 2013 =D0=B3., at 21:41, Nikita Popov =
<nikita.ppv@gmail.com> wrote:

> I'd like to propose an RFC, which allows the use of exceptions within =
the
> engine and also allows changing existing fatal errors to exceptions:
>=20
>    https://wiki.php.net/rfc/engine_exceptions
>=20
> This topic has been cropping up in the discussions for several of the
> recent RFCs and I think the time has come to consider moving away from
> fatal errors.
>=20
> Thoughts?

Thank you, Nikita!
That=E2=80=99s something which definitely needs to be done.

Catching parse-errors from includes, bad function/method calls, etc. =
will let us make complex code-bases more robust and predictable.

I think introduction of BaseException is a necessity.
This way code will stay compatible and new exceptions will just end =
their life somewhere in shutdown-handler, just as fatal errors do now.

Rowan proposed to use subclasses for different exception types =E2=80=94 =
I believe it can wait a bit. There is no need to overcomplicate this.
New classes would be added eventually, but as they will be extending =
EngineException forward-compatibility is preserved.

converting fatal-errors is a safe-enough change to be done in 5.NEXT.

converting some of the warnings is a good topic for starting 6.x

--=20
Alexey Zakhlestin
CTO at Grids.by/you
https://github.com/indeyets
PGP key: http://indeyets.ru/alexey.zakhlestin.pgp.asc




--Apple-Mail=_6932F8AC-430B-4B6F-9DA2-EC4481F480BA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJSakD3AAoJEMkJcRxZdR27nkgH/j8xJ/Dp2ILtoaQEMZM3gezZ
7hSGFtBNuz3EbtV+lfvAp9xF+QrXugHOzIJjKBqy88kLfmVbJsi/FJlOlI6x4gGp
vBVeeCQwde/mQY6kWurRrpdSh/vcNwiN/R3b/V8/TKa3uxhuVa9qnqDfIGs4OL+U
1C1RIEdoFg/I4vMWHeNcTlwGZPG1pInbkqhUxzjAeOG0o1LB6K5V0uMe+Gw5hn2p
G7VHovObHxwhmDs8KjSjIgDUaZQWfzCp3iTas8ALjW4ewhbo0EmPvMQhtINpsn1I
cba6B+TZPSXmlkN1ZmE0KXb3fYUs/CkX80Y/rXGt/Rmxh4hd31h06Sag17nABYo=
=XSL4
-----END PGP SIGNATURE-----

--Apple-Mail=_6932F8AC-430B-4B6F-9DA2-EC4481F480BA--