delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/01/30/14:46:38

From: Liche <liche AT tp DOT silkera DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: _fmalloc() equivalent in djgpp
Date: Sat, 31 Jan 1998 03:32:05 +0800
Organization: New Silkera Network
Lines: 10
Message-ID: <34D22AB4.3991C754@tp.silkera.net>
NNTP-Posting-Host: ts118.tp.silkera.net
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

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 ;-).  Does that mean malloc() will allocate memory dynamically from
all of the available ram on my machine?  Or are there other restrictions
that limit the size of memory I can allocate dynamically with malloc()?
What about new?  And if my first assumption is incorrect, what is the
_fmalloc() equivalent in djgpp?  Thanks

Liche

- Raw text -


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