Path: utzoo!utgpu!news-server.csri.toronto.edu!csri.toronto.edu!wayne
Newsgroups: comp.sys.laptops
From: wayne@csri.toronto.edu (Wayne Hayes)
Subject: Re: C Compiler Advice Sought
Message-ID: <1990Dec4.080836.16050@jarvis.csri.toronto.edu>
Organization: CSRI, University of Toronto
References: <1990Dec4.031234.15371@eng.umd.edu>
Date: 4 Dec 90 13:08:36 GMT
Lines: 21

I don't know about Quick C, but you can fit everything needed for at least
one model (small, medium, compact, large, etc) on a 1.44M floppy, and still
have about 300K left over to write code in.  Of course if you can, you should
put as much as possible on the RAM disk.

Both TurboC 2.0 and Quick C's latest version support full ANSI, both are
about the same price (with $10), both support tremendous on-line help, and
both are very fast at compiling.  I have TurboC and have had absolutely no
problems with it -- literally zero.  I've written lots of code and found
no bugs.  However, one thing I hear about Quick C that I envy is "incremental
compilation".  If you have a huge C file, and only change one function, you
can set up Quick C to recognize this and only recompile that function, rather
than recompile the entire file, as TurboC does.  Nevertheless, TurboC is so
fast that you usually don't have to worry about this except for very large
files.

-- 
"Dad, what should I be when I grow up?"
"Honest." -- Robert M. Pirsig, _Zen and the Art of Motorcycle Maintenence_.

Wayne Hayes	INTERNET: wayne@csri.utoronto.ca	CompuServe: 72401,3525