Sujet : Re: Simulating termination analyzers by dummies --- What does halting mean?
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theory sci.logicDate : 18. Jun 2024, 23:08:32
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v4st0g$1hjnp$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
User-Agent : Mozilla Thunderbird
On 6/18/2024 12:57 PM, joes wrote:
Am Tue, 18 Jun 2024 12:25:44 -0500 schrieb olcott:
On 6/18/2024 12:06 PM, joes wrote:
void DDD()
{
H0(DDD);
}
DDD correctly simulated by any H0 cannot possibly halt.
DDD halts iff H0 halts.
So H0 returns "doesn't halt" to DDD, which then stops running,
so H0 should have returned "halts".
This was three messages ago.
I had to make sure that you understood that halting
does not mean stopping for any reason and only includes
the equivalent of terminating normally.
DDD correctly emulated by H0 DOES NOT TERMINATE NORMALLY.
Some TM's loop and thus never stop running, this is classical
non-halting behavior. UTM's simulate Turing machine descriptions.
This is the same thing as an interpreter interpreting the source-code of
a program.
Some TMs do not loop and do not halt.
A UTM can be adapted so that it only simulates a fixed number of
iterations of an input that loops. When this UTM stops simulating this
Turing machine description we cannot correctly say that this looping
input halted.
Yes. We also cannot say that that input was simulated correctly.
-- Copyright 2024 Olcott "Talent hits a target no one else can hit; Geniushits a target no one else can see." Arthur Schopenhauer