Newsgroups: comp.lang.c
Path: utzoo!henry
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: Constants in conditionals, was Re: Are enums safe to use in portable code?
Message-ID: <1991Feb20.174956.28239@zoo.toronto.edu>
Organization: U of Toronto Zoology
References: <9890@dog.ee.lbl.gov> <1991Feb18.113919.28217@watmath.waterloo.edu> <1424@geovision.gvc.com>
Date: Wed, 20 Feb 1991 17:49:56 GMT

In article <1424@geovision.gvc.com> pt@geovision.gvc.com writes:
>Sorry, but #ifdef or #if is SOOO basic, that if you don't know how to use
>it (or refuse to for wierd reasons), you loose.

There are lots of good reasons to avoid using #if/#ifdef if humanly possible.
Just look at some of the code that comes out of the more enthusiastic #ifdef
factories if you don't believe me.  However, using constants in ifs does not
solve the problem; what is needed is a change in approach, not quibbling over
the exact syntax of the conditionals.
-- 
"Read the OSI protocol specifications?  | Henry Spencer @ U of Toronto Zoology
I can't even *lift* them!"              |  henry@zoo.toronto.edu  utzoo!henry