Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!csus.edu!ucdavis!iris!lim
From: lim@iris.ucdavis.edu (Lloyd Lim)
Newsgroups: comp.sys.mac.programmer
Subject: Re: OOP--What do you think?
Message-ID: <8836@ucdavis.ucdavis.edu>
Date: 23 Apr 91 07:58:38 GMT
References: <1991Apr10.210516.25812@rice.edu> <51593@apple.Apple.COM> <17229@hoptoad.uucp>
Sender: usenet@ucdavis.ucdavis.edu
Reply-To: lim@iris.ucdavis.edu (Lloyd Lim)
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science
Lines: 27

In article <17229@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>[...]
>Then there are maintenance issues.  When you wind up straightjacketed,
>there are two things you can do to escape.  One is to change the source.
>This presents major problems when there's a new release.  The other is to
>copy and edit large methods and make the edited versions your overrides.
>This presents exactly the same problem with new releases -- the edited
>copy has to be brought into line with the new version.  [...]

I agree.  I ran into similar problems when trying to change some things
with TCL.  OOP is supposed to be easy to maintain but you often end up
having to know too much about the internals of classes.

>[...]  A while ago, Keith said that no one who had
>used MacApp would ever go back to another way of programming.  [...]

Well, the CAD program Dreams from IDD started out as a MacApp program but
ended up as a straight THINK C program.  The code still looks more OO than
normal though.  I believe they gave up on MacApp because of speed problems
(which I think were design problems mainly) and because they ended up
overriding tons of methods anyway (it has floating palettes and other stuff).

+++
Lloyd Lim     Internet: lim@iris.eecs.ucdavis.edu
              America Online: LimUnltd
              Compuserve: 72647,660
              US Mail: 215 Lysle Leach Hall, U.C. Davis, Davis, CA 95616