Sujet : Re: 197 page execution trace of DDD correctly simulated by HHH
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theoryDate : 29. Jun 2024, 22:03:02
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v5pp9m$2jk8$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
User-Agent : Mozilla Thunderbird
On 6/29/2024 2:44 PM, joes wrote:
Am Fri, 28 Jun 2024 14:28:20 -0500 schrieb olcott:
On 6/28/2024 2:18 PM, joes wrote:
Am Fri, 28 Jun 2024 12:53:46 -0500 schrieb olcott:
On 6/28/2024 12:41 PM, joes wrote:
Thanks for leaving the unanswered questions in place, though I’d
rather have you answer them.
Am Fri, 28 Jun 2024 12:05:18 -0500 schrieb olcott:
On 6/28/2024 11:26 AM, joes wrote:
Am Fri, 28 Jun 2024 10:25:36 -0500 schrieb olcott:
On 6/28/2024 8:14 AM, joes wrote:
Am Thu, 27 Jun 2024 12:30:38 -0500 schrieb olcott:
To the caller DDD, which then returns to its own caller H0, which
returns „halting” to main… hold on.
Why doesn’t the first recursive H return?
Question still not answered.
HHH(DDD)
simulates DDD that calls HHH(DDD) that simulates DDD that calls HHH(DDD)
that proves to the outer directly executed HHH that it must abort and
reject.
How does it do that?
Over your head. I have explained it too many times
and you just can't get it.
Technically it is called detecting a repeating state.
I don't mean "New Jersey, New Jersey".
-- Copyright 2024 Olcott "Talent hits a target no one else can hit; Geniushits a target no one else can see." Arthur Schopenhauer
…