From: Yukihiro Matsumoto <matz@...>
Date: 2006-10-03T17:35:04+09:00
Subject: Re: Private visibility should be removed from Ruby 2 [was: Caveats with #method_missing]

Hi,

In message "Re: Private visibility should be removed from Ruby 2 [was: Caveats with #method_missing]"
    on Tue, 3 Oct 2006 16:57:02 +0900, "Tomasz Wegrzanowski" <tomasz.wegrzanowski@gmail.com> writes:


|> If you want to remove "private" from Ruby2, I expect
|> your proposal addresses the above issue.
|
|New version of my proposal:
|* add implicit_self? method analogous to block_given?
|* method called by send/funcall would have implicit_self? set to false/true
|* remove "protected" visibility completely
|* make all currently private "real" methods (that is almost all
|private methods outside Kernel) public
|* change names public/private to object/global (or something like that)
|* officially discourage using "global" visibility for real methods

Interesting.  Will you analyze consequences of above changes?
How they make the language better?  How they make it incompatible?

In addition, I didn't understand how global "global" visibility, and
why it should be discouraged.

							matz.