Xref: utzoo comp.std.c:88 comp.lang.c:10904
Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!pasteur!ucbvax!decwrl!decvax!tektronix!uunet!wucs1!plus5!hokey
From: hokey@plus5.UUCP (Hokey)
Newsgroups: comp.std.c,comp.lang.c
Subject: __STDCPP__ anybody?
Message-ID: <2459@plus5.UUCP>
Date: 26 Jun 88 04:22:54 GMT
Reply-To: hokey@plus5.UUCP (Hokey)
Organization: Plus Five Computer Services, St. Louis, MO
Lines: 12

We are in an environment in which we use a cpp which meets the (proposed)
C standard, but we don't have a standard C compiler.

As y'all well know, a standard cpp does some things differently than "older"
cpps, so we get to #ifdef our code in certain places.  Using __STDC__ as
an indicator is not going to cut it, as it indicates a standard cpp as well
as a standard C compiler.

Does anybody besides me think a __STDCPP__ predefined symbol would be of
value?
-- 
Hokey