From: Robert Klemme <bob.news@...>
Date: 2003-12-03T22:37:09+09:00
Subject: Re: Attempted roadmap of future instance variables....


"Yukihiro Matsumoto" <matz@ruby-lang.org> schrieb im Newsbeitrag
news:1070389195.767662.15370.nullmailer@picachu.netlab.jp...
> Hi,
>
> In message "Re: Attempted roadmap of future instance variables...."
>     on 03/12/03, Steve Tuckner <STUCKNER@MULTITECH.COM> writes:
>
> |OK so the jist of it is that @_var variables are stored with the class
of
> |the instance but the class has no access to that. That is all. Right?
>
> No. @_var variables are stored in the instance, but they are
> accessible only from methods defined in the same class.

Still a number of questions arise to me: How then are @_ variables treated
with respect to methods instance_variables, instance_variable_set and
instance_variable_get?  Are they ignored and there is a second set of
methods that receives the class as argument (e.g.
instance_local_variables, instance_local_variable_get,
instance_local_variable_set)

If so, what, if they are defined in an instance's private class like this:

class <<obj
  def get_foo; @_foo; end
  def set_foo(f); @_foo = f; end
end

Do we use the instance instead of the class as method argument to those
methods (see above) to get access to them via those methods?  If so, how
is that disambiguited if obj is a class?

Or do we make them unique by modifying the identifier, e.g. @_var becomes
@Foo:_var if it was defined in class Foo?

If we have this second set of methods, it seems to me as if things are
getting overly complex, i.e., away from Ruby's simplicity.  Just my 0.02
cent...

Kind regards

    robert