Bug #7675

main.protected is not defined

Added by Shugo Maeda over 1 year ago. Updated over 1 year ago.

[ruby-core:51322]
Status:Rejected
Priority:Normal
Assignee:Yukihiro Matsumoto
Category:core
Target version:2.0.0
ruby -v:ruby 2.0.0dev (2013-01-07 trunk 38731) [i686-linux] Backport:

Description

main (self at toplevel) has public and private, but doesn't have protected.

public
private
protected #=> NoMethodError

It looks a bit weird.

I guess it was forgotten to add main.protected when Module#protected was introduced
in Ruby 1.1b9_05.
main.protected seems not to be useful because it makes methods of Object protected, but
it might be good to have main.protected for consistency.

History

#1 Updated by Motohiro KOSAKI over 1 year ago

Target version: 2.0.0

2.0?

#2 Updated by Shugo Maeda over 1 year ago

kosaki (Motohiro KOSAKI) wrote:

Target version: 2.0.0

2.0?

I considered it a bug, but if Matz consider it a new feature, feel free to move it to next minor or to reject it simply.

#3 Updated by Yukihiro Matsumoto over 1 year ago

I am not positive to add it.
There's no reason to add protected except for consistency, since it behaves just like public.

Matz.

#4 Updated by Shugo Maeda over 1 year ago

  • Status changed from Assigned to Rejected

matz (Yukihiro Matsumoto) wrote:

I am not positive to add it.
There's no reason to add protected except for consistency, since it behaves just like public.

OK, so I close this ticket.

Also available in: Atom PDF