delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:4135 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Ctrl-C arg |
Date: | Mon, 20 May 1996 18:29:33 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 8 |
Message-ID: | <31a1005d.sandmann@clio.rice.edu> |
References: | <Pine DOT SGI DOT 3 DOT 91 DOT 960520151505 DOT 15841B-100000 AT tower DOT york DOT ac DOT uk> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> __djgpp_set_ctrl_c(0); > function doesn't seem to be documented anywhere: does anyone know why > not? Is there some reason why I shouldn't be using it? It's an internal function which I didn't expect to be called by the users. In the UNIX world to supress CTRL-C interrupts you would SIG_IGN SIGINT, which is a more portable way to do this. You can also set the stdin to binary which will also suppress CTRL-C (a standard way, once again).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |