From: Yukihiro Matsumoto <matz@...>
Date: 2007-03-22T17:53:51+09:00
Subject: Re: About class methods visibility (public/private)

Hi,

In message "Re: About class methods visibility (public/private)"
    on Wed, 21 Mar 2007 22:46:07 +0900, Ruby Admirer <ruby_admirer@yahoo.com> writes:

|  1/ why public, protected, private methods cannot be used for defining the visibility of class methods in addition to defining the visibility of instance methods ? Is there a technical reason or a conceptual reason for this ?

I am not sure what you mean here by "defining the visibility of class
methods in addition to defining the visibility of instance methods".
Can you elaborate?

If you want to change class method visibility, use singleton class
notation, "class <<SomeClass".

|  2/ why the protected_class_method is missing ?
|  The only methods are private_class_method and public_class_method.

We don't have private_class_methods nor public_class_methods in Ruby.
Are confusing with something else?

|  3/ The naming of these methods are quite confusing. Each time I read them I understand "give me the private/public class method ...". The naming is too/very close to private_methods, public_methods, ...
|  I would prefer something like class_private, class_protected, class_public.

What do you confuse with what?  For me, class_private etc. mean nothing.

Examining your questions before asking something is a tip to get
useful answers.

							matz.