Path: csiph.com!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: question about linker
Date: Thu, 05 Dec 2024 16:50:07 -0800
Organization: None to speak of
Lines: 26
Message-ID: <87ldwtzlc0.fsf@nosuchdomain.example.com>
References: <vi54e9$3ie0o$1@dont-email.me> <87plmfu2ub.fsf@nosuchdomain.example.com> <vi9jk4$gse4$1@dont-email.me> <vi9kng$gn4c$1@dont-email.me> <87frnbt9jn.fsf@nosuchdomain.example.com> <viaqh0$nm7q$1@dont-email.me> <877c8nt255.fsf@nosuchdomain.example.com> <viasv4$nm7q$2@dont-email.me> <vibr1l$vvjf$1@dont-email.me> <vic73f$1205f$1@dont-email.me> <20241129142810.00007920@yahoo.com> <vicfra$13nl4$1@dont-email.me> <20241129161517.000010b8@yahoo.com> <vicque$15ium$2@dont-email.me> <vid110$16hte$1@dont-email.me> <vifcll$1q9rj$1@dont-email.me> <vifiib$1s07p$1@dont-email.me> <87ldwx10gv.fsf@bsb.me.uk> <vimtt4$27vv$1@dont-email.me> <86ser1kgp5.fsf@linuxsc.com> <vit69t$1qfgg$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Fri, 06 Dec 2024 01:50:12 +0100 (CET)
Injection-Info: dont-email.me; posting-host="121d8a154b7fcd6212a7afdcdc69d1a5"; logging-data="2044949"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19YKo5mkSW7pLxOxFykkkoC"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:GrRHkmLAtsGKOk0pHmtPGl2dfyM= sha1:mGw3bw64v5GNiLQSdCZGneZr4DU=
Xref: csiph.com comp.lang.c:389436

Bart <bc@freeuk.com> writes:
[...]
> This is a discussion of language design. Not one person trying to
> understand how some feature works. I could learn how X works, but that
> won't help a million others with the same issue.

That's great, if there are a million other users who are confused
about the same things you claim to be confused about, and if you're
actually trying to help them.

Except for a couple of things.

I don't believe there are "a million other users" who are confused
about, to use a recent example, C's rules about whether a "}" needs
to be followed by a semicolon.  I've seen code with extraneous
semicolons at file scope, and I mostly blame gcc's lax default
behavior for that.  But I've never heard anyone other than you
complain about C's rules being intolerably inconsistent.

And even if those users exist, I don't see you making any effort
to help them, for example by explaining how C actually works.
(Though you do manage to provoke some of us into doing that for you.)

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