Comment on Microsoft confirms Exchange Year 2022 problemparentComments−munchler4yUnix timestamp is hardly better, due to the Year 2038 problem. I think the only truly robust solution is to use a 64-bit integer instead.−mohaine4ytime_t solved the 2038 problem a long time ago−kristiandupont4y...not according to Wikipedia: https://en.wikipedia.org/w/index.php?title=Time_t&oldid=4507...−baq4yif you recompile the world, it did...
Comments
Unix timestamp is hardly better, due to the Year 2038 problem. I think the only truly robust solution is to use a 64-bit integer instead.
time_t solved the 2038 problem a long time ago
...not according to Wikipedia: https://en.wikipedia.org/w/index.php?title=Time_t&oldid=4507...
if you recompile the world, it did...