Path: utzoo!attcan!telly!lethe!torsqnt!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!apple!oliveb!tymix!cirrusl!sun505!dhesi
From: dhesi@sun505.UUCP (Rahul Dhesi)
Newsgroups: comp.unix.questions
Subject: SunOS: 1; portability: 0
Message-ID: <880@cirrusl.UUCP>
Date: 22 Sep 89 19:23:19 GMT
Sender: news@cirrusl.UUCP
Reply-To: dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi)
Organization: Cirrus Logic Inc.
Lines: 19

For about ten years, signal() has been a function returning pointer to
int.  It worked, and we were all happily writing portable code.

So what happens?  Both Sun and ANSI decide that milliions of lines of
existing code were all wrong, and that signal() ought really to return
pointer to void.

After much thinking I have found no advantage to this change, and the
big disadvantage that stable existing code now brreaks.

Now I'm faced with this problem:  How do I use signal() in such a way
that my code is portable, without manually editing it for each
implementation?   I need a way of having my code automatically use void
or int as appropriate.

Any suggestions?
--
Rahul Dhesi <dhesi%cirrusl@oliveb.ATC.olivetti.com>
UUCP:  oliveb!cirrusl!dhesi