Re: Perl 6 modules plan

> =head2 Namespace cleanup/naming conventions
> 
> The Great Perl 6 Module Rewrite also gives us a good opportunity to clean 
> up module namespace, if necessary.  
> 
> =over 4
> 
> =item Document namespace guidelines
> 
> This is a good opportunity to iron out some namespace wrinkles.  First
> step is to figure out what's already there on CPAN and can be documented
> as current "best practice" (eg. silly modules go in Acme::*, network
> protocols in Net::*).  
> 
> Similarly, figure out areas where it's a huge mess and make a note of them 
> (eg. Date/Time, WWW/CGI/HTML/etc), then see if we can get any consensus
> on how they should be sorted out (see notes below on getting authors of
> similar modules working together).
> 
> The resulting document ("module naming guidelines") will be useful both
> for authors trying to figure out what to call their module, and for
> those who get asked for advice on the topic (so they can't point and say
> "RTFM", thus saving themselves lots of work in explaining every time).

One silliness is that the implementation "style" of the module
seems to creep to the naming:

(1) Foo vs Foo_XS
(2) Bar vs BarOO

The XS-ness or OO-ness is useful information for someone and for some
purposes but I think having it in the actual module name is wrong.

-- 
$jhi++; # http://www.iki.fi/jhi/
        # There is this special biologist word we use for 'stable'.
        # It is 'dead'. -- Jack Cohen