Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!uunet!mcsun!ukc!tcdcs!vax1.tcd.ie!hughesmp
From: hughesmp@vax1.tcd.ie
Newsgroups: comp.sys.acorn
Subject: Re: Module task terminating
Message-ID: <1991Jun28.005032.1@vax1.tcd.ie>
Date: 28 Jun 91 00:50:32 GMT
References: <1991Jun27.052256.1@vax1.tcd.ie> <8315@ecs.soton.ac.uk>
Sender: news@cs.tcd.ie
Organization: Trinity College Dublin
Lines: 29
Nntp-Posting-Host: vax1

In article <8315@ecs.soton.ac.uk>, snb90@uk.ac.soton.ecs (Stewart Brodie) writes:
> In <1991Jun27.052256.1@vax1.tcd.ie> hughesmp@vax1.tcd.ie writes:
> 
>>I am writing a module wimp task that must not survive reset

> Why don't you have a flag in your workspace which gets set when a
> Service_Reset comes along and check this flag just before calling
> Wimp_Poll

Because I would prefer if it would die on reset - I don't want it to
have to wait to be re-initialised as a wimp task before it kills itself.

>> Can a utility (filetype ffc) be a wimp task?
 
> What's the point, if you are going to use a module? (unless you want to
> use the application workspace, I suppose.)

Because a utility is a transient program, that can take up less than a page,
is unlinked on reset, and can terminate at any old point just by doing a
MOV15,14 - no need to kill itself. Basically, I have a very small program that
needs to be a wimp task, must _die_ on reset, and I don't want to be a normal
wimp application that takes up a whole page because it is a big waste of space.

Owen Smith suggested to pmf (Ian Ashley) who suggested to me doing a CallBack
on the Service_Reset, to kill the module later. I shall give this a try as it
sounds feasible...

Merlin.
--SICK--