Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!uokmax!munnari.oz.au!bunyip!brolga!uqcspe!batserver.cs.uq.oz.au!angst
From: angst@batserver.cs.uq.oz.au (Angst)
Newsgroups: comp.sys.amiga.tech
Subject: Making Intuition gadgets generate software interrupts
Message-ID: <4619@uqcspe.cs.uq.oz.au>
Date: 23 Aug 90 07:47:11 GMT
Sender: news@uqcspe.cs.uq.oz.au
Reply-To: angst@batserver.cs.uq.oz.au
Lines: 33

My colleague and I are writing an Amiga interface for a functional language
(a fully lazy version of Hope).  We would like to be able to service intuition
events without having to poll the message ports periodically, i.e. we would
like intuition events to generate software interrupts.

I have a feeling this is possible (since there are parts of the Intuition
message passing hierarchy that mention software interrupts) but I can't work
out how it all fits together.  Can anyone help ?

If it turns out that what we desire is not supported in WB1.3, then how about
this for an alternative.  The master process creates a child that does all the
actual work of the Hope interpreter.  Meanwhile, it sits around polling the
message port and acting upon any events appropriately.  Problems I can see with
this :
	+ how do we kill the child when an event (i.e. quit) so requires;
	+ how do we suspend the child when an event (i.e. inconify) so requires;
	+ how do we get the child to attach its console (for screen I/O will be
	  handled by the child) to the same window for which the master is
	  polling ?

The BYTE review mentioned a mysterious addition to WB2.0 called "HotLinks".
Does this handle this kind of process control ?

Angst

p.s. RTFM Angst !!

p.p.s. Beat you to it.

----------
"Tell the King that he's as safe as a fox being hunted by a pack of one-legged
 hunting tortoises." -- Lord Edmund Blackadder, loyalist
-----------------