Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!wugate!uunet!mitel!sce!cognos!geovision!pt
From: pt@geovision.uucp (Paul Tomblin)
Newsgroups: comp.lang.c
Subject: Re: Abandon NULL for (0)
Message-ID: <740@geovision.UUCP>
Date: 9 Oct 89 19:14:01 GMT
References: <252B5E41.1244@marob.masa.com> <19999@mimsy.UUCP>
Reply-To: pt@geovision.UUCP (Paul Tomblin)
Organization: GeoVision Corp, Ottawa, Canada
Lines: 22

In article <19999@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>One is supposed to write monstrosities like
>
>	void (*signal(int, void (*)(int)))(int);
>
For some strange reason, our VMS C compiler has the following in signal.h:

int (*signal (int sig, void (*func)(int, ...)) ) (int, ...);

which seems slightly contradictory.  Since our code doesn't use prototypes
yet, or signals in the VMS code,  I haven't been able to investigate whether
this is going to cause some sort of compiler warning every time the code
trys to capture the old signal handler, set up a new one, and restore the
old one after the signal has been handled.

Someone care to comment on why Dec did it this way, and if they are planning
to fix it later?
-- 
Paul Tomblin,  Feeping Creaturism Section, DeptRedncyDept | ADA was invented 
    UUCP:   nrcaer!cognos!geovision!pt ??                 | because  Vogon 
    Disclaimer: The opinions expressed here aren't        | Poetry wasn't
    necessarily even mine!                                | deadly enough.