#218: including a module which defines functions can mask functions of the same name in the including class -------------------------------+-------------------------------------------- Reporter: celtic@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: -------------------------------+-------------------------------------------- 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. -- Ticket URL: <http://www.macruby.org/trac/ticket/218> MacRuby <http://macruby.org/>