From: Renald Buter <buter@...>
Date: 2005-03-10T17:22:41+09:00
Subject: Re: Module#dup and Module.remove_method question

On 23:06 Wed 09 Mar     , David A. Black wrote:
> Hi --
> 
> On Wed, 9 Mar 2005, Renald Buter wrote:
> 
> B.foo lives in A (the methods don't get dup'd when the class object is
> dup'd), and to remove it from B you can use undef_method.
> remove_method will only operate on the module where the method was
> defined, whereas undef_method will take it out of the search path of
> any module that could see it before.
> 

Thank you very much for you answer, but it's still not clear to me: I
*have* removed the method from A, yet B can still access it. How's that
possible? Is it now a dangling method of some kind?

Just curious...

Renald