🚀 go-pugleaf

Bill Whedon (whedon@netcom.com) wrote:
> Here's the summary I promised.  The answers I got were mixed.  Advice to
> keep using malloc, advice to use _fmalloc, neither of which solved the
> original problem (corruption of a linked list).  The most useful was from
> raymondc@microsoft.com, who sent me a fix for the myfree() routine which
> stopped my memory leak.  Both routines follow this note.  
>
> void *mymalloc(size_t bytes)
> ...
>    h = GlobalAlloc(GMEM_FIXED | GMEM_ZEROINIT,(DWORD)bytes);
> ...
> 
> void myfree(void *p)
> ...
>       h = (GLOBALHANDLE)SELECTOROF((LPVOID)p);
> ...

Question 1)   What is SELECTOROF()?  I am assuming it is the equivalent of
              GlobalHandle()?

Question 2)   What do you do about running out of HANDLES?  It has been my
              expereince, and I have had it confirmed by a few other 
              programmers, that you only get to allocate about 8000 handles,
	      using GlobalAlloc, before you start getting incoherent results...
	      Is there any way around this, short of allocating large blocks 
	      and doing your own memory management?

	      And if there isn't, does someone have a set of routines to do
	      this allocation yet?

Noel
--
"You want it should sing too?"   | /*  Yeah we got dogs and Valvoline
  ngorelic@speclab.cr.usgs.gov   |     Its a pretty damn good time.    */
"Life is pain. Anyone that tells you different is trying to sell you something"