Sujet : Re: Defining a correct simulating halt decider
De : richard (at) *nospam* damon-family.org (Richard Damon)
Groupes : comp.theoryDate : 07. Sep 2024, 17:32:34
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <ddd238668be1d2b9e8598893336543864a3b8fef@i2pn2.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
User-Agent : Mozilla Thunderbird
On 9/7/24 11:14 AM, olcott wrote:
On 9/7/2024 10:10 AM, Richard Damon wrote:
On 9/7/24 10:54 AM, olcott wrote:
On 9/7/2024 9:46 AM, joes wrote:
Am Sat, 07 Sep 2024 08:38:22 -0500 schrieb olcott:
On 9/5/2024 12:22 PM, joes wrote:
Am Thu, 05 Sep 2024 12:17:01 -0500 schrieb olcott:
On 9/5/2024 11:56 AM, joes wrote:
Am Thu, 05 Sep 2024 11:52:04 -0500 schrieb olcott:
On 9/5/2024 11:34 AM, joes wrote:
Am Thu, 05 Sep 2024 11:10:40 -0500 schrieb olcott:
On 9/5/2024 10:57 AM, joes wrote:
Am Thu, 05 Sep 2024 08:24:20 -0500 schrieb olcott:
On 9/5/2024 2:34 AM, Mikko wrote:
On 2024-09-03 13:00:50 +0000, olcott said:
On 9/3/2024 5:25 AM, Mikko wrote:
On 2024-09-02 16:38:03 +0000, olcott said:
>
The directly executed HHH correctly determines that its emulated DDD
must be aborted because DDD keeps *THE EMULATED HHH* stuck in
recursive emulation.
Why doesn’t the simulated HHH abort?
The first HHH cannot wait for its HHH to abort which is waiting for
its HHH to abort on and on with no HHH ever aborting.
But why does HHH halt and return that itself doesn’t halt?
When HHH is waiting for the next HHH which is waiting for the next HHH
which is waiting for the next HHH...
we have an infinite chain of waiting and never aborting.
Except for the outermost one.
>
>
When the outermost HHH is waiting for its emulated HHH
to abort and this emulated HHH is waiting on its emulated
HHH to abort on and on forever waiting and none ever abort.
>
>
Which only happens if HHH is defined in a way that it never aborts this simulaiton, and that HHH isn't a correct decider.
>
That is NOT what Joes has been proposing.
Joes has been proposing that each HHH in the recursive chain
can wait until the next one aborts and that the abort will
still occur at the end of this infinite chain.
No, he is pointing out that get the right answer, each HHH NEEDS to wait for the previous one to get the right answer.
But, if to do so, it results in the definition of HHH that just never aborts and thus HHH isn't a decider.
You just don't seem to understand the difference between what you implement and what is needed to meet the requirements.
If what is needed to meet the requirements is not implementable, then the conclusion is that the problem is impossible to do, which is the case here.
Your inability to understand this just shows your fundamental lack of understanding of the system.