M. Warner Losh said:
time_t is so totally broken, it isn't funny. That's the closest thing
to a standardized API there is for time. All others are stuff folks
have done here or there, but they aren't universal enough to be
considered.
Too bad the problems with time_t are well known, well
On Dec 26, 2006, at 23:02, M. Warner Losh wrote:
Of course, needing to know TAI-UTC offsets leads one to interesting
situations. What does one do if one has TAI time, but not UTC and a
conversion is asked for?
If it's a time in the future rather than just the current time, the
thread may
On Dec 27, 2006, at 14:32, Poul-Henning Kamp wrote:
It's impossible to accurately represent a millisecond using binary
fractions. That would be unacceptable for most sub-second use.
Reality check: with a 32bit fraction, the error would be 69 ps.
...which accumulates in arithmetic and causes
Rob Seaman scripsit:
Mucking with leap seconds is equivalent to redefining the
concept of a day.
Very true. And adopting the Egyptian-Roman calendar redefined
the concept of a month. Somehow civilization survived.
--
John Cowan [EMAIL PROTECTED] http://ccil.org/~cowan
I must confess
On 27 Dec 2006 at 20:57, John Cowan wrote:
Very true. And adopting the Egyptian-Roman calendar redefined
the concept of a month. Somehow civilization survived.
Keeping months in sync with phases of the moon apparently turned out
to be insufficiently important to civilization to require it as
