Newsgroups: comp.sys.ibm.pc
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!bronze!copper!rschmidt
From: rschmidt@copper.ucs.indiana.edu (roy schmidt)
Subject: Re: c++ compilers
Message-ID: <1991Jun4.161855.3984@bronze.ucs.indiana.edu>
Keywords: c++
Sender: news@bronze.ucs.indiana.edu (USENET News System)
Organization: Indiana University, Bloomington
References: <436@netxcom.netx.com> <1991Jun4.121248.7440@news.larc.nasa.gov>
Date: Tue, 4 Jun 91 16:18:55 GMT
Lines: 37

jcburt@ipsun.larc.nasa.gov (John Burton) writes:
>In article <436@netxcom.netx.com> pdressne@netxcom.netx.com (Peter Dressner) writes:
>> I am presently considering buying the Borland C++ compiler. I understand
>> that there are 3 versions: Professional, Turbo C++ and Borland C++.
>
>Now, for the current version (2.xx) there are also two packages, Turbo C++
>and Borland C++. Borland C++ takes the place of Turbo C++ Professional
>by including the assembler, debugger and profiler.
>
Actually, Borland C++ goes one step further:  it supports writing code
to run under MS Windows 3.0.  It includes a <windows.h> file, a resource
compiler, and the Whitewater Resource Toolkit for designing the user
interface.  The assembler, debugger, and profiler programs do *not*
support windows.  Of course, you can still do standard DOS as well.

You can still get the equivalent of a TC++ professional package for
standard DOS programming by purchasing the TC++ "second edition" and the
Turbo Debugger and Tools 2.0 package.

With their Turbo Pascal for Windows package, Borland has introduced a
Turbo Debugger for Windows (I know this is off-subject a little, but I
am anticipating a question, here).  This new debugger only handles
Pascal, and only Windows apps.  As far as that goes, TPW only produces
code for Windows apps.  You  have to use TP 6.0 if you want to write
standard DOS programs in Pascal.

This reflects a new tactic for Borland:  segmenting the market between
regular DOS and Windows.  For those wanting to do both, you wind up with
more than one compiler!  I guess you could argue for specialization,
better features, etc.  Have to wait and see how the laundry comes out.


--
--------------------------------------------------------------------------
Roy Schmidt                 |  #include <disclaimer.h>     
Indiana University          |  /* They are _my_ thoughts, and you can't
Graduate School of Business |     have them, so there!  */
