gwtmp01 / mac.com wrote:
> 
> On Nov 6, 2005, at 9:47 AM, Mads Kristensen wrote:
> 
>> And BTW: what does class<<self actually mean? One < would be  
>> inheritance but what does it mean when there are two?
> 
> 
> One of the early hurdles I had with Ruby was trying to map
> the "class <<object" syntax into a useful mental model.  I'm
> not sure why "<<" was selected.  The semantics and syntax
> don't seem to be related to those of the "<<" operator and
> so you really need to form two separate mental models and just
> know which one applies.
> 
> Why not something like:
> 
> class obj.eclass
>   #
> end

Once you know what << does, there is no confusion. I suspect the same would be with your proposed 
code above. By looking at it, I am confused, but once I know what it means, there is no more confusion.

Zach