Re: No decider is ever accountable for the behavior of the computation that itself is contained within, unless that is what the input descriibes

Liste des GroupesRevenir à theory 
Sujet : Re: No decider is ever accountable for the behavior of the computation that itself is contained within, unless that is what the input descriibes
De : richard (at) *nospam* damon-family.org (Richard Damon)
Groupes : comp.theory
Date : 27. Jul 2024, 23:14:01
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <90d33090c31448c0e0c0cca8c2ab677c06004d35@i2pn2.org>
References : 1 2 3
User-Agent : Mozilla Thunderbird
On 7/27/24 10:21 AM, olcott wrote:
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).
It computes the mapping from its input to the value of their sum.
Right, and the input to HHH(DDD) is the PROGRAM DDD

 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.
 
And if that finite string doesn't contain ALL the code of DDD, it just isn't the right input, or the right inerpreation of the inpt,

The input to HHH(DDD) specifies the equivalent of infinite
recursion as fully elaborated in another reply.
 
Nope, that comment just shows that you are just an ignorant pathoological liar.
Which case is it:
The input doesn't contain the full code of DDD, and thus isn't a proper input to ask about the behavior of DDD, and thus your whole arguement is based on a false premise that you are asking the question you say you are, since HHH can not do a correct x86 emulation of code that it does not have.
That you think of the input as containing a version of HHH that differs in actual behavior from the ACTUAL HHH that is there, and thus you are lying that you are asking about the DDD that is actually there (as that DOES call the HHH that behaves as the HHH that main calls).
That you admit that the input contains the same version of HHH as is there, but HHH is allowed to think of it as something different, and ignore that it WILL abort its emulation and return, and thus you are lying about HHH actually doing something at least generically called a correct emulation, since a correct emulation must replicate the behavior of the thing being emulated.
Or, you just admit that you are lying about what HHH is doing.
You get your choice, which way are you lying
YOU ARE LYIBG,
Try to sbow how what you are doing is ACTUALLY correct, since you admit that the diffect execution of DDD will halt, and the actual question to HHH is what the direct execution does, which you admit is different then th e answer you are giving.
Where is an actually reliable source, and not just one of your LYING CLAIMS that justifies your LYING CLAIM.
Sorry, you have just built your life on lies, and are paying the price for that in a destroyed reputation.

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