Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!usc!elroy.jpl.nasa.gov!ames!dftsrv!jagmac2.gsfc.nasa.gov!jim From: jim@jagmac2.gsfc.nasa.gov (Jim Jagielski) Newsgroups: comp.unix.aux Subject: Re: signal.h and sys/signal.h on 2.0 Message-ID: <3393@dftsrv.gsfc.nasa.gov> Date: 12 Sep 90 18:29:11 GMT References: <3392@dftsrv.gsfc.nasa.gov> Sender: news@dftsrv.gsfc.nasa.gov Reply-To: jim@jagmac2.gsfc.nasa.gov (Jim Jagielski) Organization: NASA Goddard Space Flight Center Lines: 28 In article <3392@dftsrv.gsfc.nasa.gov> MY STUPID TWIN writes: >I have uncovered something in the A/UX 2.0 header files for signals >(/usr/include/signal.h and sys/signal.h) that, if I understand typedefs >right, might be wrong. > > sigfunct_t signal(); > ("signal is a function that returns a pointer to a function that > returns an int") > >IS THIS RIGHT??? DO I UNDERSTAND THIS CORRECTLY??? Sorry, sorry, sorry. Stupid me. Of course, that is what signal is. For some reason I was thinking that signal returned int (or void) directly... Here it is only Wednesday and already my mind is mush... -- ======================================================================= #include =:^) Jim Jagielski NASA/GSFC, Code 711.1 jim@jagmac2.gsfc.nasa.gov Greenbelt, MD 20771 "Kilimanjaro is a pretty tricky climb. Most of it's up, until you reach the very, very top, and then it tends to slope away rather sharply."