From: John Cowan co...@mercury.ccil.org
Subject: Re: [Chicken-hackers] [PATCH] resubmission of Win32-specific EINTR
handling
Date: Fri, 6 Jan 2012 11:00:23 -0500
Felix scripsit:
It would actually be helpful to know wether EINTR is fully working on
cygwin. To test it, one just has to start
Felix scripsit:
Excellent - thanks for the information. So Ctrl-C will not terminate csi
and leave you at the next input-prompt, right?
It will not terminate the current input prompt. It will terminate
running code.
CHICKEN
(c)2008-2011 The Chicken Team
(c)2000-2007 Felix L. Winkelmann
* felix winkelmann fe...@call-with-current-continuation.org [120105 09:45]:
Attached a patch submitted recently that adds win32-specific handling
of EINTR in reado/peek-char. Without this patch Ctrl-C will be
treated like EOF and terminate csi.
The version attached adds a CYGWIN-specific
From: Christian Kellermann ck...@pestilenz.org
Subject: Re: [Chicken-hackers] [PATCH] resubmission of Win32-specific EINTR
handling
Date: Fri, 6 Jan 2012 12:44:37 +0100
* felix winkelmann fe...@call-with-current-continuation.org [120105 09:45]:
Attached a patch submitted recently that adds
Felix scripsit:
It would actually be helpful to know wether EINTR is fully working on
cygwin. To test it, one just has to start csi and press Ctrl-C, where
csi should simply report *** user interrupt *** and show another
impot prompt.
Well, if you are at the command prompt you have to push
Attached a patch submitted recently that adds win32-specific handling
of EINTR in reado/peek-char. Without this patch Ctrl-C will be
treated like EOF and terminate csi.
The version attached adds a CYGWIN-specific preprocessor test.
Please consider signing this off, whoever you are.
cheers,
