Xref: utzoo comp.lang.c:5553 comp.sys.ibm.pc:9518
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!jade!ig!uwmcsd1!leah!itsgw!batcomputer!cornell!uw-beaver!tektronix!tekgen!sytek
From: sytek@tekgen.TEK.COM (Mike Ewan)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: Re: Microsoft C's
Message-ID: <2146@tekgen.TEK.COM>
Date: 10 Dec 87 23:49:16 GMT
References: <4640@eecae.UUCP>
Sender: news@tekgen.TEK.COM
Reply-To: sytek@tekgen.UUCP (Mike Ewan)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 20

In article <4640@eecae.UUCP> lawitzke@eecae.ee.msu.edu (John Lawitzke) writes:
>Could someone either post or e-mail a description of the differences
>between MSC v5.0 and Microsoft Quick C? I'm familiar with MSC v5 so
>I'm mainly interested in what MSC has that Quick C doesn't. I'm 
>assuming there are differences considering I've seen Quick C for $75.
>

As far as I can tell from the QuickC manual; MSC 5.0 is an "Optimizing"
compiler.  The manual states that MSC and QuickC use the same library,
they both have the same memory models, they both use CodeView etc.  So
in my opinion, unless you're doing some major project, QuickC will do
just fine.

I haven't done an exhaustive evaluation so go easy on the flames folks.

Mike Ewan
Tektronix Inc.
sytek@tekgen.TEK.COM
...!tektronix!tekgen!sytek
(503)627-6468