Re: Python recompile

On Tue, 4 Mar 2025 09:57:16 +0000
Richard Heathfield <rjh@cpax.org.uk> wibbled:

On 04/03/2025 09:23, Muttley@DastardlyHQ.org wrote:

because plenty of compilation issues are caused by code issues.

>
Undoubtedly true, and equally undoubtedly irrelevant in this
case. Were it relevant, the OP would by now have shown us the
problem code.

So what you're saying is you can't troubleshoot linking problems. Do you
get someone else to compile your code for you?

Or are you claiming those don't count as part of development?

>
Not at all. Your keyboard's shift key is part of development too,
but that isn't enough to make it topical in comp.lang.c.

Oh dear, if stuck go in circles, posted comparisons conveniently ignored.

K&R would also claim that the function parameter type definitions have to
follow the prototype. Luckily that hasn't been the case since 1989.

>
Is it, then, your claim that K&R are mistaken or outdated and

Is K&R outdated? Hmm, let me think about that for a nanosecond...

that compilation no longer depends on the system you are using
and has now become a language attribute? Can you hear the
chuckles yet?

A compiler is a compiler, a linker is a linker. Troubleshooting both is part
of the development process of any competent C dev. But we know already you
don't consider that to be the case because its beyond your abilities.

If you think you can defend your claim by showing where the
language standard supports your extraordinarily wobbly position,
by all means have a crack at it. Show us why you're right.

Wtf has the language standard got to do with anything? Moving goalposts, much?