On Sun, Aug 05, 2007 at 06:02:11PM +0200, SZALAY Attila wrote: >> This is wrong. Note that "multithreading" is a different concept from >> spawning many processes (ie. the traditional UNIX fork() model). > You are right, but (I think) it's not harder to write a program which is > multithread than which is multiprocess.
This is also wrong. All threads in a program share address space, which means that all variables are shared by default, which means that every single non-local variable access has the potential of a race condition. Multiprocess is the complete opposite -- the address spaces are separated unless you explicitly use shared memory. (You'll still have to lock files and such, but that's comparatively easy.) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
