Path: utzoo!utgpu!water!watmath!clyde!att-cb!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!husc6!uwvax!puff!avery
From: avery@puff.cs.wisc.edu (Aaron Avery)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Alloc Remember sytems.
Message-ID: <1561@puff.cs.wisc.edu>
Date: 13 Apr 88 11:57:45 GMT
References: <2804@crash.cts.com>
Reply-To: avery@puff.WISC.EDU (Aaron Avery)
Organization: U of Wisconsin CS Dept
Lines: 16

In article <2804@crash.cts.com> haitex@pnet01.cts.com (Wade Bickel) writes:
>    The puzzle is how to handle the case where CHIP memory is allocated in
>place of FAST memory (ie: No FAST mem. was avail).  This must be fast! 
 

Note: if the program requests FAST memory, and there isn't enough of it (or
none) to satisfy the request, you do NOT allocate the memory, as you couldn't
satisfy the request. You return a NULL pointer or whatever indicates failure.
If the program requests FAST memory, you MUST give it FAST memory, just like
if the program were to request CHIP memory, you MUST give it CHIP memory. I
hope I didn't mis-interpret your message, but it shouldn't be handled the way
you stated above.

-- 
Aaron Avery (avery@puff.cs.wisc.edu)
	    ({seismo,caip,allegra,harvard,rutgers,ihnp4}!uwvax!puff!avery)