Article View: comp.sys.ibm.pc.programmer
Article #1221Re: Help choosing C Compiler for specific use
From: James Birdsall
Date: Fri, 24 May 1991 20:46
Date: Fri, 24 May 1991 20:46
46 lines
2953 bytes
2953 bytes
In article <1991May23.204633.1711@cbnewsd.att.com> knudsen@cbnewsd.att.com (michael.j.knudsen) writes:
>Turbo C -- outdated, hard to find anymore, command-line only
Obsolete, yes. But just for completeness, it wasn't command-line only.
It's had an integrated environment since at least version 1.5; I still use
the integrated environment from 2.0 as my programming editor because the
TC++ integrated environments are 1) slow on my machine and 2) annoying.
>Turbo C++ -- C++, window interface, still keyboard only, no mouse routines
This is correct. As I recall, the integrated environment does support a
mouse, but there are no library mouse routines.
>Turbo C++ Professional -- does Windows, mouse support, great debugger
No. Turbo C++ Pro does NOT do Windows. The "Professional" versions were
the same as the plain version, with the following additions: Turbo
Debugger, Turbo Assembler, Turbo Profiler.
>Borland C++ 2.0 -- even more and better (?) see below.
THIS is the version that does Windows. It comes with Turbo Debugger,
Turbo Assembler, and Turbo Profiler; indeed, it is not available without
them.
>From the last posting (not quoted), I get the idea that the last
>two items are really the same, ie, "Professional" implies "not Turbo"
>so it's just called "Borland." Is that right? Better to look
>stupid here than in the store (?)
There is no longer any such thing as a "Professional" package. Borland
has segmented the market into two parts. They are now selling a Turbo C++,
Second Edition, which is supposed to be a somewhat-enhanced TC++ 1.0, and
does not come with debugger, assembler, et al., which are presumably still
available as a separate package. And they are selling Borland C++ 2.0,
which is their high-end compiler, etc., as described above.
Note that the debugger referenced above is the standalone debugger.
There is a debugger build into the integrated environment, which is pretty
good but not nearly as good as the standalone Turbo Debugger.
--
James W. Birdsall WORK: jwbirdsa@amc.com {uunet,uw-coco}!amc-gw!jwbirdsa
HOME: {uunet,uw-coco}!amc-gw!picarefy!jwbirdsa OTHER: 71261.1731@compuserve.com
================== Kitten: a small homicidal muffin on legs. ==================
=========== "For it is the doom of men that they forget." -- Merlin ===========
Technical Details
Message-ID:
<1991May24.204628.19166@amc.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!milton!sumax!amc-gw!jwbirdsaReferences:
<1991May22.225803.23546@cbnewsd.att.com> <1991May23.131006.4934@news.larc.nasa.gov> <1991May23.204633.1711@cbnewsd.att.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!milton!sumax!amc-gw!jwbirdsa From: jwbirdsa@amc.com (James Birdsall) Newsgroups: comp.sys.ibm.pc.programmer Subject: Re: Help choosing C Compiler for specific use Keywords: C Message-ID: <1991May24.204628.19166@amc.com> Date: 24 May 91 20:46:28 GMT References: <1991May22.225803.23546@cbnewsd.att.com> <1991May23.131006.4934@news.larc.nasa.gov> <1991May23.204633.1711@cbnewsd.att.com> Reply-To: jwbirdsa@europa.amc.com (James Birdsall) Organization: Applied Microsystems, Redmond, WA Lines: 46