Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!kksys!edgar!mmug!p510.f22.n282.z1.mmug.edgar.mn.org!jspencer
From: jspencer@p510.f22.n282.z1.mmug.edgar.mn.org (Jim Spencer)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think C 4.0 evolving to C++
Message-ID: <0.27C5B492@mmug.edgar.mn.org>
Date: 21 Feb 91 22:39:44 GMT
Sender: ufgate@mmug.edgar.mn.org (newsout1.26)
Organization: FidoNet node 1:282/22.510 - SmorgasBoard, Twin Cities
Lines: 19


Perry The Cynic writes in a message to All

PTC> To the first question: Yes, THINK C 4.0 is designed to look like 
PTC> a C++ subset, so that THINK C code should go through a C++ compiler 
PTC> without major modifications. Perhaps that protects your investment 
PTC> into Object C code. Of course, in my not so humble opinion, writing 
PTC> true C++ code requires a different design concept. 

Its also a little misleading.  Because Think C doesn't use the virtual keyword, if you don't go through your code and put them in, in C++ they will be treated as non-virtual functions.
 

--  

                   Jim Spencer (jspencer@mmug.edgar.mn.org)
               UUCP: ...jhereg!tcnet!vware!edgar!mmug!jspencer
                             FidoNet: 1:282/22.510

--