Date: Thu, 27 May 2021 05:05:15 -0000 (UTC)
From: [email protected] (Michael van Elst)
Message-ID: <[email protected]>
| [email protected] (Michael van Elst) writes:
|
| >Either direction mstohz or hztoms should better always round up to
| >guarantee a minimal delay.
|
| And both should be replaced by hztous()/ustohz().
While changing ms to us is probably a good idea, when a change happens,
the "hz" part should be changed too.
hz is (a unit of) a measure of frequency, ms (or us) is (a unit of) a
measure of time (duration) - converting one to the other makes no sense.
What these functions/macros do is convert between ms (or us) and ticks
(another measure of a duration), not hz, so the misleading "hz" part of
the name should be removed (changed) if a new macro/function is to be invented.
(The benefit isn't worth it to justify changing the current existing names,
but we shouldn't persist with nonsense if we're doing something new.)
kre
ps: note that the variable "hz" (and the macro HZ) are used correctly --
their values are frequencies (ticks/second).
