sequence of dates Arthur A. Gleckler (13 Oct 2022 05:57 UTC)
Re: sequence of dates Marc Nieper-Wißkirchen (13 Oct 2022 06:01 UTC)
Re: sequence of dates Arthur A. Gleckler (13 Oct 2022 17:31 UTC)
Re: sequence of dates Ray Dillinger (13 Oct 2022 18:03 UTC)
Re: sequence of dates Marc Nieper-Wißkirchen (13 Oct 2022 18:04 UTC)
Re: sequence of dates Arthur A. Gleckler (13 Oct 2022 18:08 UTC)
Re: sequence of dates Arthur A. Gleckler (13 Oct 2022 18:37 UTC)
Re: sequence of dates Shiro Kawai (13 Oct 2022 06:38 UTC)
Re: sequence of dates Arthur A. Gleckler (13 Oct 2022 18:04 UTC)

Re: sequence of dates Marc Nieper-Wißkirchen 13 Oct 2022 18:02 UTC

Am Do., 13. Okt. 2022 um 19:31 Uhr schrieb Arthur A. Gleckler
<xxxxxx@speechcode.com>:
>
> On Wed, Oct 12, 2022 at 11:01 PM Marc Nieper-Wißkirchen <xxxxxx@gmail.com> wrote:
>>
>> You can add 86,400 UTC "seconds" per day if you want UTC dates.
>
>
> That was the hack I was considering, but I thought that assuming 86,400 per day, even for UTC, was incorrect.

The interface possibly does not implement what I call a UTC second. A
UTC second would be longer than a TAI second on those days where a
(TAI) leap second is inserted.

While TAI seconds roughly measure the flow of proper time (of the
Earth geoid reference frame), what I call a UTC second would roughly
measure the time it takes for the Earth to rotate.

If no such thing as a UTC second is implemented, my idea can´t work.
But why don't you simply advance the day field by one? Or is this not
possible with the API?