Re: [fpc-pascal] Very vague gettickcount64 description?

2019-09-07 Thread Zoe Peterson
> From: Martin Frb > But that does not mean, it needs to be changed on existing targets. > And if it is not going to be changed, then it can be documented. I agree with everything Martin has said, though IMO GetTickCount must return values in ms on every single platform and any that can't should

Re: [fpc-pascal] Very vague gettickcount64 description?

2019-09-07 Thread Martin Frb
On 08/09/2019 02:07, Alexander Grotewohl wrote: but the resolution is not a ms at all. every call to gettickcount is something like 10-15ms or so off. you'd be lucky to call it a ms after it was updated by the os. do we document that too? As I said: "The minimum resolution may vary, and may be

Re: [fpc-pascal] Very vague gettickcount64 description?

2019-09-07 Thread Luca Olivetti
El 7/9/19 a les 13:38, Michael Van Canneyt ha escrit: On Sat, 7 Sep 2019, Marco van de Voort wrote: Op 2019-09-06 om 20:02 schreef Michael Van Canneyt: What I will do is explain in the documentation why the units are not mentioned. Can we remove the division in *nix also ? If ms resolut

Re: [fpc-pascal] Very vague gettickcount64 description?

2019-09-07 Thread Alexander Grotewohl
but the resolution is not a ms at all. every call to gettickcount is something like 10-15ms or so off. you'd be lucky to call it a ms after it was updated by the os. do we document that too?--Alexander Grotewohlhttp://dcclost.comOn Sep 7, 2019 7:41 PM, Martin Frb wrote:On 07/09/2019 21:42, Zoe Pet

Re: [fpc-pascal] Very vague gettickcount64 description?

2019-09-07 Thread Martin Frb
On 07/09/2019 21:42, Zoe Peterson wrote: GetTickCount and GetTickCount64 are Windows API functions that are explicitly documented as returning milliseconds, and FPC on Unix up to now is has matched that. Why in the world would you think that changing that behavior would be a good idea, *especiall

Re: [fpc-pascal] Very vague gettickcount64 description?

2019-09-07 Thread Martok
Am 07.09.2019 um 21:42 schrieb Zoe Peterson: > GetTickCount and GetTickCount64 are Windows API functions that are > explicitly documented as returning milliseconds, [...] > As an FPC user, this seems like an astoundingly bad decision to even > be considering. But it perfectly fits the "recent" tr

Re: [fpc-pascal] Very vague gettickcount64 description?

2019-09-07 Thread Zoe Peterson
GetTickCount and GetTickCount64 are Windows API functions that are explicitly documented as returning milliseconds, and FPC on Unix up to now is has matched that. Why in the world would you think that changing that behavior would be a good idea, *especially* if you keep the function name the sa

Re: [fpc-pascal] Very vague gettickcount64 description?

2019-09-07 Thread Michael Van Canneyt
On Sat, 7 Sep 2019, Marco van de Voort wrote: Op 2019-09-06 om 20:02 schreef Michael Van Canneyt: What I will do is explain in the documentation why the units are not mentioned. Can we remove the division in *nix also ? If ms resolution is not supported, then why divide the us/ns ? It s

Re: [fpc-pascal] Very vague gettickcount64 description?

2019-09-07 Thread Marco van de Voort
Op 2019-09-06 om 20:02 schreef Michael Van Canneyt: What I will do is explain in the documentation why the units are not mentioned. Can we remove the division in *nix also ? If ms resolution is not supported, then why divide the us/ns ? It serves no purpose, if rollover and unit size are n