2 ms·
Sounds a bit like a solution in search of a problem. There's no reason you can't use a 64-bit value in a 32-bit system. Much simpler to access the 64-bit valu
by simonblack 4y ago
Sounds a bit like a solution in search of a problem.
There's no reason you can't use a 64-bit value in a 32-bit system. Much simpler to
access the 64-bit value as two 32-bit words than propose a whole new confusing and ambiguous system.
In terms of current-time coding, the only time that second hi-order word would be used is when the lo-order word overflows, and on initialisation of the 64-bit variable. And if needs must, it could even be a compiled-in value, seeing it will only change once in every 68 years.
- touchpadder 4y agoThere's nothing ambiguous when the epoch is known and the previous one is long gone. So you're confused about restarting a timer every 50 years, ok. It's not true that it's much simpler to work with two 32bit words for a date than working with simply restarted clock. Basic arithmetics cannot be used reliably so every operation must go through a library like i.e. bigint used to require. This complicates the system and the goal of having a reliable 32bit date format in the future is for simplicity.