Path: ...!2.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: olcott <abc@def.com>
Newsgroups: comp.theory
Subject: Defining a correct halt decider
Date: Sun, 4 Aug 2024 09:46:02 -0500
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <v8o47a$3ml4$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 04 Aug 2024 16:46:03 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="903796c801119a1f2fd86200a8e93bf1";
	logging-data="121508"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19qoM2d4hXCLAa552VF2uw1"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:CWJJbdB/gLF28y6R05iRIja1yOo=
Content-Language: en-US
Bytes: 1509

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.

-- 
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer