On Sunday, 3 August 2025 at 22:51:48 UTC, 0xEAB wrote:
> On Saturday, 2 August 2025 at 21:51:24 UTC, kdevel wrote:
>> On Friday, 1 August 2025 at 21:18:24 UTC, 0xEAB wrote:
>>>>> [...]
>>>>> It’s Win32’s unit of time.
>>>>
>>>> Do you have any reference to MS documentation which defines "hnsecs"?
>>>
>>> Sure, check out `FILETIME`:
>>> <https://learn.microsoft.com/en-us/windows/win32/api/minwinbase/ns-minwinbase-filetime>
>>
>> My browser cannot find any of the strings "hns" and "hecto" on that page.
>> (That tics are 100 ns long is not disputed).
>
> Looking at the quote “the number of 100-nanosecond intervals” — what else would the prefix “100-” mean if not “hecto”?

So there is no reference to /MS/ documentation which /literally/
defines those abbreviations "hns", "hnsecs" etc.

On Thursday, 31 July 2025 at 21:34:03 UTC, kdevel wrote:
> I would like to suggest the following improvements:
>
> - Remove "hnsecs" [2]. Every time I read this I am under the
>   impression that somebody is mocking the SI prefix system [3].
>   My suggestions [4] and [5] are of 2019.

"remove" from outputs, I would agree. In that linked thread, I think I agreed with you on that (just print 100 ns instead of 1 hnsecs), or even better, just print the decimal (which is actually trivial, you don't even need it as a float). I might work on this.

In terms of hnsecs, I don't think we can remove it. But we can redefine it to mean "hundred nanoseconds".

-Steve