Path: utzoo!attcan!cmtl01!matrox!uvm-gen!uunet!lll-winken!ames!mailrus!eecae!netnews.upenn.edu!rutgers!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Task KILL for Amiga
Message-ID: <5799@cbmvax.UUCP>
Date: 26 Jan 89 04:47:27 GMT
References: <8901251704.AA18073@terra.oscs.montana.edu>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 16

In article <8901251704.AA18073@terra.oscs.montana.edu> iphwk@MTSUNIX1.BITNET (Bill Kinnersley) writes:
>I think the reason that people don't pay more attention to MEMF_PUBLIC is
>that it's never been documented precisely *which* system structures require
>it.  The best answer I've heard about this is "Bitmaps and sound samples
>and well, lots of others (sometimes)."

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

	Bitmaps and sound samples are actually a less problemsome case.  They
must be in chip ram anyways, and are rarely if ever (except screen bitmaps)
accessed by other tasks.

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