Sujet : Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD)
De : richard (at) *nospam* damon-family.org (Richard Damon)
Groupes : comp.theoryDate : 09. May 2025, 12:25:10
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <6228e8821a203853e0f9e752b276177146d86d21@i2pn2.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
User-Agent : Mozilla Thunderbird
On 5/8/25 6:20 PM, olcott wrote:
On 5/8/2025 5:13 PM, Richard Heathfield wrote:
On 08/05/2025 22:41, olcott wrote:
What my code actually does is totally irrelevant.
>
On that, at least, we can agree.
>
That an HHH can be created that does correctly
determine the halt status of this input is the
whole point.
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
Except that it doesn't, as your "input", being just that function, doesn't HAVE a halting status. It only gets that once it is paired with a specific version of HHH.
If that HHH aborts its simulation and returns 0, then it halts, and that HHH wasn't a correct halt decider.
Since you claim that is what you HHH does, and that would be the DD that it is given, it is thus clear that when we fix your input to be what you intend, your claim is false.
That you keep making your "clearly false due to the category error in it" claim just shows your stupidity.
You just don't understand the basic meaning of the terms you use, because you decided it would be better to be ignorant, then to know you are wrong.