Yes, i wondering myself, what is the point to reference the methods in such style. The way, how actual class & its method get resolved makes it impossible to reference a method in arbitrary class object, especially one which is not installed into system dictionary.
Indeed. I have no idea.
I think its lacking additional form of indirection, which should be an environment object who is responsible for delivering the method's source code along with resolving the class by its name. Without such indirection, i see no point in having a MethodReference per se, because you can always do the same thing by yourself , i.e. (Smalltalk at: #SomeClass) methodDict at: #someSelector.
yes
Without that, i see no point why i would want to use it, because it always points to same thing, no matter where i using the MethodReference.
I imagine that we will have to clean that. It costs me a couple of hours looking for the wrong bug when copying classes..... grgrgrgrg Stef