Bug #7675
closedmain.protected is not defined
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.
Updated by kosaki (Motohiro KOSAKI) over 9 years ago
Target version: 2.0.0
2.0?
Updated by shugo (Shugo Maeda) over 9 years 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.
Updated by matz (Yukihiro Matsumoto) over 9 years 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.
Updated by shugo (Shugo Maeda) over 9 years 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.