[fpc-pascal] Very vague gettickcount64 description?

Yuriy Sydorov jura at cp-lab.com
Fri Sep 6 18:15:11 CEST 2019

On 06.09.2019 17:06, Tomas Hajny wrote:
> The documentation is vague on purpose - due to the variety of platforms supported by FPC and the low-level nature of 
> GetTickCount, we do not want to guarantee specific units (GetTickCount is supposed to be supported directly by the 
> platform rather than having an additional RTL layer possibly unifying differences in platform behaviour on top of it).

IMO the result of GetTickCount without defined measure units is useless. Historically the result of GetTickCount is 
milliseconds (as in the corresponding winapi function). Implementations of GetTickCount for all major platforms also 
return milliseconds. If there are platform implementations which return different units for GetTickCount, they should be 
fixed. There is no real use for GetTickCount without knowing its units.

So the units of GetTickCount must be milliseconds for all platforms. The only variables - how often the result of 
GetTickCount is changed and its starting value.


More information about the fpc-pascal mailing list