Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:3307 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37921 invoked from network); 8 Jul 2003 17:58:39 -0000 Received: from unknown (HELO longsword.omniti.com) (66.80.117.3) by pb1.pair.com with SMTP; 8 Jul 2003 17:58:39 -0000 Received: from ip-66-80-117-2.nyc.megapath.net ([66.80.117.2] helo=maya.local.) by longsword.omniti.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.14) id 19ZwkB-0005Jl-Ek; Tue, 08 Jul 2003 13:59:11 -0400 Date: Tue, 8 Jul 2003 13:58:42 -0400 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v543) Cc: internals@lists.php.net To: Greg Beaver In-Reply-To: <3F0AFF96.9080600@chiaraquartet.net> Message-ID: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.543) Subject: Re: [PHP-DEV] exceptions question From: george@omniti.com (George Schlossnagle) References: <3F0AFF96.9080600@chiaraquartet.net> 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 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 > > -- George Schlossnagle -- Principal Consultant -- OmniTI Computer Consulting, Inc. -- +1.410.872.4910 x202 -- 1024D/1100A5A0 1370 F70A 9365 96C9 2F5E 56C2 B2B9 262F 1100 A5A0