On Tue, 28 Apr 2009 09:59:20 -0400, Steven Schveighoffer
<[email protected]> wrote:
On Tue, 28 Apr 2009 09:51:54 -0400, dsimcha <[email protected]> wrote:
== Quote from Steven Schveighoffer ([email protected])'s article
Have you tried synchronizing on an actual object? I remember some time
back how Walter proposed removing synchronized as you have written it.
Not sure what happened for that.
The way you have written the code, assuming that the synchronized
statement is doing what you think it's doing, the call to writeln
should
be completely syncrhonous, so multithreading issues or not, it should
work.
-Steve
Good idea, still doesn't work. All of the loops just die after a few
iterations,
leaving me at 0% CPU usage. This happens on multiple win32 boxes.
Could someone
please test this on some other OS?
Latest compiler? D1 D2?
From your code:
import core.Thread
Duh. Must be D2 :) Probably latest.
-steve
