Date: Sun, 28 Jul 1996 13:32:18 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: Opinion
In-Reply-To: <9607280701.AA13626@clio.rice.edu>
Message-Id: <Pine.SUN.3.91.960728132342.24276E-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sun, 28 Jul 1996, Charles Sandmann wrote:

> No environment variables.  Maybe a command line switch.

I was thinking about environment variable because a command-line switch 
requires CWSDPMI to be installed resident.  A variable would do that even 
for autoloaded CWSDPMI.  But if `getenv' bloats the code, then the switch 
is OK I guess.

> > Maximum memory usage, number of page faults, internal CWSDPMI memory usage 
> > (to give a clue on how close one is to exhausting the CWSDPMI heap)--anything
> > that can be of any use.  That should make diagnostics a lot easier.
> 
> None of those things are currently tracked :-)

Well, if anything at all (not necessarily from the above list) *is*
tracked, then I'd suggest printing it given that debug option is ON, even
though it doesn't seem to be of value currently.  Please consider adding 
maximum memory usage tracking (just knowing what was the largest usage 
during the client run is enough), since currently there is no simple 
method of getting that info (the simplest I know of is running under 
Windows with some kind of system-resources tracking program).