Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!fwi.uva.nl!gene!caspers
From: caspers@fwi.uva.nl (B.M. Caspers (I))
Newsgroups: comp.lang.c++
Subject: Re: Turbo C++ for windows
Message-ID: <1991Feb27.113329.26360@fwi.uva.nl>
Date: 27 Feb 91 11:33:29 GMT
References: <2817@krafla.rhi.hi.is> <551@shograf.COM> <1991Feb26.152425.4148@isis.cs.du.edu>
Organization: FWI, University of Amsterdam
Lines: 24

I've been using a beta version 1.9 of BC++ for a while, so I have some 
experience with it. It indeed takes up about 14 Mb of harddisk space, caused
by many versions of the compiler and the debugger. Of the compiler, the
following versions are available: TC, TCX (protected mode), TCC, and TCCX.
The debugger consists also of many files: TD, TDREMOTE, TD286, TD386, and
TDW (for Windows). Some of these programs take up to 0.5 Mb of disk space.

I have developed some Windows applications with BC++, and it works well. The
resulting programs are (of course) real Windows applications, and with the
WRT (Whitewater Resource Toolkit), creating resources is made very easy. 

The only problem is the enormous memory-hunger of the compiler. To use protected
mode, you must have at least 576 Kb of e-memory (extended, real or simulated
expanded) available. I use a fast 386 with 8 Mb of RAM, and the compiler
will compile a simple Windows application in about 15 seconds. I've heard from
a friend with a 286 computer with 1 Mb of (total) memory that the same program
took him 7 minutes to compile. Using the command-line version TCC or TCCX is
even faster than compiling from within the IDE.

Those who don't develop Windows applications or very large projects, should
better use Turbo C++, but for serious C++ programming jobs Borland C++ is
a great compiler.

John