Dan Sugalski <[EMAIL PROTECTED]> writes:
> At 09:34 PM 8/5/00 +0000, Nick Ing-Simmons wrote:
> >Dan Sugalski <[EMAIL PROTECTED]> writes:
> > >At 10:55 AM 8/2/00 +0200, Gisle Aas wrote:
> > >>All functions that return time values (seconds since epoch) should use
> > >>floating point numbers to return as much precision as the platform
> > >>supports. All functions that take time values as arguments should
> > >>work for fractional seconds if the platform supports it.
> > >
> > >Floats have resolution issues that exacerbate sub-second resolution issues.
> >
> >As an engineer I would really like to know when you are going to
> >run out of precision in double - that is forty something bits of mantissa.
> >That is more precision than you have in the real world.
>
> It's not precision, it's resolution. What do you do if your timers return
> values in 1/10ths of a second?
We might provide some additional API (via some module) where you can
make queries about the precision of timers.
--Gisle
