including a module which defines functions can mask functions of the same name in the including class

[celtic@…]

Simple explanation: classes A and B both define methods foo', as does module M. A includes M before defining its own foo', whereas B includes M afterwards.

Given that A and B both call super' in their foo', it turns out that only A's `foo' ends up calling M's, whereas B's does not.

Conclusion: including the module which defines the method after defining ones own causes it to be lost. I believe this is causes the problem first referred to in #215.

Attaching a test case which verifies this behaviour.

[celtic@…]

tests initialize and an arbitrary method, just to be sure

[celtic@…]

I've been trying to git bisect this with little success (I think it's my fault); in the meantime, I believe objc.m's rb_objc_register_ruby_method likely has the issue. Will look further.

[lsansonetti@…]

Sorry for the late response. Could you try this with trunk? I believe it might work.

[lsansonetti@…]

Closing.