From: "Jan E." Date: 2012-05-25T13:08:01+09:00 Subject: Re: Don't override it - Use it Doug Jolley wrote in post #1062056: > 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. It doesn't matter if the overriding method is actually completely new or if it only "refines" the original one (i. e. still calls super). In fact, the term overriding is purely technical. It only means that you define a method which is already present in another class of the inheritance chain. The actual content is not relevant. It may even consist of only calling super (though this wouldn't make sense, of course). -- Posted via http://www.ruby-forum.com/.