Liste des Groupes | Revenir à theory |
They all say that HHH must report on the behavior ofBecause that's what we want to know about:
direct execution of DDD()
yet never bother to noticeThat doesn't change the fact that we want to know if any arbitrary algorithm X with input Y will halt when executed directly, and we want an H that tell us that in *all* possible cases.
that the directly executed DDD() is the caller of HHH(DDD).
void DDD()It is accountable when that's what we're asking for.
{
HHH(DDD); // When DDD calls HHH(DDD) this HHH is not
return; // accountable for the behavior of its caller
}
On the other hand HHH(DDD) is accountable for theWhich is the behavior of the algorithm DDD consisting of the fixed code of the function DDD, the fixed code of the function HHH, and the fixed code of everything function HHH calls down to the OS level, and behavior is halting.
behavior that its actual input actually specifies.
HHH(DDD) simulates DDD that calls HHH(DDD)And again you lie by implying that Sipser agrees with your meaning of the above when the fact is that he doesn't:
that simulates DDD that calls HHH(DDD)
that simulates DDD that calls HHH(DDD)
that simulates DDD that calls HHH(DDD)...
<MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>
If simulating halt decider H correctly simulates its
input D until H correctly determines that its simulated D
*would never stop running unless aborted* then
Les messages affichés proviennent d'usenet.