delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/01/31/01:41:45

Date: Fri, 30 Jan 1998 22:40:04 -0800 (PST)
Message-Id: <199801310640.WAA09871@adit.ap.net>
Mime-Version: 1.0
To: Liche <liche AT tp DOT silkera DOT net>, djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: _fmalloc() equivalent in djgpp

At 03:32  1/31/1998 +0800, Liche wrote:
>Is there a need for the equivalent of _fmalloc() in djgpp?  I assume no,
>because there are no 64k segment restrictions (just learned that a day
>ago ;-). 
You are correct.
> Does that mean malloc() will allocate memory dynamically from
>all of the available ram on my machine? 
Essentially, yes.
> Or are there other restrictions
>that limit the size of memory I can allocate dynamically with malloc()?
It depends on your DPMI server. CWSDPMI can allocate up to (I think) 512M of
memory, 256M real and 256M swap. Windows 95 only lets you have up to 64M
total. See FAQ section 15 for more.
>What about new? 
Same. It really calls `malloc', at the bottom level.

Nate Eldredge
eldredge AT ap DOT net



- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019