From: "Peña, Botp" <botp@...>
Date: 2005-03-11T09:55:19+09:00
Subject: Re: Module#dup and Module.remove_method question

Renald Buter [mailto:buter@cwts.leidenuniv.nl] wrote:

//That's the issue: you can't restore the old method-resolving 
//behaviour in the duped object: say there is a parent of A 
//that implements 'foo' also, there is now no way of calling 
//that automatically in X, except through explicitly setting foo like:

                                          ^^^^^^^^^^
//
//   class <<X; def foo; A.foo; end; end
//

i like that. I don't want automatic behavior. It invites trouble unseen fr a
far far away child.

//Hell, of course I can live with this, but it stil feels like 
//some kind of trade-off :)
//

:-)

//Regards,
//
//Renald

kind regards -botp