From: Jeff Sturm <jsturm@sigma6.com>
To: Kresten Krab Thorup <krab@eos.dk>
Cc: Bryce McKinlay <bryce@albatross.co.nz>,
java-discuss@sourceware.cygnus.com
Subject: Re: Thread.interrupt()
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <38CE44FB.F07DC4D0@sigma6.com> (raw)
Message-ID: <20000401000000.bWSDkHTLGzR2SP4YKBROvEv0iTPvLm0wjoRge9r0T70@z> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-01 0:00 Thread.interrupt() Bryce McKinlay
2000-03-13 13:33 ` Thread.interrupt() Bryce McKinlay
2000-03-14 2:24 ` Thread.interrupt() Kresten Krab Thorup
2000-03-14 3:26 ` Thread.interrupt() Bryce McKinlay
2000-04-01 0:00 ` Thread.interrupt() Bryce McKinlay
2000-03-14 5:52 ` Jeff Sturm [this message]
2000-03-14 11:02 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Tom Tromey
2000-03-14 14:16 ` Thread.interrupt() Bryce McKinlay
2000-03-14 16:09 ` Thread.interrupt() Godmar Back
2000-04-01 0:00 ` Thread.interrupt() Godmar Back
2000-04-01 0:00 ` Thread.interrupt() Bryce McKinlay
2000-04-01 0:00 ` Thread.interrupt() Jeff Sturm
2000-04-01 0:00 ` Thread.interrupt() Kresten Krab Thorup
2000-04-01 0:00 ` Thread.interrupt() Bryce McKinlay
-- strict thread matches above, loose matches on Subject: below --
2000-03-16 4:08 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-15 13:52 Thread.interrupt() Boehm, Hans
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-15 13:06 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-15 12:55 Thread.interrupt() Boehm, Hans
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-15 11:57 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-15 11:38 Thread.interrupt() Boehm, Hans
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-15 5:51 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-14 16:30 Thread.interrupt() Boehm, Hans
2000-03-14 17:17 ` Thread.interrupt() Jesper Peterson
2000-03-14 17:27 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Jesper Peterson
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-14 11:26 Thread.interrupt() Boehm, Hans
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-14 9:57 Thread.interrupt() Boehm, Hans
2000-03-14 10:52 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Tom Tromey
2000-03-14 15:59 ` Thread.interrupt() Jesper Peterson
2000-04-01 0:00 ` Thread.interrupt() Jesper Peterson
2000-04-01 0:00 ` Thread.interrupt() Boehm, Hans
2000-03-14 7:47 Thread.interrupt() Miles Sabin
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
2000-03-14 6:00 Thread.interrupt() Miles Sabin
2000-03-14 7:36 ` Thread.interrupt() Jeff Sturm
2000-03-14 10:58 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Tom Tromey
2000-04-01 0:00 ` Thread.interrupt() Jeff Sturm
2000-04-01 0:00 ` Thread.interrupt() Miles Sabin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38CE44FB.F07DC4D0@sigma6.com \
--to=jsturm@sigma6.com \
--cc=bryce@albatross.co.nz \
--cc=java-discuss@sourceware.cygnus.com \
--cc=krab@eos.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).