dblack / wobblini.net wrote:
> Hi --
> 
> On Sun, 21 Jan 2007, Wolfgang Ndasi-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 method.  For example "methobj = x.method(:inspect)". You call it
>> later by "methobj[]" or "methobj.call". So it makes sense to ask "What
>> ist the object the Method object ist bound to", "What is the method
>> the Method object is 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.

  What about 'target', then ? It shows that it is not necessary the
receiver, but that it has been considered as a potential one.

	Vince

-- 
Vincent Fourmond, PhD student
http://vincent.fourmond.neuf.fr/