Ulrich Windl wrote:
[EMAIL PROTECTED] (Danny Mayer) writes:
[...]
Well VMS always used 64 bits for time. Windows has now added a 64 bit
version of time_t and introduced 64-bit time functions. I don't think
that the *BSD's will be far behind. Dunno about Linux or Solaris.
Talking about 128bit time formats or so: With today's computing power (just
think of MP3 decoders), a switch to BCD coded time in 128 bit should be
sufficient:
Byte#: 1 2 3 4 5 6 7 8 910 111213 141516
Value:2006-07-18 09:26:13.12 1234 567890 123456
So you'd have significant sub-picosecond resolution and peace until year
"9999".
Not at all, unfortunately!
Your time format is perfect for recording civilian events, but just as
useless as "UTC_with_pretend_no_leapseconds" for NTP which needs a
monotonic time scale. :-(
I.e. we need both ISO style date/time and TAI, and it is only for past
events that you can know how to do an exact conversion to/from these
formats.
Terje
--
- <[EMAIL PROTECTED]>
"almost all programming can be viewed as an exercise in caching"
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
