|
|
Subscribe / Log in / New account

Year 2038 preparations in 3.17 - why not use floating point?

Year 2038 preparations in 3.17 - why not use floating point?

Posted Aug 14, 2014 12:09 UTC (Thu) by JGR (subscriber, #93631)
In reply to: Year 2038 preparations in 3.17 - why not use floating point? by rbthomas
Parent article: Year 2038 preparations in 3.17

What does going to 64 bit floating point give you that 64 bit seconds + nanoseconds does not?
Migrating to floating point would be far more painful than bumping an integer from 32 to 64 bits.

Being able to change the epoch at will, and being able to regularly update the clock with small increment ticks, imply storing the "master" value in some other higher-precision format, in which case you might as well just use that for everything.


to post comments


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds