8 ms·
2038? Does this have to do with Epoch time ending somehow?
by expathacker 8y ago
2038? Does this have to do with Epoch time ending somehow?
- philwelch 8y agoYeah, coal-powered computers can only handle 32-bit integers ;)
- cozzyd 8y agoIn 2038, the coal company clocks roll back to 1901, when all was good in the world for them.
- kbutler 8y ago...to 1970...
- est31 8y ago... which was a very great year for lignite mining: https://www.oeko.de/fileadmin/oekodoc/BET2017-Hermann-Oeko-Institut.pdf#page=2 https://www.oeko.de/fileadmin/oekodoc/BET2017-Hermann-Oeko-I...
- jcranmer 8y agoNo, it rolls over to 1901. time_t is a signed value, and 2038 is when it rolls over from 2³¹ - 1 to -2³¹. That would be 2 billion seconds before 1970, or 1901.
- cozzyd 8y agoIf our Unix forefathers had the foresight to make time_t unsigned, then we wouldn't have to worry about this problem until after 2100.
- 2038AD 8y agoI would guess, when originally suggested, it was $current_year + 2 decades.