Path: utzoo!attcan!uunet!cbmvax!ditto
From: ditto@cbmvax.UUCP (Michael "Ford" Ditto)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Task KILL for Amiga
Message-ID: <5808@cbmvax.UUCP>
Date: 26 Jan 89 18:09:18 GMT
References: <8901251704.AA18073@terra.oscs.montana.edu> <5799@cbmvax.UUCP>
Reply-To: ditto@cbmvax.UUCP (Michael "Ford" Ditto)
Organization: Commodore Technology, West Chester, PA
Lines: 22

In article <5799@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes:
 [ about when to use MEMF_PUBLIC ]
>	The best answer I can give is: Anything other tasks will access,
>any system structure, perhaps anything intuition will use, stacks, ports,
>messages.  If in doubt, make it public.

Hmmm...  I think stacks should NEVER be public, and I hope "any system
structure" only means structures which will be added to an internal system
list of some sort, not things like FileInfoBlocks or NewWindows.  I think
the RKM's description is quite reasonable:  Anything that will be accessed
by another task or an interrupt handler.

Intuition things would need to be public if they will be accessed by the
input handler side of intuition, and I don't know of a rule of thumb to
know when that is the case.
-- 
					-=] Ford [=-

"The number of Unix installations	(In Real Life:  Mike Ditto)
has grown to 10, with more expected."	ford@kenobi.cts.com
- The Unix Programmer's Manual,		...!sdcsvax!crash!elgar!ford
  2nd Edition, June, 1972.		ditto@cbmvax.commodore.com