Date:	Mon, 9 Nov 92 09:31:39 EST
From:	DJ Delorie <dj AT athena DOT ctron DOT com>
To:	ms AT informatik DOT uni-hannover DOT de
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Memory allocation under Go32

> I vaguely remember that a malloc-call just allocates the memory
> internally but doesn't do anything about it.  Does that mean that
> malloc returns successfully even though there may be no swap space for
> it?  (meaning: does GO32 allocate swap space for rquested memory if
> there's no RAM left?)  In consequence, if so, would that mean there's
> no safe way to check if memory allocation is possible at all?

Correct.  The actual memory (ram or swap) is allocated as the virtual
memory is *accessed*, and when you run out it's go32 that complains.
Great for sparse arrays, though :-)

DJ
dj AT ctron DOT com
Life is a banana.

- Raw text -