Path: utzoo!attcan!ncrcan!becker!hybrid!scifi!bywater!uunet!nwnexus!roper
From: roper@nwnexus.WA.COM (Michael Roper)
Newsgroups: comp.windows.ms
Subject: Re: DLL memory management and the heapsize
Message-ID: <388@nwnexus.WA.COM>
Date: 25 Sep 90 01:12:01 GMT
References: <4944@hsv3.UUCP>
Reply-To: roper@nwnexus.UUCP (Michael Roper)
Distribution: usa
Organization: hDC Computer Corporation, Redmond WA
Lines: 22

James Seidman writes:

> The SDK doesn't describe very clearly (at least to me) how DLLs handle
> their local heap.  It says at one point that the heap can grow if a
> LocalAlloc requires more memory than is currently available.  Does it
> mean only up to the amount specified in HEAPSIZE?  Does that mean that
> I can set HEAPSIZE to 64K and not necessary have that much memory munched
> if I don't allocate it?

HEAPSIZE is the initial size of the heap.  The heap can never be smaller
than HEAPSIZE, but it can be bigger.

> (And please don't tell me to use GlobalAlloc(), either... I'm
> dereferencing pointers in tight loops and having them be far would cause
> performance impairments.)

If you have C 6.0, based pointers will solve your "tight loop" problem
when using global memory.


Michael Roper
hDC Computer Corporation