  `method_missing` call stack in Ruby  November 23rd, 2010
Posted in Programming, Ruby  Just found out something cool from
reading “Don’t Know Metaprogramming In Ruby?” from RubyLearning
blog. Consider this code snippet:  class Person class Student <
Person class HighSchoolStudent < Student  If you’re calling some
method that’s undefined, let’s say we’re calling
HighSchoolStudent#name Ruby will try to call the method in this
order:    1. HighSchoolStudent#name   2. Student#name   3.
Person#name   4. Object#name   5. Kernel#name   6.
BasicObject#name   7. HighSchoolStudent#method_missing   8.
Student#method_missing   9. Person#method_missing   10.
Object#method_missing   11. Kernel#method_missing   12.
BasicObject#method_missing  From this example, you can see that
not explicitly define method and capture it in method_missing
might not be good in terms of the performance. So, what should
you do?  I think the best way to do it, if you know that this
method will get called again, would be define the ‘real’ metho