Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!execu!sequoia!memqa!r91400
From: r91400@memqa.uucp (Michael C. Grant)
Newsgroups: comp.lang.c++
Subject: Re: Borland Turbo C++ compile size
Message-ID: <4971@memqa.uucp>
Date: 6 Aug 90 08:53:23 GMT
References: <7921@tekgvs.LABS.TEK.COM> <380@taumet.com>, 	<1990Aug4.233013.20500@cs.columbia.edu> <Uaitime00VB5E1pYAT@andrew.cmu.edu> <383@taumet.com>
Organization: Memory R&QA, Motorola SPD
Lines: 24

In article <383@taumet.com>, steve@taumet.com (Stephen Clamage) writes:
> The editing/compiling/linking processes could be more integrated, whereby
> a database is maintained to keep track of things.  As you edit a
> program, it could be incrementally compiled, incrementally linked, as
> you go.  This would dramatically improve productivity.

I personally use Think C, which you could call 'C+' because it is C
which has a C++-like class handling set.

On the Mac, an 'integrated' programming environment is essential,
and Think C provides it.  It performs incremental compilation, and
linking is amazingly fast--and, it provides SMART LINKING!

It would be awfully nice if Symantec would come out with an actual
C++ compiler using the same user interface--I KNOW it would sell.

But, for now, I can't use references, or overload operators, or hide
my private variables from view, but I can use classes and that is
a step in the right direction.

And, since I work for Motorola, I won't be using ANYTHING but
Macintoshes anyway. :-)

Michael C. Grant