Date: Sun, 13 Dec 1998 10:32:10 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: rylan AT intekom DOT co DOT za
cc: allegro AT canvaslink DOT com, djgpp AT delorie DOT com
Subject: Re: Allegro Dialog procedures memory utilization?
In-Reply-To: <005401be2642$7b34afa0$a56f19c4@default>
Message-ID: <Pine.SUN.3.91.981213103147.26792Y-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Sun, 13 Dec 1998 rylan AT intekom DOT co DOT za wrote:

> I've noticed that after calling any of the Allegro dialog execution =
> procedures (do_dialog, popup_dialog, etc), _go32's "remaining physical =
> memory" function returns 4096 byte (4k) less memory as available than =
> before the call. Why is this? Do these functions use static variables?

Did you read section 15.2 of the FAQ?  It should answer this
question.  If it doesn't, please ask more specific questions, based on
what the FAQ explains.