[Interest] Expected event execution order in this multi-thread application

Konstantin Shegunov kshegunov at gmail.com
Mon Sep 30 17:24:09 CEST 2019

On Mon, Sep 30, 2019 at 6:07 PM Ola Røer Thorsen <ola at silentwings.no> wrote:

> What's wrong with the sleep functions in particular?

They're uninterruptible. In 99.9(9)% of cases there's a better way to
suspend a thread for some time than unconditionally putting it to sleep.

> Are they worse than calling for example unistd.h's "usleep" or
> "std::this_thread::sleep_for(std::chrono::milliseconds(x));"?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20190930/b954e9e7/attachment.html>

More information about the Interest mailing list