Path: csiph.com!news.mixmin.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: invalid universal character gives error even after #if 0
Date: Tue, 13 Sep 2022 07:54:03 -0700
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <86sfkvnx4k.fsf@linuxsc.com>
References: <temv38$kie6$1@solani.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader01.eternal-september.org; posting-host="92872b52a6f682cd3838888a35637fbb"; logging-data="2744000"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1929eDJyQEyKYV5Yet/eniBkc1ESSFMqIc="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:pgB6z0rPLwoKRvkhzqEf3zVM3pA= sha1:+WumC8wxuSeMJnTpXRCLYxDmVEk=
Xref: csiph.com comp.lang.c:167674

Philipp Klaus Krause <pkk@spth.de> writes:

> I noticed that current gcc and clang give an error on the following:
>
> #if 0
> \u003a
> #endif
>
> but not on
>
> /*
> \u003a
> */
>
> While I see that \u003a is a constraint violation, I do not see how it
> follows from the standard that this is a constraint violation even
> inside #if 0.

I believe this behavior is a misdiagnosis on the part of these
compilers.  Please see also my response to Kaz Kylheku in this
thread.