Re: HHH(DDD)==0 is correct

On 7/4/25 6:17 PM, olcott wrote:

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

On 7/4/25 2:24 PM, olcott wrote:

On 7/4/2025 12:48 PM, Richard Damon wrote:

On 7/4/25 9:32 AM, olcott wrote:

On 7/4/2025 8:22 AM, joes wrote:

Am Fri, 04 Jul 2025 07:50:23 -0500 schrieb olcott:

On 7/4/2025 2:35 AM, Mikko wrote:

On 2025-07-03 12:56:42 +0000, olcott said:

On 7/3/2025 3:57 AM, Mikko wrote:

On 2025-07-03 02:50:40 +0000, olcott said:

On 7/1/2025 11:37 AM, Mr Flibble wrote:

On Mon, 30 Jun 2025 21:12:48 -0400, Richard Damon wrote:

On 6/30/25 2:30 PM, Mr Flibble wrote:

>

No. A simulator does not have to run a simulation to completion if
it can determine that the input, A PROGRAM, never halts.

>

If. But here it confuses that with not being able to simulate past the
recursive call.
>

>
It is the correct simulation of the input that
specifies the actual behavior of this input.

>
Right, and that means correctly simulating EVERY instruction that makes up the PROGRAM, which must include the code of *THE* HHH, or you can't "correctly simulate" the call instruction.
>
SIn
>

>
If this simulation cannot simulate past the recursive
call then this correctly simulated input cannot possibly
reach its own correctly simulated final halt state.
>

>
But it can, as the call goes into HHH, and you then just simulate the code of HHH.
>

>
Do you mean like this? (as I have been telling you for three years)
https://liarparadox.org/HHH(DDD)_Full_Trace.pdf

>
Yes, so where in that trace does HHH's "correct simulation" differ from the exact same simulation generated by HHH1 before HHH aborts?
>
>

 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.

And where does that show as a difference in the trace?
"itself" isn't something in the code/
Both are supposed to be simuating the input, which is DDD calling HHH.
You still need to try to prove your FALSEHOOD that the simualtion of the HHH called by DDD depends on who is doing the simulation, when that concept is in direct contradiction to the defintions of correct simulation.
Sorry, you are just proving you are a stupid liar,

 HHH doesn't actually abort its simulation of DDD until
after has simulated many hundreds of simulated instructions
later. HHH simulates itself simulating DDD until DDD calls
HHH(DDD) again.

And thus HHH is part of the input, and thus is the same HHH as is simulating it, and thus the first HHH simulated will also abort its simulation and return 0, a fact IGNORED by you, because you are too stupid.

 I only address one point at a time because you
find that one single point to be impossibly too
difficult for you. When I tell you something
500 times you never notice that I even said it once.
 

So ADDRESSS it. You just repeat your same lies.
Your "one thing at a time" is just your excuse to not get to the actual problems, and just let you keep on equivocating between you multiple inconsistant definitions of what you are talking about.
That is the FACT of you argument, it is based on internally self-contradictory meanings.
For example, is the code of HHH part of the input, you need both:
NO, so that every variation of the program DDD is the "same", but also
YES, as you need it to be there to simulate it, it just isn't a "constant" part
In other words, your world is just based on lies.