🚀 go-pugleaf

In article <4100@mace.cc.purdue.edu> afc@mace.cc.purdue.edu (Greg Flint) writes:
>The problem that I'm having is that when I request 1-8 bytes, I'm given
>16.  When I request 9-16, I'm given 32 bytes...and so on.  This causes
>me to run out of memory long before I should.  (This is determined by
>calling "farcoreleft" after each "farmalloc" call.)
>-------------------------------------------------------------------------------
>Greg Flint 	  Math G-169   (317) 494-1787   UUCP:  purdue!klaatu.cc!afc
>  Purdue Univ.	  Purdue University	    INTERNET:  afc@klaatu.cc.purdue.edu
>  Computing Ctr.  West Lafayette, IN 47907    BITNET:  flint@purccvm.bitnet

   Since I'm not at my computer just now, I can't say for sure, but I
think that farmalloc is just an interface to the DOS memory-allocation
functions. These, of course, allocate memory in paragraphs. Since
several bytes at the beginning of every memory block are reserved for
system use, when you try for 9 bytes, it has to give you two
paragraphs, etc.
   Worse, there have been the occasional rumors about bugs in DOS's
memory handling functions, leading to system corruption if lots of small
blocks are allocated and released frequently.
   Things you could try: you could try switching to a larger memory
model (one with multiple data segments) and use malloc(). I've never
gotten malloc() to work right in larger memory models, but I've never
tried very hard.
   Otherwise I think you're going to have to write or find a library of
memory-management functions.


-- 
James W. Birdsall  jwbirdsa@phoenix.Princeton.EDU  jwbirdsa@pucc.BITNET
   ...allegra!princeton!phoenix!jwbirdsa   Compu$erve: 71261,1731
"For it is the doom of men that they forget." -- Merlin