Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!mentor.cc.purdue.edu!pur-ee!pur-phy!sho
From: sho@pur-phy (Sho Kuwamoto)
Newsgroups: comp.sys.mac.programmer
Subject: THINK C 4.0 (C++ questions)
Message-ID: <2394@pur-phy>
Date: 2 Aug 89 01:00:15 GMT
Reply-To: sho@newton.physics.purdue.edu.UUCP (Sho Kuwamoto)
Organization: Purdue Univ. Physics Dept., W. Lafayette, IN
Lines: 27

I don't think I've seen the answers to these yet...

1) I know 4.0 isn't (and wasn't supposed to be) a full implementation
of Cfront 2.0.  Is exact compatibility planned?  Or is this not so
high on the priority list?  (I'd like to see overloading and multiple
inheritance, for one...)

2) Why was a new class library made to handle Mac stuff?  On one hand,
I am excited at the prospect, because MacApp could stand a good
rewrite (have never used it, just seen it, so I could be wrong).  In
either case, I'm sure improvements could be made.  However, MacApp
*does* seem to be a very stable product, with a lot of error checking,
and Apple seems committed to updating it as the System software
evolves.  There is some comfort in using such a de facto standard.
Are there any plans for MacApp support?  If (when, more like) I learn
to use this class library, I will be stuck with one compiler, and it
may be the case that there will be a greater lag time between the
introduction of new toolbox calls and new classes.  (not to be nasty.
Just a thought.)

3) I bought 3.0 the same month it came out, and *still* haven't turned
in the registration form.  Is this going to cause any problems?
Should I just send it in along with a check for $69?

-Sho
--
sho@risc.com  <<-- flies in his eyes.