Re: RFC: Higher resolution time values

[Dan Sugalski]

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.

Could we consider:

1) Defining it to be a larger integer (64-bit, say)
2) Defining a smaller resolution (ns, 10ns, or 100ns resolution)
3) Changing the base date to something more meaningful? The smithsonian 
base date, the astronomical base date, year 0 of the Chinese calendar, or 
Larry's birthday, say? Heck, Even Jan 1, 1900 would be better. (Or Jan 1, 
2000, I suppose)
4) Allowing negative times

                                        Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
[EMAIL PROTECTED]                         have teddy bears and even
                                      teddy bears get drunk