Re: ReallocMem

Article View: comp.sys.amiga.tech

Article #12072

Back to comp.sys.amiga.tech Previous Next

#12072

From: dougp
Date: Sun, 02 Apr 1989 00:56

14 lines
1019 bytes

In article <11848@umn-cs.CS.UMN.EDU>, brant@uf.msc.umn.edu (Gary Brant) writes...

>of the requested size.  If a new block is needed, ReAllocMem copies the
>contents of the old block to the new one before releasing the old block to
>the free storage pool.  I don't see why any Forbid/Permit's would be needed


You might also include the ability to change the type of memory by
specifing a new set of memory type flags. Of course this would
REQUIRE copying the memory if you changed from FAST to CHIP, but it
might require only messing with some registers in the MMU of future
amigas if you changed from PUBLIC to private ram.

Douglas Peale

Technical Details

Message-ID: <1394@hub.ucsb.edu>

Path:

arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!ucsbcsl!dougp@sbphy.ucsb.edu

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!ucsbcsl!dougp@sbphy.ucsb.edu
From: dougp@sbphy.ucsb.edu
Newsgroups: comp.sys.amiga.tech
Subject: Re: ReallocMem
Message-ID: <1394@hub.ucsb.edu>
Date: 2 Apr 89 00:56:03 GMT
Sender: news@hub.ucsb.edu
Organization: UC, Santa Barbara. Physics Computer Services
Lines: 14