Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17561 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90169 invoked by uid 1010); 6 Aug 2005 15:19:10 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 90154 invoked from network); 6 Aug 2005 15:19:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Aug 2005 15:19:10 -0000 X-Host-Fingerprint: 212.202.20.97 port-212-202-20-97.dynamic.qsc.de Received: from ([212.202.20.97:25216] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 55/45-04646-EE4D4F24 for ; Sat, 06 Aug 2005 11:19:10 -0400 Message-ID: <55.45.04646.EE4D4F24@pb1.pair.com> To: internals@lists.php.net Date: Sat, 06 Aug 2005 17:19:35 +0200 User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Posted-By: 212.202.20.97 Subject: (re)throwing exceptions From: lists@darknoise.de (Dennis Sterzenbach) Hi Folks! What do you think about re-throwing an Exception? I think of a situation when writing a complex framework and one call on a lower hierachy level throws an Exception, the higher levels should be able to get to know. If I have to catch it on a higher level, I can't leave the caught Exception as is just adding my current context to the stack trace. Sometimes you need something like that. VB.NET for example allows you something like: Public Sub foo() Try ... Catch e AS NastyException ... throw End Try End Sub Best Regards Dennis Sterzenbach