Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!ginosko!usc!ucsd!ogccse!blake!uw-beaver!fluke!mce
From: mce@tc.fluke.COM (Brian McElhinney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: ThinkSpeed C++--------
Message-ID: <11104@fluke.COM>
Date: 14 Sep 89 20:20:30 GMT
References: <336@castle.ed.ac.uk> <13519@well.UUCP> <6494@columbia.edu> <1478@bnlux0.bnl.gov> <3949@ncsuvx.ncsu.edu> <60557@tut.cis.ohio-state.edu>
Sender: news@tc.fluke.COM
Organization: Guild of the Software Defenestrators
Lines: 19

In article <60557@tut.cis.ohio-state.edu> wilson m liaw <macgyver@cis.ohio-state.edu> writes:
>
>	What difference does it make if the class library is written in C++
>or not? I know the licensing fee is dumb [IMHO]. But as long as you can use
>the library from c++, it doesn't matter what lang. the library is in.

Because you can't write a non-trivial application unless you spend a *large*
amount of time studying the MacApp source code.  It is certainly possible to
switch back in forth between languages, but at the intimate level of
inheritance it is not much fun.

Prepackaged class libraries are great, but you can rarely ignore what you are
inheriting from.  If you don't need to inherit from a class *then* you can
ignore the implementation.  Inheriting is much different from simply using a
class (such as a matrix class).
 
 
Brian McElhinney
mce@tc.fluke.com