This is why I think the biggest win for memory would be having XS based
time zones. This would also help speed somewhat, but I think the memory
savings could be very, very substantial.
If you look at the compiled Olson DB bits used by libc, they're fairly
small binary files (<1-2k usually).
Just FYI...
1. Store the timezone data in C structures or in some easy to access DB
format (CDB or TDB?) to reduce the memory footprint size, and the load
time.
I'm almost done with porting DT::TimeZone to XS (at least the most
oft-used portions). The XS portion is already working, and I'm c
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
