Path: utzoo!attcan!uunet!lll-winken!sol.ctr.columbia.edu!emory!hubcap!grimlok
From: grimlok@hubcap.clemson.edu (Mike Percy)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: TC++ bug
Message-ID: <9764@hubcap.clemson.edu>
Date: 19 Jul 90 21:11:37 GMT
References: <9747@discus.technion.ac.il>
Organization: Clemson University, Clemson, SC
Lines: 32

aviv@discus.technion.ac.il (Aviv Siegel) writes:
>   Well, first of all, the package is HUGE. If you want to work without
> a VERY fast disk, or vast amount of EMS (more than 1M) and a fast machine
> (at least 10MHz 286) - you'll have to wait ...
 
I disagree.  I am running on a very slow disk (20M), 8MHz 286 XT, and
only have the standard 640K.  While it's not the fastest thing in the
world, I think it's still as fast as TC2.0 (talking about command line
setup here, haven't done too much with the IDE, since the old IDE made
me throw up).  
 
I use some of the options which more than buy back any lost time due to
having to load a bigger tcc.exe  (458560 vs. 179917,  but TC++ _must_
use VROOMM, otherwise I don't think I could compile anything! To hazzard
a guess the .cpp and .c compilers overlay each other.)
For instance, I use the make -S option, which swaps make out allowing
more free space for compiling, which makes compiling faster.  I also use
the command batching facility of make -- this alone shaves 15sec from my
typical full re-make (loading and unload the compiler takes a lot of
time, load it once to compile a handful of programs instead of load,
compile, unload, load, compile, unload...).
The improved assembly listings are a boon.  Autodependency checking
looks useful too, but I haven't had time to mess with it yet.
I look forward to using the VROOMM overlay technology, as I have some
stuff that is pushing the limit as it is.
The documentation seems to be much cleaner and useful, even though I
have found some misprints (check out the v..printf functions).
 
All this and a [supposedly] ANSI conformant compiler with C++ to boot!
 
It's not perfect, as is made clear by a number of posts.  But for a 1.0
release, I'll take it.