From: Phrogz <gavin@...>
Date: 2006-12-28T03:05:10+09:00
Subject: Re: Using an UnboundMethod instead of an alias to redefine a method

Pit Capitain wrote:
> Sorry I didn't answer your original post. I waited until somebody else
> would answer it, and then I forgot it :-(
[snip[
> Module#method always creates a new Ruby object around the internal
> method implementation. Currently you have to cache your method objects
> in order to be able to retrieve them later.

Ah, thanks, that explains it all. (Must have missed the earlier
discussions about this.)