multithreading

[Cliff Wells]

On Sun, 19 May 2002 22:05:30 +0200
Nils Kassube wrote:

> "Rob Hall" <bloke at ii dot net> writes:
> 
> > Can anyone point me to a useful tutorial on multithreading?
> 
> One advice: Avoid multithreading like the plague. 
> 
> Multithreading is a very big stability risk if you don't know exactly
> what you are doing, i.e. most programmers most of the time.

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
multithreaded solution.  The argument about knowing exactly what you are doing
could be easily applied to any moderately complex programming endeavor (network
programming, GUI programming, etc).  Should these be avoided as well?  In fact,
programming itself poses the same risks. Learning to write threaded programs is
a natural step in a programmer's development.  

-- 
Cliff Wells, Software Engineer
Logiplex Corporation (www.logiplex.net)
(503) 978-6726 x308  (800) 735-0555 x308