From: Tom M <thomas.macklin@...>
Date: 2007-09-27T03:20:08+09:00
Subject: Re: best way to 'hide' a method when method_missing is in town


>
> A parent's private method? I'm not sure I follow. Do you mean
> something like the following?
>
> class A
>   private
>
>   def priv_method
>     'private'
>   end
> end
>
> class B < A
> end
>
> b = B.new
> b.priv_method
 Yes... that is the scenario I was referring to.
>
> Because that's not calling a parent private method. The private method
> is inherited from A and part of B now.
That's how I understand it to work.

Your analysis seems sound enough.  When using a class or module, I
consider it's interface to be its public methods.  Unless you override
the default behavior of Object#respond_to?, it responds false for
private methods.  Also, whether you are inside our outside a class,
you can't call a private method w/ an explicit receiver, so
foo.priv_method is _never_ valid; regardless of whether or not you are
in the class.  Thus, to me, priave methods are "fair game" to be
appropriated by method_missing.  (Note: I am not weighing in here on
what I think *good* usage of method_missing is!)

At the end of the day though, I think this point can be argued both
ways ad infinitum.

Cheers,

Tom