From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9605221654.AA12885@clio.rice.edu>
Subject: Re: Ctrl-C arg
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Wed, 22 May 1996 11:54:53 -0600 (CDT)
Cc: djgpp AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.960522185810.2226B-100000@is> from "Eli Zaretskii" at May 22, 96 07:02:37 pm
Content-Type: text
Content-Length: 1128      

> The problem is that setting SIGINT to SIG_IGN also suppresses signals
> generated by Ctrl-Break.  Also, if you switch stdin to binary mode, Ctrl-C
> stops generating SIGINT even if you don't want to ignore SIGINT.  So
> `__djgpp_set_ctrl_c' is most useful in re-enabling SIGINT after switching
> stdin to binary, or selectively disabling only Ctrl-C but not Ctrl-Break. 

Yes, if you want additional flexibility I can see why you might want to 
do this.  I didn't burn the bridges when I designed it.  One thing we 
discussed at the time was making these be separate signals, but then decided
to just allow the binary interaction for CTRL-C and the go32_want_ctrl_brk
stuff for ctrl-break.  

> Which is why it *will* be documented in the next release of DJGPP. 

I don't disagree it should be documented now that it's clear that it's
useful and being used.  At the time I wrote it, I wasn't clear on if it had
any use, or if the interface was appropriate (there is another way to do the
exact same thing setting a bit in a global variable, BTW).

I don't want to fess up to the other things in the libc I didn't document ;-(