On Aug 18, 2006, at 12:45 PM, Norman Palardy wrote:
And empty run event is a case where the right answer is "Don't do
that"
I should say where an adequate work around is "Don't do that"
I'd agree an empty thread that you tell to run should do precisely
nothing and not consume any CPU since there is nothing for it to do.
But the work around is simple.
One that does something very simple, like I suggested, but consumes
a huge amount of CPU would be a very different serious problem
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
Even putting the code you suggested produces the same result. I
updated the bug report.
Regards,
Tomas
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
