>People are complaining about code breakage with the new sigset_t.
>Correctly written code should *not* have problems.
>But I thought I'd take us all on a quick tour of signal.h to explain
>what's changed, and why it doesn't (shouldn't) matter --- and why some
>programs written by lousy programmers break.
Err, could you tell me why sigemptyset and sigfillset are missing in
the `new' signal stuff? It looks like we're using old-style sigemptyset
on the new-style signal structs.
Alex