delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/08/16/06:04:57

Date: Wed, 16 Aug 2000 13:07:20 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: r_maj AT poczta DOT onet DOT pl
Message-Id: <9003-Wed16Aug2000130720+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC: djgpp AT delorie DOT com
In-reply-to: <8ndkdm$lt8$3@info.cyf-kr.edu.pl> (r_maj@poczta.onet.pl)
Subject: Re: changing memory manager
References: <8ndkdm$lt8$3 AT info DOT cyf-kr DOT edu DOT pl>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> From: "Rafał Maj" <r_maj AT poczta DOT onet DOT pl>
> Newsgroups: comp.os.msdos.djgpp
> Date: Wed, 16 Aug 2000 10:41:59 +0200
> 
> 1) Is it possible to change the memory manager, so the DJGPP allocates the
> memory in more economic way (avoiding memory fragmentation)?

You probably mean to change the malloc/free implementation, not the
memory manager.  (The latter is forced on you, at least on Windows.)

Yes, you can replace malloc, but why would you want to?  Do you have
any specific problems?  If so, please describe them: it's quite
possible that you are looking for solutions in the wrong direction.

> 2) Is it possibly, when running a program, to defragment memory?

Yes, but it's not easy.  The easy part is already done by malloc and
free: they splice together adjacent memory chunks that are free'd by
the application.

- Raw text -


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