> > I assume that this is an ordered preference in case the APIs overlap. so > Class::Date will be used first, then Date::Parse, then Date::Format >
I didn't tried it, but from the docs of Class::Date it should be possible to utilize Date::Parse for it's parseing. So there should be no need for using Date::Parse directly. So interface should always be via Class::Date. Also I don't see what you can do with Date::Format, what can't be done with Class::Date. So (in case I am not wrong) we should only use Class::Date and access Date::Parse only via the Class::Date interface. Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 -------------------------------------------------------------
