#error

Norman Diamond diamond at jit345.swstokyo.dec.com
Tue Apr 23 10:04:27 AEST 1991


In article <18721 at crdgw1.crd.ge.com> volpe at camelback.crd.ge.com (Christopher R Volpe) writes:
>In article <1991Apr22.075125.6828 at tkou02.enet.dec.com>,
>diamond at jit345.swstokyo.dec.com (Norman Diamond) writes:
>>In article <14793 at darkstar.ucsc.edu> daniel at 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 at tkov50.enet.dec.com
If this were the company's opinion, I wouldn't be allowed to post it.



More information about the Comp.std.c mailing list