Newsgroups: comp.lang.c
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: A solution to the multiple inclusion problem
Message-ID: <1989Oct27.165023.6481@utzoo.uucp>
Organization: U of Toronto Zoology
References: <14240@well.UUCP> <11396@smoke.BRL.MIL> <288@charyb.COM> <FOX.89Oct26215145@novax.allegra.att.com>
Date: Fri, 27 Oct 89 16:50:23 GMT

In article <FOX.89Oct26215145@novax.allegra.att.com> fox@allegra.att.com (David Fox) writes:
>A problem with the idea of having the compiler recognize the
>
>	#ifndef FOO
>	#define FOO
>	...
>	#endif
>
>arrangement (I wouldn't call it a construct) is what if the
>including file explicitly #undefs FOO? ...

Then the compiler notices that the magic symbol associated with the file
has been messed with, and suppresses the optimization.  Really, it can
be done, and it's not even hard.
-- 
A bit of tolerance is worth a  |     Henry Spencer at U of Toronto Zoology
megabyte of flaming.           | uunet!attcan!utzoo!henry henry@zoo.toronto.edu
