• Re: DD specifies non-terminating behavior to HHH --- RECURSIVE CHAIN

    From Richard Damon@21:1/5 to olcott on Sun Feb 16 07:09:36 2025
    On 2/15/25 10:25 PM, olcott wrote:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about that >>>>>>>>>> paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism. >>>>>>>> In order to determine the claim is false one needs some knowledge >>>>>>>> that is not obvious.
    When you try to show the steps attempting to show that it is false I >>>>>>> will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.

    But why are you not passing the same instance to HHH?


    The first instance of recursion is not exactly the same as subsequent instances of the exact same sequence of recursive invocations.

    Why not? What ACTUALLY was different?


    It is the same with recursive simulations. When the second recursive invocation has been aborted the first one terminates normally misleading people into believing that the recursive chain terminates normally.


    Because the second still has the property of aborting when correctly
    simulated.

    Your problem is you think LIES are true.

    Sorry, you are just too stupid to understand.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Feb 16 07:19:34 2025
    Continuing to direct follow-ups, and then adding back in your own
    replies can be considered abusive posting.

    It is a sign that you understand that your arguments are weak and do not
    stand the test of scrutiny. It also might rise to the level of a TOS
    violation, which could cost you the ability to post.

    On 2/15/25 10:25 PM, olcott wrote to comp.lang.c comp.lang.c++, comp.ak.philosophy:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about that >>>>>>>>>> paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism. >>>>>>>> In order to determine the claim is false one needs some knowledge >>>>>>>> that is not obvious.
    When you try to show the steps attempting to show that it is false I >>>>>>> will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.

    But why are you not passing the same instance to HHH?


    The first instance of recursion is not exactly the same as subsequent instances of the exact same sequence of recursive invocations.

    It is the same with recursive simulations. When the second recursive invocation has been aborted the first one terminates normally misleading people into believing that the recursive chain terminates normally.


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Sun Feb 16 12:55:32 2025
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism. >>>>>>>> In order to determine the claim is false one needs some knowledge >>>>>>>> that is not obvious.
    When you try to show the steps attempting to show that it is false >>>>>>> I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive invocation has been aborted the first one terminates normally misleading people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically
    toggles termination?

    --
    Am Sat, 20 Jul 2024 12:35:31 +0000 schrieb WM in sci.math:
    It is not guaranteed that n+1 exists for every n.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mr Flibble@21:1/5 to All on Sun Feb 16 13:50:06 2025
    On Sun, 16 Feb 2025 07:32:01 -0600, olcott <[email protected]>
    wrote:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism. >>>>>>>>>> In order to determine the claim is false one needs some knowledge >>>>>>>>>> that is not obvious.
    When you try to show the steps attempting to show that it is false >>>>>>>>> I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent
    instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive
    invocation has been aborted the first one terminates normally misleading >>> people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically
    toggles termination?


    The key verified fact that makes all such counter-arguments moot
    is that DD correctly simulated by HHH cannot possibly terminate normally.

    The input DD to HHH(DD) cannot possibly terminate normally
    HHH correctly reports this. No one else has ever gotten this
    far with the halting problem ever before.

    For a total decider there is no way to "correctly simulate" ALL inputs
    to achieve a halting result.

    /Flibble

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Feb 16 13:40:29 2025
    On 2/16/25 8:32 AM, olcott wrote:
    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism. >>>>>>>>>> In order to determine the claim is false one needs some knowledge >>>>>>>>>> that is not obvious.
    When you try to show the steps attempting to show that it is false >>>>>>>>> I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent
    instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive
    invocation has been aborted the first one terminates normally misleading >>> people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically
    toggles termination?


    The key verified fact that makes all such counter-arguments moot
    is that DD correctly simulated by HHH cannot possibly terminate normally.

    But that only applies *IF* HHH does such a correct simulation, which it doesn't.

    The input DD to HHH(DD) cannot possibly terminate normally
    HHH correctly reports this. No one else has ever gotten this
    far with the halting problem ever before.


    OF courrse it does, since it calls the HHH(DD) that also aborts and returns.

    Your problem is you just don't understand what "behavior" is.

    You are just showing that you don't understand the meaning of the basic
    terms you are using, and that you just don't care about that. becuase
    "truth" isn't actually an important concept to you, just your perversion
    of it that says that lies are ok to make up a truth if it supports what
    you want to be true.

    Thus, you are shown to be nothing but an ignornat pathological lying fraud.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sun Feb 16 21:24:43 2025
    Op 16.feb.2025 om 14:32 schreef olcott:
    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism. >>>>>>>>>> In order to determine the claim is false one needs some knowledge >>>>>>>>>> that is not obvious.
    When you try to show the steps attempting to show that it is false >>>>>>>>> I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent
    instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive
    invocation has been aborted the first one terminates normally misleading >>> people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically
    toggles termination?


    The key verified fact that makes all such counter-arguments moot
    is that DD correctly simulated by HHH cannot possibly terminate normally.
    Reporting that HHH is unable to simulate the halting program up to the
    end is indeed correct.
    This is very different from reporting that the program described by the
    input does not halt. That is something HHH cannot do correctly.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Thu Feb 20 10:28:31 2025
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism. >>>>>>>>>> In order to determine the claim is false one needs some knowledge >>>>>>>>>> that is not obvious.
    When you try to show the steps attempting to show that it is false >>>>>>>>> I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent
    instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive
    invocation has been aborted the first one terminates normally misleading >>> people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically
    toggles termination?

    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.

    Wrong. Termination analyzers deremine whether a program can run forever.
    They needn't determine whether the termination is normal. A termination analyzer may also report whatever it can determine from the analysis.

    All of which is of course irrelevant to the question whether the claim
    on the subject line is true.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Thu Feb 20 10:00:33 2025
    Am Wed, 19 Feb 2025 22:08:05 -0600 schrieb olcott:
    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a
    truism.
    In order to determine the claim is false one needs some
    knowledge that is not obvious.
    When you try to show the steps attempting to show that it is >>>>>>>>> false I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent
    instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive
    invocation has been aborted the first one terminates normally
    misleading people into believing that the recursive chain terminates
    normally.
    How interesting. Might this be due to a global variable that basically
    toggles termination?
    Termination analyzers determine whether or not their input could
    possibly terminate normally. Nothing can toggle this.
    Not even the variable Root in line 502 of Halt7.c?

    --
    Am Sat, 20 Jul 2024 12:35:31 +0000 schrieb WM in sci.math:
    It is not guaranteed that n+1 exists for every n.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Thu Feb 20 07:19:39 2025
    On 2/19/25 11:08 PM, olcott wrote:
    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism. >>>>>>>>>> In order to determine the claim is false one needs some knowledge >>>>>>>>>> that is not obvious.
    When you try to show the steps attempting to show that it is false >>>>>>>>> I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent
    instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive
    invocation has been aborted the first one terminates normally misleading >>> people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically
    toggles termination?


    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.



    Right, but "terminate normally" is defined by the RUNNING of that
    program, not by the analysers trying to simulate it.

    Partial simulation does not prove non-termination, only not-yet terminated.

    Sorry, you are just exposing your stupidity,

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Thu Feb 20 20:12:32 2025
    On 2/20/25 8:02 AM, olcott wrote:
    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a >>>>>>>>>>>> truism.
    In order to determine the claim is false one needs some >>>>>>>>>>>> knowledge
    that is not obvious.
    When you try to show the steps attempting to show that it is >>>>>>>>>>> false
    I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent >>>>> instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive >>>>> invocation has been aborted the first one terminates normally
    misleading
    people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically >>>> toggles termination?

    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.

    Wrong. Termination analyzers deremine whether a program can run forever.

    This would define simulating termination analyzers as impossible
    because every input that would otherwise run forever is aborted.

    The fact that the task is imposible, doesn't mean it is wrong.

    Note, an input that represents a program that actually WOULD run forever
    can be aborted by the analyzer. and the value 0 returned.

    The problem is the input has to be exactly the actual input, and it
    needs to be a program, which means it includes all the code that it
    uses, and thus DD is calling the HHH that will abort, and thus when you
    give the input to your correct emulator to try to show the behavior, it
    needs to still call that original decider.

    DD doesn't change what it is calling just because you are making a
    hypothetical change to the code of HHH, and you can't change the ACTUAL
    code of HHH, is it is defined in the input, so to change it is to lie
    about what you are looking at.

    Since your HHH that you say is correct is aborting and returning 0, then
    the actual behavior of DD is to call such an HHH, so the direct
    execution of it and the correct simulation of it does exactly that, and
    shows that HHH was just wrong to abort, because you programmed it with incorrect logic.

    Your failure to understand this is just showing your utter stupidity, so
    big that you can't understand your own stupidity, but just believe your
    own lies.


    They needn't determine whether the termination is normal. A termination
    analyzer may also report whatever it can determine from the analysis.

    All of which is of course irrelevant to the question whether the claim
    on the subject line is true.




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Fri Feb 21 10:10:08 2025
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism. >>>>>>>>>>>> In order to determine the claim is false one needs some knowledge >>>>>>>>>>>> that is not obvious.
    When you try to show the steps attempting to show that it is false >>>>>>>>>>> I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent >>>>> instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive >>>>> invocation has been aborted the first one terminates normally misleading >>>>> people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically >>>> toggles termination?

    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.

    Wrong. Termination analyzers deremine whether a program can run forever.

    This would define simulating termination analyzers as impossible
    because every input that would otherwise run forever is aborted.

    It would be aborted by external causes but not by the program itself so
    we can say that the program could run forever.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Fri Feb 21 20:05:36 2025
    On 2/21/25 5:39 PM, olcott wrote:
    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to >>>>>>>>>>>>>>>>>> that
    article before or when HHH
    That paper and its code are the only thing that I have >>>>>>>>>>>>>>>>> been
    talking about in this forum for several years. >>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are talking >>>>>>>>>>>>>>>> about
    that paper.
    Anyway, that is irrelevant to the fact that the subject >>>>>>>>>>>>>>>> line
    contains a false claim.
    It is a truism and not one person on the face of the >>>>>>>>>>>>>>> Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false is not a >>>>>>>>>>>>>> truism.
    In order to determine the claim is false one needs some >>>>>>>>>>>>>> knowledge
    that is not obvious.
    When you try to show the steps attempting to show that it >>>>>>>>>>>>> is false
    I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as
    subsequent
    instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive >>>>>>> invocation has been aborted the first one terminates normally
    misleading
    people into believing that the recursive chain terminates normally. >>>>>> How interesting. Might this be due to a global variable that
    basically
    toggles termination?

    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.

    Wrong. Termination analyzers deremine whether a program can run
    forever.

    This would define simulating termination analyzers as impossible
    because every input that would otherwise run forever is aborted.

    It would be aborted by external causes but not by the program itself so
    we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.



    But, since it does, the actual input DD is halting.

    A conclusion based on a false premise is invalid.

    And, HHH must be defined, and thus it has a single definintion, and thus
    always does the same thing for a given input.

    Something you seem too stupid to undetstand.

    WHen you include Halt7.c in the definitions of your logic, HHH is FIXED
    and is exactly as defined, and since that HHH does abort, it is
    illogical to talk about what happens if it doesn't.

    And thus Halt7.c can't be part of your logic system when you make that
    claim, and thus DD isn't a program, and thus your statement is a LIE
    since you can't determine halting on something that isn't a program.

    Again, just proving your total ignorance.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Sat Feb 22 10:45:13 2025
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>>>>>> talking about in this forum for several years. >>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are talking about >>>>>>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a truism.
    In order to determine the claim is false one needs some knowledge
    that is not obvious.
    When you try to show the steps attempting to show that it is false
    I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent >>>>>>> instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive >>>>>>> invocation has been aborted the first one terminates normally misleading
    people into believing that the recursive chain terminates normally. >>>>>> How interesting. Might this be due to a global variable that basically >>>>>> toggles termination?

    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.

    Wrong. Termination analyzers deremine whether a program can run forever. >>>
    This would define simulating termination analyzers as impossible
    because every input that would otherwise run forever is aborted.

    It would be aborted by external causes but not by the program itself so
    we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/master/Halt7.c that statement is void: that HHH does abort is simulation of DD. If you mean any function HHH allowed by OP then that statement is false.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Sat Feb 22 11:01:51 2025
    Am Fri, 21 Feb 2025 21:55:32 -0600 schrieb olcott:
    On 2/20/2025 4:00 AM, joes wrote:
    Am Wed, 19 Feb 2025 22:08:05 -0600 schrieb olcott:
    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to >>>>>>>>>>>>>>>> that article before or when HHH
    That paper and its code are the only thing that I have >>>>>>>>>>>>>>> been talking about in this forum for several years. >>>>>>>>>>>>>> Doesn't matter when you don't say that you are talking >>>>>>>>>>>>>> about that paper.
    Anyway, that is irrelevant to the fact that the subject >>>>>>>>>>>>>> line contains a false claim.
    It is a truism and not one person on the face of the Earth >>>>>>>>>>>>> can possibly show otherwise.
    The fact that the claim on subject line is false is not a >>>>>>>>>>>> truism.
    In order to determine the claim is false one needs some >>>>>>>>>>>> knowledge that is not obvious.
    When you try to show the steps attempting to show that it is >>>>>>>>>>> false I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as
    subsequent instances of the exact same sequence of recursive
    invocations.
    It is the same with recursive simulations. When the second recursive >>>>> invocation has been aborted the first one terminates normally
    misleading people into believing that the recursive chain terminates >>>>> normally.
    How interesting. Might this be due to a global variable that
    basically toggles termination?
    Termination analyzers determine whether or not their input could
    possibly terminate normally. Nothing can toggle this.
    Not even the variable Root in line 502 of Halt7.c?
    https://github.com/plolcott/x86utm/blob/master/Halt7.c You are not even
    in the correct function.
    1059

    --
    Am Sat, 20 Jul 2024 12:35:31 +0000 schrieb WM in sci.math:
    It is not guaranteed that n+1 exists for every n.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Feb 22 07:15:18 2025
    On 2/21/25 10:55 PM, olcott wrote:
    On 2/20/2025 4:00 AM, joes wrote:
    Am Wed, 19 Feb 2025 22:08:05 -0600 schrieb olcott:
    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>>>> talking about in this forum for several years.
    Doesn't matter when you don't say that you are talking about >>>>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can >>>>>>>>>>>>> possibly show otherwise.
    The fact that the claim on subject line is false is not a >>>>>>>>>>>> truism.
    In order to determine the claim is false one needs some >>>>>>>>>>>> knowledge that is not obvious.
    When you try to show the steps attempting to show that it is >>>>>>>>>>> false I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent >>>>> instances of the exact same sequence of recursive invocations.
    It is the same with recursive simulations. When the second recursive >>>>> invocation has been aborted the first one terminates normally
    misleading people into believing that the recursive chain terminates >>>>> normally.
    How interesting. Might this be due to a global variable that basically >>>> toggles termination?
    Termination analyzers determine whether or not their input could
    possibly terminate normally. Nothing can toggle this.
    Not even the variable Root in line 502 of Halt7.c?


    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    You are not even in the correct function.


    So, HHH doesn't call that code (or an equivalent)?

    I guess you don't know what a computational function is.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Sat Feb 22 16:49:23 2025
    Am Sat, 22 Feb 2025 10:06:08 -0600 schrieb olcott:
    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:
    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:
    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:
    On 2/16/2025 6:55 AM, joes wrote:

    How interesting. Might this be due to a global variable that
    basically toggles termination?
    Termination analyzers determine whether or not their input could >>>>>>> possibly terminate normally. Nothing can toggle this.
    Wrong. Termination analyzers deremine whether a program can run
    forever.
    This would define simulating termination analyzers as impossible
    because every input that would otherwise run forever is aborted.
    It would be aborted by external causes but not by the program itself
    so we can say that the program could run forever.
    OK great we finally got mutual agreement on one point. Unless the C
    function HHH aborts its simulation of the C function DD this DD C
    function DOES NOT TERMINATE.
    If you mean the HHH on https://github.com/plolcott/x86utm/blob/master/
    Halt7.c that statement is void: that HHH does abort is simulation of
    DD. If you mean any function HHH allowed by OP then that statement is
    false.
    I am not talking about one statement.
    The statement "unless HHH aborts..." is void, because HH does abort.

    --
    Am Sat, 20 Jul 2024 12:35:31 +0000 schrieb WM in sci.math:
    It is not guaranteed that n+1 exists for every n.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Feb 22 19:02:34 2025
    On 2/22/25 11:06 AM, olcott wrote:
    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no reference >>>>>>>>>>>>>>>>>>>> to that
    article before or when HHH
    That paper and its code are the only thing that I >>>>>>>>>>>>>>>>>>> have been
    talking about in this forum for several years. >>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are talking >>>>>>>>>>>>>>>>>> about
    that paper.
    Anyway, that is irrelevant to the fact that the >>>>>>>>>>>>>>>>>> subject line
    contains a false claim.
    It is a truism and not one person on the face of the >>>>>>>>>>>>>>>>> Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false is not >>>>>>>>>>>>>>>> a truism.
    In order to determine the claim is false one needs some >>>>>>>>>>>>>>>> knowledge
    that is not obvious.
    When you try to show the steps attempting to show that it >>>>>>>>>>>>>>> is false
    I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as
    subsequent
    instances of the exact same sequence of recursive invocations. >>>>>>>>> It is the same with recursive simulations. When the second
    recursive
    invocation has been aborted the first one terminates normally >>>>>>>>> misleading
    people into believing that the recursive chain terminates
    normally.
    How interesting. Might this be due to a global variable that
    basically
    toggles termination?

    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.

    Wrong. Termination analyzers deremine whether a program can run
    forever.

    This would define simulating termination analyzers as impossible
    because every input that would otherwise run forever is aborted.

    It would be aborted by external causes but not by the program itself so >>>> we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/master/
    Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If
    you mean
    any function HHH allowed by OP then that statement is false.


    I am not talking about one statement. I am referring to
    all of the code and all of code this this code refers to
    in every other file.

    If you want to refer to one statement every software engineer
    knows this means FILENAME : LINE NUMBER.


    ANd thus HHH has fixed defined behavior, and talking about it behaving differently is just a LIE.

    You don't get to change your fixed parameters, and HHH can't be a
    variable and still have DD be a valid input, as the input string must be
    a constant.

    Your failure to understand this just shows your total ignorance of the
    topic, and your refusal to learn shows your stupidity.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Sun Feb 23 11:43:07 2025
    On 2025-02-22 16:06:08 +0000, olcott said:

    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said:
    On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no reference to that >>>>>>>>>>>>>>>>>>>> article before or when HHH
    That paper and its code are the only thing that I have been >>>>>>>>>>>>>>>>>>> talking about in this forum for several years. >>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are talking about >>>>>>>>>>>>>>>>>> that paper.
    Anyway, that is irrelevant to the fact that the subject line >>>>>>>>>>>>>>>>>> contains a false claim.
    It is a truism and not one person on the face of the Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false is not a truism.
    In order to determine the claim is false one needs some knowledge
    that is not obvious.
    When you try to show the steps attempting to show that it is false
    I will point out the error.
    We havm, but you are too stupid to understand it.
    Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent >>>>>>>>> instances of the exact same sequence of recursive invocations. >>>>>>>>> It is the same with recursive simulations. When the second recursive >>>>>>>>> invocation has been aborted the first one terminates normally misleading
    people into believing that the recursive chain terminates normally. >>>>>>>> How interesting. Might this be due to a global variable that basically >>>>>>>> toggles termination?

    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.

    Wrong. Termination analyzers deremine whether a program can run forever. >>>>>
    This would define simulating termination analyzers as impossible
    because every input that would otherwise run forever is aborted.

    It would be aborted by external causes but not by the program itself so >>>> we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If you mean >> any function HHH allowed by OP then that statement is false.


    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT TERMINATE."

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/master/Halt7.c that statement is void: that HHH does abort is simulation of DD. If you mean any function HHH allowed by OP then that statement is false.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Feb 23 19:12:21 2025
    On 2/23/25 12:34 PM, olcott wrote:
    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:

    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no reference >>>>>>>>>>>>>>>>>>>>>> to that
    article before or when HHH
    That paper and its code are the only thing that I >>>>>>>>>>>>>>>>>>>>> have been
    talking about in this forum for several years. >>>>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are >>>>>>>>>>>>>>>>>>>> talking about
    that paper.
    Anyway, that is irrelevant to the fact that the >>>>>>>>>>>>>>>>>>>> subject line
    contains a false claim.
    It is a truism and not one person on the face of the >>>>>>>>>>>>>>>>>>> Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false is >>>>>>>>>>>>>>>>>> not a truism.
    In order to determine the claim is false one needs >>>>>>>>>>>>>>>>>> some knowledge
    that is not obvious.
    When you try to show the steps attempting to show that >>>>>>>>>>>>>>>>> it is false
    I will point out the error.
    We havm, but you are too stupid to understand it. >>>>>>>>>>>>>>>> Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as >>>>>>>>>>> subsequent
    instances of the exact same sequence of recursive invocations. >>>>>>>>>>> It is the same with recursive simulations. When the second >>>>>>>>>>> recursive
    invocation has been aborted the first one terminates normally >>>>>>>>>>> misleading
    people into believing that the recursive chain terminates >>>>>>>>>>> normally.
    How interesting. Might this be due to a global variable that >>>>>>>>>> basically
    toggles termination?

    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.

    Wrong. Termination analyzers deremine whether a program can run >>>>>>>> forever.

    This would define simulating termination analyzers as impossible >>>>>>> because every input that would otherwise run forever is aborted.

    It would be aborted by external causes but not by the program
    itself so
    we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/
    master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If
    you mean
    any function HHH allowed by OP then that statement is false.


    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT TERMINATE."

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/master/
    Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If
    you mean
    any function HHH allowed by OP then that statement is false.


    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.



    But a "Hypothetical" possiblity, needs to be something that CAN happen.

    This HHH can't not abort its simulation, and if you think about a
    different HHH, then DD still must call THIS one, not the hypothetical
    one, as to get the hypothetical one, you need to change it, so it would
    change DD, which means you aren't looking at THIS DD.

    Sorry, all you are doing is proving your logic is based on LYING.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Mon Feb 24 10:32:56 2025
    On 2025-02-23 17:34:21 +0000, olcott said:

    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:

    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott:
    On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no reference to that
    article before or when HHH
    That paper and its code are the only thing that I have been
    talking about in this forum for several years. >>>>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are talking about
    that paper.
    Anyway, that is irrelevant to the fact that the subject line
    contains a false claim.
    It is a truism and not one person on the face of the Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false is not a truism.
    In order to determine the claim is false one needs some knowledge
    that is not obvious.
    When you try to show the steps attempting to show that it is false
    I will point out the error.
    We havm, but you are too stupid to understand it. >>>>>>>>>>>>>>>> Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH?
    The first instance of recursion is not exactly the same as subsequent
    instances of the exact same sequence of recursive invocations. >>>>>>>>>>> It is the same with recursive simulations. When the second recursive
    invocation has been aborted the first one terminates normally misleading
    people into believing that the recursive chain terminates normally. >>>>>>>>>> How interesting. Might this be due to a global variable that basically
    toggles termination?

    Termination analyzers determine whether or not their input
    could possibly terminate normally. Nothing can toggle this.

    Wrong. Termination analyzers deremine whether a program can run forever.

    This would define simulating termination analyzers as impossible >>>>>>> because every input that would otherwise run forever is aborted.

    It would be aborted by external causes but not by the program itself so >>>>>> we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/ master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If you mean
    any function HHH allowed by OP then that statement is false.


    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT TERMINATE."

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If you mean >> any function HHH allowed by OP then that statement is false.

    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.

    Yes, I understand that a simulator that both abort its simulation and
    does not abort is not a hypothetical possibility.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Feb 24 19:04:54 2025
    On 2/24/25 6:22 PM, olcott wrote:
    On 2/24/2025 2:32 AM, Mikko wrote:
    On 2025-02-23 17:34:21 +0000, olcott said:

    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:

    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no >>>>>>>>>>>>>>>>>>>>>>>> reference to that
    article before or when HHH
    That paper and its code are the only thing that I >>>>>>>>>>>>>>>>>>>>>>> have been
    talking about in this forum for several years. >>>>>>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are >>>>>>>>>>>>>>>>>>>>>> talking about
    that paper.
    Anyway, that is irrelevant to the fact that the >>>>>>>>>>>>>>>>>>>>>> subject line
    contains a false claim.
    It is a truism and not one person on the face of >>>>>>>>>>>>>>>>>>>>> the Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false is >>>>>>>>>>>>>>>>>>>> not a truism.
    In order to determine the claim is false one needs >>>>>>>>>>>>>>>>>>>> some knowledge
    that is not obvious.
    When you try to show the steps attempting to show >>>>>>>>>>>>>>>>>>> that it is false
    I will point out the error.
    We havm, but you are too stupid to understand it. >>>>>>>>>>>>>>>>>> Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH? >>>>>>>>>>>>> The first instance of recursion is not exactly the same as >>>>>>>>>>>>> subsequent
    instances of the exact same sequence of recursive invocations. >>>>>>>>>>>>> It is the same with recursive simulations. When the second >>>>>>>>>>>>> recursive
    invocation has been aborted the first one terminates >>>>>>>>>>>>> normally misleading
    people into believing that the recursive chain terminates >>>>>>>>>>>>> normally.
    How interesting. Might this be due to a global variable that >>>>>>>>>>>> basically
    toggles termination?

    Termination analyzers determine whether or not their input >>>>>>>>>>> could possibly terminate normally. Nothing can toggle this. >>>>>>>>>>
    Wrong. Termination analyzers deremine whether a program can >>>>>>>>>> run forever.

    This would define simulating termination analyzers as impossible >>>>>>>>> because every input that would otherwise run forever is aborted. >>>>>>>>
    It would be aborted by external causes but not by the program
    itself so
    we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/
    master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD.
    If you mean
    any function HHH allowed by OP then that statement is false.


    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT TERMINATE." >>>>
    If you mean the HHH on https://github.com/plolcott/x86utm/blob/
    master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If
    you mean
    any function HHH allowed by OP then that statement is false.

    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.

    Yes, I understand that a simulator that both abort its simulation and
    does not abort is not a hypothetical possibility.


    HHH aborts its emulation of DD.
    When we imagine the exact same HHH with the
    one single change that it never aborts its input
    then we can see that this HHH cannot possibly
    terminate normally.




    Which then isn't "the exact same HHH".

    ANd thus your logic is based on a LIE.

    Note, this new case fails because HHH never returns an answer.

    But, if we make a NEW copy of that slightly modified HHH, and give it
    the original input, that calls the original HHH, we see that this input
    (the input you actually had) will halt, and thus HHH is just wrong, and
    your logic proved to be unsound, and stupid.

    Your logic is based on the insanity that two different things can also
    be the same.

    BOOM goes your logic.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Tue Feb 25 08:09:52 2025
    Am Mon, 24 Feb 2025 17:22:23 -0600 schrieb olcott:
    On 2/24/2025 2:32 AM, Mikko wrote:
    On 2025-02-23 17:34:21 +0000, olcott said:
    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:
    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:
    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:
    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:
    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said:

    Termination analyzers determine whether or not their input >>>>>>>>>>> could possibly terminate normally. Nothing can toggle this. >>>>>>>>>>
    Wrong. Termination analyzers deremine whether a program can run >>>>>>>>>> forever.

    This would define simulating termination analyzers as impossible >>>>>>>>> because every input that would otherwise run forever is aborted. >>>>>>>>
    It would be aborted by external causes but not by the program
    itself so we can say that the program could run forever.

    OK great we finally got mutual agreement on one point. Unless the >>>>>>> C function HHH aborts its simulation of the C function DD this DD >>>>>>> C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/
    master/ Halt7.c that statement is void: that HHH does abort is
    simulation of DD. If you mean any function HHH allowed by OP then
    that statement is false.

    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT
    TERMINATE."

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/
    master/ Halt7.c that statement is void: that HHH does abort is
    simulation of DD. If you mean any function HHH allowed by OP then
    that statement is false.

    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.

    Yes, I understand that a simulator that both abort its simulation and
    does not abort is not a hypothetical possibility.

    HHH aborts its emulation of DD.
    When we imagine the exact same HHH with the one single change that it
    never aborts its input then we can see that this HHH cannot possibly terminate normally.
    LOLOLOL that is not "the exact same HHH"

    --
    Am Sat, 20 Jul 2024 12:35:31 +0000 schrieb WM in sci.math:
    It is not guaranteed that n+1 exists for every n.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Tue Feb 25 10:32:15 2025
    Op 25.feb.2025 om 00:22 schreef olcott:
    On 2/24/2025 2:32 AM, Mikko wrote:
    On 2025-02-23 17:34:21 +0000, olcott said:

    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:

    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no >>>>>>>>>>>>>>>>>>>>>>>> reference to that
    article before or when HHH
    That paper and its code are the only thing that I >>>>>>>>>>>>>>>>>>>>>>> have been
    talking about in this forum for several years. >>>>>>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are >>>>>>>>>>>>>>>>>>>>>> talking about
    that paper.
    Anyway, that is irrelevant to the fact that the >>>>>>>>>>>>>>>>>>>>>> subject line
    contains a false claim.
    It is a truism and not one person on the face of >>>>>>>>>>>>>>>>>>>>> the Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false is >>>>>>>>>>>>>>>>>>>> not a truism.
    In order to determine the claim is false one needs >>>>>>>>>>>>>>>>>>>> some knowledge
    that is not obvious.
    When you try to show the steps attempting to show >>>>>>>>>>>>>>>>>>> that it is false
    I will point out the error.
    We havm, but you are too stupid to understand it. >>>>>>>>>>>>>>>>>> Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH? >>>>>>>>>>>>> The first instance of recursion is not exactly the same as >>>>>>>>>>>>> subsequent
    instances of the exact same sequence of recursive invocations. >>>>>>>>>>>>> It is the same with recursive simulations. When the second >>>>>>>>>>>>> recursive
    invocation has been aborted the first one terminates >>>>>>>>>>>>> normally misleading
    people into believing that the recursive chain terminates >>>>>>>>>>>>> normally.
    How interesting. Might this be due to a global variable that >>>>>>>>>>>> basically
    toggles termination?

    Termination analyzers determine whether or not their input >>>>>>>>>>> could possibly terminate normally. Nothing can toggle this. >>>>>>>>>>
    Wrong. Termination analyzers deremine whether a program can >>>>>>>>>> run forever.

    This would define simulating termination analyzers as impossible >>>>>>>>> because every input that would otherwise run forever is aborted. >>>>>>>>
    It would be aborted by external causes but not by the program
    itself so
    we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/
    master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD.
    If you mean
    any function HHH allowed by OP then that statement is false.


    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT TERMINATE." >>>>
    If you mean the HHH on https://github.com/plolcott/x86utm/blob/
    master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If
    you mean
    any function HHH allowed by OP then that statement is false.

    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.

    Yes, I understand that a simulator that both abort its simulation and
    does not abort is not a hypothetical possibility.


    HHH aborts its emulation of DD.
    When we imagine the exact same HHH with the
    one single change that it never aborts its input
    then we can see that this HHH cannot possibly
    terminate normally.
    How many changes are allowed before HHH is no longer 'the exact same HHH'?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Tue Feb 25 16:35:06 2025
    On 2025-02-24 23:22:23 +0000, olcott said:

    On 2/24/2025 2:32 AM, Mikko wrote:
    On 2025-02-23 17:34:21 +0000, olcott said:

    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:

    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott:
    On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote:
    On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no reference to that
    article before or when HHH
    That paper and its code are the only thing that I have been
    talking about in this forum for several years. >>>>>>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are talking about
    that paper.
    Anyway, that is irrelevant to the fact that the subject line
    contains a false claim.
    It is a truism and not one person on the face of the Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false is not a truism.
    In order to determine the claim is false one needs some knowledge
    that is not obvious.
    When you try to show the steps attempting to show that it is false
    I will point out the error.
    We havm, but you are too stupid to understand it. >>>>>>>>>>>>>>>>>> Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH?
    I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH? >>>>>>>>>>>>> The first instance of recursion is not exactly the same as subsequent
    instances of the exact same sequence of recursive invocations. >>>>>>>>>>>>> It is the same with recursive simulations. When the second recursive
    invocation has been aborted the first one terminates normally misleading
    people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically
    toggles termination?

    Termination analyzers determine whether or not their input >>>>>>>>>>> could possibly terminate normally. Nothing can toggle this. >>>>>>>>>>
    Wrong. Termination analyzers deremine whether a program can run forever.

    This would define simulating termination analyzers as impossible >>>>>>>>> because every input that would otherwise run forever is aborted. >>>>>>>>
    It would be aborted by external causes but not by the program itself so
    we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/ master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If you mean
    any function HHH allowed by OP then that statement is false.


    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT TERMINATE." >>>>
    If you mean the HHH on https://github.com/plolcott/x86utm/blob/ master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If you mean
    any function HHH allowed by OP then that statement is false.

    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.

    Yes, I understand that a simulator that both abort its simulation and
    does not abort is not a hypothetical possibility.

    HHH aborts its emulation of DD.
    When we imagine the exact same HHH with the
    one single change that it never aborts its input
    then we can see that this HHH cannot possibly
    terminate normally.

    That's right. But OP did not specify which HHH is called by DD.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Tue Feb 25 18:13:11 2025
    Am Tue, 25 Feb 2025 11:51:42 -0600 schrieb olcott:
    On 2/25/2025 2:09 AM, joes wrote:
    Am Mon, 24 Feb 2025 17:22:23 -0600 schrieb olcott:
    On 2/24/2025 2:32 AM, Mikko wrote:
    On 2025-02-23 17:34:21 +0000, olcott said:
    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:
    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:
    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:
    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:
    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2025-02-11 14:41:38 +0000, olcott said:

    Termination analyzers determine whether or not their input >>>>>>>>>>>>> could possibly terminate normally. Nothing can toggle this. >>>>>>>>>>>>
    Wrong. Termination analyzers deremine whether a program can >>>>>>>>>>>> run forever.

    This would define simulating termination analyzers as
    impossible because every input that would otherwise run
    forever is aborted.

    It would be aborted by external causes but not by the program >>>>>>>>>> itself so we can say that the program could run forever.

    OK great we finally got mutual agreement on one point. Unless >>>>>>>>> the C function HHH aborts its simulation of the C function DD >>>>>>>>> this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/ >>>>>>>> master/ Halt7.c that statement is void: that HHH does abort is >>>>>>>> simulation of DD. If you mean any function HHH allowed by OP then >>>>>>>> that statement is false.

    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT
    TERMINATE."

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/
    master/ Halt7.c that statement is void: that HHH does abort is
    simulation of DD. If you mean any function HHH allowed by OP then
    that statement is false.

    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.

    Yes, I understand that a simulator that both abort its simulation and
    does not abort is not a hypothetical possibility.

    HHH aborts its emulation of DD.
    When we imagine the exact same HHH with the one single change that it
    never aborts its input then we can see that this HHH cannot possibly
    terminate normally.
    LOLOLOL that is not "the exact same HHH"
    DAMNED WEASEL WORDS
    X WITH X == X WITH Y
    A REBUTTAL OF THIS SAYING X WITH Y != X WITHOUT Y IS MERE DECEPTION.
    When we imagine the exact same peter with the one single change that he
    doesn't survive his therapy we can see that this peter cannot possibly
    die naturally.

    --
    Am Sat, 20 Jul 2024 12:35:31 +0000 schrieb WM in sci.math:
    It is not guaranteed that n+1 exists for every n.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Feb 25 18:41:07 2025
    On 2/25/25 4:16 PM, olcott wrote:
    On 2/25/2025 8:35 AM, Mikko wrote:
    On 2025-02-24 23:22:23 +0000, olcott said:

    On 2/24/2025 2:32 AM, Mikko wrote:
    On 2025-02-23 17:34:21 +0000, olcott said:

    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:

    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no >>>>>>>>>>>>>>>>>>>>>>>>>> reference to that
    article before or when HHH
    That paper and its code are the only thing that >>>>>>>>>>>>>>>>>>>>>>>>> I have been
    talking about in this forum for several years. >>>>>>>>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are >>>>>>>>>>>>>>>>>>>>>>>> talking about
    that paper.
    Anyway, that is irrelevant to the fact that the >>>>>>>>>>>>>>>>>>>>>>>> subject line
    contains a false claim.
    It is a truism and not one person on the face of >>>>>>>>>>>>>>>>>>>>>>> the Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false >>>>>>>>>>>>>>>>>>>>>> is not a truism.
    In order to determine the claim is false one needs >>>>>>>>>>>>>>>>>>>>>> some knowledge
    that is not obvious.
    When you try to show the steps attempting to show >>>>>>>>>>>>>>>>>>>>> that it is false
    I will point out the error.
    We havm, but you are too stupid to understand it. >>>>>>>>>>>>>>>>>>>> Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH? >>>>>>>>>>>>>>>>> I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH? >>>>>>>>>>>>>>> The first instance of recursion is not exactly the same >>>>>>>>>>>>>>> as subsequent
    instances of the exact same sequence of recursive >>>>>>>>>>>>>>> invocations.
    It is the same with recursive simulations. When the >>>>>>>>>>>>>>> second recursive
    invocation has been aborted the first one terminates >>>>>>>>>>>>>>> normally misleading
    people into believing that the recursive chain terminates >>>>>>>>>>>>>>> normally.
    How interesting. Might this be due to a global variable >>>>>>>>>>>>>> that basically
    toggles termination?

    Termination analyzers determine whether or not their input >>>>>>>>>>>>> could possibly terminate normally. Nothing can toggle this. >>>>>>>>>>>>
    Wrong. Termination analyzers deremine whether a program can >>>>>>>>>>>> run forever.

    This would define simulating termination analyzers as impossible >>>>>>>>>>> because every input that would otherwise run forever is aborted. >>>>>>>>>>
    It would be aborted by external causes but not by the program >>>>>>>>>> itself so
    we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/ >>>>>>>> master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. >>>>>>>> If you mean
    any function HHH allowed by OP then that statement is false.


    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT
    TERMINATE."

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/
    master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD.
    If you mean
    any function HHH allowed by OP then that statement is false.

    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.

    Yes, I understand that a simulator that both abort its simulation and
    does not abort is not a hypothetical possibility.

    HHH aborts its emulation of DD.
    When we imagine the exact same HHH with the
    one single change that it never aborts its input
    then we can see that this HHH cannot possibly
    terminate normally.

    That's right. But OP did not specify which HHH is called by DD.


    DD does not terminate normally either way so it
    is stupid to need to know which one.


    OF course DD terminates normally if HHH aborts its simulation.

    It is the partial (and thus incorrect) simuolation by HHH that doesn't.

    You are just so stupid you don;t understand the meaning of the words of
    the problem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Feb 25 23:21:32 2025
    On 2/25/25 8:50 PM, olcott wrote:
    On 2/25/2025 5:41 PM, Richard Damon wrote:
    On 2/25/25 4:16 PM, olcott wrote:
    On 2/25/2025 8:35 AM, Mikko wrote:
    On 2025-02-24 23:22:23 +0000, olcott said:

    On 2/24/2025 2:32 AM, Mikko wrote:
    On 2025-02-23 17:34:21 +0000, olcott said:

    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:

    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/13/25 7:07 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>> On 2/13/2025 3:20 AM, Mikko wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no >>>>>>>>>>>>>>>>>>>>>>>>>>>> reference to that
    article before or when HHH >>>>>>>>>>>>>>>>>>>>>>>>>>> That paper and its code are the only thing >>>>>>>>>>>>>>>>>>>>>>>>>>> that I have been
    talking about in this forum for several years. >>>>>>>>>>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are >>>>>>>>>>>>>>>>>>>>>>>>>> talking about
    that paper.
    Anyway, that is irrelevant to the fact that >>>>>>>>>>>>>>>>>>>>>>>>>> the subject line
    contains a false claim.
    It is a truism and not one person on the face >>>>>>>>>>>>>>>>>>>>>>>>> of the Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false >>>>>>>>>>>>>>>>>>>>>>>> is not a truism.
    In order to determine the claim is false one >>>>>>>>>>>>>>>>>>>>>>>> needs some knowledge
    that is not obvious.
    When you try to show the steps attempting to show >>>>>>>>>>>>>>>>>>>>>>> that it is false
    I will point out the error.
    We havm, but you are too stupid to understand it. >>>>>>>>>>>>>>>>>>>>>> Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH? >>>>>>>>>>>>>>>>>>> I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH? >>>>>>>>>>>>>>>>> The first instance of recursion is not exactly the same >>>>>>>>>>>>>>>>> as subsequent
    instances of the exact same sequence of recursive >>>>>>>>>>>>>>>>> invocations.
    It is the same with recursive simulations. When the >>>>>>>>>>>>>>>>> second recursive
    invocation has been aborted the first one terminates >>>>>>>>>>>>>>>>> normally misleading
    people into believing that the recursive chain >>>>>>>>>>>>>>>>> terminates normally.
    How interesting. Might this be due to a global variable >>>>>>>>>>>>>>>> that basically
    toggles termination?

    Termination analyzers determine whether or not their input >>>>>>>>>>>>>>> could possibly terminate normally. Nothing can toggle this. >>>>>>>>>>>>>>
    Wrong. Termination analyzers deremine whether a program >>>>>>>>>>>>>> can run forever.

    This would define simulating termination analyzers as >>>>>>>>>>>>> impossible
    because every input that would otherwise run forever is >>>>>>>>>>>>> aborted.

    It would be aborted by external causes but not by the
    program itself so
    we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C >>>>>>>>>>> function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/ >>>>>>>>>> blob/ master/ Halt7.c
    that statement is void: that HHH does abort is simulation of >>>>>>>>>> DD. If you mean
    any function HHH allowed by OP then that statement is false. >>>>>>>>>>

    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its >>>>>>>> simulation of the C function DD this DD C function DOES NOT
    TERMINATE."

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/ >>>>>>>> master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. >>>>>>>> If you mean
    any function HHH allowed by OP then that statement is false.

    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.

    Yes, I understand that a simulator that both abort its simulation and >>>>>> does not abort is not a hypothetical possibility.

    HHH aborts its emulation of DD.
    When we imagine the exact same HHH with the
    one single change that it never aborts its input
    then we can see that this HHH cannot possibly
    terminate normally.

    That's right. But OP did not specify which HHH is called by DD.


    DD does not terminate normally either way so it
    is stupid to need to know which one.


    OF course DD terminates normally if HHH aborts its simulation.


    Only if you are clueless about both c and x86, otherwise
    it is dead obvious that the entire recursive chain totally
    stops and zero elements of the recursive chain can possibly
    reach their "ret" or "return" instruction as soon as the
    outermost instance is aborted.

    No, it is dead obvious that since the HHH that DD DOES ABORT (and to say otherwise is just a DAMNED LIE) then the behavior of the executed DD is
    to return.

    IT seems it is YOU that is clueless as to the behavior of what you are
    talking about.

    THe code above is *NOT* a valid C program, as HHH is not defined, and
    thus you can't talk about it "behavior" per the C language, unless you
    include the code from your Halt7.c file, but then you have fully defined
    the behaivor of HHH, and can't talk about it doing something else.

    Also, it is clear you don't understand the behavior of the x86 as you
    think it is "correct" to presume that the execution of a program will
    just spontainously abort, since that is the behavior you are calling a
    correct simulation of that input.


    Since this is ordinary software engineering and requires zero
    knowledge of computer science that proves that anyone disagreeing
    is simply clueless.


    No, ait proves that you are just a clueless pathological liar.

    This is confirmed by the fact you have never shown any actual basis for
    any of your claims, the closest you have come is trying to quote some
    other people making the same mistakes.

    Sorry, but you are just proving that you are totally ignorant of what
    you say, and don't care about that, as you are just a pathological liar.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Wed Feb 26 10:39:43 2025
    On 2025-02-25 21:16:30 +0000, olcott said:

    On 2/25/2025 8:35 AM, Mikko wrote:
    On 2025-02-24 23:22:23 +0000, olcott said:

    On 2/24/2025 2:32 AM, Mikko wrote:
    On 2025-02-23 17:34:21 +0000, olcott said:

    On 2/23/2025 3:43 AM, Mikko wrote:
    On 2025-02-22 16:06:08 +0000, olcott said:

    On 2/22/2025 2:45 AM, Mikko wrote:
    On 2025-02-21 22:39:01 +0000, olcott said:

    On 2/21/2025 2:10 AM, Mikko wrote:
    On 2025-02-20 13:02:28 +0000, olcott said:

    On 2/20/2025 2:28 AM, Mikko wrote:
    On 2025-02-20 04:08:05 +0000, olcott said:

    On 2/16/2025 6:55 AM, joes wrote:
    Am Sat, 15 Feb 2025 21:25:12 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/15/2025 4:03 AM, joes wrote:
    Am Fri, 14 Feb 2025 17:29:45 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/14/2025 6:54 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:21:59 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/13/2025 9:15 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/13/25 7:07 PM, olcott wrote:
    On 2/13/2025 3:20 AM, Mikko wrote:
    On 2025-02-13 04:21:34 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>> On 2/12/2025 4:04 AM, Mikko wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2025-02-11 14:41:38 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>>>
    Of course not. However, the fact that no reference to that
    article before or when HHH
    That paper and its code are the only thing that I have been
    talking about in this forum for several years. >>>>>>>>>>>>>>>>>>>>>>>> Doesn't matter when you don't say that you are talking about
    that paper.
    Anyway, that is irrelevant to the fact that the subject line
    contains a false claim.
    It is a truism and not one person on the face of the Earth can
    possibly show otherwise.
    The fact that the claim on subject line is false is not a truism.
    In order to determine the claim is false one needs some knowledge
    that is not obvious.
    When you try to show the steps attempting to show that it is false
    I will point out the error.
    We havm, but you are too stupid to understand it. >>>>>>>>>>>>>>>>>>>> Since when DD run, it halts,
    THAT IS A DIFFERENT INSTANCE
    Why are you passing the wrong input to HHH? >>>>>>>>>>>>>>>>> I will begin ignoring insincere replies.
    Yes, please shut up.
    But why are you not passing the same instance to HHH? >>>>>>>>>>>>>>> The first instance of recursion is not exactly the same as subsequent
    instances of the exact same sequence of recursive invocations. >>>>>>>>>>>>>>> It is the same with recursive simulations. When the second recursive
    invocation has been aborted the first one terminates normally misleading
    people into believing that the recursive chain terminates normally.
    How interesting. Might this be due to a global variable that basically
    toggles termination?

    Termination analyzers determine whether or not their input >>>>>>>>>>>>> could possibly terminate normally. Nothing can toggle this. >>>>>>>>>>>>
    Wrong. Termination analyzers deremine whether a program can run forever.

    This would define simulating termination analyzers as impossible >>>>>>>>>>> because every input that would otherwise run forever is aborted. >>>>>>>>>>
    It would be aborted by external causes but not by the program itself so
    we can say that the program could run forever.


    OK great we finally got mutual agreement on one point.
    Unless the C function HHH aborts its simulation of the C
    function DD this DD C function DOES NOT TERMINATE.

    If you mean the HHH on https://github.com/plolcott/x86utm/blob/ master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If you mean
    any function HHH allowed by OP then that statement is false.


    I am not talking about one statement.

    I am, about one you made: "Unless the C function HHH aborts its
    simulation of the C function DD this DD C function DOES NOT TERMINATE." >>>>>>
    If you mean the HHH on https://github.com/plolcott/x86utm/blob/ master/ Halt7.c
    that statement is void: that HHH does abort is simulation of DD. If you mean
    any function HHH allowed by OP then that statement is false.

    Do you understand the notion of hypothetical possibilities?
    It really seems that you do not.

    Yes, I understand that a simulator that both abort its simulation and
    does not abort is not a hypothetical possibility.

    HHH aborts its emulation of DD.
    When we imagine the exact same HHH with the
    one single change that it never aborts its input
    then we can see that this HHH cannot possibly
    terminate normally.

    That's right. But OP did not specify which HHH is called by DD.


    DD does not terminate normally either way so it
    is stupid to need to know which one.

    OP did not exlude a HHH that aborts its simulation and returns 0. In
    that case DD terminates, so DD does not specify non-terminating
    behaviour.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)