Re: warnings about signal() calls on HP

> We see these warnings on Solaris, too, where SIG_IGN is defined as
> 
> #define SIG_IGN (void (*)())1
> 
> I assume the complaint is about this definition, which isn't a
> prototype.

Bah.  This means our ideal of a warning-free compilation cannot be
accomplished as long as we use GCC with -Wstrict-prototypes.  Is
having that warning really worth the noise it generates?

--Guido van Rossum (home page: http://www.python.org/~guido/)