delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/01/17/15:16:00

To: DJGPP List <djgpp AT sun DOT soe DOT clarkson DOT edu>
Subject: catching ctrl-break vs. ctrl-c
Reply-To: pgf AT Cayman DOT COM
Date: Mon, 17 Jan 94 13:59:31 EST
From: Paul Fox <_pgf AT Cayman DOT COM>

hi -- last week i asked how to prevent getting the "Ctrl-C Hit!" message
when my program is running and doesn't have a pending read() on stdin.
someone sent me info on the go32_want_ctrl_break()/go32_was_ctrl_break_hit()
calls, and they work just great at preventing me from ever seeing a ctrl-break.
however, i _still_ get ctrl-c being reported.  i sort of thought these two
interrupts were supposed to be equivalent?

any ideas?


---------------------
    paul fox, pgf AT cayman DOT com (cayman systems inc. cambr^H^H^H^H^Hwoburn, ma)
    	home: pgf AT foxharp DOT boston DOT ma DOT us (arlington, ma)


- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019