Linked by Thom Holwerda on Fri 28th Oct 2005 11:17 UTC
Thread beginning with comment 52520
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
Windows developers have many choices and Microsoft provides many ways NOT to use multithreading in Apps.
Some of these are a hangover from early non preemptive versions of Windows that used to run cooperative multitasking around the message loop.
There are asynch sockets calls you can use instead of forking processes. There are windows timers which can fire a regular event into the message loop.
No doubt there are other alternatives to threads.
There is plenty of support for threads in Windows but they may not be the natural thing to do. In BEOS not spawning a thread would generally be a very peverse choice.
I bet most modern apps on Windows are multithreaded, it helps to stop the GUI from locking up for a start.