multithreading

[Nils Kassube]

Cliff Wells <logiplexsoftware at earthlink.net> writes:

> I think this is a bit of an overstatement.  Many problems are best
> expressed as multithreaded programs. Trying to solve a naturally
> multithreaded problem as a single-threaded app can be more complex
> and error-prone than the natural

man fork

Often you do not need shared memory space. Dealing with shared memory
and multiple threads can introduce subtle bugs that will be extremely
hard to reproduce. Using multiple processes is in many cases the
better solution (on real operating systems).