From: janburse@fastmail.fm   
      
   John Harris schrieb:   
   > Your JavaScript code includes some form of garbage   
   > collection. Has that influenced the data structures ?   
      
   There is a long thread about the early Garbage Collection   
   of Dogelog Player in comp.lang.python. Especially whether   
   it can be made fast, with useful input from a few   
   Pythonistas.   
      
   Then I post regularly about the evolution of the GC   
   of Dogelog Player. It was just posted a few days ago,   
   when you were still on your silly tangent that my   
      
   posts are nauseating. Now you are asking stuff, that   
   I am anyway posting about. Whats is wrong with you?   
   Do you have a PhD in being the most stupid person   
      
   on this planet? See here, few days ago,   
   to be exact 5 days ago:   
      
   Mild Shock schrieb 23.03.2024, 16:43:   
    >   
    > Dogelog Player is a Prolog system that features   
    > a generational garbage collector scheme and a   
    > change_arg/3 primitive built-in. So far the two   
    > didn’t go together and we had to use a cludge.   
    > With the upcoming release we provide a proper   
    > solution based on marking write-barriers.   
    >   
    > Our remembered set on the variable binding trail   
    > has the benefit that it can reduce itself during   
    > backtracking. By adopting conductor variables, i.e.   
    > instantiated variables that are not trailed, from   
    > formerly Jekejeke Prolog, we could recreate a   
    > similar benefit for Dogelog Players change_arg/3.   
    >   
    > See also:   
    >   
    > Marking Write-Barriers for Dogelog Player   
    > https://twitter.com/dogelogch/status/1771559896741192186   
    >   
    > Marking Write-Barriers for Dogelog Player   
    > https://www.facebook.com/groups/dogelog   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)