This is the mail archive of the java-discuss@sourceware.cygnus.com mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Thread.interrupt()

To: Kresten Krab Thorup <krab at eos dot dk>
Subject: Re: Thread.interrupt()
From: Jeff Sturm <jsturm at sigma6 dot com>
Date: Tue, 14 Mar 2000 08:56:11 -0500
CC: Bryce McKinlay <bryce at albatross dot co dot nz>, java-discuss at sourceware dot cygnus dot com
Organization: AppNet
References: <38CCAD8B.5F7B8259@albatross.co.nz> <38CD5EB7.C1DBECA9@albatross.co.nz> <38CE13CE.B8D1D6B8@eos.dk>

Kresten Krab Thorup wrote:
[...]
> As of today, the interruptable io has officially deprecated. We are not
> going to fix this bug. However, we leave the current implementation as
> it is for backward compatibility.
> 
> xxxxx@xxxxx 1999-09-12

IOW, Sun crippled their API because Win32 doesn't handle interruptable
I/O portably.  Not a good policy.

Since Java doesn't support read() with timeouts either, it is easy to
create a "stuck" thread that can never die.

Question: do the libgcj maintainers feel obligated to follow Sun's
interpretation of the JLS?

-- 
Jeff Sturm
jsturm@sigma6.com

Follow-Ups:
- Re: Thread.interrupt()
  - From: Tom Tromey
- Re: Thread.interrupt()
  - From: Bryce McKinlay

References:
- Thread.interrupt()
  - From: Bryce McKinlay
- Re: Thread.interrupt()
  - From: Bryce McKinlay
- Re: Thread.interrupt()
  - From: Kresten Krab Thorup

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]