Threads, revisited

[itix]

The stop() method will not return until the process has ended. Calling stop will also interrupt any sleep state the thread is presently in (from calling Thread::sleep()), causing it to return a value signifying that the thread has been asked to quit.

What if thread in question is waiting for input from a thread that called stop() ?

[itix]

It is. While spawning new processes is very cheap in AmigaDOS in Ambient, which uses threading heavily, we have always few spare processes waiting for work.

[itix]

Yep, that is right.

In C++ (Ambient is purely C with MUI) you could also consider implementing thread pool where C++ thread objects allocate threads from the pool... maybe overkill though...

[itix]

Ah well Just a thought.