Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!brutus.cs.uiuc.edu!rpi!leah!bingvaxu!bingsuni.cc.binghamton.edu!consp21
From: consp21@bingsuni.cc.binghamton.edu (Ken Hoover)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Best C Compiler
Keywords: MIX Power C is plenty good
Message-ID: <3204@bingvaxu.cc.binghamton.edu>
Date: 24 Mar 90 18:07:10 GMT
References: <705.UUL1.3#5129@willett.UUCP> <3207@uudell.dell.com>
Sender: usenet@bingvaxu.cc.binghamton.edu
Reply-To: consp21@bingsuni.cc.binghamton.edu (Ken Hoover)
Organization: SUNY Binghamton
Lines: 64


In article <705.UUL1.3#5129@willett.UUCP>, dwp@willett.UUCP (Doug
Philips) writes:
[ in reference to MIX Power C ]
> I have version 1.3.0 (No idea what current version is).  It only supports
> the medium memory model.  I have no feel for the speed of the compiler,
> I don't have MSC or Turbo or anything else to compare it to.
> [...]  It doesn't have an integrated
> environment, at least not the version they had out when I bought it, but
> I (personally) hate such things anyway.  I haven't been using it much
> since I'm not doing much PC programming anymore.  Its a *great* value.
> Especially since you can get library source.

  I talked with several people in the Computer Center here while looking
for a good C compiler, and they all recommended Power C to me on the
basis of its documentation alone (I'm still learning C).  To them, the
fact that you get a pretty decent C compiler was secondary, because for
$19.95 the manual by itself was worth the money.  I took the plunge and
bought the whole package -- compiler, debugger, and lib source -- for
$50.  For Turbo C professional, $150 + $150 (?) for lib source.  Four
360k disks and two well-written manuals. 

  The compiler is pretty good, although this version (1.3.0) only
supports medium memory models; and is plenty fast for me (speed is not
really important to me; but the stuff included with the compiler showed
it as being faster than Turbo C and Quick C while generating smaller
.EXE files).  The debugger (v1.2.0) is also nice, but I quickly
discovered a way to make it go kablooie (crash messily) on something
that it ought to prevent me from doing.

  Also included with the library source was an assembler, PCA.EXE, which
the README files say little about, other than it's for compiling the
.ASM with the library source code.  I haven't tried to use it, but
perhaps it will be developed further in the future?

  I also think that integrated environments are for the birds.  If I
need a debugger, I'll use a separate one (like the one in power C)
rather than have it get in my way while I'm just generating code. 
Besides, I haven't found an integrated environment editor that would
make me give up standalone ones I prefer to use.

  For me, Power C is perfect.  If I find that it ever can't do what I
need it to do, I may switch; but if they keep me notified of upgrades
and keep building on their excellent start, I'll stick with them and
keep chuckling at those people who shelled out a lot more to get the
same results.

> 
> I'm not affliated with MIX except as a very happy customer.
> 
> 		-Doug

  Me too.

						- Ken

PS:  Is there any way to get in contact with MIX over the net via email
or other means?

------------------------------------------------------------------------------
Ken Hoover [ consp21@bingsuns.pod.binghamton.edu | consp21@bingvaxa.BITNET ]
            Resident computer jock, SUNY-Binghamton Bio dept.
     Senior undergraduate consultant, SUNY-Binghamton Computer Center
------------------------------------------------------------------------------