In perl.datetime, you wrote:
>
>First, there's the Time:: vs Date:: issue. That is, there are Time::
>modules, and there are Date:: modules, and there's no consistent
>definition of what goes in which. An appeal to [EMAIL PROTECTED] for a
>little direction on this matter did not produce a particularly helpful
>answer, and so it seems up to the authors of these modules to make
>sensible choices.
How's this for a concept: anything that deals with days or any greater
unit goes in Date, anything that only deals with smaller units goes
in Time. So IMO, Time::HiRes and Time::Beat are in the right place, but
Time::DaysInMonth (part of Time-Modules) is in the wrong place.
>I'd like to have some discussion as to what people think these
>namespaces mean, and then to request that authors respect those
>definitions, and, if a particular module is not in the namespace that
>it should be, that it migrate to the correct namespace via a
>several-month period of adding warnings to modules, asking people to
>move to the new version of the module in the new namespace.
The inevitable Perl 6 rewrite of most of CPAN should probably be the
deadline for this. That gives us a couple of years to sort it out.
Hopefully we'll get most of it in place sooner, but we could set that as
the *absolute* limit.
I'm meant to be babysitting the modules side of Perl 6, and I'm starting
to think about stuff like namespace cleanups etc, so I'm *very* happy to
see this stuff starting to happen on the datetime list.
>What I'd like to propose here is a namespace hierarchy where modules
>get put in places that reflect their purpose. Something like, perhaps:
>
>Date::Algorithm - Modules that do things like calculate leapyears,
>calculate golden numbers, calculate epacts, full moons, and so on. So
>Date::Leapyear would become Date::Algorithm::Leapyear, for example.
>
>Date::Calendar - Modules that implement a particular (usually
>non-Gregorian) calendar. So Date::Discordian would become
>Date::Calendar::Discordian
>
>Date::Holiday - Modules that calculate the date of a particular
>holiday. So Date::Easter becomes Date::Holiday::Easter
These all sound great to me.
>There are also a variety of things that purport to be the One True
>Module that should be the base class for all Date:: and Time::
>modules. There are at least 4 of these that I know of. And I wrote one
>of them. All of them have shortcomings. These folks need to get
>together and compromise on some things, so we can actually have one of
>these that doesn't suck, and which people can agree on.
Can you let us know what the other ones are?
>On a related note, I'm working on lists of all the Date:: and Time::
>modules (yeah, I know, you can just do an ls in your CPAN mirror) and
>trying to understand what they all do, where there is overlap, and
>where various authors aught to get together and cooperate on some
>things. I know, this is like herding cats, but it keeps me off the
>streets.
How many date/time module authors are on this list? Have the rest been
contacted and invited to subscribe?
>Please let me know what your thoughts are on these things. And let me
>know that I'm not just talking to myself on this list.
You're not just talking to yourself.
Namespace cleanup is a *good* thing, IMHO.
K.
--
Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/
"So shall we do it on the floor then ... did I phrase that incorrectly?"
-- Sofi runs a Mgt meeting (from the Netizen quotes file)
