Re: Python recompile

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

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

On 04/03/2025 08:32, Muttley@DastardlyHQ.org wrote:

Oh well, in that case I bow down in front of his magnificence, he must not
be contradicted!

>
James would be the first to say that he should be contradicted
when he is mistaken.
>
Here, he is not mistaken. You are.

 No, I'm not,

Yes, you are.

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.

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.
Show us the code.

Compilation is a fundamental part of the process of programming in C whether
you and Kuyper like it or not.

>
Quoth K&R in "The C Programming Language":

 *yawn*
 

Just how to run this program depends on the system you are using.
As a specific example, on the UNIX operating system you must

 Blah blah.
 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 that compilation no longer depends on the system you are using and has now become a language attribute? Can you hear the chuckles yet?
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.
--
Richard Heathfield
Email: rjh at cpax dot org dot uk
"Usenet is a strange place" - dmr 29 July 1999
Sig line 4 vacant - apply within