Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!munnari.oz.au!labtam!eyrie!phoenix!billy
From: billy@phoenix.pub.uu.oz.au (Jeff Coleman)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Dumb windows from SAS/C programs on Workbench
Message-ID: <1991May18.090444.12119@phoenix.pub.uu.oz.au>
Date: 18 May 91 09:04:44 GMT
Article-I.D.: phoenix.1991May18.090444.12119
References: <1991May14.164909.19186@NCoast.ORG> <chopps.0607@ro-chp.UUCP> <1991May17.022136.1539@NCoast.ORG>
Organization: Phoenix ComSystem. Public UNIX Melbourne Australia.
Lines: 33

In <1991May17.022136.1539@NCoast.ORG> davewt@NCoast.ORG (David Wright) writes:

>Draco compiles just fine, I never seem to get the break signals. What do
>you have to do to get things like SIG_BRKF to appear in your input
>stream, or, for instance, prevent a USER from breaking out by entering
>CTRL-C in the program, but allowing someone to use the "BREAK" CLI command
>to send you a CTRL-C and have it correctly (IE, call my handler only when I
>can safely process the event) handle it?


how about something like 

sigs=SIGBREAKF_CTRL_C|whateverelseuwant
Wait(sigs);  

I assume you would have some type of loop and be waiting on message ports as
well these signals.
After the wait you could just do 

if (sigs & SIGBREAKF_CTRL_C) {
  whatever you want to do upon getting this signal
}

Don't forget to disable ctl-c/d/e catching.
The RKM libs+devices is a useful tool for finding these things out.

regards
 jeff.

<----------------------------------------------------------------------------->
	Jeff Coleman          billy@phoenix.pub.uu.oz.au
 	                ..!uunet!munnari.oz!phoenix.pub.uu.oz.au!billy
<----------------------------------------------------------------------------->