Sujet : Re: Python recompile
De : Muttley (at) *nospam* DastardlyHQ.org
Groupes : comp.lang.c comp.lang.c++ comp.lang.pythonDate : 04. Mar 2025, 09:31:03
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vq6do7$1psap$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10
On Mon, 3 Mar 2025 18:22:52 +0100
David Brown <
david.brown@hesbynett.no> wibbled:
On 03/03/2025 17:56, 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.
>
If the problem could be solved by understanding C better, it would be
relevant. But the problem has nothing to do with the C /code/ in
question, nor the C language. It's a matter of the build process for
Compilation is a fundamental part of developing in C.
For the obligatory car metaphor, imagine a group dedicated to learning
to drive and driving techniques. A post about a particular make of car
would be off-topic, but perhaps okay on occasion. The OP's post here is
asking for the best way to avoid roadworks on the Bath to Reading road.
Lousy metaphor. Its more like writing C code is building the car and
compilation is starting it up at the end.