Re: No decider is accountable for the computation that itself is contained within

Liste des GroupesRevenir à theory 
Sujet : Re: No decider is accountable for the computation that itself is contained within
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theory
Date : 30. Jul 2024, 23:22:49
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v8blja$16ibk$3@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12
User-Agent : Mozilla Thunderbird
On 7/30/2024 4:09 PM, joes wrote:
Am Tue, 30 Jul 2024 15:13:34 -0500 schrieb olcott:
On 7/30/2024 2:52 PM, joes wrote:
Am Tue, 30 Jul 2024 11:24:35 -0500 schrieb olcott:
On 7/30/2024 2:24 AM, joes wrote:
Am Mon, 29 Jul 2024 15:32:44 -0500 schrieb olcott:
On 7/29/2024 3:17 PM, joes wrote:
Am Mon, 29 Jul 2024 11:32:00 -0500 schrieb olcott:
On 7/28/2024 3:40 AM, Mikko wrote:
On 2024-07-27 14:21:50 +0000, olcott said:
On 7/27/2024 2:46 AM, Mikko wrote:
On 2024-07-26 16:28:43 +0000, olcott said:
>
Halt deciders are not allowed to report on the behavior of the
actual computation that they themselves are contained within. They
are only allowed to compute the mapping from input finite strings.
What if the input is the same as the containing computation?
It always is except in the case where the decider is reporting on
the TM description that itself is contained within.
>
I don't understand. "The input is not the same as the containing
computation when deciding on the description of the containing
computation"?
I mean: is that an accurate paraphrase?
>
An executing Turing machine is not allowed to report on its own
behavior. Every decider is only allowed to report on the behavior that
its finite string input specifies.
And what happens when those are the same?

That is always the case except in the rare exception that I discovered
where a simulating halt decider is simulating the input that calls
itself.

Always? Most TMs don't get themselves as input. OTOH that is one of
the most interesting cases.
The description of a TM specifies the behaviour of that machine
when it is running.
 
The x86 code of DDD when correctly emulated by HHH according
to the semantics of the x86 code of DDD and HHH does have
different behavior that the directly executed DDD as a matter
of verified fact for three years.
People deny this as if a smash a Boston Cream pie in the face
and they deny that there ever was any pie even while their
voice is incoherent because they are talking through the pie
smashed on their face.
*I do not a more precise way to say this now*
DDD is emulated by HHH according to the semantics of the
x86 code of DDD and HHH. This does include a recursive call
from DDD to HHH(DDD) that cannot possibly stop repeating
unless HHH aborts its emulation of DDD.
--
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

Date Sujet#  Auteur
26 Jul 24 * No decider is ever accountable for the behavior of the computation that itself is contained within45olcott
26 Jul 24 +* Re: No decider is ever accountable for the behavior of the computation that itself is contained within6olcott
26 Jul 24 i+* Re: No decider is ever accountable for the behavior of the computation that itself is contained within3olcott
27 Jul 24 ii+- Re: No decider is ever accountable for the behavior of the computation that itself is contained within (unless that is its input)1Richard Damon
27 Jul 24 ii`- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Fred. Zwarts
27 Jul 24 i+- Re: No decider is ever accountable for the behavior of the computation that itself is contained within (unless that is its input)1Richard Damon
27 Jul 24 i`- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Fred. Zwarts
27 Jul 24 +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within (Unless that is its input)1Richard Damon
27 Jul 24 +* Re: No decider is ever accountable for the behavior of the computation that itself is contained within32Mikko
27 Jul 24 i`* Re: No decider is ever accountable for the behavior of the computation that itself is contained within31olcott
27 Jul 24 i +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Fred. Zwarts
28 Jul 24 i +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within, unless that is what the input descriibes1Richard Damon
28 Jul 24 i `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within28Mikko
29 Jul 24 i  `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within27olcott
29 Jul 24 i   +* Re: No decider is accountable for the computation that itself is contained within19joes
29 Jul 24 i   i`* Re: No decider is accountable for the computation that itself is contained within18olcott
30 Jul 24 i   i `* Re: No decider is accountable for the computation that itself is contained within17joes
30 Jul 24 i   i  `* Re: No decider is accountable for the computation that itself is contained within16olcott
30 Jul 24 i   i   +* Re: No decider is accountable for the computation that itself is contained within4Fred. Zwarts
30 Jul 24 i   i   i`* Re: No decider is accountable for the computation that itself is contained within3olcott
31 Jul 24 i   i   i +- Re: No decider is accountable for the computation that itself is contained within, unless that is its input1Richard Damon
31 Jul 24 i   i   i `- Re: No decider is accountable for the computation that itself is contained within1Fred. Zwarts
30 Jul 24 i   i   +* Re: No decider is accountable for the computation that itself is contained within10joes
30 Jul 24 i   i   i`* Re: No decider is accountable for the computation that itself is contained within9olcott
30 Jul 24 i   i   i +* Re: No decider is accountable for the computation that itself is contained within7joes
30 Jul 24 i   i   i i`* Re: No decider is accountable for the computation that itself is contained within6olcott
31 Jul 24 i   i   i i +* Re: No decider is accountable for the computation that itself is contained within4Mike Terry
31 Jul 24 i   i   i i i`* Re: No decider is accountable for the computation that itself is contained within3olcott
31 Jul 24 i   i   i i i +- Re: No decider is accountable for the computation that itself is contained within, unless that is its input1Richard Damon
31 Jul 24 i   i   i i i `- Re: No decider is accountable for the computation that itself is contained within1Fred. Zwarts
31 Jul 24 i   i   i i `- Re: No decider is accountable for the computation that itself is contained within1Fred. Zwarts
31 Jul 24 i   i   i `- Re: No decider is accountable for the computation that itself is contained within, unless that is its input1Richard Damon
31 Jul 24 i   i   `- Re: No decider is accountable for the computation that itself is contained within, unless that is its input1Richard Damon
30 Jul 24 i   +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within UNLESS that is what the input actually describes1Richard Damon
30 Jul 24 i   `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within6Mikko
31 Jul 24 i    `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within5olcott
1 Aug 24 i     `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within4Mikko
1 Aug 24 i      `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within3olcott
1 Aug 24 i       +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1joes
2 Aug 24 i       `- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Mikko
27 Jul 24 +- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Fred. Zwarts
27 Jul 24 `* Re: No decider is ever accountable for the behavior of the computation that itself is contained within4Mad Hamish
27 Jul 24  +* Re: No decider is ever accountable for the behavior of the computation that itself is contained within DETAILS2olcott
28 Jul 24  i`- Re: No decider is ever accountable for the behavior of the computation that itself is contained within DETAILS unless that is what the input is representing.1Richard Damon
28 Jul 24  `- Re: No decider is ever accountable for the behavior of the computation that itself is contained within1Mikko

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal