Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: "Fred. Zwarts" <F.Zwarts@HetNet.nl>
Newsgroups: comp.theory,sci.logic
Subject: Re: DDD correctly emulated by HHH is correctly rejected as
 non-halting.
Date: Wed, 10 Jul 2024 20:30:44 +0200
Organization: A noiseless patient Spider
Lines: 48
Message-ID: <v6mk0k$20sio$3@dont-email.me>
References: <v6m7si$1uq86$2@dont-email.me> <v6mhc7$20hbo$2@dont-email.me>
 <v6mhr3$20kkr$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 10 Jul 2024 20:30:44 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="ed324ae554c0f53fe92fe56911420f63";
	logging-data="2126424"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+Tm24Q7NBCWhvcXWgHla45"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:cELgPwv30CZxR69yCcuuquD3gcQ=
In-Reply-To: <v6mhr3$20kkr$2@dont-email.me>
Content-Language: en-GB
Bytes: 2587

Op 10.jul.2024 om 19:53 schreef olcott:
> On 7/10/2024 12:45 PM, Fred. Zwarts wrote:
>> Op 10.jul.2024 om 17:03 schreef olcott:
>>> typedef void (*ptr)();
>>> int HHH(ptr P);
>>>
>>> void DDD()
>>> {
>>>    HHH(DDD);
>>> }
>>>
>>> int main()
>>> {
>>>    HHH(DDD);
>>> }
>>
>> Unneeded complexity. It is equivalent to:
>>
>>         int main()
>>         {
>>           return HHH(main);
>>         }
>>
> 
> 
> Every time any HHH correctly emulates DDD it calls the
> x86utm operating system to create a separate process
> context with its own memory virtual registers and stack,
> thus each recursively emulated DDD is a different instance.

Irrelevant information.

> 
> The instance of main() can't possibly halt HHH correctly
> aborts and rejects as non-halting. The entirely different
> instance of main() that calls HHH only halts because HHH
> was correct to abort its simulated instance.
> 

HHH cannot possibly simulate itself correctly. So, it aborts the 
simulation one cycle too soon. So, it aborts incorrectly.
Aborting a halting program halfway its simulation is incorrect.
Therefore, its report is not about halting, but about correct simulation.
HHH reports that its simulation failed.
When HHH aborts, it can only report that its simulation failed. It 
cannot report about halting behaviour, because that behaviour is present 
in the part of the program that was skipped by the abort.