On Tue, 7 Aug 2001, Mark Tearle wrote:
> On Mon, 6 Aug 2001, Rich Bowen wrote:
>
> > 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
> >
>
> Sounds good, may I suggest also:
>
> Date::Parse - Modules that parse date strings, eg Date::Parse::ISO8601
Time::Parsedate does that. I'm not sure what other modules do that
exclusively, although most of the Date::Calendar modules (ISO,
Discordian, ICal, etc) do that as part of their object creation
process.
--
Rich Bowen - [EMAIL PROTECTED]
Have trouble remembering things?
http://www.idforgetmyhead.com/
