Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60666
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain l-i-e.com designates 67.139.134.202 as permitted sender)
Message-ID: <07444e5aa334ac4fa880fb28326ad6bc.squirrel@www.l-i-e.com>
In-Reply-To: <4F7BABC8.7040904@akbkhome.com>
References: <4F7BABC8.7040904@akbkhome.com>
Date: Tue, 22 May 2012 16:32:15 -0500
To: internals@lists.php.net
User-Agent: SquirrelMail/1.4.21 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] Catchable - marking methods just like static?
From: ceo@l-i-e.com ("Richard Lynch")

On Tue, April 3, 2012 9:02 pm, Alan Knowles wrote:
> I just saw Daniel changing some of the PEAR classes to use Exceptions,
> and it's pretty clear that this could cause havoc with the end users.
> The problem being that there is no 'soft' landing for the migration
> process.

If I understand set_exception_handler correctly, you could simply make
anything that reaches that state simply not return at all, and exit.

If you are that serious about the problem, the code expecting a result
and not an exception won't get anything at all.

And code with proper exception handling will do the right thing,
assuming you have written all your exception handlers at every layer
correctly.

Personally, try/catch and throw always felt like "GOTO" to me, and the
larger the codebase, the harder I found it to track down who was the
thrower and who was the catcher.

Reminded me of the old Abbot and Costello baseball routine.

-- 
brain cancer update:
http://richardlynch.blogspot.com/search/label/brain%20tumor
Donate:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE