Liste des Groupes | Revenir à theory |
On 10/15/2024 9:11 PM, Richard Damon wrote:Other than producing a different trace. Seriously, why else should itOn 10/15/24 4:01 PM, olcott wrote:It has no effect on the trace itself.On 10/15/2024 2:33 PM, joes wrote:No, that code is still active. it is the source of the value for theAm Tue, 15 Oct 2024 13:25:36 -0500 schrieb olcott:There is some code that was obsolete several years ago.On 10/15/2024 10:17 AM, joes wrote:>Am Tue, 15 Oct 2024 08:11:30 -0500 schrieb olcott:On 10/15/2024 6:35 AM, Richard Damon wrote:On 10/14/24 10:13 PM, olcott wrote:On 10/14/2024 6:50 PM, Richard Damon wrote:On 10/14/24 11:18 AM, olcott wrote:On 10/14/2024 7:06 AM, joes wrote:Am Mon, 14 Oct 2024 04:49:22 -0500 schrieb olcott:On 10/14/2024 4:04 AM, Mikko wrote:On 2024-10-13 12:53:12 +0000, olcott said:Oh, did you take out the check if HHH is the root simulator?There are no static root variables. There never has been any "not aYes! It really has different code, by way of the static RootIt explains in great detail that another different DDD (samehttps://chatgpt.com/share/6709e046-4794-8011-98b7-27066fb49f3eI did that, and it admitted that DDD halts, it just tries to
When you click on the link and try to explain how HHH must be
wrong when it reports that DDD does not terminate because DDD
does terminate it will explain your mistake to you.
justify why a wrong answer must be right.
machine code different process context) seems to terminate only
because the recursive emulation that it specifies has been aborted
at its second recursive call.
variable.
No wonder it behaves differently.
pure function of its inputs" aspect to emulation.
variable Root that is passed around, and is checked in the code to
alter the behavior.
It only affects the termination status decision that I conclusivelySure, "DDD is the same program, except for a variable which directly
prove is unequivocally correct no matter how HHH detects this.
Les messages affichés proviennent d'usenet.