Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!rutgers!cunixf.cc.columbia.edu!cs.columbia.edu!kearns
From: kearns@cs.columbia.edu (Steve Kearns)
Newsgroups: comp.lang.c++
Subject: Turbo C++ Bummmer
Message-ID: <1990Jul24.212832.23427@cs.columbia.edu>
Date: 24 Jul 90 21:28:32 GMT
References: <9007230453.AA12697@ucbvax.Berkeley.EDU>
Reply-To: kearns@cs.columbia.edu (Steve Kearns)
Followup-To: comp.lang.c++
Distribution: na
Organization: Columbia University Department of Computer Science
Lines: 20

Turbo C++ is very solid, fast enough, and has lots of whiz bang
features... but I discovered a serious problem recently.  

I have a number of C++ files which will not compile because of
insufficient space.  Even though I have 640K + 4 Meg of extended
memory.  

Turbo swaps out its CODE to extended memory or disk, but none of its
data.  Coupled to the fact that Turbo insists on in-memory compilation
for speed, the result is a limitation on the size of files that can be
compiled.  I find this rather inexcusable for a robust programming
tool.  How hard can it be to for them to recompile their program using
Rational Dos Extender, or write out part of the compilation to disk
when neccessary?  Zortech C++ makes full use of extended memory, as
does Glockenspiel C++.  But turbo has the best environment, debugger,
and most robust implementation of the three.

Life can be hard....

-steve