Liste des Groupes | Revenir à theory |
On 8/21/2024 1:21 PM, Fred. Zwarts wrote:You keep forgetting that when the code to abort is added, the program changes, another HHH is created, for which another DDD can be created that calls the aborting HHH.Op 21.aug.2024 om 14:35 schreef olcott:<MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>>>
No. This is your lack of software engineering skill.
>
Mike understands this:
Each HHH has seen one more execution trace than the next inner HHH.
Thus when the outermost one waits for its inner on to abort this
forms an infinite chain or waiting with none of them ever aborting.
>
Yes, HHH cannot possibly simulate itself correctly. If it aborts, it aborts too soon, one cycle before the simulated HHH would abort and halt. But if it waits for completion, it waits forever. There is no correct way for a simulator to simulate itself correctly.
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
H can abort its simulation of D and correctly report that D
specifies a non-halting sequence of configurations.
</MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>
HHH only needs to simulate itself simulating DDD once to
correctly determine that its simulated DDD would
never stop running unless aborted...
Les messages affichés proviennent d'usenet.