Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!cbmvax!higgin
From: higgin@cbmvax.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Assigned names and system requesters
Message-ID: <1379@cbmvax.cbmvax.cbm.UUCP>
Date: Mon, 9-Feb-87 08:51:48 EST
Article-I.D.: cbmvax.1379
Posted: Mon Feb  9 08:51:48 1987
Date-Received: Tue, 10-Feb-87 04:48:44 EST
References: <108@batcomputer.tn.cornell.edu> <1358@cbmvax.cbmvax.cbm.UUCP> <1035@uwmacc.UUCP>
Reply-To: higgin@cbmvax.UUCP (Paul Higginbottom SALES)
Organization: Commodore Technology, West Chester, PA
Lines: 25
Keywords: ASSIGN

In article <1035@uwmacc.UUCP> aaron@unix.macc.wisc.edu.UUCP (Aaron Avery) writes:
$In article <1358@cbmvax.cbmvax.cbm.UUCP> higgin@cbmvax.UUCP (Paul Higginbottom SALES) writes:
$) ...My code to disable requesters...
$     It seems to me that there should be a Forbid()..Permit() around those
$references to the process structure, or at least writes to it. As this same
$case came up in Matt Dillons code fragment doing the same thing, could
$someone please respond, letting me know if I'm even close to right in
$suggesting this.
$
$Aaron Avery ({seismo,harvard,caip,topaz,allegra,ihnp4}!uwvax!uwmacc!aaron)
$            (aaron%maccunix@rsch.wisc.edu)
$            (aaron@unix.macc.wisc.edu)

The only reason I can think of for doing Forbid/Permit around it is if
the program has done something prior to this code which could cause
a requester (opening a file on a disk no longer in a drive, for example).

People shouldn't get Forbid/Permit paranoid because each time a program
does this it's effectively "stopping the world", doing whatever it feels
like, and then allowing the world to start again.  Hardly in the spirit
of multi-tasking!

	Paul.

Disclaimer: I work for Commodore, but opinions expressed are mine only.