Path: utzoo!utgpu!tmsoft!dptcdc!dpmizar!swrinde!cs.utexas.edu!rutgers!mailrus!cornell!uw-beaver!rice!titan!phil
From: phil@titan.rice.edu (William LeFebvre)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Memory Allocation Question
Message-ID: <2302@kalliope.rice.edu>
Date: 9 Dec 88 22:50:49 GMT
References: <155@bhpese.bhpese.oz> <2077@nunki.usc.edu>
Sender: usenet@rice.edu
Reply-To: phil@Rice.edu (William LeFebvre)
Organization: Rice University, Houston
Lines: 29

In article <2077@nunki.usc.edu> raddison@castor.usc.edu (Richard Addison) writes:
>If you ask for MEMF_FAST, you will only get memory that is identified as
>FAST; if you ask for MEMF_CHIP, you will only get CHIP memory; if you ask
>for MEMF_PUBLIC, you will get PUBLIC memory.
>...
>(Aside:  I sure hope anyone who wants their software to survive any
>upgrade to an MMU version of Exec pays strict attention to allocating
>shared data objects in PUBLIC memory!)

The documentation is not particularly clear when something should be
public and when it should not be.  For example, does the string pointed to
by an IntuiText structure need to be public?  My intuition (no pun
intended) says "yes".

It would also be handy if it was easy to pre-declare hunks to be, say,
both chip and public.  "atom" sure won't let you do it!  In fact, it's not
even clear to me if atom's idea of "public" is the same as MEMF_PUBLIC.
The documentation implies (at least to me) that using atom to change
something to "p" just means that it can come out of either chip or fast.
That's not quite the same thing.  I'd like to put all my Intuition
structures (new window and the gadgets especially) in the same hunk and
just delcare that hunk to be public:  I don't want to have to AllocMem all
those suckers.  But, at least in A68K, I'm not sure that I can request
that a given hunk be public.

			William LeFebvre
			Department of Computer Science
			Rice University
			<phil@Rice.edu>