Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sftig.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!mhuxl!mhuxt!mhuxm!sftig!rbt
From: rbt@sftig.UUCP (R.Thomas)
Newsgroups: net.lang.c
Subject: Re: Standardization questions (cpp mostly)
Message-ID: <464@sftig.UUCP>
Date: Wed, 10-Oct-84 11:59:42 EDT
Article-I.D.: sftig.464
Posted: Wed Oct 10 11:59:42 1984
Date-Received: Fri, 12-Oct-84 07:58:45 EDT
References: <1209@rti-sel.UUCP> <4102@tekecs.UUCP>
Organization: AT&T Bell Laboratories, Summit, NJ
Lines: 17

>                                                 The current draft will
> state that predefined macros are implementation defined (They will
> exist BUT you will be provided with a list of them and what they are
> defined to be), and all conforming compilers MUST have some way of
> disabling all predefined macros. This way if your application does not
> want to use them, you may easily remove them without a never-ending,
> always changing list of #undef foobar's.

I hope that the standard will allow you to turn off all predefined
preprocessor variables, and give an exception list (that your program needs to
have).  Things like '__LINE__' and '__FILE__' are too good to loose (in
certain applications) just because the local C compiler defines 'stack' (in a
mistaken attempt to tell you that you are executing on a stack machine, or
something...)  I don't want to be forced to throw out the baby with the bath
water.

Rick Thomas