Re: [Windows] Any way to distinguish ^C Induced EOF from ^Z EOF?

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer

Date:

Tue, 13 Mar 2012 11:36:39 -0400

Message-ID:

<4f5f6989$0$295$14726298@news.sunsite.dk>

On 3/13/2012 9:06 AM, Jan Burse wrote:

Arne Vajh?j schrieb:

If what you want is not in the docs, then it
is not broken as you claim.

Its simply broken because of the following
chain of reasoning.

- InputStream/OutputStream are supposed
to be blocking IO in contrast to NIO.

- When a shutdown sequence is initiated
no InputStream/OutputStream is killed
they remain blocking in case they were
already blocking.

so that the shutdown hooks can gracefully
terminate their service. For example
a goodbye sequence with a web server, etc..

- SIGINT when available, by default
initiates a shutdown sequence.

- The Windows behaviour for CONIN$ violates
the above, since during SIGINT the
CONIN$ becomes non-blocking in that
it returns EOF.

So this is what is broken here. It contaminates
any sensible use of shutdown hooks as described
here in the case of Windows:
http://docs.oracle.com/javase/1.4.2/docs/api/java/lang/Runtime.html#addShutdownHook%28java.lang.Thread%29

Well that doc does not state anything about streams remain blocked.

It is just something you have invented.

You may still consider that "sensible use", but the fact
remains that:
* nothing in Java is broken
* your code is broken
because the behavior is not specified.

You can not design your programs after how you think
the platform should behave - you have to code after
how it actually behave.

And that includes staying away from something that
is not well defined.

Arne