Path: utzoo!utgpu!watserv1!watmath!att!att!emory!wuarchive!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!ericom!eos.ericsson.se!epames
From: epames@eos.ericsson.se (Michael Salmon)
Newsgroups: comp.lang.c
Subject: Re: availability of ANSI-conformant compilers
Keywords: ANSI compiler availability
Message-ID: <1990Nov19.075143.11956@ericsson.se>
Date: 19 Nov 90 07:51:43 GMT
References: <16440@csli.Stanford.EDU> <14487@smoke.brl.mil> <16457@csli.Stanford.EDU>
Sender: news@ericsson.se
Reply-To: epames@eos.ericsson.se
Organization: Ericsson Telecom AB
Lines: 20

In article <16457@csli.Stanford.EDU> poser@csli.stanford.edu (Bill Poser) writes:
>In article <14487@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>>Consequently, I key
>>on the __STDC__ preprocessing macro and include code for both
>>standard-C and UNIX-pcc environments.  This works fairly well
>>and could be done more spiffily than I usually bother to do it.
>
>Doesn't this mean that you either don't use prototypes or have to
>include both a prototype and a non-prototyped declaration for every
>function?

I recently saw a programme that used cpp macros to define either
prototypes or use traditional declarations. The idea is to use a macro
for each number of parameters then expand it 2 ways. Unfortunately it
does mean that programmes that expect a certain format (perhaps indent)
may become confused.

Michael Salmon
L.M.Ericsson
Stockholm