Subj : Re: thread control by mutex, predicates and conditions puzzle
To   : comp.programming.threads
From : roland
Date : Mon Jan 03 2005 07:03 am

Jomu wrote:
> Single lock will defeat most of thread usability. IMO, threads are all
> about decentralization and paralelization, and smallest number of any
> kind of congestion points possible.

True.

> I don't really understand how that
> general scheme can help you in thread programming, but your a is too
> much of congestion point for healthy thread program.

You might have got me wrong, but I am in no way suggesting this as
anything like a "general scheme". On the contrary I do find this
construct very problematic.

> Just avoid it.

This is exactly my point: How can I avoid this sucessfully, while
still beeing able to have a "global stop/action flag"?

I.e. how can I then achieve the below behaviour correctly?

Roland wrote:

 > E.g. a
 > contains a flag requesting the thread to abort
 > whatever it is doing and to restart.

Roland

.