Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!odi!dlw
From: dlw@odi.com (Dan Weinreb)
Newsgroups: comp.lang.lisp
Subject: Re: CLOS: is it OOP?
Message-ID: <1989Sep19.193636.10454@odi.com>
Date: 19 Sep 89 19:36:36 GMT
References: <19582@mimsy.UUCP> <29564@news.Think.COM> <11815@polya.Stanford.EDU> <29573@news.Think.COM> <1989Sep18.015805.9592@odi.com> <29625@news.Think.COM>
Reply-To: dlw@odi.com
Distribution: usa
Organization: Object Design, Inc.
Lines: 13
In-Reply-To: barmar@think.COM's message of 18 Sep 89 21:45:53 GMT

In article <29625@news.Think.COM> barmar@think.COM (Barry Margolin) writes:


   I just wrote the following code on my Lispm and it worked fine.  FOO
   and BAR are sibling flavors in FOOBAR, and FOO's methods can access
   BAR's instance variable A.

Well, of course it can; you explicitly requested it by saying
"(:required-instance-variables a)", which is like what C++ calls a
"friend" declaration.  Your house won't be very secure if you leave
the key out front with a huge day-glo "Here's The Key!!!" sign,
either.  Like any good encapsulation system, Flavors lets you
control the encapsulation selectively when you need to.