I.e., use a double parameter that specifies seconds, instead of an uint32_t that specifies milliseconds.
This can have surprising and sometimes unpleasant consequences; see https://0.30000000000000004.com
This can have surprising and sometimes unpleasant consequences; see https://0.30000000000000004.com
No ambiguity for the programmer as to what the underlying units are, and no unnecessary int/float conversions. All the book-keeping and conversions are taken care of by the compiler with zero run-time size or perf overhead.
Using an uint64_t (instead of uint32_t or double) to carry "opaque ticks", and a handful conversion function to convert to real-world time units is fine and just a few lines of code.
http://www-users.math.umn.edu/~arnold//disasters/patriot.htm...
No they weren't using floats. The article you've linked to says this really clearly.
> This calculation was performed using a 24 bit fixed point register
They meant fixed precision not fixed point math.