Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!dali.cs.montana.edu!milton!uw-beaver!zephyr.ens.tek.com!tektronix!reed!minar
From: minar@reed.bitnet (Nelson Minar,(???))
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: TC++ 1.0 Trouble
Message-ID: <15137@reed.UUCP>
Date: 30 Jun 90 00:29:57 GMT
References: <1990Jun27.205532.21508@ecn.purdue.edu> <5869@videovax.tv.tek.com> <7740@tekgvs.LABS.TEK.COM>
Sender: news@reed.UUCP
Reply-To: minar@reed.bitnet (Nelson Minar)
Distribution: usa
Organization: Reed College, Portland, OR
Lines: 14

In article <7740@tekgvs.LABS.TEK.COM> toma@tekgvs.LABS.TEK.COM (Tom Almy) writes:
>
>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. :-(
>

But there is a definition of __cplusplus, as per the C++ 2.0 standard. So
one CAN differentiate between Turbo C 1.0 and Turbo C++ 1.0.

does anyone know why my copy of Turbo C++ Professional was marked "not for
export"?