Hi,

In message "Re: Different Behavior of Class Variables w.r.t ||="
    on 02/10/12, Kent Dahl <kentda / stud.ntnu.no> writes:

|> Oops, 1.7 behavior has changed.  Bad idea?
|> # [ruby-talk:50421] & [ruby-dev:18278]

|If all types of variables now work with ||=, that isn't necessarily a
|bad idea, but writing Ruby code that sets a class variable using ||=
|somewhere which might cause it to be defined at the wrong hierarchy
|level might be a bad idea. As for what Ruby should do, it really is a
|weighing of "shooting foot" versus "ease of toe nail cutting" that it
|appears Matz already has made a call on. :-)

Class variables themselves have same kind of problem.

  def foo
    @@c = 42
  end

does not raise error nor warning.  Let me think it again.

							matz.