Re: Every D(D) simulated by H presents non-halting behavior to H ###

Liste des GroupesRevenir à theory 
Sujet : Re: Every D(D) simulated by H presents non-halting behavior to H ###
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theory
Date : 19. May 2024, 05:27:58
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v2brju$36n5f$3@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
User-Agent : Mozilla Thunderbird
On 5/18/2024 9:58 PM, André G. Isaak wrote:
On 2024-05-17 18:24, olcott wrote:
On 5/17/2024 6:15 PM, André G. Isaak wrote:
On 2024-05-17 17:00, olcott wrote:
On 5/17/2024 3:02 PM, Alan Mackenzie wrote:
>
That "program" doesn't compile.  It's ill-formed.
>
This does compile under C17 and C11
with Microsoft Visual Studio 2022
 >
*Maybe you forgot to take the line numbers out*
*Maybe you forgot to take the line numbers out*
*Maybe you forgot to take the line numbers out*
*Maybe you forgot to take the line numbers out*
>
typedef int (*ptr)();
int H(ptr P, ptr I);
>
But that's not the code you provide in your numerous previous posts where you insist on
>
int H(ptr x, ptr x);
>
Maybe when people point out that there is an error you should actually proofread what you wrote.
>
[remaining code deleted].
>
André
>
>
*Whoops my mistake*
*Whoops my mistake*
*Whoops my mistake*
*Whoops my mistake*
>
Thanks for your review.
>
I couldn't see my mistake when I tried to compile it
so I used an old trick, refactor from working code.
I still didn't see my mistake, yet got it to compile.
 You're missing the point. This error had been pointed out to you multiple times by multiple posters. Alan even pointed out the *specific* compiler errors which it generated under GCC. Yet you refused to correct it for weeks on end, insisting that everyone else was wrong.
 
Yes and several people also continue to point out that D
correctly simulated by H can reach its own line 06 and halt
even when an execution trace of H simulating itself simulating
D proves otherwise.

A competent C programmer wouldn't have run into this issue since they would have declared the function as something like:
 int H(ptr programDescription, ptr programInput); // no silly x and y
 
The actual names are P and I.
Yes I agree that meaningful variable names are very important
yet computer scientists don't do it that was when referring
to the halting problem.

Yet you continue to question everyone else's 'C-credentials' when you are the one making very basic errors. That hardly inspires confidence in anything else you might say about C.
 André
 
Several people continue to lie about the execution trace
that is proven by H simulating itself simulating D.
--
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

Date Sujet#  Auteur
10 Nov 24 o 

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal