Re: New draft (#2) of SRFI 226: Control Features
Marc Nieper-WiÃkirchen 13 Oct 2022 06:39 UTC
Am Do., 13. Okt. 2022 um 02:02 Uhr schrieb John Cowan <xxxxxx@ccil.org>:
>
>
>
> On Mon, Oct 10, 2022 at 12:48 PM Marc Nieper-Wißkirchen <xxxxxx@gmail.com> wrote:
>
>> (epoch-time)
>> Returns the POSIX epoch as a time value.
>
>
> This should be split into posix-epoch-time and tai-epoch-time.
This procedure (epoch-time) aims to give the time value for at least
one event (on the worldline of Earth). The event is itself arbitrary
as long as it is well-defined. It is up to a higher-level API (like
SRFI 19) that consumes this foundational API to provide time values
for other events, e.g. for every UTC calendar datum.
Note that "00:00:00 UTC on 1 January 1970" is a well-defined absolute
time (quantity) independent of any unit or epoch chosen.
What do you mean by "tai-epoch-time", by the way?
>> > Nanoseconds would be fine with me as well. But what's the purpose of
>> > jiffies in R7RS then?
>
>
> Primarily because that's the way Common Lisp does it. But it's also the case that the jiffy system adapts well to a broad variety of systems, which is what R7RS-small was designed for.
Would it make sense to define a jiffy as a nanosecond for
implementations of the large language?