Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dogie.macc.wisc.edu!uwvax!daffy!cat9.cs.wisc.edu!schaut
From: schaut@cat9.cs.wisc.edu (Rick Schaut)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Turbo C or MSC
Message-ID: <4548@daffy.cs.wisc.edu>
Date: 29 Mar 90 03:26:52 GMT
References: <924@ns-mx.uiowa.edu> <1468@watserv1.waterloo.edu> <9944@pyr.gatech.EDU> <35104@cci632.UUCP> <2602972a.42b0@polyslo.CalPoly.EDU> <1990Mar26.154024.11739@dasys1.uucp> <1990Mar26.174313.1976@eng.umd.edu>
Sender: news@daffy.cs.wisc.edu
Organization: U of Wisconsin CS Dept
Lines: 23

In article <1990Mar26.174313.1976@eng.umd.edu> dank@eng.umd.edu (Daniel R. Kuespert) writes:
| For fast code and really good optimization, MSC is the way to go.
| Unless you're doing really loop-intensive types of code, though, it 
| may not be worth coping with all the command-line switches and 
| byzantine error messages MSC spews out, though.

As far as speed of the resultant program is concerned, MSC 6.0 has Watcom on
the run.  It's impressive.  However, there is one other plus for MSC.  Since
ver 5.0, the compiler has generated re-entrant code (i.e. code that will
run in protected mode).  Being able to port code from MS-DOS to OS/2 or
WinNext with a minimum of hassle seems, to me at least, to be a _big_ plus.

Don't get me wrong.  I'm a TC user, and I like Borland's product very much.
However, I'm rapidly reaching the point where I wish I had chosen MSC
instead.  Hell, Borland won't even support Windows.  It get's a little
irksome when a company with a fine product refuses to support a particular
environment for political reasons.

--
Rick (schaut@garfield.cs.wisc.edu)

"Your degree in Economics is not necessarily an aide to finding gainfull
emplyoment, but at least it helps you understand why you're unemployed"