Newsgroups: comp.sys.amiga.programmer
Path: utzoo!utgpu!watserv1!watdragon!rose!ccplumb
From: ccplumb@rose.uwaterloo.ca (Colin Plumb)
Subject: Re: Can you use Signal() from an input handler?
Message-ID: <1991Jan26.180117.1122@watdragon.waterloo.edu>
Sender: daemon@watdragon.waterloo.edu (Owner of Many System Processes)
Organization: University of Waterloo
References: <2032@ria.ccs.uwo.ca>
Date: Sat, 26 Jan 91 18:01:17 GMT
Lines: 20

terry@csd.uwo.ca (Terry Cudney) wrote:
>     Question:
>     Can the Signal() function not be called from an input handler
> to signal another process? If not, what other mechanism (without busy-waiting)
> could tell the other process that a particular input event
> (RAMIGA + ALPHABETIC KEY)? has occurred?

The input handler is a full task, so you can call any Exec function
(excpet OpenLibrary() or OpenDevice() that might need to load from
disk) from within it.  And Signal() can be called from anything other
than an NMI handler.  So yes, it's quite safe.  I don't know why your
code is Guruing, but it's not because you've described any rule
violations.

Only suspiscion: are you calling Signal(task, signum) or
Signal(task, 1<<signum)?  The latter form is correct.  If you
use the dos.library's signal bit, icky things could happen the
next time you make a Dos call.
-- 
	-Colin