Sujet : Re: Defining a correct halting decidability decider
De : abc (at) *nospam* def.com (olcott)
Groupes : comp.theoryDate : 04. Aug 2024, 19:49:57
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v8oigl$6kik$1@dont-email.me>
References : 1 2
User-Agent : Mozilla Thunderbird
On 8/4/2024 1:38 PM, Richard Damon wrote:
On 8/4/24 10:46 AM, olcott wrote:
When we define an input that does the opposite of whatever
value that its halt decider reports there is a way for the
halt decider to report correctly.
>
int DD()
{
int Halt_Status = HHH(DD);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
>
int main()
{
HHH(DD);
}
>
HHH returns false indicating that it cannot
correctly determine that its input halts.
True would mean that its input halts.
>
But false indicates that the input does not halt, but it does.
I made a mistake that I corrected on a forum that allows
editing: *Defining a correct halting decidability decider*
1=input does halt
0=input cannot be decided to halt
You don't get to redefine that meaning of the answers.
Sorry, you ar just proving you are a pathological liar that doesn't understand what truth is.
-- Copyright 2024 Olcott "Talent hits a target no one else can hit; Geniushits a target no one else can see." Arthur Schopenhauer