From: "T. Onoma" <transami@...>
Date: 2003-11-27T17:50:02+09:00
Subject: Re: Method wrapping

On Thursday 27 November 2003 08:57 am, T. Onoma wrote:
> > If you are redefining someone else's method in production, on your own
> > head be it.  You should be keeping to the same interface of the
> > original, or else other code is likely to break.
>
> Exactly, and to do this requires understanding the interface. And more
> times than not, if you are REDEFINING a method in this manner, your doing
> it in totality. Juggling the hooks from before is not condusive. You'll end
> up remove_method'ing them all anyway.

I forgot to add that if you are not redefining, then your adding an additional 
wrap, as you do with subclasses. Access to a particular indexed wrap just 
won't be useful except for "mucking around", as Gavin put it. So if there's 
some tucked away method for doing it, that's fine. But it shouldn't be a 
"common spec" or part of the def syntax in anyway.

-t0