Re: [Scheme-reports] current-posix-second is a disastrous mistake Ray Dillinger (17 Dec 2010 00:39 UTC)
Re: current-posix-second is a disastrous mistake Taylor R Campbell (17 Dec 2010 03:41 UTC)
Re: [Scheme-reports] current-posix-second is a disastrous mistake Taylor R Campbell (17 Dec 2010 03:41 UTC)
Re: current-posix-second is a disastrous mistake Taylor R Campbell (17 Dec 2010 16:41 UTC)
Re: [Scheme-reports] current-posix-second is a disastrous mistake Taylor R Campbell (17 Dec 2010 16:41 UTC)

Re: [Scheme-reports] current-posix-second is a disastrous mistake Ray Dillinger 17 Dec 2010 00:36 UTC

In practice, on machines with POSIX time available, there is no
error in any interval which does not include the midnight following
June 30 or December 31 in any year.  Assuring that condition
is sufficient for the accuracy of most short-term timing
applications using the POSIX-ish calendrical second.

Long-term timing applications are usually denoted in civil time,
rather than absolute time, which sort-of justifies the POSIX
approach to leap seconds; POSIX seconds approximate civil-time
seconds in the long run.

				Bear

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports