From: "dunric (David Unric)" <dunric29a@gmail.com>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:54464] [ruby-trunk - Bug #8297] extend & inherited class variable issue
Date: Fri, 19 Apr 2013 21:12:54 +0900 [thread overview]
Message-ID: <redmine.journal-38747.20130419211254@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-8297.20130419210206@ruby-lang.org
Issue #8297 has been updated by dunric (David Unric).
=begin
By the current documentation, Object#extend method has to (only) add instance methods of a module given as a parameter.
In the following example, the class ((*C*)) is extended with module ((*M*)).
By ((*class_variables*)) method sent to singleton class of C also did inherit class variable ((*@@xyz*)).
However when inherited ((*@@xyz*)) is accessed, ((*NameError*)) exception is raised as it is was not initialized:
module M
@@xyz = 123
end
M.class_variables # [:@@xyz]
M.class_variable_get :@@xyz # 123 , so far so good
class C
extend M
end
p C.singleton_class.class_variables # [:@@xyz]
p C.singleton_class.class_variable_get :@@xyz # NameError exception
Either ((*class_variables*)) returns invalid array - ie. ((*@@xyz*)) was not inherited at all or ((*class_variable_get*)) ignores class variables inherited from module (when sent to a singleton).
Prior Ruby versions like 1.9.3p392 does not suffer this issue as Module#class_variables returns an empty array.
=end
----------------------------------------
Bug #8297: extend & inherited class variable issue
https://bugs.ruby-lang.org/issues/8297#change-38747
Author: dunric (David Unric)
Status: Open
Priority: Normal
Assignee:
Category: core
Target version:
ruby -v: 2.0.0p0
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN
=begin
By the current documentation, Object#extend method has to (only) add instance methods of a module given as a parameter.
In the following example, the class ((*C*)) is extended with module ((*M*)).
By ((*class_variables*)) method sent to singleton class of C also did inherit class variable ((*@@xyz*)).
However when inherited ((*@@xyz*)) is accessed, ((*NameError*)) exception is raised as it is was not initialized.
(({module M
@@xyz = 123
end
M.class_variables # [:@@xyz]
M.class_variable_get :@@xyz # 123 , so far so good
class C
extend M
end
((*p C.singleton_class.class_variables # [:@@xyz]
p C.singleton_class.class_variable_get :@@xyz # NameError exception*))
}))
Either ((*class_variables*)) returns invalid array - ie. ((*@@xyz*)) was not inherited at all or ((*class_variable_get*)) ignores class variables inherited from module (when sent to a singleton).
=end
Prior Ruby versions like 1.9.3p392 does not suffer this issue as return with Module#class_variables returns an empty array.
--
http://bugs.ruby-lang.org/
next prev parent reply other threads:[~2013-04-19 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 12:02 [ruby-core:54463] [ruby-trunk - Bug #8297][Open] extend & inherited class variable issue dunric (David Unric)
2013-04-19 12:12 ` dunric (David Unric) [this message]
2013-04-19 14:53 ` [ruby-core:54469] [ruby-trunk - Bug #8297] " nobu (Nobuyoshi Nakada)
2019-01-14 17:37 ` [ruby-core:91085] [Ruby trunk Bug#8297] " justin
2019-08-10 4:33 ` [ruby-core:94242] [Ruby master " merch-redmine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-38747.20130419211254@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).