[TUHS] The 2038 bug...
norman at oclsc.org
Sat Jan 9 18:44:28 AEST 2021
Less ugly would be to declare time_t to be unsigned instead of signed...
It would break less code... Making time_t 64 bits also breaks code, even if
you declare you don't care about binary compat since many older apps know
time_t is 32-bits.
I remember chatting in 1998 with a consultant who worked with
clients in the financial industry. They still used 32-bit systems
at the time, and had already converted critical programs (I don't
know whether that included parts of libc or they had their own
conversion routines) to make time_t unsigned.
It mattered early to those folks because of 40-year bonds.
That suggests to me that the financial-services world may have
a head start on the 2038 problem, but I fear many others are
still lagging behind. 64 bits will help but not as much for
embedded systems and legacy stuff.
Us hobbyists will doubtless have fun too, as we already do
(ask Warren) when running the earliest existing UNIX images,
in which times are stored in sixtieths of a second.
More information about the TUHS