signal.h and sys/signal.h on 2.0
Jim Jagielski
jim at jagmac2.gsfc.nasa.gov
Thu Sep 13 04:29:11 AEST 1990
In article <3392 at 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 <std/disclaimer.h>
=:^)
Jim Jagielski NASA/GSFC, Code 711.1
jim at 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."
More information about the Comp.unix.aux
mailing list