throwing exceptions in PHP? Is it as
expensive as in .Net or C++?
-Original Message-
From: Greg Beaver [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 1:30 PM
To: [EMAIL PROTECTED]
Subject: [PHP-DEV] exceptions question
Hi,
In experimenting with exceptions, I notice that throw
++?
-Original Message-
From: Greg Beaver [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 1:30 PM
To: [EMAIL PROTECTED]
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
That's not the way exceptions work in any language I know.
On Tuesday, July 8, 2003, at 01:29 PM, Greg Beaver wrote:
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 w
> 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().
That is precisely how exceptions are supposed to work.
> Are we forced to use trigger_error() or some
> custom function for
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 "g
