Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD)

On 5/11/2025 7:09 AM, Mr Flibble wrote:

On Sun, 11 May 2025 12:57:21 +0100, Richard Heathfield wrote:
 

On 11/05/2025 12:48, Mr Flibble wrote:

On Sun, 11 May 2025 10:34:18 +0000, Alan Mackenzie wrote:
>

Mr Flibble <flibble@red-dwarf.jmc.corp> wrote:

>
<snip>
>

Nope, I have formally defined the error that doesn't contradict
Peter's work.

>
You don't even understand what "formally" means.

>
Sure I do. I can formally define it again for you if you like? Here is
the formal definition:
>
What constitutes halting problem pathological input:
>
Input that would cause infinite recursion when using a decider of the
simulating kind.

>
When executed directly, such an input would either halt or not,
category error or no.
>
Which is it?

 Peter's view:
* direct execution results in infinite recursion which is treated as non-
halting.
 

Not exactly, it is not direct execution.
int DD()
{
   int Halt_Status = HHH(DD);
   if (Halt_Status)
     HERE: goto HERE;
   return Halt_Status;
}
DD emulated by HHH according to the rules
of the x86 language cannot possibly reach
its own emulated final halt state.

Flibble's view:
* direct execution results in manifestation of the category error: which
in practice means a crash in the form of a stack fault (debatable halting
equivalance) for a decider with finite resources (stack space) or non-
halting for a decider with infinitie resources (stack space).
 /Flibble

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