Right I got that from before,

The thing is in most static languages they check to make sure your not using
an instance variable in one class that has the same name in one above it.
In ruby we are allowing this, in fact making sure of it, and thus we are
getting a dynamic scoping situation out of it.  Or perhaps dynamic scoping
is the wrong word, but the binding on which variable we are using allows
scoping "fall through" mechanics.

Charles Comstock

> -----Original Message-----
> From: ts [mailto:decoux / moulon.inra.fr]
> Sent: Wednesday, December 03, 2003 10:24 AM
> To: ruby-talk ML
> Cc: ruby-talk / ruby-lang.org
> Subject: Re: Attempted roadmap of future instance variables....
> 
> >>>>> "C" == Charles Comstock <cc1 / cec.wustl.edu> writes:
> 
> C> So these @_instace vars are giving us dynamic scoping in one instance
> right?
> 
>  @_instance are instance variables (they are described in the slide 13)
> 
> C> class Super
> C> 	@_var = 0
> 
>   this is an instance variable for the class Super
> 
> C> 	def get
> C> 		@_var
> 
>  this is an instance variable for an *instance* of Super. This mean that
>  this variable is different than the previous one
> 
> C> 	end
> C> end
> 
> 
> Guy Decoux
>