Multiple inheritance method resolution

[gvidon]

Multiple inheritance method resolution

[nicolas-van]

This behavior is normal. You shouldn't try to call $super in A nor B, has they don't have any super class with the same method.

In cases where you have a class C inheriting from 2 classes and both those classes have the same methods that were never thought to be inherited from (which is the case here), one solution is to manually decide what to do. Example:

var C = ring.create([A, B], {
    testMe: function() {
        A.prototype.testMe.call(this);
        B.prototype.testMe.call(this);
    },
});

This kind of dilemma would be solved this same way if you were in Python (ring.js is inspired by Python's multiple inheritance system). You can basically apply any solution that would apply to Python, like those found on this stackoverflow thread:

http://stackoverflow.com/questions/3810410/python-multiple-inheritance-from-different-paths-with-same-method-name

Hope that helped.

[gvidon]

How about such a situation in python?

http://stackoverflow.com/a/3810720/2516177

https://www.dropbox.com/s/2nckbbdv7cz1web/%D0%A1%D0%BA%D1%80%D0%B8%D0%BD%D1%88%D0%BE%D1%82%202014-11-30%2023.59.02.png

Does ring.js MRO fully copy what is implemented in python?

[nicolas-van]

Yep, that solution would work exactly the same in ring.js

[gvidon]

Ok, thank you!