Date: Wed, 8 May 1996 13:12:21 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: stwand07 AT uctvms DOT uct DOT ac DOT za
Cc: djgpp AT delorie DOT com
Subject: Re: ANSI C signal definitions
In-Reply-To: <1996May8.100808@uctvms.uct.ac.za>
Message-Id: <Pine.SUN.3.91.960508130716.17904B-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 8 May 1996 stwand07 AT uctvms DOT uct DOT ac DOT za wrote:

> One should be aware that the Ctrl-C signal will not work 100% of the time,
> depending on DPMI ...

Of course anything's possible, but currently I'm not aware of any DPMI
host that screws up SIGINT handling in v2 programs.  CWSDPMI works OK
(what'd you expect?), and so are QDPMI and Windows.  If anybody knows
about specific DPMI host and specific case where ^C doesn't work, please
tell so.  The only subtle aspect of ^C (as I wrote in another message in
this thread) is that when you switch stdin to binary mode (e.g., with 
`setmode'), you have to call `__djgpp_set_ctrl_c' to cause ^C generate 
SIGINT.