Geoff Steckel wrote:
This is my last posting on this, take heart.
The "threads" advocates have never specified any
advantages of a program written using that model
(multiple execution points in a single image)
over a multiple process model, assuming that
parallelism is useful.
If the purported advantage is access to shared
data structures without explicit access mechanisms,
let's say I strongly disagree that that is an advantage.
It is a whole set of fatal bugs waiting to happen.
Please enlighten me if there are any -other-
qualities of this model which are supposed to be
advantageous to the people paying for and using
the programs. I count faster development as an
advantage, increased maintenance (bugs) as a
disadvantage. The second strongly outweighs the
first.
I suggest that you read "Programming with POSIX Threads" by
David Butenhof and then draw your own conclusion.
For some applications, threading is a good tool, for others not.
But you have to be proficient in the area to make the decision.
