Adam Shelly wrote:
> On 7/18/06, Trans <transfire / gmail.com> wrote:
> > On a side note I think I found a bug in Ruby, maybe
> >
> >   class << X
> >     undef_method :method_added
> >   end
> >
> >   class X
> >     def y; end
> >   end
> >   => NoMethodError: undefined method `method_added' for X:Class
> >
> >
> You get the same error even if you don't override method_added first.
> It looks like the call to method_added is hard-coded in
> rb_add_method() in eval.c.. (also in rb_alias())
>
> It seems like a bug to me - the c code should check that callback
> methods still exist before calling them.

I see. Okay, at least that makes sense. I agree though, I seem more
logical that it would check for the method, rather then hard coding an
empty one into core. But maybe it's more efficient that way?

Thanks,
T.