From: Gary Wright <gwtmp01@...>
Date: 2009-02-26T12:28:00+09:00
Subject: [ruby-core:22529] Re: YASNP (Yet Another Selector Namespace  Proposal)


On Feb 25, 2009, at 9:24 PM, Jim Weirich wrote:

>
> On Feb 25, 2009, at 9:16 PM, Gary Wright wrote:
>
>> In my understanding of the namespace proposal, the same overall  
>> algorithm applies except that the exact sequence of modules/classes  
>> is modified according to the modules 'inserted' via the 'using'  
>> keyword.  If namespaces can be 'nested' so that multiple namespace  
>> modules are in the lookup sequence then shouldn't 'super' behave as  
>> normal and just resume the lookup process including any unsearched  
>> namespaces?
>
> Which namespaces?  The ones in scope at the original call site, or  
> the ones in scope at the super invocation?

My first thought was the one in scope at the original call site.  I'll  
have to think harder about what it would mean for a different set of  
namespaces to be in play at the super invocation than at the original  
call site.

There has to be some state retained during calls normally since  
'super' can't restart method lookup based strictly on self, which is  
why I assumed that the state would be available to restart a search  
including the original namespaces.

Gary Wright