From: Gregory Brown <gregory.t.brown@...>
Date: 2007-06-26T01:01:46+09:00
Subject: Re: alias and subclasses

On 6/25/07, Logan Capaldo <logancapaldo@gmail.com> wrote:

> Of course now you have the problem of if the sublass decides to override
> unhold instead of unreserve. The real solution to this problem IMO is to not
> start aliasing things in the first place. A given method should have one
> name. (I know Ruby does it with map/collect etc., but that doesn't mean I
> have to agree does it? :) )

Also, I always look at this as a feature and not a bug, as in:

alias_method :old_something, :something

def something
  #do some hackery
  old_something
end