Sujet : Re: Python recompile
De : gazelle (at) *nospam* shell.xmission.com (Kenny McCormack)
Groupes : comp.lang.c comp.lang.c++ comp.lang.pythonDate : 04. Mar 2025, 00:42:34
Autres entêtes
Organisation : The official candy of the new Millennium
Message-ID : <vq5epa$10cem$1@news.xmission.com>
References : 1 2 3 4
User-Agent : trn 4.0-test77 (Sep 1, 2010)
In article <
vq4n05$1d5dv$1@dont-email.me>, <
Muttley@DastardlyHQ.org> wrote:
On Mon, 3 Mar 2025 11:39:58 -0500
James Kuyper <jameskuyper@alumni.caltech.edu> wibbled:
On 3/3/25 11:24, geodandw wrote:
On 3/3/25 10:22, James Kuyper wrote:
On 03/03/2025 08:13, Muttley@DastardlyHQ.org wrote:
....
That sounds like a C issue to me.
>
If it were a C problem, then the C source code that produced the problem
should have been shown. It's hard to debug code that you can't see.
Why is this group so intolerant?
>
Because what you call intolerance, we call topicality. When you post a
message to a group where it is on-topic, the message gets seen and
>
Only an arrogant idiot would think that errors on linking object files
generated by a C compiler are not relevant in a C language group.
>
>
Indeed. And as you see, there is no shortage of arrogant idiots in
comp.lang.c
'Tis always been thus, and always will be.
BTW, I note that this thread is (still!) posted to 2 other groups, besides
CLC, but the main topic of discussion in the thread (the usual topicality
BS) is, of course, only relevant to CLC.
Funny, that.
-- The book "1984" used to be a cautionary tale;Now it is a "how-to" manual.