Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3341
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: "'Greg Beaver'" <greg@chiaraquartet.net>, <internals@lists.php.net>
Date: Wed, 9 Jul 2003 20:57:32 -0400
Organization: Jcx.Software Corp.
Message-ID: <000001c3467e$41f98100$6401a8c0@juanhp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <3F0AFF96.9080600@chiaraquartet.net>
Subject: RE: [PHP-DEV] exceptions question
From: juan.rivera@jcxsoftware.com ("Juan C. Rivera")
References: <3F0AFF96.9080600@chiaraquartet.net>

You should not use exceptions for program logic. Exceptions are use to
handle exceptional cases and the overhead of handling an exception may
be quite expensive. At least on other languages.

So, what is the overhead of throwing exceptions in PHP? Is it as
expensive as in .Net or C++?

-----Original Message-----
From: Greg Beaver [mailto:greg@chiaraquartet.net] 
Sent: Tuesday, July 08, 2003 1:30 PM
To: internals@lists.php.net
Subject: [PHP-DEV] exceptions question

Hi,

In experimenting with exceptions, I notice that throw() always jumps to 
the first catch() (as expected), and there is no way to return to the 
line after the throw().  Are we forced to use trigger_error() or some 
custom function for this kind of exception, or is there a way to tell 
PHP 5 "go back, the exception is fixed"?

Thanks,
Greg


-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php