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

Liste des GroupesRevenir à theory 
Sujet : Re: No decider is ever accountable for the behavior of the computation that itself is contained within
De : polcott333 (at) *nospam* gmail.com (olcott)
Groupes : comp.theory
Date : 01. Aug 2024, 12:38:36
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v8fs3s$24rl1$3@dont-email.me>
References : 1 2 3 4 5 6 7 8
User-Agent : Mozilla Thunderbird
On 8/1/2024 2:40 AM, Mikko wrote:
On 2024-07-30 23:20:43 +0000, olcott said:
 
On 7/30/2024 1:56 AM, Mikko wrote:
On 2024-07-29 16:32:00 +0000, olcott said:
>
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:
>
No decider is ever accountable for the behavior of the
computation that itself is contained within.
>
That claim is fully unjustified. How do you even define "accountable"
in the context of computations, automata, and deciders?
>
int sum(int x, int y){ return x + y; }
sum(5,6) is not accountable for reporting sum(3,2).
>
That claim is fully unjustified. How do you even define "accountable"
in the context of computations, automata, and deciders?
>
It computes the mapping from its input to the value of their sum.
>
That's obvious but is it relevant?
>
HHH must compute the mapping from its input finite string
of the x86 machine code of DDD to the behavior that this
finite string specifies and then report on the halt status
of this behavior.
>
Now is that relevant?
>
Halt deciders report the halt status on the basis
of the behavior that a finite string input specifies.
>
How is that relevant?
>
Computable functions are the formalized analogue of the intuitive notion of algorithms, in the sense that a function is computable if there exists an algorithm that can do the job of the function, i.e. *given an* *input of the function domain it can return the corresponding output* https://en.wikipedia.org/wiki/Computable_function
 How is that relevant?
 The question is still unanswered. Apparently the answer is "no way" or
an answer would already be given.
 
int main() { DDD(); } halts yet is HHH is no allowed
to consider that. HHH is not allowed to report on the
behavior of the computation that itself is contained
within. HHH is only allowed to report on the behavior
that its input finite string specifies.
It is a matter of verified fact that when DDD is correctly
emulated by HHH that the sequence of steps is different
than when DDD is correctly emulated by HHH1.
correctly emulated* According to the x86 semantics of
DDD, HHH, and HHH1.
It has always been correct for the last three years
and people try to get away with "it doesn't do what
I expect therefore its wrong".
--
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