Holy moly. I didnt know that there were so many of them.
I knew only y2k problem and 2038 Unix Epoch sign overflow.
Anyway, I think that making Unix epoch signed was one of the biggest mistakes in that case. When you design stuff that cannot live for at least 100 years, you do it wrong imo.
Having Unix TS unsigned 32bit, problem would surface in 2106. Probably most system would be 64bit by that date and so the Unix TS itself.
I recently had to fix this bug in my software. Now I store file TS as 48bit unsigned unix TS. Should be enough for livespan of that civilization ;)
@splorp - Thanks for posting this. I have always resisted posting wikipedia stuff - like the Atari Video Music[1] in favour of blogs etc of the same subject. But now I realize that some stuff is so rare that wikipedia may be the only source of truth on the subject.
also - thanks to the article my retirement date is moved by two years. originally I was going to avoid Y2K38, but now the Y2K36 bug with NNTP is going to be more serious. I plan to be offgrid in a unibomber cabin in the great white north woods...
Anyway, I think that making Unix epoch signed was one of the biggest mistakes in that case. When you design stuff that cannot live for at least 100 years, you do it wrong imo.
Having Unix TS unsigned 32bit, problem would surface in 2106. Probably most system would be 64bit by that date and so the Unix TS itself.
I recently had to fix this bug in my software. Now I store file TS as 48bit unsigned unix TS. Should be enough for livespan of that civilization ;)
also - thanks to the article my retirement date is moved by two years. originally I was going to avoid Y2K38, but now the Y2K36 bug with NNTP is going to be more serious. I plan to be offgrid in a unibomber cabin in the great white north woods...
[1] - https://en.wikipedia.org/wiki/Atari_Video_Music
Although, I will have to add a few missing entries related to Newton OS.