From: David Flanagan <david@...>
Date: 2009-02-26T05:16:41+09:00
Subject: [ruby-core:22498] Re: YASNP (Yet Another Selector Namespace Proposal)

I have not been following this thread, and have no detailed 
understanding of the proposal at all.  But, I think it is worth 
mentioning that a bunch of smart people tried very hard to add 
namespaces to JavaScript (in ECMAScript 4) and have recently abandoned 
the effort.  The proposals sounded very cool; I'm not sure what the 
practical difficulties were, but it would be great if someone who 
understood the ECMAScript experience with namespaces could comment on 
its implications for Ruby.  Perhaps someone could have a chat with 
Brendan Eich...

	David Flanagan

Yukihiro Matsumoto wrote:
> Hi,
> 
> In message "Re: [ruby-core:22490] Re: YASNP (Yet Another Selector Namespace Proposal)"
>     on Thu, 26 Feb 2009 04:08:19 +0900, Ola Bini <ola.bini@gmail.com> writes:
> 
> |If any of this has been answered, or if I misunderstood something, I 
> |apologize in advance:
> 
> Here's MY opinion.
> 
> |- How would this interact with send?
> 
> send should honor namespaces.
> 
> |- How would it interact with other introspection facilities? Kernel#method ?
> |     Basically, what is the runtime behavior of all metaprogramming and 
> |introspection features here...
> 
> and other introspection features as well.
> 
> |- Do I understand correctly that this is supposed to be a lexical 
> |effect, and not a dynamic one?
> 
> I think so.
> 
> |   ... in that case I have no idea how it's supposed to work at parse 
> |time.
> 
> One possible idea is making symbols to belong to each namespace, like
> Common Lisp does, in that case,
> 
>   obj.foo(bar)
> 
> should be work as
> 
>   obj.<namespace::foo>(bar)
> 
> where <namespace::foo> means "symbol foo in that namespace", and its
> correspondence can be modified by (dynamic) method definitions.
> 
> 							matz.
> 
>