On 17 Jan 2019 at 15:57, Brooks Harris wrote:
> In private discussion with one member of that committee on that topic
> it was said "... but the time people would just not stop arguing!".
> Funny how everybody knows what time is but can't agree on what time
> is.
The music group Chicago discussed
On 2019-01-17 12:38 PM, Steve Allen wrote:
On Thu 2019-01-17T18:12:25+0100 Martin Burnicki hath writ:
Hm, maybe that was originally the case. I wonder whether the folks who
wrote the text just had UTC in mind when they "invented" time_t.
The best insight into the POSIX committee was posted on L
On Thu 2019-01-17T18:12:25+0100 Martin Burnicki hath writ:
> Hm, maybe that was originally the case. I wonder whether the folks who
> wrote the text just had UTC in mind when they "invented" time_t.
The best insight into the POSIX committee was posted on LEAPSECS in
2003
https://www.mail-archive.c
Steve Summit wrote:
> Martin Burnicki wrote:
>> Just a few general thoughts based on an internal note...
>
> And some very good points they were.
>
>> ...The same applies to the time_t type, IMO. If you let the system kernel
>> run on TAI or whatever then the time() function still returns a time_
On Wed 2019-01-16T22:24:46-0800 Paul Hirose hath writ:
> On 2019-01-16 1:35, Steve Allen wrote:
> >
> > Does it know that rubber seconds do not apply to timestamps in central
> > Europe made using DCF77 from 1970-01-01 to 1972-01-01?
>
> All my DLL knows is what's in the UTC file. If the file indic
