Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!mcsun!ukc!icdoc!sot-ecs!snb90
From: snb90@uk.ac.soton.ecs (Stewart Brodie)
Newsgroups: comp.sys.acorn
Subject: Re: Module task terminating
Message-ID: <8315@ecs.soton.ac.uk>
Date: 27 Jun 91 12:10:58 GMT
Article-I.D.: ecs.8315
References: <1991Jun27.052256.1@vax1.tcd.ie>
Sender: news@ecs.soton.ac.uk
Lines: 21
Originator: snb90@gloriana

In <1991Jun27.052256.1@vax1.tcd.ie> hughesmp@vax1.tcd.ie writes:

>I am writing a module wimp task that must not survive reset, ie it must
>be rmkilled after / just before a reset/break occurs. Bearing in mind that
>it cannot call OS_Module 6 (Delete) from within a Service_Reset with
>guaranteed success, how can it kill itself? I want it to be a module
>task so that it does not need a whole page to itself.

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 - then you can kill OS_ExitAndDie or whatever it is. That is
the normal way of signalling conditions to your main program from code
which is not allowed to call it directly.

> 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.)

Stewart Brodie
University of Southampton