Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!ads.com!killer!usenet
From: anders@verity.com (Anders Wallgren)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacApp & C++ destructors
Message-ID: <1991Apr16.010101.26184@verity.com>
Date: 16 Apr 91 01:01:01 GMT
References: <9827@etsu.CMI.COM> <1991Apr13.235903.26110@ux1.cso.uiuc.edu> <1991Apr14.015647.3521@verity.com> <13080@goofy.Apple.COM>
Sender: usenet@verity.com (USENET News)
Reply-To: anders@verity.com (Anders Wallgren)
Organization: Verity, Inc., Mountain View, CA
Lines: 17
In-Reply-To: lsr@Apple.COM (Larry Rosenstein)

In article <13080@goofy.Apple.COM>, lsr@Apple (Larry Rosenstein) writes:
>In article <1991Apr14.015647.3521@verity.com> anders@verity.com (Anders Wallgren) writes:
>>
>>This is one of the penalties of using an Object Pascal library from
>>C++ - you also can't use multiple inheritance and I think overloading
>>is also a no-no.
>
>Strictly speaking, this isn't true.  Just because you are linking with
>MacApp doesn't mean you can't use the full power of C++ in classes that you
>write.  You can implement the internals of your app with "native" C++
>objects if you choose.
>

Correct - I didn't mean to imply that you couldn't use C++ to it's
fullest in non-{MacApp/TObject} related classes.

anders