Path: utzoo!attcan!uunet!lll-winken!ames!pasteur!ucbvax!MTSUNIX1.BITNET!iphwk
From: iphwk@MTSUNIX1.BITNET (Bill Kinnersley)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Task KILL for Amiga
Message-ID: <8901251704.AA18073@terra.oscs.montana.edu>
Date: 25 Jan 89 17:04:42 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 19

[In "Re: Task KILL for Amiga", Randell Jesup said:]
:
: written programs, probably.  Remember, if anyone might need to look at
: memory you allocate, use MEMF_PUBLIC - and don't allocate such things as
: globals/statics in your program, since it may not be public.  That will at
: least help a little if we go to an MMU system.
:
: Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup
:
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)."


--
--Bill Kinnersley
  Physics Department   Montana State University    Bozeman, MT 59717
  INTERNET: iphwk@terra.oscs.montana.edu      BITNET: IPHWK@MTSUNIX1