On Wed, 27 Dec 2006, John Cowan wrote:
>
> If we confine ourselves to the Gregorian calendar, a time interval can
> be safely represented as a triple of months, minutes, and seconds.
It seems to me that that would put too much complexity at too low a level
but still without enough complexity to deal with the whole problem. How
does your proposal deal with local time zone changes, e.g. "same time
tomorrow", or times based on weeks, e.g. "last thursday in the month"? I
don't see much point in having an intermediate stage between day counts
and fully broken down dates. Similarly for times, I favour a split between
interval time (which the RTC would produce) and broken-down time of day
plus day count (with leap seconds and local time handled in the latter
layer).
Tony.
--
f.a.n.finch <dot_at_dotat.at> http://dotat.at/
FISHER GERMAN BIGHT HUMBER: NORTHWEST BACKING SOUTH 4 OR 5, INCREASING 6 OR 7.
SLIGHT OR MODERATE, OCCASIONALLY ROUGH LATER. OCCASIONAL RAIN. MODERATE OR
GOOD.
Received on Thu Dec 28 2006 - 09:45:30 PST