Issue #8164 has been updated by drbrain (Eric Hodel).

Category set to core

=begin

If private_class_method is removed, how will the class method foo be set to private here:

  class C
    def self.foo() end
    def foo() end

    private :foo
  end

=end

----------------------------------------
Feature #8164:  Public/Private
https://bugs.ruby-lang.org/issues/8164#change-37926

Author: Anonymous
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: 


 - #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/