Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!trwind!gumby!wiley!scott
From: scott@wiley.uucp (Scott Simpson)
Newsgroups: comp.lang.clos
Subject: Re: Is CLOS Object-Oriented ???
Summary: CLOS question on dynamic binding and setf
Keywords: CLOS, dynamic binding, setf, Flavors
Message-ID: <27443D49.2BE8@wilbur.coyote.trw.com>
Date: 16 Nov 90 19:26:01 GMT
References: <1990Nov15.101847.26285@diku.dk> <3904@s3.ireq.hydro.qc.ca>
Sender: news@wilbur.coyote.trw.com (News Software)
Reply-To: scott@wiley.UUCP (Scott Simpson)
Distribution: comp
Organization: TRW Inc., Redondo Beach, CA
Lines: 19

In article <3904@s3.ireq.hydro.qc.ca> gamin@ireq-robot.hydro.qc.ca (Martin Boyer) writes:
>The way I see it, what "send" used to do in Flavors (finding which
>method to call and then calling it) is now done in CLOS by the generic
>function.
>
>Agreed, it *looks* like we are going back to the old way of doing
>things, when functions had to look at the arguments type to decide
>what to do with them.  Except that the programmer still writes
>methods; all this generic function stuff is done internally.

I thought they were the same too until someone at work came up with
this problem in Flavors:

	(setf (send self (send button :slot-to-change)) value)

What is happening is that (send button :slot-to-change) returns the
name of a slot to change and that slot is changed to VALUE on the
object SELF. How do you do this is CLOS?
Scott Simpson			TRW			scott@coyote.trw.com