Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: do { quit; } else { }
Date: Thu, 10 Apr 2025 04:28:05 -0700
Organization: None to speak of
Lines: 21
Message-ID: <87wmbs45oa.fsf@nosuchdomain.example.com>
References: <vspbjh$8dvd$1@dont-email.me> <20250406161323.00005809@yahoo.com> <86ecy5fjin.fsf@linuxsc.com> <20250406190321.000001dc@yahoo.com> <86plhodtsw.fsf@linuxsc.com> <20250407210248.00006457@yahoo.com> <vt15lq$bjs0$3@dont-email.me> <vt2lp6$1qtjd$1@dont-email.me> <vt31m5$2513i$1@dont-email.me> <vt3d4g$2djqe$1@dont-email.me> <vt3iqh$2ka99$1@dont-email.me> <868qoaeezc.fsf@linuxsc.com> <vt3oeo$2oq3p$1@dont-email.me> <86mscqcpy1.fsf@linuxsc.com> <vt48go$35hh3$2@dont-email.me> <86iknecjz8.fsf@linuxsc.com> <vt4del$3a9sk$1@dont-email.me> <86o6x5at05.fsf@linuxsc.com> <vt712u$1m84p$1@dont-email.me> <20250409170901.947@kylheku.com> <vt88bk$2rv8r$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Thu, 10 Apr 2025 13:28:07 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="b22cabfa06f6271bcf7b0b42430aa8f3"; logging-data="3041883"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/12Y0F4hjZo620MayNdsE6"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:J49rXWatVVxXZZwlHb5klWp11XE= sha1:sAk765SYfNGVnOGKqyqK0zlbb04=
Xref: csiph.com comp.lang.c:392314

bart <bc@freeuk.com> writes:
[...]
> Someone, not anyone but the all-knowing Tim, said: "and those types
> are not compatible, because the two struct tags are different."
>
> Do you agree with that? Or is there something more to making two types
> be incompatible?

I don't recall the exact discussion and I wouldn't try to speak
for Tim, but I suspect he was saying that the fact that the two
struct tags are different is enough to know that the types are
not compatible.  In a similar vein, I know that 152016259867 and
152016259868 are unequal because one of them is even and the other
is odd.  That doesn't imply that 152016259867 and 3 are equal.

The rules for type compatibility are in the C standard.  Reading them
could give you even more things to complain about.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */