News for hackers. Stuff that matters.
Re:Windows Timer Resolution: The Great Rule Change by stinos on Monday October 05, 2020 @03:29AM (#24685386)
It shouldn’t be doing this, but it is

In my opinion this still remains the conclusion, as it has been for the past decades. I cannot remember when I read a bit on Sleep() behavior and timeBeginPeriod() but I remember that what I read was enough to make clear you just shouldn't rely on these (unless you're 100% sure the consequences are within your spec and will remain so), also not because the workarounds are also widely known (IIRC - things like using WaitForSingleObject if you need accurate Sleep).

Re:Windows Timer Resolution: The Great Rule Change by vardump on Monday October 05, 2020 @05:40AM (#24686037)
> things like using WaitForSingleObject if you need accurate Sleep

You won't get any more timing accuracy with WFSO.

Re:Windows Timer Resolution: The Great Rule Change by stinos on Monday October 05, 2020 @06:33AM (#24686345)
Yeah I see now other comments mention this as well; any idea if this has been changed then, or was the info I seem to recall having read wrong? (and is there another way to achieve it?)
Re:Windows Timer Resolution: The Great Rule Change by stinos on Tuesday October 06, 2020 @03:35AM (#24695501)
Too late to edit my other reply, but note that according to sibling comment from jlokier elsewhere, you will.