From: Old Echo Date: 2008-06-14T23:09:22+09:00 Subject: Re: Modules, Overloading, and some Confusion Hello all, Thank you for your responses. This is more of a philosophical rather than a practical question -- I'm not facing this situation in any application that I'm trying to write. Background: I used to work at a company that was an all-Java shop where I would occasionally debate the merits of Ruby vs. Java (dynamic vs. static, etc etc etc) with one of my co-workers who is a big Java guy. Somehow the topic of multiple inheritance came up, and one of the "shoot Ruby down" arguments was that because of this "last-one-in" wins behavior, Ruby couldn't really help solve the issues that come up when trying to do multiple inheritance. Of course, it was pointed out that Java doesn't really have a good way to do this either, but I left the conversation feeling like something was amiss with the argument. Now, I've wracked my brain for a real example of when you'd *actually* run into this kind of problem where two modules define the same method, and then when you mix both in to a class, problems come up. I can't really think of any - which leads me to believe that the problem set for these things is different in Ruby than in language where the type system is more strict. But again, these are really just philosophical ponderings more than anything else. Good discussion, though! I'd love to hear more from anyone who has thoughts on this. Thanks, kodama -- Posted via http://www.ruby-forum.com/.