From: Trans <transfire@...>
Date: 2005-11-16T07:42:16+09:00
Subject: Re: toplevel namespace justification

> Might be an interesting discussion to talk about this aspect.
>  For example, let's say my Webcache were in Facets as
> Facets::Webcache.
>
> If someone wants to use it at the top level, they can do:
>
> Webcache = Facets::Webcache

Sure. But waht if you decided to release Webcache as an independent
project...not out of the question, certainly. Then it would end up in
the toplevel namespace anyway. Others have done. Instead of
participating in a larger collection they've just released their single
class/module as a project in and of itself.

I think we may be dealing with name clash issues b/c we are
uneccessarily depending on absolutes defined by other users, and thus
outside the realm of our control when putting them to use. Of course
some will say it's too rare to worry about. But as Ruby grows the less
that argument holds up --there's already been some notable occurances.

So what about the alternate possibility of "requiring into" an
arbitrary namespace?

T.