Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: Why does C allow structs to have a tag?
Date: Tue, 10 Aug 2021 11:22:03 -0700
Organization: None to speak of
Lines: 38
Message-ID: <87eeb1f9dg.fsf@nosuchdomain.example.com>
References: <s9iea5$n5c$1@dont-email.me> <see4ea$uop$1@dont-email.me> <see71a$gk4$1@dont-email.me> <seebtt$jrq$1@dont-email.me> <CjzOI.1030$Bg6.61@fx42.iad> <seejf8$9ti$1@dont-email.me> <WowPI.4743$NQ1.1007@fx48.iad> <sembba$oul$1@dont-email.me> <CrQPI.669$bS5.239@fx21.iad> <seoqf4$pj7$1@dont-email.me> <87czqnlp2m.fsf@bsb.me.uk> <sepbrd$vg4$1@dont-email.me> <877dgvljpf.fsf@bsb.me.uk> <2a1b4347-595a-469a-8df1-db64af9896acn@googlegroups.com> <Wg_PI.6656$NQ1.5159@fx48.iad> <94f47c65-5f5f-44d1-bc37-d51155624ae5n@googlegroups.com> <sesbbk$63q$1@dont-email.me> <87y29afah5.fsf@nosuchdomain.example.com> <seshh0$onu$1@dont-email.me> <87r1f2f7e1.fsf@nosuchdomain.example.com> <setjnn$d4c$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="4ba2c969ae0e906c6600fce7cdb6f53e"; logging-data="29950"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18i2a7NPqrWqTzmBHi8MxMA"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Cancel-Lock: sha1:T5db06ulNXjEeM5DgiYcpi0izRg= sha1:JMTNWJrFxIBuwLLVCGa8JLGIr4Q=
Xref: csiph.com comp.lang.c:162294

Bart <bc@freeuk.com> writes:
> On 10/08/2021 01:52, Keith Thompson wrote:
[...]
>> You continue to pretend not to understand the distinction between a
>> compiler and an implementation in a thread that demonstrates just how
>> important that distinction is.
>
> I think the [sub-]thread demonstrates exactly the opposite!
>
> The fact is that, outside of Unix (and outside of compilers that
> originated in Unix or Unix-like systems, or that try and emulate
> those) a compiler is a whole package.

You use TDM-GCC.  Yes, it's a "whole package" by the time you download
it, but it was assembled from independent components.

> And outside of C, that is generally the case too.
>
> Actually, try and do something different, like compiling this program:
>
>  extern int printf(intptr_t);
>
> then gcc/tdm will complain that it it does match what it expects for
> the BUILT-IN function 'printf'.

Yes, because it knows what the standard guarantees for the printf
function, not because it knows anything about a particular library
implementation.

> I am just NOT INTERESTED in the 'distinction'.

You're interested enough to argue about it every time someone mentions
it.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */