Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Ruby
The Case for Multiple-Inheritance
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Trans, post: 4578948"] Bahahahahahahahahaha! You're right! But it's only painful b/c it's what you HAVE to do today to achieve this level of code reuse. If I had my way, it would as simple as: class X def self.foo # instead of needing M ... end class Y; end class Z is X is Y end And we'd still have complete code reuse. T. [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Ruby
The Case for Multiple-Inheritance
Top
