|
From: | Paul Eggert |
Subject: | bug#55163: 29.0.50; master 4a1f69ebca (TICKS . HZ) for current-time broke lsp-mode |
Date: | Mon, 2 May 2022 10:27:14 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 |
On 5/1/22 09:43, Eli Zaretskii wrote:
one such occurrence won't be enough, not in my book.
If one such occurrence makes Emacs significantly slower for a common-enough use, it can be important enough to improve Emacs. And as I wrote, I'm sure there are more occurrences.
What's the difference, for the purpose of this discussion, between having the code in C and having it in internal Lisp functions?
The internal Lisp function would need an efficient way to get a file's timestamp. It can't do that if there's no C primitive to do it.
What we have established is that Emacs apps need to be able to measure time intervals, not that they need a monotonic clock. Functions for measuring time intervals can be built on functions that return monotonic clock time, but they can also be built on other bases that have very little with actual time stamps.
What other bases would these be? Monotonic clocks are relatively portable; other methods that come to mind are not.
[Prev in Thread] | Current Thread | [Next in Thread] |