Skip to content

Instantly share code, notes, and snippets.

Created February 1, 2012 00:44
  • Star 1 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
Star You must be signed in to star a gist
What would you like to do?

#include and #extend have same effect on instances as inheritance

Let's say we have this

module A; end
module B; end
class C; end
class D < C; end

Then we modify instance

d =
D.send(:include, A)
d_meta = class << d; self; end

Lets see what we got (method dispatch lookup table)

=> [D, A, C, Object, Kernel, BasicObject]

=> [B, D, A, C, Object, Kernel, BasicObject]

So it's all up to how and what structure you see

and to me, benefits of composition over inheritance is that it doesn't modify object dispatch hierarchy.

PS: pls comment here.

Copy link

gmarik commented Feb 8, 2012

Well, the statement was "it's a good hack, but bad practice".
Works fine on small scopes, but once grows it becomes harder to read thus understand the code, given this as a normal practice.
Debugging is hard because it's not quite obvious why it's doing one thing instead of another and that's only because at some point of call stack an object got extended with a module.

Don't get me wrong, it works. But at certain point it's like "magic" )

I don't do enough obscure programming

well, that's how you start! ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment