Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67381
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mindplay.dk from 209.85.212.46 cause and error)
MIME-Version: 1.0
Sender: rasmus@mindplay.dk
Date: Thu, 9 May 2013 18:00:23 -0400
Message-ID: <CADqTB_jNFN0oUmrxef-p3Yn7in0u6jMo-2Wi2QyqA983R5bBtA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b5d626461385704dc502dae
Subject: exceptions during __toString()
From: me@rasmus-schultz.com (Rasmus Schultz)

--047d7b5d626461385704dc502dae
Content-Type: text/plain; charset=ISO-8859-1

I just ran into this issue again:

http://stackoverflow.com/questions/2429642/why-its-impossible-to-throw-exception-from-tostring

Instead of throwing some nonsense "you're not allowed to throw from here"
error-message, how about actually unwinding the stack and passing the
exception to the global exception-handler?

I understand there's a technical limitation making it difficult/impossible
to handle exceptions during __toString() - and it looks like you can still
try {...} catch (Exception $e) in __toString() just fine, but then what?
You have the exception, but you have no way to pass it to the standard
global exception-handler.

If the script has to terminate either way, why not terminate the same way
an unhandled exception would normally cause the script to terminate?

E.g. output the actual error-message, or pass it to whatever was registered
with register_exception_handler() so it can be output or handled in the
usual way?

--047d7b5d626461385704dc502dae--