From: Doug Jolley <lists@...>
Date: 2012-05-25T10:10:25+09:00
Subject: Re: Don't override it - Use it

> And it *is* actually called overriding:
> http://en.wikipedia.org/wiki/Method_overriding

I read the wikipedia link.  As a reader who knows nearly nothing, it 
would seem to me that the methodology that I described would not qualify 
as "overriding" according to the definition contained in the wikipedia 
post because the wikipedia post (like other posts I have read) says that 
in order to qualify as "overriding" the method in the child class has to 
*replace* the method in the super class.  In my example, I don't see the 
method in the child class *replacing* the method in the super class 
because the method in the child class actually uses the method in the 
super class.  I don't see how one can say that a method has been 
*replaced* if it is being used.  None-the-less, if that is the 
conventional wisdom, I'm happy to go along with it. I just need to 
adjust my understanding of what "overriding" means.

Thanks again for the input and for helping me understand what 
"overriding" means.

      ... doug

-- 
Posted via http://www.ruby-forum.com/.