From: dblack@...
Date: 2007-01-21T04:28:12+09:00
Subject: Re: Minor Change Proposal for Classes 'Object' and 'Method'

---2049402039-189632428-1169321290=:26229
Content-Type: MULTIPART/MIXED; BOUNDARY="-2049402039-189632428-1169321290=:26229"

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---2049402039-189632428-1169321290=:26229
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

Hi --

On Sun, 21 Jan 2007, Wolfgang N=E1dasi-Donner wrote:

> dblack@wobblini.net schrieb:
>
>> I'm not quite understanding the idea of meth.receiver, though.  How
>> does that fit in with the idea of the receiver being whatever object a
>> given message is sent to (which could, in most cases, be any of many
>> objects)?
>
> "Method#bind" creates an object which contains a fixed object an a fixed=
=20
> method.  For example "methobj =3D x.method(:inspect)". You call it later =
by=20
> "methobj[]" or "methobj.call". So it makes sense to ask "What ist the obj=
ect=20
> the Method object ist bound to", "What is the method the Method object is=
=20
> bound to", and "to which class does the bound method belong to".

Right, but I don't see that relationship as the same as what we
usually call "receiver", which is part of the dynamic process of an
object actually receiving a certain message.


David

--=20
Q. What is THE Ruby book for Rails developers?
A. RUBY FOR RAILS by David A. Black (http://www.manning.com/black)
    (See what readers are saying!  http://www.rubypal.com/r4rrevs.pdf)
Q. Where can I get Ruby/Rails on-site training, consulting, coaching?
A. Ruby Power and Light, LLC (http://www.rubypal.com)
---2049402039-189632428-1169321290=:26229--
---2049402039-189632428-1169321290=:26229--