From: transfire@...
Date: 2006-05-21T00:56:38+09:00
Subject: Re: Ruby namespaces and require

Austin may be right that there are too many problems with doing this
effectively as a standard. But I'm not yet sure of that. All I have
seen for sure is the problem of core extensions, which like I said can
be resolved using a prefix '::'. Of course one should be careful not to
reference things in the absolute but rather in the relative. For
instance, never do:

  class X
    def X.foo

but always

  class X
    def self.foo

Following some simple guidelines should make importing feasible. NAd of
course, it's okay if something is not importable --one can decument
that fact too.

But perhaps Austin you have a better solution?

T.