"EEeeks!" for both the FreeBSD and MinGW results (not your fault obviously).
Can you try again with a `Delay(10)` and `Delay(100)` to see what
happens? And if they behave nicely (i.e. give results of 10s upward and
100s upward, respectively), can you spare some time and try to figure
out what the "sweet spot" is?
In case you're curious what I'm doing: I'm testing whether
`std::this_thread::sleep_for()` is - as advertised by the C++11 standard
- suitable as a portable way of waiting for _at least_ the specified
duration. If that is the case, then `Delay(msec)` should wait for at
least the specified number of millisconds, and thus the entire program
(doing 1000 such invocations in a loop) should wait for at least the
specified number of seconds.
But alas! Standards are only as good as the rigorosity by which they are
Am 13.02.2019 um 23:02 schrieb ingo:
> in news:XnsA9F5E84C73117seed7@news.povray.org ingo wrote:
> On Win with Mingwing
> $ gcc --version
> gcc.exe (Rev1, Built by MSYS2 project) 8.2.1 20181207
> Copyright (C) 2018 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> $ time test.exe
> real 0m0.065s
> user 0m0.015s
> sys 0m0.015s
Post a reply to this message