delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/01/09/14:06:45

From: bruffald AT vub DOT ac DOT be (RUFFALDI BATTISTA)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allocating and using memory with the dpmi functions
Date: 9 Jan 1997 12:21:59 GMT
Organization: Brussels Free Universities (VUB/ULB), Belgium
Lines: 32
Message-ID: <5b2nt7$bjd@rc1.vub.ac.be>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970102083550 DOT 17516B-100000 AT is> <19970104 DOT 000402 DOT 4727 DOT 1 DOT aclemmer AT juno DOT com>
NNTP-Posting-Host: is3.bfu.vub.ac.be
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Aaron m Clemmer (aclemmer AT juno DOT com) wrote:
: On Thu, 2 Jan 1997 08:49:59 +0200 (IST) Eli Zaretskii
: <eliz AT is DOT elta DOT co DOT il> writes:
: >IMHO, this is a bad decision.  What's wrong with using `malloc' and 
: >Co.?  I think that going for the DPMI functions will make things 
: >considerably more complex for you (see below), without any real 
: >reason.  
: 	After reading below, I agree... I was under the impression that
: 'malloc' was somehow limited in how much I could allocate, but apparently
: not... Yeah, I'll go rewrite those functions...

: >Believe  me, you DON'T want to do that on your own without a *very* good

: >reason!
: 	I suppose there aren't many?

--


If you really have troubles, you could just use a big malloc at the beginning of your code and then use your own malloc routines grabbing memory from the memory allocated with the big malloc


  Battista Ruffaldi



--------------

Virtual Presence,

all kind of computer services.
 

- Raw text -


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