From: "Christoph R." <chr_news@...>
Date: 2003-09-18T00:15:22+09:00
Subject: Re: Nested class/module namespace

Nathaniel Talbott wrote:
....
> In many cases this form of nesting will create more typing for me than the
> normal form of nesting! OTOH, I haven't ever had trouble with too much
> namespace exposure except with top-level classes (like Queue) that cause
> confusion when I forget to require something and they magically get used
> instead of my classes without an (immediate) error. But this new form
> doesn't solve that problem, so I don't see any benefit in how it behaves.

If this does not benefit you just don't use the new feature.  Remember the
protracted trouble with the scoping rules of Ruby's class variables (it took
Matz a fairly long time to get things right).  Ruby's scoping are already
complicated enough (especially in combination with eval scope).

The feature you are requesting run IMHO squarely against the current
scoping rules and might push them over the edge (of being too
complicated) ...


  /Christoph