Ruby Dynamic Classes. How to fix "warning: class variable access from toplevel"
Solution 1
Just to remove this warning, you should use class_variable_set
method:
x = [1,2,3]
Test = Class.new do
class_variable_set(:@@mylist, x)
def foo
puts @@mylist
end
end
Solution 2
This isn't doing what you think it's doing. Since you're not creating a class with the class
keyword, your class variable is being set on Object
, not Test
. The implications of this are pretty huge, which is why Ruby is warning you. Class variables are shared between ancestors, and objects usually inherit from Object
.
Solution 3
Rather than defining your "mylist" class variable on the class when declaring the class, you can declare class level variables on it later on as below. Two different methods are shown. The former only works in 1.9, the latter works in both versions, but is less idiomatic.
x = [1,2,3]
Test = Class.new do
def foo
puts @@mylist
end
end
# ruby 1.9.2
Test.class_variable_set(:@@mylist, x)
# ruby 1.8.7
Test.class_eval {
@@mylist = x
}
Test.new.foo
Solution 4
if you want only to suppress this warnings you can use
$VERBOSE = nil
in top of you code
yoda_alex
Updated on June 08, 2022Comments
-
yoda_alex about 2 years
I'm trying to write a program that dynamically defines ruby classes based on configuration read from a file. I know I can use Class.new to do this. Here's an example program:
x = [1,2,3] Test = Class.new do @@mylist = x def foo puts @@mylist end end Test.new.foo
When I run this I get the following output (running with ruby 1.9.3p0):
c:/utils/test.rb:4: warning: class variable access from toplevel c:/utils/test.rb:7: warning: class variable access from toplevel 1 2 3
Does anyone know what causes these warnings and how I can get rid of them?
I've tried replacing the line tjhat does
@@mylist = x
with this
class_variable_set(:@@mylist, x)
But when I do that I get this error instead:
c:/utils/test.rb:7: warning: class variable access from toplevel c:/utils/test.rb:7:in `foo': uninitialized class variable @@mylist in Object (NameError) from c:/utils/test.rb:11:in `'
Thanks in advance!
-
yoda_alex over 12 yearsThat gives me an error unfortunately. I've updated the original question with the details.
-
WarHog over 12 yearsHmm - only Ruby 1.9.2 may give you a such warning about 'class variable access from toplevel'. But
NameError
withuninitialized class variable
message may only come from Ruby 1.8 because methodclass_variable_set
is private in this version. Maybe it's stupid question :) but are you sure that you're running both version in the same ruby version? If I use 1.8 with your initial snippet, I don't have any warning message and if I use 1.9 with my snippet it seems to be ok too... -
yoda_alex over 12 yearsThanks WarHog. I just tried your code on 1.9.2p290 and it worked with no errors. But when I run it with 1.9.3p0 I get the error I describe above. I'll take a look at the what's new for 1.9.3 and see if anything might explain the difference in behavior.
-
yoda_alex over 12 yearsThanks for the reply. Unfortunately when running with 1.9.3, the first version causes the error I saw, and the second gives the warnings I had! I'm starting to suspect this is a change in behaviour / regression in ruby 1.9.3.
-
yoda_alex over 12 yearsIt might be issue 3080 (redmine.ruby-lang.org/issues/3080) that's causing my problem on 1.9.3. Seems like its a regression.
-
Luc Wollants over 10 yearsAnother possible solution is to use a class method to access the class variable as also described here stackoverflow.com/a/21444098/1145454