Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!mtune!codas!killer!fmayhar
From: fmayhar@killer.UUCP (Frank Mayhar)
Newsgroups: comp.sys.ibm.pc
Subject: Re: QuickC
Message-ID: <1485@killer.UUCP>
Date: Sat, 5-Sep-87 19:28:08 EDT
Article-I.D.: killer.1485
Posted: Sat Sep  5 19:28:08 1987
Date-Received: Sun, 6-Sep-87 09:42:50 EDT
References: <4491@vrdxhq.UUCP>
Organization: The Unix(tm) Connection, Dallas, Texas
Lines: 25
Keywords: QuickC MSC
Summary: Quick C vs MSC v5.0

In article <4491@vrdxhq.UUCP>, williams@vrdxhq.UUCP (Tim Williams) writes:
> I saw an add in this weeks PC Mag. for QuickC from Microsoft.  It gives
> a list of things it has and TurboC doesn't.  My question is what does
> MSC 5.0 have that QuickC doesn't?
> Tim Williams <:-0

Not having the Microsoft product description right here (it's at work), I
can't provide too many details, but the difference is bascially that Quick C
is meant to be a small-scale programming environment like Turbo C (albeit
with extensions).  MSC 5.0, on the other hand, is a real, production-quality
optimizing C compiler with a very good standard library.  Quick C is meant for
quick program development and debugging.  MSC is meant for large programs, and
for production programs.

Incidentally, MSC 5.0 has some neat improvements over MSC 4.0, including a set
of graphics routines in the standard library, and in-line code generation for
certain commonly-used standard library functions (eliminates the procedure call
overhead).  It also has a little better optimization, and a few other bells and
whistles that I can't remember right off-hand.

-- 
Frank Mayhar        UUCP: ..!{ihnp4,dj3b1}!killer!fmayhar
                    ARPA: Frank-Mayhar%ladc@BCO-MULTICS.ARPA
                    USmail: 680 Grand Ave #201 Long Beach, CA 90814
                    DeathStarNet: (213) 438-7899