[snip]
> 
> I think in many cases one would get away with AUTOLOAD. Move the code
> to the new namespace and let the old namespace be handled by an
> AUTOLOAD dispatcher that simply calls the new namespace. In the
> beginning you issue a warning when the old namespace gets loaded. Time
> goes by and you add a warning to the dispatcher whenever old namespace
> is called. Then you slowly stop maintaining the dispatcher.
> 
> A similar approach has successfully been done with my Msql.pm which
> predated the DBI. When Jochen Wiedmann's DBD::Msql started to work, we
> made all Msql.pm classes simple wrappers to DBD::Msql. Today Msql.pm
> is phased out, I don't think that anybody is still using it.

Andreas's advice is, as always, excellent.

Autoloads (and wrappers) can go a long way.  And might get you and the
other Weather module authors all the way there.  Many have expressed
frustration with the Namespace of CPAN modules especially top level NSs.
I went through this process for a new module a year ago. 

If I were looking for Weather modules, would probably look first for
Weather:: not Geo::Weather.  BUT, a CPAN module search would find your
modules under Geo::.  I guess the really question you have to answer (or
get answered), is would the other Weather module authors support the
move.  It would take several years of diligence and 
evangelism to put it off.

Further, Weather::Underground is a "cute" or "silly" name, that does not
even usefull describe what it does... For instance what is
wonderground.com?  

Geo::Weather is not terrible as namespaces go... infact it is a heck of
a lot better than Weather::Underground.

I guess I am saying I think like the idea of moving the Weather
modules... unless there are a bunch of other modules under Geo:: that
could be consider related to Geo:: in a way similar to the way Weather
might be consider related to Geo... (which I presume refers to Earth). 
If we start consider other planets, on the other hand... may Geo should
really be Planitary::  sigh... or maybe Weather should stand on its
own...  Enough rambling.

Good luck...

-- 
Lincoln A. Baxter <[EMAIL PROTECTED]>

Reply via email to