Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!gem.mps.ohio-state.edu!ginosko!uunet!kddlab!titcca!sragwa!wsgw!socslgw!diamond From: diamond@csl.sony.co.jp (Norman Diamond) Newsgroups: comp.lang.c Subject: Re: #endif ??? Message-ID: <10899@riks.csl.sony.co.jp> Date: 5 Oct 89 05:06:15 GMT References: Reply-To: diamond@ws.sony.junet (Norman Diamond) Distribution: comp Organization: Sony Computer Science Laboratory Inc., Tokyo, Japan Lines: 17 In article jfr@tel3.tel3.tel.vtt.fi (Jim Reilly) writes: >`#endif sparc` >never caused any complaints on the sun's normal C compiler, but our >'Designer C++' compiler doesn't like it. Is this just something >funny with the c compilers on the SUN ? It's something funny with pcc-based compilers. It's something funnier with SUN to depend on this particular undefined behavior. Extra tokens after #endif (or #else) are not permitted by ANSI or K&R-1, though the processor (e.g. pcc) is not required to notice them. -- Norman Diamond, Sony Corp. (diamond%ws.sony.junet@uunet.uu.net seems to work) The above opinions are inherited by your machine's init process (pid 1), after being disowned and orphaned. However, if you see this at Waterloo or Anterior, then their administrators must have approved of these opinions.