On Fri, 29 Dec 2006, Rob Seaman wrote:
Folks keep fretting here about retrieving lists of leap seconds
autonomously, although no specific use case is proffered about why
one needs to use UTC to measure intervals across various and sundry
leap second events.
You need to do so in order to
On Fri 2006-12-29T07:43:56 +, Tony Finch hath writ:
Astronomers still count Julian
years (365.25 days instead of exact years) when dealing with long MJD
intervals.
Such intervals are almost always expressed in the IAU's time scale of
Terrestrial Time (TT) which is taken to be a more
On Thu 2006-12-28T18:31:43 -0700, M. Warner Losh hath writ:
Let's turn the question around. What would the harm be if |DUT1| were
1.1s? 1.5s? 2.0s? Contrast this with the harm and difficulty that
the current 6 month scheduling window affords.
I have previously indicated that I believe this
Tony Finch wrote:
You need to do so in order to implement an accurate clock, since
the clock produces interval time and you need a way to convert its
output to time of day.
As Steve Allen has pointed out, it is in the nature of a clock to be
reset on occasion. What is NTP but a mechanism for
Rob Seaman scripsit:
Seems like? Chances are? Pick some other random technical issue -
say, automobile airbags, standardized educational testing, the lead
content of pigment in children's crayons, and so forth and so on.
Would seems like and chances are be phrases you would want to see
in
On 2006-12-09, Clive D.W. Feather challenged, and I couldn't resist:
For something more challenging, try the 8 Bank Holidays in England:
...
(8) Second weekday after 24th December.
second weekday after 24th December in Gregorian year( Y )
= Gregorian calendar( Y, December, 26
On Fri 2006-12-29T09:25:33 +, Clive D.W. Feather hath writ:
Why is this challenging? It's whichever of 23 to 29 November (inclusive) is
a Friday.
Yes, and without bothering to patch a version of the old Tcl/Tk ical
well enough to run on what I have here, I believe that is pretty much
the
