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

From:

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

Newsgroups:

comp.lang.java.programmer

Date:

Sun, 11 Mar 2012 18:13:48 -0400

Message-ID:

<4f5d239d$0$293$14726298@news.sunsite.dk>

On 3/11/2012 5:49 PM, Jan Burse wrote:

Arne Vajh?j schrieb:

That type of stuff is very OS specific.

I will (again) suggest using JNI to get the specific
behavior that you desire.

Java IO is just for the 98% of cases.

Arne

When I raise the signal manually, for example
as follows:

new Thread() {
public void run() {
try {
Thread.sleep(2000);
} catch (InterruptedException x) {
/* */
}
Signal.raise(new Signal("INT"));
}
}.start();

Then the EOF does not happen. So it is not a problem
of the Java dispatcher, more of the ReadFile operation.

I am open to JNI, and also to JNA.

JNA is also JNI just encapsulated a bit.

Best would
be if there is something out of the box.

Of course.

But Java was not designed to provide that type of
fine control over terminal IO.

It could be fixed, if one would have access to
GetLastError. Namely the MS docs do write:

"Characters can be read from the console input buffer by using ReadFile
with a handle to console input. The console mode determines the exact
behavior of the ReadFile function. By default, the console mode is
ENABLE_LINE_INPUT, which indicates that ReadFile should read until it
reaches a carriage return. If you press Ctrl+C, the call succeeds, but
GetLastError returns ERROR_OPERATION_ABORTED. For more information, see
CreateFile."
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365467%28v=vs.85%29.aspx

With JNI you can use it and get exactly the behavior you want.

Arne