From: Minkoo Seo <minkoo.seo@...>
Date: 2006-02-14T16:38:25+09:00
Subject: Re: Private methods - only available to oneself?

I don't think the following statement make sense.

gwtmp01@mac.com wrote:
> One reason to support the distinction in Ruby is the existence of
> singleton methods.  It is possible for an instance to behave differently
> than any other instance of the class and as such you might want to
> support that different behavior by marking some methods as private.
>

For example,

class Foo
end

f1 = Foo.new
f2 = Foo.new

class << f1
    def bar
        puts "hi"
    end
end

f1.bar
f2.bar

In this case, we do not need to declare bar method as private to
support instance dependent behavior. What do you say?

Best,
Minkoo Seo