Path: utzoo!attcan!uunet!know!sdd.hp.com!ucsd!ames!eos!shelby!msi.umn.edu!aps1.spa.umn.edu!zoo From: zoo@grumpy.spa.umn.edu (david d [zoo] zuhn) Newsgroups: comp.lang.c Subject: Re: C Compiler under Unix System VR4 Message-ID: Date: 12 Oct 90 17:26:57 GMT References: <125@alfrat.uucp> <3158@unisoft.UUCP> <3159@unisoft.UUCP> Sender: news@s1.msi.umn.edu Organization: Minnesota Automated Plate Scanner Lab Lines: 21 In-Reply-To: rembo@unisoft.UUCP's message of 11 Oct 90 22:31:24 GMT >>>>> On 11 Oct 90 22:31:24 GMT, rembo@unisoft.UUCP (Tony Rems) said: [regarding the S5R4 #machine debate, which is this: #assert #machine(pdp11) #if #machine(pdp11) ... #endif Tony> One more thing. Although I haven't confirmed this, it seem that Tony> the #if #machine construct *is* ANSI, but that gcc is not Tony> entirely ANSI (even with the -ansi option). I would say that it is NOT ansi legal, or at least there is NO mention of #assert (a basic element of this mechanism) in the ANSI standard. I couldn't find exact wording about additional preprocessing directives being implementation defined, undefined, or what, but it's not part of the Standard. david d [zoo] zuhn Univ. of Minnesota Dept. of Astronomy zoo@aps1.spa.umn.edu Automated Plate Scanner Project