To time_t or not to time_t, that's the tea
Considering the real time clock on the Asspull IIIx runs at an offset from the host's reported time and defaults to January 1 1984 (you're supposed to reset it), and considering this is the only 64-bit register on the system... I wonder if that's worth the effort?
GCC actually has to pull in some extra support routines just to let the time functions handle such a large value.
If I make its time_t 32-bit it'll cut its range, but it'll look more contemporary and simplifies the compiled code.
What do you think?
Fake systems can have little a Y2038 bug as a treat
Keep it as it is now
Yes, I did ask the same thing on Mastodon. It was pretty nearly a 50/50 split. But I feel like I might get a bigger audience on Tumblr (especially if @foone helps out) and I'm curious.

















