Re: HHH(DDD) computes the mapping from its input to HHH emulating itself emulating DDD

On 12/4/24 9:27 AM, olcott wrote:

On 12/3/2024 5:39 PM, Richard Damon wrote:

On 12/3/24 6:08 PM, olcott wrote:

On 12/3/2024 3:03 AM, joes wrote:

Am Mon, 02 Dec 2024 20:48:49 -0600 schrieb olcott:

On 11/28/2024 1:48 PM, joes wrote:

>

You said:
  >>> HHH can't simulate itself.
That is WRONG !!!
HHH DOES EMULATE ITSELF PROVING THAT IT CAN EMULATE ITSELF.

We know that HHH halts. It doesn't simulate itself halting.
>

>
Please try and explain how you are not dishonest what you
try to change the subject from my rebuttal of your statement:
>
 >>> HHH can't simulate itself.
>
That HHH does emulate itself emulating DDD proves
THAT IT CAN DO THIS.
>

>
But only if your think that wrong answer can be right.

 I did not mention anything about answers my entire
scope is that HHH does emulate itself emulating DDD
thus conclusively proving that HHH can emulated itself
emulating DDD.
 Whenever you go out-of-scope like this it surely
seems dishonest to me.
 

But the behaivor that HHH shows that it has *IS* an "answer", and if it shows wrong behaivor (like HHH(DDD) not returning, when it does) it MSUT be an incorrecte behavior.
The problem is HHH is doing incorrect logic because it doesn't actually look at the behaior of the exact HHH that DDD is calling, in part because you don't include it in the input so it can think of that HHH as something other that what it is.
Haven't you claim that HHH looks at an "idealized" HHH, but DDD calls the ACTUAL HHH? That is just exposing your lies.