Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: "Mike Schilling" Newsgroups: comp.lang.java.programmer Subject: Re: Proposed new Java feature Date: Tue, 29 May 2012 18:53:50 -0700 Organization: A noiseless patient Spider Lines: 20 Message-ID: References: <8Euwr.47425$On2.20024@newsfe16.iad> Injection-Date: Wed, 30 May 2012 01:53:58 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="AXjbjGvakNxR7/6Xyznwww"; logging-data="2415"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/frdGeugBr623J5vwOuPXerpJdymd0DB0=" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-RFC2646: Format=Flowed; Response X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 Cancel-Lock: sha1:+LrVkuy7YhnbXrurmMivxOUUzDk= X-Priority: 3 X-MSMail-Priority: Normal Xref: csiph.com comp.lang.java.programmer:14930 "Robert Klemme" wrote in message news:a2kr84F7kbU1@mid.individual.net... > On 05/29/2012 06:40 AM, Mike Schilling wrote: >> "Robert Klemme" wrote in message >> news:a2i77nFik2U1@mid.individual.net... >>> The point is that with the global reference cleanup the specific code >>> does >>> not have a chance to run because it does not know when. The proper >>> point >>> in time is just before or during remove(). >> >> How would the cleanup code knew when to run during Thread exit? > > Obviously that would have to be implemented in class Thread using a > finally block. Do the same with Threads returned to ThreadPools and we're good.