Subj : Re: A pity that there is no forkall() which clones threads
To   : comp.programming.threads
From : Giancarlo Niccolai
Date : Sat Mar 05 2005 01:35 pm

Marcin 'Qrczak' Kowalczyk wrote:

> My language Kogut has three variants of fork:
> 
>   * ForkProcess - other threads are stopped at a point where signals
>     are unblocked; the process is forked; in the child process threads
>     are canceled, and in the parent they are resumed
>     (the safest default)
> 
>   * ForkProcessCloneThreads - all threads continue running in both
>     processes
>     (the simplest to describe semantics)
> 
>   * ForkProcessKillThreads - other threads are killed immediately with
>     no cleanup
>     (used before ExecProgram)

No polemic here: a true suggestion (you helped me with that paper...): I
suggest you to study the topic before writing the code, and not to get in
love with your code before studying what others have done and why. I talk
on live experience.

There something deeply problematic with your views of threading that you
should consider with care. Unless you are talking about "lightweight" or
"emulated" language level threading, where you are free to do whatever may
seem consistent as you can control it; but in the rest of your mail you
talk about pthreads, so I suppose that this three functions are not the
case.

Bests,
Giancarlo Niccolai.

.