Newsgroups: comp.std.c
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!pa.dec.com!jrdzzz.jrd.dec.com!tkou02.enet.dec.com!jit345!diamond
From: diamond@jit345.swstokyo.dec.com (Norman Diamond)
Subject: Re: #error
Message-ID: <1991Apr23.000427.14716@tkou02.enet.dec.com>
Sender: usenet@tkou02.enet.dec.com (USENET News System)
Reply-To: diamond@jit345.enet@tkou02.enet.dec.com (Norman Diamond)
Organization: Digital Equipment Corporation Japan , Tokyo
References: <14793@darkstar.ucsc.edu> <1991Apr22.075125.6828@tkou02.enet.dec.com> <18721@crdgw1.crd.ge.com>
Date: Tue, 23 Apr 1991 00:04:27 GMT
Lines: 21

In article <18721@crdgw1.crd.ge.com> volpe@camelback.crd.ge.com (Christopher R Volpe) writes:
>In article <1991Apr22.075125.6828@tkou02.enet.dec.com>,
>diamond@jit345.swstokyo.dec.com (Norman Diamond) writes:
>>In article <14793@darkstar.ucsc.edu> daniel@terra.ucsc.edu (Daniel
>Edelson) writes:
>>>There is no constraint to the effect:
>>>	``The #error directive shall not be present.''
>>>Therefore, a strictly conforming program may contain #error.
>>Yes.
>Are we drawing any distinction between "containing an error directive" and
>"invoking an error directive during the course of preprocessing"???

I wasn't.  As far as I can tell, if an #error directive is correctly
processed and obeyed, the processor still has to proceed to translate
the program successfully, unless an implementation limit is exceeded.

For an #error directive that is (correctly) skipped due to #if, etc.,
I'd say the question didn't even require asking.
--
Norman Diamond       diamond@tkov50.enet.dec.com
If this were the company's opinion, I wouldn't be allowed to post it.