Xref: utzoo comp.lang.c:19741 comp.std.c:1342
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!uflorida!novavax!twwells!bill
From: bill@twwells.com (T. William Wells)
Newsgroups: comp.lang.c,comp.std.c
Subject: Re: __STDC__
Message-ID: <1989Jul5.003917.739@twwells.com>
Date: 5 Jul 89 00:39:17 GMT
References: <225800190@uxe.cso.uiuc.edu> <10448@smoke.BRL.MIL> <12378@bloom-beacon.MIT.EDU>
Organization: None, Ft. Lauderdale, FL
Lines: 21

In article <12378@bloom-beacon.MIT.EDU> scs@adam.pika.mit.edu (Steve Summit) writes:
: Even so, I can provide a realistic example of why mucking with
: __STDC__ would be useful: suppose I am interested in keeping my
: code compatible with earlier, non-ANSI compilers (a far from
: hypothetical suggestion).  If my primary development machine uses
: an ANSI compiler, I might from time to time want to check if the
: changes and additions I have been making are (at least
: syntactically) still usable on the non-ANSI machine, without
: necessarily taking all of the code over to the old machine and
: compiling it.  It seems natural to say
:
:       cc -U__STDC__
:
: yet this is forbidden.

In fact, for exactly the reasons you mention, I modified gcc's
preprocessor to permit me to do just that.

---
Bill                    { uunet | novavax | ankh | sunvice } !twwells!bill
bill@twwells.com