strange handling of invalid pre-processor directives

[Zack Weinberg]

"Thomas R. Truscott" <trt@cs.duke.edu> writes:

> /*
>  * This file compiles without complaint,
>  * despite the "elsewhere" and "elifndef" preprocessor directives.
>  * I think there should be a diagnostic.

No.  Both are inside failed conditional blocks, so they are ignored.

>  * And/or gcc could support elifdef and elifndef
>  * as extensions to the pre-processor language.

No.  Use #elif [!]defined.

zw