[ruby-core:18300] Re: Heisencallback?

On Aug 14, 10:03=A0am, Calamitas <[e-mail]> wrote:
>
> While we're at it:
>
> =A0 class Class
> =A0 =A0 def method_added(m)
> =A0 =A0 =A0 =A0puts m
> =A0 =A0 end
> =A0 end
>
> This came up when looking for a full-proof way of catching all method
> definitions. There is one however that can never be caught, and that's
> the one above. To that end, it would help a lot if the *old* callback
> were called instead of the new one.

Not quite the same issue, but closely related... Personally, I would
like to see the particular callback completely deactivated while
executing. It seems to me that recursing on

  def method_added(m)
    define_method("#{m}2"){  }
  end

is not only annoying, but almost certainly unnecessary, since by
defining a method within method_added, I already know it's happening.

T.