Liste des Groupes | Revenir à theory |
*The best selling author of theory of computation textbooks*Right, if the correct (and thus complete) emulation of this precise input would not halt.
<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
H can abort its simulation of D and correctly report that DWhich your H doesn't do.
specifies a non-halting sequence of configurations.
</MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>
Correct simulation is defined as D is emulated by H according toAnd also means that it can not be aborted, as "stopping" in the middle is not to the semantics of the x86 language.
the semantics of the x86 language thus includes H emulating itself
emulating D.
I made D simpler so that the key essence of recursive simulationNope, your broke the rules of the field, and thus invalidates your proof.
could be analyzed separately. ChatGPT totally understood this.
void DDD()But DDD doesn't call an "ideaized" verision of HHH, it calls the exact function defined as HHH, s0 your arguemet is based on false premises, and thus is just a :OE/
{
HHH(DDD);
return;
}
ChatGPT
Simplified Analogy:
Think of HHH as a "watchdog" that steps in during real execution
to stop DDD() from running forever. But when HHH simulates DDD(),
it's analyzing an "idealized" version of DDD() where nothing stops the
recursion. In the simulation, DDD() is seen as endlessly recursive, so
HHH concludes that it would not halt without external intervention.
https://chatgpt.com/share/67158ec6-3398-8011-98d1-41198baa29f2No, because there aren't "levels" of emulation under consideration here. Only does the emulation that the top level HHH is doing, since everything else is just fixed by the problem.
This link is live so you can try to convince ChatGPT that its wrong.
On 11/3/2024 12:20 PM, Richard Damon wrote:
> On 11/3/24 9:39 AM, olcott wrote:
>>
>> The finite string input to HHH specifies that HHH
>> MUST EMULATE ITSELF emulating DDD.
>
> Right, and it must CORRECTLY determine what an unbounded
> emulation of that input would do, even if its own programming
> only lets it emulate a part of that.
>
*Breaking that down into its key element*
> [This bounded HHH] must CORRECTLY determine what
> an unbounded emulation of that input would do...
When that input is unbounded that means it is never
aborted at any level, otherwise it is bounded at some
level thus not unbounded.
>
Les messages affichés proviennent d'usenet.