Re: warnings about signal() calls on HP

 >I understand that it's about SIG_IGN etc.
 >
 >Are you saying that we have our own prototype for signal()?  Shouldn't
 >the compiler's prototype for signal() be picked up from <signal.h>?

It's not really the prototype for signal(); it's a "type" used
to define markers (SIG_IGN, SIG_DFL, etc.) so that when those
are passed around instead of actual signal handlers the comparisons
will not generate warnings about mismatched types (!).  Just
pointing out that the one that Python uses, in the places where
it needs it, *is* standards-conforming; the warning indicates that
maybe certain OS vendors have not been so careful with theirs ....