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: Mon, 09 Aug 2021 17:52:38 -0700
Organization: None to speak of
Lines: 35
Message-ID: <87r1f2f7e1.fsf@nosuchdomain.example.com>
References: <s9iea5$n5c$1@dont-email.me> <se41h9$kbs$1@gioia.aioe.org> <sedtrl$irb$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>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="4ba2c969ae0e906c6600fce7cdb6f53e"; logging-data="21340"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/dWV1kGYscHdMG7joBvpA2"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Cancel-Lock: sha1:gkC9pbm3pMDgpa5yVk2JDsMN568= sha1:BN6uLq83QRs7xUs/K7Ufy0lSoqc=
Xref: csiph.com comp.lang.c:162283

Bart <bc@freeuk.com> writes:
> On 10/08/2021 00:45, Keith Thompson wrote:
>> Bart <bc@freeuk.com> writes:
>> [...]
>>> And when I have to play with C, I prefer my own small C compiler; you
>>> know, that one with the faster printf than gcc/tdm.
>> Really?  Your *compiler* implements printf?  Not the runtime
>> library?
>> Yes, the distinction matters.
>> [...]
>
> Not to most normal people, where a language and its implementation is
> just expected to provide print facilities.
>
> The same goes for C. And no the distinction doesn't really matter
> unless you come from the Unix world, which apparently 'owns' C and
> gets to decide all this stuff.
>
> The 'faster' printf I'm refering to is the one inside msvcrt.dll,
> which my gcc/tdm and clang/llvm don't appear capable of using without
> some arm-twisting.
>
> (Would it be that remarkable to implement a function like 'printf'?
> That's the sort of thing I used to do all the time. But since it's 
> available in msvcrt.dll, there's no point in repeating stuff I've done
> innumerable times.)

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.

-- 
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 */