On Fri, 8 Jul 2005, Rob Mueller wrote:
3. Have only 1 timezone class (well, not including Local/Floating/etc, 1
class for all the "standard" timezones). Do all the separate timezone classes
actually contain any code, or do they just store data? Why should they be
separate classes, rather than 1 class with different instance data for each
timezone?
It's the instance data that's sucking up all the memory, trust me ;)
Anyway, as Daisuke mentioned, he's already done a working XS
implementation, and once there's a pure Perl fallback option it'll be
released.
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/
