From: "nobu (Nobuyoshi Nakada)" <nobu@...>
Date: 2013-03-27T06:10:47+09:00
Subject: [ruby-core:53751] [ruby-trunk - Feature #8164]  Public/Private


Issue #8164 has been updated by nobu (Nobuyoshi Nakada).


Class methods and instance methods are different things.
I don't see advantages of this proposal.
----------------------------------------
Feature #8164:  Public/Private
https://bugs.ruby-lang.org/issues/8164#change-37947

Author: Anonymous
Status: Assigned
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: Next Major


 - #private<http://www.ruby-doc.org/core-1.9.3/Module.html#method-i-private>
    - #private_class_method<http://www.ruby-doc.org/core-1.9.3/Module.html#method-i-private_class_method>
    - #public<http://www.ruby-doc.org/core-1.9.3/Module.html#method-i-public>
    - #public_class_method<http://www.ruby-doc.org/core-1.9.3/Module.html#method-i-public_class_method>
 
 Would it be a good idea to compress these 4 methods to 2 methods?
 
 public - Can set both instance *and* class methods to public by passing
 them in as symbol
 private - Can set both instance *and* class methods to private by passing
 them in as symbol
 
 and enable them to be called at top of class? Is this a good idea? It would
 clean up Module# and encourage use of these two
 as methods rather than keywords


-- 
http://bugs.ruby-lang.org/