As: Windows, as in 'QueryPerformanceCounter', is returning it as a Int. (LARGE_INTEGER)
If AutoIt is not using 'QueryPerformanceCounter' to get the target value. What is it using? (or: additional info on reason(s) for it to be a float)
If AutoIt is using 'QueryPerformanceCounter' ... The only thing that makes sense to me here is that TimerInit() was implemented before 64bit value support where implemented. (in which case the question comes down to 'why not update TimerInit() to make use of the 64bit value support.)
As Valiks closing comment on ticket 2008 seems to be related to TimerDiff() (which was not the subject of the ticket) its not helping in this matter.
The general benefits would be minor. Seemingly more consistency in the returned TimerInit() data(type) in relation to windows 'QueryPerformanceCounter' and a little speedup in special AutoIt timer scripts. (Int versus float math. ... assuming of course.)
Edited by iEvKI3gv9Wrkd41u, 30 September 2011 - 08:26 AM.