Hi!

Thus spake Robert Dober on 04/22/2007 11:17 AM:
> Sorry but this is not true, we get a method object bound to the
> instance which can be called without any problem. Look at this code,
> just to convince you

You are right in that the method object is bound to _an_ instance.
The question is: instance of what?

Your code differs from the OPs example in that your method is
defined inside the same class. If you grab this with method(), you
of course get a method object in the context of the instance that
defined it. Reflection would be no good if this was not the case.

If, however, the method is defined in another module and included,
the call to this method and all methods it calls itself are
dispatched at runtime.

In the OPs example, method() gets you the boo() method out of the
module and it shares the context of that module only, not the
instance including the module.

> The behavior seems wrong to me too

Heh... this, of course, is a totally different question...
I might agree with you that a consistent behavior between native
method calls and reflected method calls would be better, but that
does not mean that the current behavior is a bug. As far as I
understand it, it's intended.

Regards,

	Phil