Article View: borland.public.jbuilder.java.language
Article #16337Re: finally and return
From: Tor Iver Wilhelmsen
Date: Tue, 02 Mar 1999 00:00
Date: Tue, 02 Mar 1999 00:00
11 lines
1019 bytes
1019 bytes
dchamberlinNOSPAM@dlawton.com (Doug Chamberlin) writes: > What other statements, if placed in a finally block, cause an > exception to stop being "thrown"? Only the aforementioned return, or throwing a different exception, AFAIK. You can also have it throw the exception.fillInStackTrace() in order to ignore underlying method calls: especially useful for MSIE, where the depth of the call stack can be quite... daunting. However, the throw is better suited for placement in a catch().
Technical Details
Message-ID:
<ur9r88cti.fsf@sds.no>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<36d6e3bb.6330119@forums.inprise.com> <u678p34ga.fsf@sds.no> <36d6c8a3.275742@forums.inprise.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f74b3,92c7634c9c470034 X-Google-Attributes: gidf74b3,public From: Tor Iver Wilhelmsen <tor.wilhelmsen@sds.no> Subject: Re: finally and return Date: 1999/03/02 Message-ID: <ur9r88cti.fsf@sds.no> X-Deja-AN: 450300691 Sender: towi@SDSA1761 References: <36d6e3bb.6330119@forums.inprise.com> <u678p34ga.fsf@sds.no> <36d6c8a3.275742@forums.inprise.com> Organization: Another Netscape Collabra Server User Newsgroups: borland.public.jbuilder.java.language