Two thoughts on the TimeZone issue: 1. Create DateTime::TimeZone::Lite. - This would return a subset of the Olson data that assumed the current rules extend infinitely in both directions. - This would not be a prereq, or be installed by DateTime itself. - I suggest we might make this assumption on the grounds that we already make a similar assumption with DateTime: The Gregorian Calendar wasn't used back at the year 0, but DateTime assumes it does.
2. Create DateTime::TimeZone::Olson::XS - The Olson Database is already an open-source, free distributable C library, would we not save considerable space/memory by creating an XS interface to the library? - The DateTime::TimeZone::Olson::XS module would be a part of the DateTime::TimeZone distro, and would be the default, if it can find the Olson database. Otherwise TimeZone falls back on the perlified version. Unfortunately I'm not a C programmer and, although I just read right through perlxs and perlxstut I'm still none-the-wiser ;) Cheers! Rick
