From: Julian Leviston <julian@...>
Date: 2009-02-06T12:26:45+09:00
Subject: Re: Method Precedence

FYI, it's not a compiler, it's an interpreter.

Also, by "the object did not get affected" you mean the instance  
object... just to clarify for him.

Julian.

On 06/02/2009, at 2:19 PM, Phlip wrote:

> When the compiler first encountered Example, it plugged one() and  
> the outer two() into Example's class instance list.
>
> The first call to one() then bonds the inner two() to the class. The  
> object did not get affected in either case. (Always remember classes  
> are objects around here!)
>
> If you ran the program again (a new Ruby "VM"), and never called  
> one(), you would only get the outer two().