> The hugeness is the DateTime::TimeZone object, not DateTime itself. > Those are all singletons, so you only pay the price once per time zone.
ok, but how does that affect storable-style serializations? I noticed that you have some storable hooks, but I didn't see exactly how it worked. > > The ultimate fix is to implement this code in C with C data structures, > I think. > > Not doing the precalculations might be possible, but it'd make many > things much slower, since the code that I use to generate this data is > completely unoptimized. Plus it's ugly as hell ;) > > Making loading the pre-calculated data _optional_, as opposed to > removing it entirely, would be best. if it wasn't clear, that's what I was suggesting. > I'm open to a patch, but it's a > lot of work, and not something I'd have time to do any time soon. I can take a crack at it, but it wasn't clear exactly how these things interlaced, or even what the span foo was. if you could sorta point me in the right direction for implementing it in a way you'd prefer I'll have a go at it. --Geoff
