Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: Interrupted exception chaining Date: Tue, 25 Sep 2012 13:12:10 -0400 Organization: A noiseless patient Spider Lines: 23 Message-ID: References: <5ec3b39d-32ee-4956-a8f2-1ae18e9d0924@s8g2000vbc.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Tue, 25 Sep 2012 17:12:11 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="ffb8f7085759b339c1002252b48331a4"; logging-data="11528"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1//mkSBJv+iuwBoDa+qaMPj" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 In-Reply-To: <5ec3b39d-32ee-4956-a8f2-1ae18e9d0924@s8g2000vbc.googlegroups.com> Cancel-Lock: sha1:0rjvTS5xPhCJwXymnaEplxzlWxU= Xref: csiph.com comp.lang.java.programmer:18915 On 9/25/2012 12:28 PM, Ivan Ryan wrote: > On Sep 25, 4:33 pm, markspace <-@.> wrote: >> On 9/25/2012 3:25 AM, raph...@gmail.com wrote: >> >>> Is there a recommended way of "chaining" interrupted exceptions? >> >> I mostly agree with Eric. You shouldn't suppress interrupts unless you >> must. > > Well, the idea is to be able to have a method where the caller doesn't > have to worry about handling interrupts. Fine: The called method handles its own interrupts, and that's that. But then, the O.P. wants the information about the interrupt to propagate back to the caller -- the very same caller that "doesn't have to worry about handling interrupts!" "Pick a card, any card, don't show it to me. Okay, what card is it?" -- Eric Sosman esosman@ieee-dot-org.invalid