Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!ksand
From: ksand@Apple.COM (Kent Sandvik, 120dB or more)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacApp & C++ destructors
Message-ID: <13148@goofy.Apple.COM>
Date: 23 Apr 91 18:58:12 GMT
References: <671846404.0@mmug.mn.org>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 20

In article <671846404.0@mmug.mn.org> Jim.Spencer@p510.f22.n282.z1.mn.org (Jim Spencer) writes:

>As I understand it (and there will certainly be hell to pay if this is not true), the rewrite of MacApp in C++ will NOT use any features of C++ that Object Pascal doesn't have, e.g. constructors and destructors.  To do so would be to abandon all of the Object Pascal users who have hung in with MacApp through thick and thin over the last 5 years or so.

That's right, no constructor/destructors with parameter passing, no
function defaults, no const methods, no MI, no inline, in general everything
that the class library exports should work from both OP and C++ with
MacApp 3.0. The OP header files will reflect the possibilities, and 
any possible C++ semantic notion which is not supported by OP is not 
present in either header file. Note that the internals of the class
could be implemented with C++ semantics. The internals should not be
used by the programmer anyway...

Also MacApp 3.0 will have some additional C++ features, like Point/Rect
classes with operator overload, which only works from C++, but these
are additions, not elementary pieces for MacApp.

Kent 
-- 
Kent Sandvik, DTS junkie