From: MaggotChild <hsomob1999@...>
Date: 2009-09-17T17:05:09+09:00
Subject: Re: Monkey Patching 2 Methods, Overrides One Method, Not The

On Sep 16, 10:51 pm, 7stud -- <bbxx789_0...@yahoo.com> wrote:
> MaggotChild wrote:
> > #test program
>
> > ToBePatched::Foo.class_eval do
> >   include MyModule::Main
> > end
>
> > class Bs < ToBePatched::Foo
> >   i_want_that_great_feature
> > end
>
> > bs = Bs.new
> > bs.bar
> > bs.some_method
> > bs.another_method
>
> $ ruby r1test.rb
> r1test.rb:1: uninitialized constant ToBePatched (NameError)

Not sure what's in r1test.rb, my above code does indeed run.
Regardless, that example is just a simplified version of the monkey
patching paradigm that's causing problems.

What I'm interested in is why would one overridden method in a module
run while another would fall back to the original as if it were never
overridden?