Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!leah!rpi!batcomputer!lijewski
From: lijewski@batcomputer.tn.cornell.edu (Mike Lijewski)
Newsgroups: comp.lang.c
Subject: signal & sigvec error return codes
Keywords: signal sigvec error
Message-ID: <8044@batcomputer.tn.cornell.edu>
Date: 25 May 89 11:44:37 GMT
Distribution: comp
Organization: Cornell National Supercomputer Facility
Lines: 17


     Do all vendors still document the return code of signal and
sigvec as being -1 (implicitely an int)?  My problem with this is
that if you try to be a "good" programmer and check for an error as
in 
    if(signal(SIGINT, SIG_IGN) == -1){
      perror("signal");
      exit(1);
    }

say, you will either get a warning or an error, depending on how smart
your compiler is.  Why not document the error return as being something
along the lines of SIG_ERR, where SIG_ERR is defined as

#define SIG_ERR ((int(*)())-1)

in <signal.h>?