Path: utzoo!attcan!uunet!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Task KILL for Amiga
Message-ID: <5813@cbmvax.UUCP>
Date: 26 Jan 89 19:55:12 GMT
References: <8901251704.AA18073@terra.oscs.montana.edu> <5799@cbmvax.UUCP> <5808@cbmvax.UUCP>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 27

In article <5808@cbmvax.UUCP> ditto@cbmvax.UUCP (Michael "Ford" Ditto) writes:
>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.

	FileInfoBlocks and NewWindows are probably ok.  Stacks must be public
if you plan to call anything that might use a Dos call OR call anything that
might use SignalSemaphores.  This is, of course, all speculation, and all
the MEMF_PUBLICs in the world won't guarantee your program will work if we
do a protected mode OS, but they certainly give your program a much better
chance!

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

	Which is why I was vague.  Even if I gave a list, it might change
tomorrow (or at least next time we release an OS upgrade).

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup