On Jul 25 22:43 96, Paul Edwards of 3:711/934.9 wrote to david begley:

PE> But other products have a "/386" version or a
"/2" version etc to 
PE> distinguish the platform.  I don't see any problem with tacking that on the 

That's only needed if the executables are to some degree interchangeable. 
For example, there's no need to identify the Solaris version of Oracle7 vs.
the HP-UX version, because neither will run on the other platform at all. 
On the other hand, an 8088 version of something will run (or limp) on
anything up to a Pentium Pro, and on anything from DOS to OS/2 to NT.  In
that case, it's necessary to know which version is which.  Some programs
written for OS/2 will run on NT, and some Windows programs will run on
either OS/2 or NT.

In that case, you need to be able to identify the flavor of a seemingly
interchangeable set of executables.  You might even want to have different
versions available at the same time.  That doesn't mean the product has to
have a distinct name, though.  This is a matter of taste.

PE> end, the same as the version number, so that goes into the PID when a user 
PE> reports a problem.  Also, it is useful to determine whether there are in 
PE> fact any dos/386 users of a product, to know whether there is actually a 
PE> point in compiling and supporting that platform.  Just another thought!  
PE> BFN.  Paul. 

You can't tell that by naming the product, unless it doesn't work and they
complain.  My vote would be to have the program called msged, dropping the
sq in case somebody feels like adding JAM or something else to it: you
don't want to be stringing more and more suffixes onto it.  Then have an
About screen which identifies the version of the executable, including the
target platform AND the platform on which it is running (software as well
as hardware, and any networking you can identify).

Do yourself a favor, and add an About edit command that pumps this stuff
into the body of the message so the user can easily include it in a bug
report.

Jerry Schwartz
@EOT:

--- MsgedSQB 3.30.01


SD®¯–l