From: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro And Alternate Memory Handling
Date: Tue, 10 Mar 1998 19:34:28 +0000
Organization: None
Message-ID: <GM9C3EAEXZB1EwVi@talula.demon.co.uk>
References: <01bd4a2c$40ac6be0$2d48a5c6 AT technoid>
NNTP-Posting-Host: talula.demon.co.uk
MIME-Version: 1.0
Lines: 17
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Luke Bishop writes:
>       I was wondering if there were any plans to make Allegro support 
>something useful for this, like a custom memory allocation/locking 
>scheme

Even if you modified Allegro to do this, you would still run into major
problems any time you called a libc function that allocates any memory.
Unless you are not going to use any library routines at all, I don't
think you can disable malloc() and expect things to go on working.

Why not just link your program with custom versions of malloc() and
free()?


--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
"Pigs use it for a tambourine" - Frank Zappa