>BTW...if you want to write portable code, this idiom *doesn't* work.
>And I don't mean sigismember() problems...
>
>An invalid signal number doesn't mean you're past the valid signal number.
>
>Your best bet is using NSIG or picking some arbirtrary maximum, and if you
>really care, keeping a mask of valid signals.

Oh, I'm not saying the cvs code was good by any means, just that there was
no way for the macro to generate the proper output in any case.

I don't program that way :-)

James