Stefano Crocco <stefano.crocco / alice.it> wrote:


> Ruby implements private methods forbidding to call them with an explicit
> receiver, but only with the explicit receiver, self. This is enough to ensure
> a private instance method of class A can't be called by, for example an
> instance method of class B, because in the latter self is an instance of class
> B, not of class A.

I don't know if I understand correctly your last sentence, but also less
rescrictive (compared to private) protected methods behave the way you
described, am I right? I am asking because I don't get the link between
the 2 sentences quoted above. 
Sorry, while the rest of your post is pretty clear it seems I am missing
something here... any further explaination is welcome :)

Bye
Andrea


-- 

http://myretrocomputing.altervista.org