|No such thing as a small change|
Re^4: pipe fork win32by BrowserUk (Pope)
|on Aug 26, 2012 at 14:05 UTC||Need Help??|
Firstly, this perl-internals implementation bug is totally unrelated to the issue of whether "sleep work on multiple threads".
Secondly, the "bug" in that RT isn't a bug.
It basically says that sleep doesn't guarantee to return exactly when you asked for it to. But I'm not aware of any OS that gives such a guarantee, It is documented to sleep for at least the number of seconds requested.
It does not say that it will break out of a broken device driver, or debugger, nor VM, nor preempt a higher priority CPU-intensive thread or process.
I'm really confused why you thought it was relevant to raise that non-related, non-issue in this context?
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.