Mail Archives: djgpp/1998/03/10/11:30:30
From: | "Luke Bishop" <lbishop AT calvin DOT stemnet DOT nf DOT ca>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Allegro And Alternate Memory Handling
|
Date: | 8 Mar 1998 22:58:19 GMT
|
Organization: | The Zone
|
Lines: | 11
|
Message-ID: | <01bd4a2c$40ac6be0$2d48a5c6@technoid>
|
NNTP-Posting-Host: | n072h045.thezone.net
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
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.
- Raw text -