News for hackers. Stuff that matters.
Re:2038: Only 21 years away by lazyjones on Tuesday March 21, 2017 @11:48AM (#13923271)
Meh, we'll just redefine time_t as (signed) seconds since 2000 or so and subtract 30 years in seconds from all timestamps ... ;-)
Re:2038: Only 21 years away by devcpp on Tuesday March 21, 2017 @04:00PM (#13925661)
All transactions between 1970 and 1999 have/will now occur between 2038 and 2068.
Re:2038: Only 21 years away by btilly on Tuesday March 21, 2017 @11:52AM (#13923314)
No, you make it time_t (unsigned) seconds since the epoch. That pushes the problem out 70+ years and doesn't break any binary APIs.
Re:2038: Only 21 years away by simias on Tuesday March 21, 2017 @12:00PM (#13923406)
Changing from signed to unsigned is very much an ABI break.
Re:2038: Only 21 years away by btilly on Tuesday March 21, 2017 @01:59PM (#13924572)
Yes, it is an ABI break.

But if you took code that was compiled with each version, the binary data that they will produce/consume for dates between the epoch and 2038 is bit for bit identical.