Hi --

On Thu, 9 Mar 2006, itsme213 wrote:

>
> <dblack / wobblini.net> wrote
>
>> You can look at it the other way around, though: you *always* specify
>> a receiver explicitly in Ruby, except in the one case where the
>> receiver is self and the syntax is such as to be unambiguously a
>> method call.
>
> Not quite. I believe
>    self.foo
> does completely different privacy checks than just
>    foo
>
> Specifically,
>    self.foo
> on a private foo will fail, while
>    self.foo=
> on private foo= will succeed.

I don't think that's an exception to what I said, though.  A call to a
private (non-=) method falls into the category I'm describing: the
receiver is self, and the syntax is such as to be unambiguously a
method call.


David

-- 
David A. Black (dblack / wobblini.net)
Ruby Power and Light, LLC (http://www.rubypowerandlight.com)

"Ruby for Rails" chapters now available
from Manning Early Access Program! http://www.manning.com/books/black