Message-Id: <m0yCOfy-000S2kC@inti.gov.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization: INTI
To: "Luke Bishop" <lbishop AT calvin DOT stemnet DOT nf DOT ca>, djgpp AT delorie DOT com
Date: Tue, 10 Mar 1998 16:04:05 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Allegro And Alternate Memory Handling
In-reply-to: <01bd4a2c$40ac6be0$2d48a5c6@technoid>
Precedence: bulk

"Luke Bishop" <lbishop AT calvin DOT stemnet DOT nf DOT ca> wrote:

> 	I am using a special memory daemon for my 3D game to ensure correct
> allocation of memory.  The problem is, no routine can use
> malloc/realloc/free/new/delete!  ALL of these functions will probably
> crash, as the daemon has allocated ALL free memory and even locked all
> lockable pages.  This makes ALLEGRO want to DIE.
> 	I was wondering if there were any plans to make Allegro support something
> useful for this, like a custom memory allocation/locking scheme (my daemon
> lets you "lock alloc" a block of LOCKED memory).
> 	This is very important to me, as I plan on using this daemon a lot and
> don't like the idea of rewriting Allegro.

So: why you don't simply replace malloc/realloc/free from libc?

SET 
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-sot AT usa DOT net - ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013