Burke Libbey, Software Developer at ShopifyThere are some interesting corrections in the thread on reddit: http://www.reddit.com/r/ruby/comments/e0g1s/a_look_into_rubys_object_model/c14d0xq2 years ago
Are you sure you want to
Burke Libbey, Software Developer at Shopify@Alexandr It made more sense when I was explaining this in person, but I was trying to contrast two different methods that ruby _could_ have used to implement modules. I sort of explained some of the consequences of copying a module at include time, and why that's a bad idea. Slide 44 explains the other possible method, and the way ruby actually does it.2 years ago
module M;def m()puts '1';end;end;
class C;include M;end;
module M;def m()puts '2';end;end;
puts C.new.m 2 years ago
p43 '... saves a snapshot of the module at time of include'
1 module M
2 def m
3 puts '1'
4 end
5 end
6
7 class C
8 include M
9 end
10
11
12 module M
13 def m
14 puts '2'
15 end
16 end
17
18
19 C.new.m
=> 2 2 years ago