Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86359
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.177 as permitted sender)
To: =?UTF-8?Q?'Jakub_Kub=C3=AD=C4=8Dek'?= <kelerest123@gmail.com>
Cc: "'PHP Internals'" <internals@lists.php.net>
References: <000301d09526$ee7b0580$cb711080$@gmail.com> <CAHvhOfi+yiPtGJM8Z00hOFWq0qxoi=yy5Of2wwfEff28nxtviA@mail.gmail.com>
In-Reply-To: <CAHvhOfi+yiPtGJM8Z00hOFWq0qxoi=yy5Of2wwfEff28nxtviA@mail.gmail.com>
Date: Sun, 24 May 2015 00:03:49 +0200
Message-ID: <002101d095a4$5992c330$0cb84990$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0022_01D095B5.1D1E7960"
Thread-Index: AQDFeEiRVHSznqdoLEDL5s4dwAb0JgF9yaEBn5Rm8gA=
Content-Language: en-gb
Subject: RE: [PHP-DEV] Allow __toString() to throw exceptions
From: benjamin.morel@gmail.com ("Benjamin Morel")

------=_NextPart_000_0022_01D095B5.1D1E7960
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> Hi Benjamin.

=20

Hi Janub,

=20

> I have a question: is there any reason to throw an exception from =
__toString, other than a non-recoverable error, which would denote that =
the object, which the __toString method is called on, does not have any =
meaningful string representation? Because if not, core implementation =
fully serves its purpose throwing Fatal error now, even if it is =
non-standard way.

=20

There are many reasons why you would want to throw an exception in =
__toString(), just like in any other method.=20

Some of them may be recoverable, some may not be. Sorry I don=E2=80=99t =
have an example at hand.

=20

But even if the error is =E2=80=9Cnot recoverable=E2=80=9D, you still =
want to leave your framework a chance to catch the uncaught exception to =
present a nice error page to the user, and handle the error =
appropriately (log, notify, etc.)

=20

I=E2=80=99ve been thrilled to see that some move in the right direction =
has already been made in PHP 7 : for example, calling a method on a NULL =
value will throw an exception instead of resulting in a fatal error as =
before.

As I see it, fatal errors should be reserved to *really* unrecoverable =
stuff, like memory exhausted or max execution time exceeded; the rest is =
just annoyance.

=20

Anyway it would be good to just reopen the bug for now to give it some =
attention, as Zend Engine 3 is being written!

=20

Cheers,

Ben

=20


------=_NextPart_000_0022_01D095B5.1D1E7960--