[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CLOS, and slot hiding.
- To: mike%acorn@LIVE-OAK.LCS.MIT.EDU
- Subject: Re: CLOS, and slot hiding.
- From: Danny Bobrow <Bobrow.pa@Xerox.COM>
- Date: 6 Apr 88 10:40 PDT
- Cc: kempf@Sun.COM, firstname.lastname@example.org, sidney@LIVE-OAK.LCS.MIT.EDU, email@example.com
- In-reply-to: mike%acorn@LIVE-OAK.LCS.MIT.EDU (firstname.lastname@example.org any day now)'s message of Tue, 5 Apr 88 15:05 est
- Sender: Bobrow.pa@Xerox.COM
I agree with the comments made by Moon about the design goals of CLOS. Alan
Snyder made a big pitch for having encapsulation be an important goal for the
Common Lisp community, and it was rejected. One reason is that it was hard (as
Moon mentioned) and another is because it does not fit into the philosophy of
Lisp, which has always prided itself on being an open system (this is the point
that Jim made so well).
The metaobject protocol (Chapter 3) is designed to allow people to experiment
with additions and variations on the language. Jim Kempf put Common Objects on
top of CLOS using the MOP, and Common Objects has some of the properties you are
talking about (if I understand you properly). Do you have a real example in