>
> I generally divide signals into two groups:
>
> *) Messages from outside (i.e. SIGHUP)
> *) Indicators of Horrific Failure (i.e. SIGBUS)
>
> Generally speaking, parrot should probably just up and die for the first
> type, and turn the second into events.
I don't know. SIGHUP is useful to capture. Not to mention, how else
would you maintan Perl5 compatibility $SIG{HUP}. If you're a daemon,
sighup is good to restart off of.
I'm seriously doubting that you're going to get a fully portable
threading model. One size doesn't fit all. Usually that's something
that the JIT would take care of (hense my preoccupation with
fake-threads).. How does python handle MT?
-Michael
