From: "shugo (Shugo Maeda)" Date: 2013-01-09T10:42:29+09:00 Subject: [ruby-core:51327] [ruby-trunk - Bug #7675][Rejected] main.protected is not defined Issue #7675 has been updated by shugo (Shugo Maeda). 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. ---------------------------------------- Bug #7675: main.protected is not defined https://bugs.ruby-lang.org/issues/7675#change-35296 Author: shugo (Shugo Maeda) Status: Rejected Priority: Normal Assignee: matz (Yukihiro Matsumoto) Category: core Target version: 2.0.0 ruby -v: ruby 2.0.0dev (2013-01-07 trunk 38731) [i686-linux] 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. -- http://bugs.ruby-lang.org/