Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!zephyr.ens.tek.com!tekcrl!tekgvs!toma
From: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: TC++ 1.0 Trouble
Message-ID: <7740@tekgvs.LABS.TEK.COM>
Date: 29 Jun 90 19:53:45 GMT
References: <1990Jun27.205532.21508@ecn.purdue.edu> <5869@videovax.tv.tek.com>
Reply-To: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Distribution: usa
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 16


Here's a "good one." Borland defines a constant __TURBOC__ that is a hex
constant representing the version number. Unfortunately, TC++ gives the 
value 0x100, just line version 1.0 of Turbo C! There is no __TURBOCPP__
constant which means programs that are compiler dependent (such as to get
around bugs) can't differentiate between Turbo C 1.0 and Turbo C++ 1.0. :-(

On a more positive note, TC++ compiled and ran with no difficulty the programs
that I could never get running under two v1.xx versions of Zortech C++. 
I don't believe I'll spend the $250 to get the new Zortech package.
(If somebody has compared TC++ 1.0 and Zortech C++ 2.x, and feels that
the Zortech compiler has merit, let me know!)

Tom Almy
toma@tekgvs.labs.tek.com
Standard Disclaimers Apply