,
4 tweets,
1 min read
Read on Twitter
So that thing you didn't realize you needed to do in order to prepare for the 2038 epochalypes is test your code on a Raspberry Pi running FreeBSD. 
You've tested your code where (long) and (time_t) are both 32-bits. And you've tested your code where (long) and (time_t) are both 64-bits. But you haven't tested your code where (long) is 32-bits but (time_t) is 64-bits. As shown in the picture below:
So what happens is that sometimes in code:
long x = time(0);
And come 2038, this will mysteriously fail on some platforms because you've only tested on normal platforms.
long x = time(0);
And come 2038, this will mysteriously fail on some platforms because you've only tested on normal platforms.
The reason this is important is because all Linux 32-bit is still broken, using 32-bit (time_t). At some point in the next few years they are going to have to fix this, and it's probably going to look like FreeBSD's solution.
