In message: p06230903c587bf762...@[192.168.0.5]
Jonathan E. Hardis jhar...@tcs.wap.org writes:
: It is also remarkable that about one-fourth (12) of the U.S. states
: are bisected by timezones
:
: 14 states:
:
: Alaska, Idaho, Oregon, Nevada, North Dakota, South Dakota, Nebraska,
:
Magnus Danielson wrote:
Hate to nitpick you, but that is a different representation, not a
different interpretation.
Even in technical documentation, words retain their broader meanings.
I was suggesting that instead of interpreting sexagesimal values as
sets of integers, one can
In message: alpine.lsu.2.00.0901051603040.10...@hermes-1.csi.cam.ac.uk
Tony Finch d...@dotat.at writes:
: On Mon, 5 Jan 2009, Poul-Henning Kamp wrote:
:
: The proper thing for the future is either a int128_t 64.64
: fixedpoint time representation or a double ditto.
:
: Do you mean
M. Warner Losh wrote:
And how are leap seconds represented in this convention?
They aren't. The choice of the underlying time or angular scale is an
orthogonal issue.
Begin aside:
To comment further, the apparent separate fields of sexagesimal
fractions are not generally not
On Mon, 5 Jan 2009, Poul-Henning Kamp wrote:
The proper thing for the future is either a int128_t 64.64
fixedpoint time representation or a double ditto.
Do you mean double as in the C type? Which is surely too small - you want
quad-precision FP or perhaps double double (paired doubles to get
M. Warner Losh wrote:
So leap seconds are hard, eh?
You know, it isn't as if we haven't been talking about this stuff for
nine years. We all know where the bodies are buried. Leap seconds
can be a bit awkward. Not having them is also awkward. But for most
purposes, a more frequent
On Mon, 5 Jan 2009, Rob Seaman wrote:
The recent leap second passed (yet again) with no major issues.
Wrong.
Loads of Oracle RAC servers crashed because of a bug triggered by the
clock going backwards.
http://www.merit.edu/mail.archives/nanog/msg13857.html
Many time dissemination systems got
Rob Seaman sea...@noao.edu wrote:
If you're looking for an Arizona-based standard, surely Sedona is the
benchmark :-)
http://www.lovesedona.com/01.htm
Yup, been there once for a UFO/spiritual conference. Very beautiful
indeed.
MS
___
LEAPSECS
Rob,
Rob Seaman skrev:
Magnus Danielson wrote:
time_t = d*86400 + h*3600 + m*60 + s
Just thought I'd note an alternate interpretation. In NOAO's widely
distributed image processing system (IRAF) a sexagesimal number is a
double precision floating point number, not an integer:
In message: alpine.lsu.2.00.0901051819010.10...@hermes-1.csi.cam.ac.uk
Tony Finch d...@dotat.at writes:
: On Mon, 5 Jan 2009, Rob Seaman wrote:
:
: The recent leap second passed (yet again) with no major issues.
:
: Wrong.
:
: Loads of Oracle RAC servers crashed because of a bug
In message: 496214f4.1090...@rubidium.dyndns.org
Magnus Danielson mag...@rubidium.dyndns.org writes:
: Rob,
:
: Rob Seaman skrev:
: Magnus Danielson wrote:
:
: time_t = d*86400 + h*3600 + m*60 + s
:
: Just thought I'd note an alternate interpretation. In NOAO's widely
:
Tony Finch wrote:
On Mon, 5 Jan 2009, Rob Seaman wrote:
The recent leap second passed (yet again) with no major issues.
Wrong.
Loads of Oracle RAC servers crashed because of a bug triggered by the
clock going backwards.
http://www.merit.edu/mail.archives/nanog/msg13857.html
Where the
In message: 20090105102452.gj14...@fysh.org
Zefram zef...@fysh.org writes:
: M. Warner Losh wrote:
: So time_t is effectively defined in POSIX to be:
:
: d * 86400 + min(tod(x), 86399)
:
: where d is the number of days since 01-01-1970, and tod is the second
: since midnight
In message: 51302552-875a-4e99-937c-bdba26ae0...@noao.edu
Rob Seaman sea...@noao.edu writes:
: Tony Finch wrote:
:
: On Mon, 5 Jan 2009, Rob Seaman wrote:
:
: The recent leap second passed (yet again) with no major issues.
:
: Wrong.
:
: Loads of Oracle RAC servers crashed
In message alpine.lsu.2.00.0901051603040.10...@hermes-1.csi.cam.ac.uk, Tony F
inch writes:
On Mon, 5 Jan 2009, Poul-Henning Kamp wrote:
The proper thing for the future is either a int128_t 64.64
fixedpoint time representation or a double ditto.
Do you mean double as in the C type? Which is
Zefram skrev:
M. Warner Losh wrote:
So time_t is effectively defined in POSIX to be:
d * 86400 + min(tod(x), 86399)
where d is the number of days since 01-01-1970, and tod is the second
since midnight within the day.
Actually it's simpler than that. The expression given by POSIX
Magnus Danielson wrote:
time_t = d*86400 + h*3600 + m*60 + s
Just thought I'd note an alternate interpretation. In NOAO's widely
distributed image processing system (IRAF) a sexagesimal number is a
double precision floating point number, not an integer:
12:34:56 = 12 + 34/60 +
Rob Seaman skrev:
Magnus Danielson wrote:
Hate to nitpick you, but that is a different representation, not a
different interpretation.
Even in technical documentation, words retain their broader meanings. I
was suggesting that instead of interpreting sexagesimal values as sets
of
M. Warner Losh skrev:
In message: 20090105102452.gj14...@fysh.org
Zefram zef...@fysh.org writes:
: M. Warner Losh wrote:
: So time_t is effectively defined in POSIX to be:
:
: d * 86400 + min(tod(x), 86399)
:
: where d is the number of days since 01-01-1970, and tod is the second
[[ continuation of a discussion from time-nuts ]]
In message: 496157c4.2050...@erols.com
Chuck Harris cfhar...@erols.com writes:
: Magnus Danielson wrote:
: Chuck Harris skrev:
: One of us is confused about what time_t is... I think it is
: you.
:
: I know of three different
M. Warner Losh skrev:
[[ continuation of a discussion from time-nuts ]]
In message: 496157c4.2050...@erols.com
Chuck Harris cfhar...@erols.com writes:
: Magnus Danielson wrote:
: Chuck Harris skrev:
: One of us is confused about what time_t is... I think it is
: you.
:
: I
Rob,
Rob Seaman skrev:
M. Warner Losh wrote:
POSIX doesn't support leap seconds.
I'm curious. Is this the only widely recognized shortcoming of POSIX?
I mean - either POSIX is riddled with numerous other mistakes - or this
is the only issue remaining to address before POSIX is perfected
In message: 5806d024-146d-43e4-aea0-a7aa514e3...@noao.edu
Rob Seaman sea...@noao.edu writes:
: M. Warner Losh wrote:
:
: POSIX doesn't support leap seconds.
:
: I'm curious. Is this the only widely recognized shortcoming of POSIX?
No. There's others, but they are generally minor
Hello all,
This discussion about the meaning of UNIX and POSIX time_t in terms of
UTC/TAI/whatnot that has just moved here from the time-nuts list has
pushed some of my religious hot buttons, so I feel the rhetorical
imperative to state my position.
But first a disclaimer: I absolutely do not
M. Warner Losh i...@bsdimp.com wrote:
Almost all the posix mistakes are
relegated to tty handling :).
That's another major reason why I hate POSIX. I will never adopt termios
and I'm very proud to have the original sgtty in 4.3BSD-Quasijarus instead!
MS
In message: 0901050622.aa00...@ivan.harhan.org
msoko...@ivan.harhan.org (Michael Sokolov) writes:
: under my control that contains a time_t value, that value will measure
: the rotation angle of a clock in Phoenix, AZ, *NOT* time of any kind.
Is that an adjusted or unadjusted clock?
M. Warner Losh i...@bsdimp.com wrote:
Is that an adjusted or unadjusted clock? :)
Adjusted for what?
MS
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
In message 5806d024-146d-43e4-aea0-a7aa514e3...@noao.edu, Rob Seaman writes:
M. Warner Losh wrote:
POSIX doesn't support leap seconds.
I'm curious. Is this the only widely recognized shortcoming of POSIX?
No, POSIX has numerous defects and bad choices, but barring a major
effort by major
Poul-Henning,
Poul-Henning Kamp skrev:
In message 5806d024-146d-43e4-aea0-a7aa514e3...@noao.edu, Rob Seaman writes:
M. Warner Losh wrote:
POSIX doesn't support leap seconds.
I'm curious. Is this the only widely recognized shortcoming of POSIX?
No, POSIX has numerous defects and bad
29 matches
Mail list logo
