Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!well!jef
From: jef@well.sf.ca.us (Jef Poskanzer)
Newsgroups: comp.lang.c
Subject: Re: Constants in conditionals
Message-ID: <23253@well.sf.ca.us>
Date: 20 Feb 91 21:44:25 GMT
References: <1424@geovision.gvc.com>
Reply-To: Jef Poskanzer <jef@well.sf.ca.us>
Organization: Paratheo-Anametamystikhood Of Eris Esoteric, Ada Lovelace Cabal
Lines: 15

In the referenced message, pt@geovision.gvc.com wrote:
}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.

Using "if" for conditional compilation instead of "#if" has one major
advantage: the outshipped code continues to get checked for syntax
errors.  For machine-dependent code you probably don't want this,
otherwise you probably do.  But you're right, you do have to check
the generated assembly code to make sure your compiler is doing
the right thing.  These days, most do.
---
Jef

  Jef Poskanzer  jef@well.sf.ca.us  {apple, ucbvax, hplabs}!well!jef
"It's what you learn after you know it all that counts." -- John Wooden