home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.vms:21872 comp.lang.c:20145 vmsnet.alpha:146 cern.alpha:32
- Path: sparky!uunet!stanford.edu!agate!doc.ic.ac.uk!warwick!uknet!miclon!nreadwin
- From: nreadwin@micrognosis.co.uk (Neil Readwin)
- Newsgroups: comp.os.vms,comp.lang.c,vmsnet.alpha,cern.alpha
- Subject: Re: functions as arguments in DEC C
- Message-ID: <C1DCr5.2v1@micrognosis.co.uk>
- Date: 24 Jan 93 17:33:04 GMT
- References: <1993Jan24.094945.7767@dxcern.cern.ch>
- Sender: news@micrognosis.co.uk
- Organization: Micrognosis, a division of CSK(UK) Ltd
- Lines: 20
-
- In article <1993Jan24.094945.7767@dxcern.cern.ch>, burow@dxcern.cern.ch (Burkhard Burow) writes:
- |>That's why I need a cast for saying:
- |> 'This is a pointer to a function.
- |> I don't give a flying f*** about the type of argument the function returns.'
-
- Having spent a little time reading through both the standard and the Rationale
- (especially 3.2.2.3), I do not think that ANSI C provides this. This came as
- something of a surprise to me.
-
- |> EXCEPT SO FAR FOR DEC C, WHICH I CAN'T CONVINCE,
- |> BUT I'M HOPING SOMEONE OUT THERE CAN TELL ME HOW.
-
- You could try /STANDARD=COMMON. You could also try complaining to Digital
- and asking them to make this a warning instead of an error, since it seems
- unreasonable to refuse to produce an object file due to this kind of
- mismatch. The five other compilers that I have to hand (SunOS, AIX, NeXT
- (aka gcc), HP/UX and Ultrix) give a warning about this and continue. Neil.
- --
- Phone: +44 71 815 5283 E-mail: nreadwin@micrognosis.co.uk
- Anything is a cause for sorrow that my mind or body has made
-