[time-nuts] TymServe 2100 1995 Issue - A Kludgy Fix

[Alan Ambrose]

Hi,

>>>

It's not that simple. First, it's not 20 years, but 1024 weeks (19.6 years). And not UTC weeks (which may have leap seconds) but GPS weeks (which do not, and are always 604800 seconds long). etc

<<<



Don't think it's _that_ much code though. There's some open source ACM date algorithms, and it would be easy enough to implement a quick and dirty fix, adding a number of days offset, while the rest of the algorithm is tested. Will the next time this problem reoccurs be another 20 years?



Alan