From: Tobias Reif <tobiasreif@...>
Date: 2002-02-25T21:24:42+09:00
Subject: Re: [ANN] TestUnit 0.1.1

Dave Thomas wrote:

 > A minor incompatibility: the original toplevel 'rubyunit' aliased the
 > > global constant
 >
 > TestCase = RUNIT::TestCase

That looks strange to me.

 > so that all you had to write was
 >
 > require 'rubyunit'
 >
 > class TestFred < TestCase

AFAICS, the same (not having to type RUNIT::) can be achieved by not 
including it in a module named RUNIT(?)

I don't have a full overview of all that, and I appreciate insights.

I thought that I either
a) don't use a module wrapper as namespace separator for a lib, then the 
user doesn't have to type MODULE_NAME:: ; but then there can be 
conflicts with other namespaces;
or
b) wrap the classes in a module to separate the namespace: then the user 
has the choice of
   1) including the namespace and saving some keystrokes, which is
      OK if there can't be a conflict because no other namspaces are
       used,
   or
   2) dont' include the namespace, type the MODULE_NAME::s, and thus
      avoid conflicts with other lib's namespaces.

In your example, it looks to me as if the advantage of wrapping the lib 
in a module RUNIT is lost by the aliasing: there could be conflicts with 
other namespaces, but no namespace "prefix" can be used.

I suspect that either a) I'm missing something or b) there won't be a 
problem in this case anywasy.

Tobi

-- 

* peace&love.
* http://www.pinkjuice.com/