You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2017/09/11 16:24:00 UTC

[jira] [Resolved] (WHIMSY-133) roster/main.rb: warning: class variable access from toplevel

     [ https://issues.apache.org/jira/browse/WHIMSY-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb resolved WHIMSY-133.
-------------------------
    Resolution: Fixed

> roster/main.rb: warning: class variable access from toplevel
> ------------------------------------------------------------
>
>                 Key: WHIMSY-133
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-133
>             Project: Whimsy
>          Issue Type: Bug
>            Reporter: Sebb
>
> The server error logs are full of warnings such as the following:
> /x1/srv/whimsy/www/roster/main.rb:57: warning: class variable access from toplevel
> /x1/srv/whimsy/www/roster/main.rb:58: warning: class variable access from toplevel
> /x1/srv/whimsy/www/roster/main.rb:59: warning: class variable access from toplevel
> /x1/srv/whimsy/www/roster/main.rb:61: warning: class variable access from toplevel
> /x1/srv/whimsy/www/roster/main.rb:63: warning: class variable access from toplevel
> It looks like this is because the variables are defined at class level, but the code is not in a class (other than Object, which is why the warning is generated)
> Do the variables need to be defined at class level?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)