Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!mcdchg!chinet!patrickd
From: patrickd@chinet.chi.il.us (Patrick Deupree)
Newsgroups: comp.lang.c++
Subject: Re: Turbo c++
Message-ID: <1990Aug23.145812.12760@chinet.chi.il.us>
Date: 23 Aug 90 14:58:12 GMT
References: <3836@nisca.ircc.ohio-state.edu>
Organization: The Whitewater Group, Evanston, IL
Lines: 32

In article <3836@nisca.ircc.ohio-state.edu> omathuna@hpuxa.ircc.ohio-state.edu (Eoin OMathuna) writes:
>Hi,
>
>At the moment I program in Turbo C v2.0 and a friend of mine
>suggested that I change over to C++, in particular Turbo C++
>
>Could someone tell me the main difference between C and C++ and
>if Turbo C++ is a good version, and is it worth getting the professional
>edition?

I've just started using Turbo C++ after having used Turbo C 1.0 a while back
at a previous job.  I'd recommend getting it for the simple reason that you'll
be able to use/learn C++ (which is likely to become the new way to program
in C).  However, you can still use normal straight C code if you like, so you
won't be stuck doing everything in C++.  The only complaint I've had about
C++ from Borland is the "class hierarchy" they provide.  Basically, they
include sample class files that compose a class hierarchy dealing with
Arrays, Collections, Strings and other "collection" oriented objects.

It seems these were provided as just samples which explains the fact that
theres very little documentation on the classes themselves and no documentation
on how to make constructive use of them.  However, after doing a tiptoe
through the CPP and .H files it becomes obvious what is expected (oh, also
after a couple of errors from the pre-processor saying I hadn't defined
a few routines for my descendants.)

I've been having fun with the language, though.
-- 
"Organized fandom is composed of a bunch of nitpickers with a thing for
 trivial pursuit."  -Harlan Ellison

Patrick Deupree ->	patrickd@chinet.chi.il.us