Tim Shepard scripsit:
> A computer system could represent UTC time in a way which also makes
> this clear, for example by a structure or abstract data type which
> includes in it (1) the day number and (2) how-many nanoseconds are we
> into this day. When executing a leap second insertion, we would get
> all the way up to 86,400,999,999,999 nano seconds in the day before we
> wrapped around that field to zero and incremented the day number (one
> nanosecond later).
How is this really different from using broken-out time and allowing
the seconds field to go up to 60?
Current Posix broken-out time has a field for "DST in effect", which can
be ignored most of the time except during the fall transition hour, when
it is on for the first run from 02:00:00 to 02:59:59 and off for the
second run.
--
My confusion is rapidly waxing John Cowan
For XML Schema's too taxing: cowan_at_ccil.org
I'd use DTDs http://www.reutershealth.com
If they had local trees -- http://www.ccil.org/~cowan
I think I best switch to RELAX NG.
Received on Sat Feb 04 2006 - 10:40:37 PST