1. Forum
  2. Newsgroups
  3. comp.theory

  • Re: I've written the code which shows HHH's DDD simulation halts.

    From olcott@polcott333@gmail.com to comp.theory on Fri Oct 31 09:11:31 2025
    From Newsgroup: comp.theory

    On 10/25/2025 9:40 PM, Kaz Kylheku wrote:
    On 2025-10-26, Kaz Kylheku <643-408-1753@kylheku.com> wrote:
    I am still puzzled by a few things:

    - why I am not seeing more than one unfinished simulation captured,
    since the simulated DDD is expected to be starting one.

    I see why now. The recursive simulations are not allocating
    ane xecution trace (because sharing one execution trace is necessary
    for Olcott to confuse himself into thinking that nested simulation
    is recursion, by pretending that there is only one instruction stream
    or control flow.

    My "reckoning" machinery looks for certain Allocate calls in certain
    sizes by which it detects that Init_Halts_HH is executing and
    setting up a new simulation.

    But the nested simuations do not allocate the execution trace. I made
    it a condition for recognizing the start of a simulation that the
    execution trace Allocate must be observed.

    So that is why DDD simulations after the first one are not being tracked
    in my system.


    That is ridiculously stupid.
    You could do this same stupid thing with
    infinite recursion and then have no idea
    why your program keeps crashing.

    "I've written the code which shows HHH's
    DDD simulation halts."

    That is a damned lie. You have written code
    that ignores why DDD does not halt. that it
    never returns from the command prompt should
    tell you how stupid this is.


    That doesn't prevent anything from working and showing what is necessary.

    --
    Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
    hits a target no one else can see." Arthur Schopenhauer
    --- Synchronet 3.21a-Linux NewsLink 1.2