On Fri, 10 Jan 2003, Matt Sergeant wrote: > On Fri, 10 Jan 2003, Dave Rolsky wrote: > > > This is the reason I want to talk first about the API. That's what is > > missing. We have lots of great functionality, but every piece has a > > different, and incompatible, API. That's what sucks! > > To someone like you and I (and probably most people following this list) > it's fairly obvious what makes good APIs for these modules. What we're > missing is code, not discussions of APIs.
I'm not sure it's so obvious. If it was obvious the various date modules would all work together. But they don't even come close. So obviously each module author has their own idea of what makes a good API. Look at Date::Calc. It's a very _useful_ module, but I'm not too fond of the API. Anyway, I don't want to beat API discussion into the ground, I just want to make sure that before we (whoever "we" ends up being) start coding this stuff, that we have a basic idea of the variety of things that need to be handled (basic datetime stuff, sets, timespans, timezones, parsing, etc.), and a basic idea of what the APIs for each of those pieces needs to be. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
