[M3devel] chosing SIG_SUSPEND?

[Mika Nystrom]

Tony Hosking writes:
>
...
>> probably my statement has the order backwards.
>> The point is to check them and not just hijack them.
>
>Maybe.  I would argue the opposite: that M3 apps that use signals  
>should avoid using the one dedicated to thread suspension.

I agree!  Signals are not the Modula-3 Way.  Something you mess
with only when you're trying to interface with C code that hasn't
heard of "threads".  Yuck.

...
>> Is the signal mechanism actually preemptive anyway?
>
>Preemptive in what sense?  Depending on the OS, signals tend to get  
>delivered at system calls or thread context-switches.

Isn't the whole point of signals to interrupt a computation...?
ctrl-C, ctrl-Z, ctrl-\, SIGALRM, etc....

     Mika