Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site utcsrgv.UUCP
Path: utzoo!utcsrgv!dave
From: dave@utcsrgv.UUCP (Dave Sherman)
Newsgroups: net.unix,net.lang.c,net.unix-wizards
Subject: Re: Standardized predefined CPP symbols, down with folklore
Message-ID: <4914@utcsrgv.UUCP>
Date: Sun, 15-Jul-84 10:22:43 EDT
Article-I.D.: utcsrgv.4914
Posted: Sun Jul 15 10:22:43 1984
Date-Received: Sun, 15-Jul-84 12:02:29 EDT
References: <2065@rlgvax.UUCP>  <142@pyuxt.UUCP>  <8241@watmath.UUCP> <297@watdcsu.UUCP> <4842@utcsrgv.UUCP> <936@orca.UUCP>
Reply-To: dave@utcsrgv.UUCP (& Sherman)
Organization: The Law Society of Upper Canada, Toronto
Lines: 25

In article <936@orca.UUCP> andrew@orca.UUCP (Andrew Klossner) writes:
~| []
~| 
~| 	"Actually, it wouldn't matter if the implementors had had the
~| 	sense to have cpp implcitly "#define unix unix", instead of
~| 	"#define unix 1".  The first would still permit all "#ifdef
~| 	unix" work, while the actual implementation caused me grief one
~| 	day when I tried to create a function called unix()"
~| 
~| Nope.  "#define unix unix" followed by a use of "unix" will put the
~| preprocessor into a loop, scanning "unix" over and over, until the
~| recursion depth is hit and it punts with a fatal error message.
~| 

Why should that be true? Since the preprocessor is putting it in
implicitly anyway, it could easily have the smarts to skip over "unix"
in any re-scans of lines. This can obviously be made different from
a user-suppled "#define unix unix".

Dave Sherman
Toronto
-- 
 {allegra,cornell,decvax,ihnp4,linus,utzoo}!utcsrgv!dave
or
 David_Sherman%Wayne-MTS%UMich-MTS.Mailnet@MIT-Multics.ARPA