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 : mikko.levanto (at) *nospam* iki.fi (Mikko)
Groupes : comp.theory
Date : 30. Jul 2024, 07:56:21
Autres entêtes
Organisation : -
Message-ID : <v8a2ql$u68g$1@dont-email.me>
References : 1 2 3 4 5
User-Agent : Unison/2.2
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?
--
Mikko

Date Sujet#  Auteur
3 Jul 25 o 

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal