Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/17/84; site opus.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!hao!cires!nbires!opus!rcd From: rcd@opus.UUCP (Dick Dunn) Newsgroups: net.lang.c Subject: Re: Standardization questions (cpp mostl Message-ID: <878@opus.UUCP> Date: Thu, 11-Oct-84 15:14:27 EDT Article-I.D.: opus.878 Posted: Thu Oct 11 15:14:27 1984 Date-Received: Sat, 13-Oct-84 02:20:43 EDT References: <51@ism780b.UUCP> Organization: NBI,Inc, Boulder CO Lines: 22 >... > > 1. undefined token has the value zero (in #if's). Cpp should > > print a warning -- or error if the evaluator is intelligent > > about statements like: > > #if defined (foo) && foo == 0 >... > I disagree. I've seen plenty of code which does > > #if foo > or > #if !foo > > and I don't think a "-Dfoo 0" should be required. Looks like you've seen plenty of code which is confused about the difference between testing whether a symbol is defined and testing its value. That's a fairly fundamental confusion, and it's easily remedied by using ifdef/ifndef. I don't see why poor usage becomes an argument in the standardization process. (Well, in reality I do; I wish I didn't:-) -- Dick Dunn {hao,ucbvax,allegra}!nbires!rcd (303)444-5710 x3086 ...Relax...don't worry...have a homebrew.