Xref: utzoo comp.lang.c:32818 comp.unix.questions:26167
Path: utzoo!attcan!uunet!cs.utexas.edu!usc!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c,comp.unix.questions
Subject: Re: C Compiler under Unix System VR4
Message-ID: <14132@smoke.BRL.MIL>
Date: 12 Oct 90 14:35:28 GMT
References: <125@alfrat.uucp> <3158@unisoft.UUCP> <3159@unisoft.UUCP>
Followup-To: comp.lang.c
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 10

In article <3159@unisoft.UUCP> rembo@unisoft.UUCP (Tony Rems) writes:
>One more thing.  Although I haven't confirmed this, it seem that 
>the #if #machine construct *is* ANSI, but that gcc is not 
>entirely ANSI (even with the -ansi option).

Would you guys please quit cluttering the net with wild guesses?
"#if #machine(...)" cannot be used in a strictly conforming C program.
That is why I say that that whole approach is a botch.  It's intended
specifically to aid in porting across environments, but it interferes
with porting to most environments!