Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Why does C allow structs to have a tag? Date: Tue, 10 Aug 2021 11:17:22 -0700 Organization: None to speak of Lines: 25 Message-ID: <87im0df9l9.fsf@nosuchdomain.example.com> References: <87czqnlp2m.fsf@bsb.me.uk> <877dgvljpf.fsf@bsb.me.uk> <2a1b4347-595a-469a-8df1-db64af9896acn@googlegroups.com> <94f47c65-5f5f-44d1-bc37-d51155624ae5n@googlegroups.com> <87y29afah5.fsf@nosuchdomain.example.com> <1617a372-38e2-4729-a058-8f1ca95d5a49n@googlegroups.com> 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="U2FsdGVkX193Xc7IwaiRDU86U/JXB9F4" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:kK+YRTN5Oo9As+y2lPJDAGSyuRw= sha1:VPmjDaDzFx+healDysWAqWqiVL8= Xref: csiph.com comp.lang.c:162293 Bart writes: [...] > According to Keith, every C implementation consists of assorted > components like this: > > * Possibly, a discrete preprocessor > * Compiler > * Standard headers > * Assembler > * Linker > * Standard library > * Extensions > > which everyone who ever installs an implementation is expected to > obtain from different sources and mix and match to create a custom C > system. That is a lie. I did not say that. [...] -- 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 */