Yukihiro Matsumoto wrote:
> Hi,
>
> In message "Re: using a module at the toplevel doesn't work"
>     on Tue, 22 Aug 2006 14:05:06 +0900, "Trans" <transfire / gmail.com> writes:
>
> |As you can see my particlar 'test' example will cause an infinite loop
> |because the toplevel definition is being added to all objects. :(
>
> But they are private by default, so that 1.9 send will call
> method_missing if you specify the explicit receiver.

Ah, okay so fixing my toplevel #define_method to privatize the method
should do the trick, at least in my case, I see. Thanks. Of course,
just my luck, I also need 1.9's #send that doesn't invoke private
methods now! ;) How do I get around that in 1.8 again?

So #private saves the situation. Hmm... Still, the subtleties involved
here make me wonder, is it worth it? Has the embuing of toplevel
methods throughout all objects proven of significant worth? I knwo I
have never intentially created a toplevel method with the intended
effect of adding it to all objects. And Mathew makes another good case.

Thanks,
T.