Commit Graph

8 Commits

Author SHA1 Message Date
aj
a90d6246ec moving from mnesia to ets. matchspecs are complicated when dates and atoms are involved. 2010-11-18 00:28:50 -08:00
aj
bd4e6078f2 ezic:local_to_utc/2 added, working.
in the case of ambiguous timezones, an "ambiguous_zone" error is thrown with the two valid zones.
if no zones existed for the given local time (i.e. DST eliminated the hour in question), a "no_zone" error is thrown.
otherwise, the date is returned
2010-11-14 00:46:00 -08:00
aj
22395e2f47 max_year base case bug fixed. ezic:localtime/1 works.
the final flatzone for every Zone should end at "current" for every *_to time. This is inaccurate, but accuracy is only guaranteed up to ?MAX_YEAR (=2500 by default).
that working, I fleshed out the few methods required to get ezic:utc_to_localtime/2 working, thus localtime/1 working. I've only tested localtime/1 at this point.
additionally, mnesia appears to have its data corrupted every time I stop and start a node. I've got to read up on working with mnesia; it's not behaving as I would expect.
2010-11-14 00:27:44 -08:00
aj
d664384c60 Costa Rica's flatzones aren't processed after 1992. Gotta check her out. 2010-11-13 22:54:44 -08:00
aj
c976e63349 removed all warnings. fixed bug in ezic_zone:next/3. unit tests for ezic_zone:next/3
ezic_zone:next/3 was not filtering the Zones to only those after UTCFrom. This may have caused an endless loop, always returning the earliest zone regardless of the progress of time. I wont know; I caught it rather early.
2010-11-11 23:52:10 -08:00
aj
9ad8f3c826 lots of work towards flattening the records. stalled at ezic_rule:next_event/4 2010-11-07 18:32:37 -08:00
aj
9ac6f0cc4a eliminated warnings. there were lots of unnecessary variables created in function parameters 2010-11-04 20:57:23 -07:00
aj
7dd76519a0 happy path tested! current times correctly reported for LA, NY, Tokyo, and Jamaica!
Japan doesn't observer DST. I didn't know that.
2010-11-04 04:20:38 -07:00