Object#initialize_copy should always be private
-----------------------------------------------
Key: JRUBY-2624
URL: http://jira.codehaus.org/browse/JRUBY-2624
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1.1.2
Environment: Latest JRuby
Reporter: Vladimir Sizikov
Assignee: Vladimir Sizikov
Fix For: JRuby 1.1.3
It seems that MRI always make "initialize" and "initialize_copy" methods
private, automatically.
JRuby does not do that for initialize_copy, but should.
We've seen quite a number of rubyspec failures about initialize_copy for some
classes not being private, and fixed them one by one.
But it's not even always possible to fix that, if some class doesn't have the
java source, like, Set. stdlib's Set#initialize_copy is not defined as private
in the set.rb, but still made private by the runtime.
Fix is coming.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
