Re: My reviewers think that halt deciders must report on the behavior of their caller

Op 05.jul.2025 om 18:12 schreef olcott:

On 7/5/2025 2:39 AM, Fred. Zwarts wrote:

Op 05.jul.2025 om 00:15 schreef olcott:

On 7/4/2025 3:53 PM, Richard Damon wrote:

On 7/4/25 4:43 PM, olcott wrote:

On 6/3/2025 10:02 PM, dbush wrote:

On 6/3/2025 10:58 PM, olcott wrote:

On 6/3/2025 9:46 PM, dbush wrote:

On 6/3/2025 10:34 PM, olcott wrote:

On 6/3/2025 9:12 PM, dbush wrote:

>
Given any algorithm (i.e. a fixed immutable sequence of instructions) X described as <X> with input Y:
>
A solution to the halting problem is an algorithm H that computes the following mapping:
>
(<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
(<X>,Y) maps to 0 if and only if X(Y) does not halt when executed directly
>

>
Yes there is no algorithm that does that

>
Excellent!
>
Let The Record Show
>
That Peter Olcott
>
Has *EXPLICITLY* admitted
>
That no algorithm H exists that meets the above requirements, which is precisely the theorem that the halting problem proofs prove.

>
In the exact same way that there is no set of all set
that contain themselves. ZFC did not solve Russell's
Paradox as much as it showed that Russell's Paradox
was anchored in an incoherent foundation, now called
naive set theory.

>
Which arose because the axioms of naive set theory created a contradiction.
>

>
Likewise with halt deciders that are required to report
on the behavior of directly executed Turing machines.

>
And what is the CONTRADICTION?
>
The result is just some things are not computable.
>

>
Directly executed Turing machines are outside of the
domain of every Turing machine decider.

>
Then so is mathematics, as "numbers" can't be given to Turing Machines, only representations of them.
>

>
Numbers always work the same way so it makes no difference.
>
*HHH(DDD)==0 and HHH1(DDD)==1 are both correct*
https://claude.ai/share/da9b8e3f-eb16-42ca-a9e8-913f4b88202c
>
When we compare DDD emulated by HHH and DDD emulated
by HHH1 SIDE-BY-SIDE. (Mike didn't do it this way).
>
*The difference is when*
HHH begins to simulate itself simulating DDD and
HHH1 NEVER begins to simulate itself simulating DDD.
>

Misleading words. Both simulators are given the same input. Both are simulating the same input, which includes HHH, not HHH1. So, there is no difference.

 *Its just over your head*
HHH(DDD) Does simulate itself simulating DDD
thus causing recursive simulation that cannot
possibly reach the simulated final halt state of DDD.
 

It is apparently over your head that when HHH is unable to reach the end of the simulation, this is not a proof that the end does not exist.
A failing HHH that forgets to count all relevant conditional branch instructions is not a proof that a correct simulation is unable to reach that end.
We see that HHH1 and HHH are simulating exactly the same instructions, but HHH fails to reach the end, because of a premature abort, where HHH1 has no problem to reach the end. This proves that the input specifies an end, but HHH fails to reach it. You still cannot point to one single instruction that is correctly simulated differently by HHH1 and HHH. Only the last instruction simulated by HHH is incorrect, because the semantics of the x86 language requires the processing of the next instruction, but HHH gives up.