On 11/3/2025 6:24 PM, Kaz Kylheku wrote:
On 2025-11-03, olcott <polcott333@gmail.com> wrote:
On 11/3/2025 4:40 PM, Kaz Kylheku wrote:
On 2025-11-03, olcott <polcott333@gmail.com> wrote:
On 11/3/2025 2:43 PM, Kaz Kylheku wrote:
On 2025-11-02, Kaz Kylheku <643-408-1753@kylheku.com> wrote:
On 2025-11-02, olcott <polcott333@gmail.com> wrote:
You said they be identical. If they are not equivlaent they can't >>>>>>>> be identical.
Identical code and different behavior
because D calls H in recursive simulation
and D does not call H1 in recursive simulation.
Can you show that concretely with C?
Didn't think so.
I have done that hundreds of times and you just ignore it.
What? Where? All you ever post these days is useless talk.
Where is the URL to a project with .c files and a Makefile, etc?
Are you saying that you are smart enough to do this:
On 10/31/2025 7:44 PM, Kaz Kylheku wrote:
I can write a C interpreter which can interpret itself.
Yet not smart enough to do a simple execution trace in your head?
Bleeping idiot, of course it was the "execution trace in my head"
which led me to the realization that abandoned simulations of D have
a continuable future which leads to termination.
int D()
{
int Halt_Status = H(D);
if (Halt_Status)
HERE: goto HERE;
return Halt_Status;
}
Then try and prove this by showing an execution
trace of D simulated by H entirely in C.
Don't show any execution trace of anything besides
D and do this entirely in C. I will get you started:
H simulates D that calls H(D) that simulates D that calls H(D)
What step(s) of D come next in C?
--
Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer
--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)