Hi, All! --- Matt Sergeant <[EMAIL PROTECTED]> wrote: > On Thu, 15 Nov 2001, Gerald Richter wrote: > > > > Class::Date > > > > Date::Parse > > > > Date::Format > > > Can anyone explain what these 3 modules gain me over the 1 > module Time::Piece?
We'll discusss this question over and over again. Here is the situation. For some fields we have several modules on CPAN that have similar functionality, for others we have none. We want to choose/create/bless one API per field. We can either create/borrow new API or we can choose and bless one from already existent modules. This API serves at least three purposes: 1. it allows to build other components using it 2. it allows to use it directly in p5ee applications 3. it tells all other developers (not even p5ee aware) that module behind this API gives (almost) all functionality they need. This goal is not less important than the first two. Working more than eight years with Perl and CPAN I'm sometimes just getting confused choosing module from CPAN esp. if it's not in the area of my expertise. It's much easier to use already existent API unless there is a value to borrow some API that is well established in the industry (esp. if there is no Perl module for that yet). Ideally I would like to see something similar to XML::SAX interface (btw, API for loading extensions should be also common) where you can choose among modules that all support the same interface (SAX in this case) based on different criteria: XS vs. pure Perl, performance, extensions, etc. Best wishes, Paul. __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com
