Xref: news2.mv.net comp.os.msdos.djgpp:8413
From: "Maan M. Hamze" <mmhamze AT mail DOT utexas DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: CWSDPMI V3 - what's new versus V2?
Date: 8 Sep 1996 08:25:14 GMT
Organization: University of Texas at Austin
Lines: 46
Message-ID: <01bb9d5f$238b3440$64fe5380@maan-m.-hamze>
References: <323128DA DOT 3938 AT drao DOT nrc DOT ca> <3231b405 DOT sandmann AT clio DOT rice DOT edu>
NNTP-Posting-Host: slip-75-4.ots.utexas.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Charles Sandmann <sandmann AT clio DOT rice DOT edu> wrote in article
<3231b405 DOT sandmann AT clio DOT rice DOT edu>...

> The hazards of inadequate testing.  So, maybe there will be an R4...
> but not until I see if anyone notices other problems with R3...
> 
If there will be version 4, you may want to consider the following minor
things that actually have nothing to do with running games :)

1.  The program is reloaded again and again whenever the user runs:
cwsdpmi -p

It may be nice for the prgram to load only once with one:
cwsdpmi -p 
and to report that:
cwsdpmi loaded into memory

and to report that:
cwsdpmi is already loaded into memory 
when the user attempts another:
cwsdpmi -p

2.  As things are now, when cwsdpmi is reloaded as in above with the -p
switch it will be unloaded once at a time with every:
cwsdpmi -u

Now if point 1 is taken into account then:

cwsdpmi -u
will unload the program if the program was loaded before, reporting:
cwsdpmi has been unloaded

and
cwsdpmi -u
will report:
cwsdpmi is not loaded
if the user has not loaded the program before.

These are minor points that make for a more consistent behaviour as "house
cleaning chores" more than anything else.
M
-- 
Maan M. Hamze
mmhamze AT mail DOT utexas DOT edu
http://leb.net/~mmhamze