home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!wupost!uwm.edu!ogicse!reed!chaffee
- From: chaffee@reed.edu (Alex Chaffee)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: Persistence in Think Class Library
- Message-ID: <1992Aug12.162409.4426@reed.edu>
- Date: 12 Aug 92 16:24:09 GMT
- References: <1992Aug9.170900.24145@reed.edu>
- Organization: Reed College, Portland, OR
- Lines: 38
-
- Thanks to everyone who responded. The overwhelming consensus seems to be, go
- ahead and modify the TCL, just be careful. Useful tips include writing a
- separate file and #including it in the TCL file, and/or heavily commenting
- the changes so they won't be overlooked when an upgrade comes along.
-
- Another suggestion (made by a co-worker) is this: make a new *superclass*
- for CObject.
-
- ## CMyObject.h :
-
- class CMyObject {
- Handle Wrap(void);
- void Unwrap(Handle h);
- }
-
- ## CObject.h :
-
- #include <CMyObject.h>
-
- class CObject : public CMyObject {
- ...
-
-
- It's a kludge, but so is mucking with CObject.c.
-
- So which kludge is cleaner?
-
- "In our experience, we find multiple inheritance to be like a
- parachute: you don't always need it, but when you do, you're really
- happy to have it on hand."
- - Grady Boch, "Object Oriented Design"
-
- - Alex
- --
- Alex Chaffee
- chaffee@reed.edu
- Reed College, Portland OR 97202
- ____________________
-