|
From: | Paul Eggert |
Subject: | bug#55163: 29.0.50; master 4a1f69ebca (TICKS . HZ) for current-time broke lsp-mode |
Date: | Sun, 1 May 2022 08:08:00 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 |
On 4/30/22 22:40, Eli Zaretskii wrote:
Using "universal" will IMO make the discovery even more difficult, because no one will think of looking up time functions under "universal".
Yes, it shouldn't be "universal" by itself. It should be (time-now 'universal) or something like that, where the context is clear.
I did consider "UTC"; unfortunately something like (time-now 'UTC) would imply that the timestamps include leap seconds, which they typically don't. "Universal" is a more-general term that includes both UTC and POSIX time (the latter omits leap seconds).
..
I still don't understand why we don't want to use "time-" as the prefix of these APIs.
Sure, we can stick with "time-" for new functions.
[Prev in Thread] | Current Thread | [Next in Thread] |