• Re: Sufficient knowledge of C proves that DD specifies non-terminating

    From Richard Damon@21:1/5 to olcott on Fri Feb 7 20:27:06 2025
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:
    This treatment does not typically last very long and >>>>>>>>>>>>> will be immediately followed by a riskier fourth line >>>>>>>>>>>>> of treatment that has an initial success rate much higher >>>>>>>>>>>>> than its non progression mortality rate.


    Halting problem solved !


    The halting problem proof input does specify non-halting >>>>>>>>>>> behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language
    sufficiently well (thus not confused by the unreachable
    "if" statement) correctly understands that DD simulated
    by HHH cannot possibly reach its own return instruction.


    And anyone that understand the halting problem knows that isn't >>>>>>>> the question being asked. The quesiton you NEED to ask is will >>>>>>>> the program described by the input halt when run?

    Since you start off with the wrong question, you logic is just >>>>>>>> faulty.


    Everyone that thinks my question is incorrect is wrong.
    It has always been a mathematical mapping from finite
    strings to behaviors. That people do not comprehend this
    shows the shallowness of the depth of the learned-by-rote
    (lack of) understanding.


    No, you are just incorreect as you don't know what you are talking >>>>>> about.

    Yes, it is a mapping of the string to the behavior, and that
    mapping is DEFINED to be the halting behavior of the program the
    string describes.


    No this is incorrect. The input finite string specifies
    (not merely describes) non halting behavior to its decider.


    No, since the definition of "Halting Behavior" is the behavior of
    the progran being run.


    It may seem that way to people that have learned-by-rote
    as their only basis. It is actually nothing like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings
    specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior of running
    the program. WHich means the finite string has to fully define a program.

    THose are DEFINITIONS.

    You ignorance by never learning is just proving your stupidity.

    Sorry, but everything you do just shows that you are nothing but a
    pathological liar that doesn't care about what is actually true, but
    what you want to be true, and are too stupid to understand the problem
    with that.

    Your inability to understand that there ARE definitions are rules just
    futhers that observation.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sat Feb 8 10:57:12 2025
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:
    This treatment does not typically last very long and >>>>>>>>>>>>>>> will be immediately followed by a riskier fourth line >>>>>>>>>>>>>>> of treatment that has an initial success rate much higher >>>>>>>>>>>>>>> than its non progression mortality rate.


    Halting problem solved !


    The halting problem proof input does specify non-halting >>>>>>>>>>>>> behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language
    sufficiently well (thus not confused by the unreachable
    "if" statement) correctly understands that DD simulated
    by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>

    And anyone that understand the halting problem knows that
    isn't the question being asked. The quesiton you NEED to ask >>>>>>>>>> is will the program described by the input halt when run?

    Since you start off with the wrong question, you logic is just >>>>>>>>>> faulty.


    Everyone that thinks my question is incorrect is wrong.
    It has always been a mathematical mapping from finite
    strings to behaviors. That people do not comprehend this
    shows the shallowness of the depth of the learned-by-rote
    (lack of) understanding.


    No, you are just incorreect as you don't know what you are
    talking about.

    Yes, it is a mapping of the string to the behavior, and that
    mapping is DEFINED to be the halting behavior of the program the >>>>>>>> string describes.


    No this is incorrect. The input finite string specifies
    (not merely describes) non halting behavior to its decider.


    No, since the definition of "Halting Behavior" is the behavior of
    the progran being run.


    It may seem that way to people that have learned-by-rote
    as their only basis. It is actually nothing like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings
    specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior of
    running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The simulation
    aborts too soon on unsound grounds, one cycle before the normal
    termination of the program.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Feb 8 06:50:14 2025
    On 2/8/25 12:53 AM, olcott wrote:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:
    This treatment does not typically last very long and >>>>>>>>>>>>>>> will be immediately followed by a riskier fourth line >>>>>>>>>>>>>>> of treatment that has an initial success rate much higher >>>>>>>>>>>>>>> than its non progression mortality rate.


    Halting problem solved !


    The halting problem proof input does specify non-halting >>>>>>>>>>>>> behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language
    sufficiently well (thus not confused by the unreachable
    "if" statement) correctly understands that DD simulated
    by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>

    And anyone that understand the halting problem knows that
    isn't the question being asked. The quesiton you NEED to ask >>>>>>>>>> is will the program described by the input halt when run?

    Since you start off with the wrong question, you logic is just >>>>>>>>>> faulty.


    Everyone that thinks my question is incorrect is wrong.
    It has always been a mathematical mapping from finite
    strings to behaviors. That people do not comprehend this
    shows the shallowness of the depth of the learned-by-rote
    (lack of) understanding.


    No, you are just incorreect as you don't know what you are
    talking about.

    Yes, it is a mapping of the string to the behavior, and that
    mapping is DEFINED to be the halting behavior of the program the >>>>>>>> string describes.


    No this is incorrect. The input finite string specifies
    (not merely describes) non halting behavior to its decider.


    No, since the definition of "Halting Behavior" is the behavior of
    the progran being run.


    It may seem that way to people that have learned-by-rote
    as their only basis. It is actually nothing like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings
    specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior of
    running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    And where is the difference?

    What instruction, correctly simulated, behaved differently?

    Your arguement has always been based on instuctions NOT correctly
    simulated (like the call instruction) and thus has always been based on
    a lie.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Feb 8 06:48:45 2025
    On 2/8/25 12:53 AM, olcott wrote:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:
    This treatment does not typically last very long and >>>>>>>>>>>>>>> will be immediately followed by a riskier fourth line >>>>>>>>>>>>>>> of treatment that has an initial success rate much higher >>>>>>>>>>>>>>> than its non progression mortality rate.


    Halting problem solved !


    The halting problem proof input does specify non-halting >>>>>>>>>>>>> behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language
    sufficiently well (thus not confused by the unreachable
    "if" statement) correctly understands that DD simulated
    by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>

    And anyone that understand the halting problem knows that
    isn't the question being asked. The quesiton you NEED to ask >>>>>>>>>> is will the program described by the input halt when run?

    Since you start off with the wrong question, you logic is just >>>>>>>>>> faulty.


    Everyone that thinks my question is incorrect is wrong.
    It has always been a mathematical mapping from finite
    strings to behaviors. That people do not comprehend this
    shows the shallowness of the depth of the learned-by-rote
    (lack of) understanding.


    No, you are just incorreect as you don't know what you are
    talking about.

    Yes, it is a mapping of the string to the behavior, and that
    mapping is DEFINED to be the halting behavior of the program the >>>>>>>> string describes.


    No this is incorrect. The input finite string specifies
    (not merely describes) non halting behavior to its decider.


    No, since the definition of "Halting Behavior" is the behavior of
    the progran being run.


    It may seem that way to people that have learned-by-rote
    as their only basis. It is actually nothing like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings
    specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior of
    running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    WHere do you get your definition.


    Your problem is you lie to even yourself about the meaning of the words.

    It seems, you don't even know what a program is, because you are so
    utterly stupid.

    And it appears that you understand this enough to know you need to avoid looking at it, showing you are just a pathological liar.

    "HHH", to be an actual program, once defined, will have a specific
    behavior to any given actual input.

    Halting is defined as the behavior of actually running the program the
    input specifies, which will always be the same for a given program/input
    pair.

    For HHH to be "correct", it must answer, and thus the DD that it was
    given must be calling that HHH that returns an answer.

    This shows by simple inspection, that DD must halt, as verified by
    running it.

    That you try changing HHH to something other than what it is, just prove
    that you think that LYING is valid logic, and thus you are nothing but a pathological liar.

    Sorry you don't like it, but it has been your choice all the time.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan Mackenzie@21:1/5 to Fred. Zwarts on Sat Feb 8 12:53:53 2025
    Fred. Zwarts <F.Zwarts@hetnet.nl> wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:

    [ .... ]

    If so, then it proves the failure of the simulation. The simulation
    aborts too soon on unsound grounds, one cycle before the normal
    termination of the program.

    Hello, Fred.

    Welcome back!

    --
    Alan Mackenzie (Nuremberg, Germany).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Sat Feb 8 18:11:14 2025
    Am Sat, 08 Feb 2025 08:59:11 -0600 schrieb olcott:
    On 2/8/2025 5:48 AM, Richard Damon wrote:
    On 2/8/25 12:53 AM, olcott wrote:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:

    The source-code of DD and HHH specifies that DD calls HHH in recursive simulation making it impossible for DD to terminate normally. https://github.com/plolcott/x86utm/blob/master/Halt7.c Disagreeing with source-code is not a smart thing to do.
    Ever heard of bugs?

    --
    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 Sat Feb 8 22:54:43 2025
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:
    This treatment does not typically last very long and >>>>>>>>>>>>>>>>> will be immediately followed by a riskier fourth line >>>>>>>>>>>>>>>>> of treatment that has an initial success rate much higher >>>>>>>>>>>>>>>>> than its non progression mortality rate.


    Halting problem solved !


    The halting problem proof input does specify non-halting >>>>>>>>>>>>>>> behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language
    sufficiently well (thus not confused by the unreachable >>>>>>>>>>>>> "if" statement) correctly understands that DD simulated >>>>>>>>>>>>> by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>>>

    And anyone that understand the halting problem knows that >>>>>>>>>>>> isn't the question being asked. The quesiton you NEED to ask >>>>>>>>>>>> is will the program described by the input halt when run? >>>>>>>>>>>>
    Since you start off with the wrong question, you logic is >>>>>>>>>>>> just faulty.


    Everyone that thinks my question is incorrect is wrong.
    It has always been a mathematical mapping from finite
    strings to behaviors. That people do not comprehend this >>>>>>>>>>> shows the shallowness of the depth of the learned-by-rote >>>>>>>>>>> (lack of) understanding.


    No, you are just incorreect as you don't know what you are >>>>>>>>>> talking about.

    Yes, it is a mapping of the string to the behavior, and that >>>>>>>>>> mapping is DEFINED to be the halting behavior of the program >>>>>>>>>> the string describes.


    No this is incorrect. The input finite string specifies
    (not merely describes) non halting behavior to its decider.


    No, since the definition of "Halting Behavior" is the behavior >>>>>>>> of the progran being run.


    It may seem that way to people that have learned-by-rote
    as their only basis. It is actually nothing like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings
    specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior of
    running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The simulation
    aborts too soon on unsound grounds, one cycle before the normal
    termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally
    is a verified fact.


    Which proves that HHH fails to make a correct decision about DD's
    halting behaviour. All other methods (direct execution, simulation by a
    world class simulator, etc.) show that DD halts. But HHH fails to see
    it. Everyone with sufficient understanding of programming sees that HHH
    is not correctly programmed when it aborts one cycle before the
    simulation would end normally.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Feb 8 17:28:51 2025
    On 2/8/25 9:59 AM, olcott wrote:
    On 2/8/2025 5:48 AM, Richard Damon wrote:
    On 2/8/25 12:53 AM, olcott wrote:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:
    This treatment does not typically last very long and >>>>>>>>>>>>>>>>> will be immediately followed by a riskier fourth line >>>>>>>>>>>>>>>>> of treatment that has an initial success rate much higher >>>>>>>>>>>>>>>>> than its non progression mortality rate.


    Halting problem solved !


    The halting problem proof input does specify non-halting >>>>>>>>>>>>>>> behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language
    sufficiently well (thus not confused by the unreachable >>>>>>>>>>>>> "if" statement) correctly understands that DD simulated >>>>>>>>>>>>> by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>>>

    And anyone that understand the halting problem knows that >>>>>>>>>>>> isn't the question being asked. The quesiton you NEED to ask >>>>>>>>>>>> is will the program described by the input halt when run? >>>>>>>>>>>>
    Since you start off with the wrong question, you logic is >>>>>>>>>>>> just faulty.


    Everyone that thinks my question is incorrect is wrong.
    It has always been a mathematical mapping from finite
    strings to behaviors. That people do not comprehend this >>>>>>>>>>> shows the shallowness of the depth of the learned-by-rote >>>>>>>>>>> (lack of) understanding.


    No, you are just incorreect as you don't know what you are >>>>>>>>>> talking about.

    Yes, it is a mapping of the string to the behavior, and that >>>>>>>>>> mapping is DEFINED to be the halting behavior of the program >>>>>>>>>> the string describes.


    No this is incorrect. The input finite string specifies
    (not merely describes) non halting behavior to its decider.


    No, since the definition of "Halting Behavior" is the behavior >>>>>>>> of the progran being run.


    It may seem that way to people that have learned-by-rote
    as their only basis. It is actually nothing like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings
    specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior of
    running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    WHere do you get your definition.



    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
      int Halt_Status = HHH(DD);
      if (Halt_Status)
        HERE: goto HERE;
      return Halt_Status;
    }

    int main()
    {
      HHH(DD);
    }

    The source-code of DD and HHH specifies that DD calls
    HHH in recursive simulation making it impossible for DD
    to terminate normally.

    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    Disagreeing with source-code is not a smart thing to do.



    Try to compile that "program" and you will get a link error, and thus it
    isn't actually a program.

    All you are doing is proving your whole arguement is based on a lie, and
    that you knpw that but don't care.

    Note, if we include ALL of Halt7.c in the program, then we can show that
    DD() is a halting program and HHH is just an incorrect simulator and
    halting decider.

    Sorry, you are just proving that you are too stupid to understand your stupidity because you have destroyed your intelegence by gaslighting
    yourself with your lies turning you into an ignorant pathological lying
    idiot.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sun Feb 9 09:13:35 2025
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:
    This treatment does not typically last very long and >>>>>>>>>>>>>>>>>>> will be immediately followed by a riskier fourth line >>>>>>>>>>>>>>>>>>> of treatment that has an initial success rate much >>>>>>>>>>>>>>>>>>> higher
    than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>

    Halting problem solved !


    The halting problem proof input does specify non-halting >>>>>>>>>>>>>>>>> behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language >>>>>>>>>>>>>>> sufficiently well (thus not confused by the unreachable >>>>>>>>>>>>>>> "if" statement) correctly understands that DD simulated >>>>>>>>>>>>>>> by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>>>>>

    And anyone that understand the halting problem knows that >>>>>>>>>>>>>> isn't the question being asked. The quesiton you NEED to >>>>>>>>>>>>>> ask is will the program described by the input halt when run? >>>>>>>>>>>>>>
    Since you start off with the wrong question, you logic is >>>>>>>>>>>>>> just faulty.


    Everyone that thinks my question is incorrect is wrong. >>>>>>>>>>>>> It has always been a mathematical mapping from finite >>>>>>>>>>>>> strings to behaviors. That people do not comprehend this >>>>>>>>>>>>> shows the shallowness of the depth of the learned-by-rote >>>>>>>>>>>>> (lack of) understanding.


    No, you are just incorreect as you don't know what you are >>>>>>>>>>>> talking about.

    Yes, it is a mapping of the string to the behavior, and that >>>>>>>>>>>> mapping is DEFINED to be the halting behavior of the program >>>>>>>>>>>> the string describes.


    No this is incorrect. The input finite string specifies
    (not merely describes) non halting behavior to its decider. >>>>>>>>>>>

    No, since the definition of "Halting Behavior" is the behavior >>>>>>>>>> of the progran being run.


    It may seem that way to people that have learned-by-rote
    as their only basis. It is actually nothing like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings
    specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior of
    running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The simulation
    aborts too soon on unsound grounds, one cycle before the normal
    termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally
    is a verified fact.


    Which proves that HHH fails to make a correct decision about DD's
    halting behaviour. All other methods (direct execution, simulation by
    a world class simulator, etc.) show that DD halts. But HHH fails to
    see it. Everyone with sufficient understanding of programming sees
    that HHH is not correctly programmed when it aborts one cycle before
    the simulation would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
      int Halt_Status = HHH(DD);
      if (Halt_Status)
        HERE: goto HERE;
      return Halt_Status;
    }

    int main()
    {
      HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD...

    The execution trace only shows that HHH is unable to complete its
    simulation, because HHH is unable to simulate itself.

    Remember that HHH reports false negatives?

    int main() {
    return HHH(main);
    }

    Here HHH halts, but reports that it does not halt.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Feb 9 08:08:41 2025
    On 2/9/25 1:10 AM, olcott wrote:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:
    This treatment does not typically last very long and >>>>>>>>>>>>>>>>>>> will be immediately followed by a riskier fourth line >>>>>>>>>>>>>>>>>>> of treatment that has an initial success rate much >>>>>>>>>>>>>>>>>>> higher
    than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>

    Halting problem solved !


    The halting problem proof input does specify non-halting >>>>>>>>>>>>>>>>> behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language >>>>>>>>>>>>>>> sufficiently well (thus not confused by the unreachable >>>>>>>>>>>>>>> "if" statement) correctly understands that DD simulated >>>>>>>>>>>>>>> by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>>>>>

    And anyone that understand the halting problem knows that >>>>>>>>>>>>>> isn't the question being asked. The quesiton you NEED to >>>>>>>>>>>>>> ask is will the program described by the input halt when run? >>>>>>>>>>>>>>
    Since you start off with the wrong question, you logic is >>>>>>>>>>>>>> just faulty.


    Everyone that thinks my question is incorrect is wrong. >>>>>>>>>>>>> It has always been a mathematical mapping from finite >>>>>>>>>>>>> strings to behaviors. That people do not comprehend this >>>>>>>>>>>>> shows the shallowness of the depth of the learned-by-rote >>>>>>>>>>>>> (lack of) understanding.


    No, you are just incorreect as you don't know what you are >>>>>>>>>>>> talking about.

    Yes, it is a mapping of the string to the behavior, and that >>>>>>>>>>>> mapping is DEFINED to be the halting behavior of the program >>>>>>>>>>>> the string describes.


    No this is incorrect. The input finite string specifies
    (not merely describes) non halting behavior to its decider. >>>>>>>>>>>

    No, since the definition of "Halting Behavior" is the behavior >>>>>>>>>> of the progran being run.


    It may seem that way to people that have learned-by-rote
    as their only basis. It is actually nothing like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings
    specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior of
    running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The simulation
    aborts too soon on unsound grounds, one cycle before the normal
    termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally
    is a verified fact.


    Which proves that HHH fails to make a correct decision about DD's
    halting behaviour. All other methods (direct execution, simulation by
    a world class simulator, etc.) show that DD halts. But HHH fails to
    see it. Everyone with sufficient understanding of programming sees
    that HHH is not correctly programmed when it aborts one cycle before
    the simulation would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
      int Halt_Status = HHH(DD);
      if (Halt_Status)
        HERE: goto HERE;
      return Halt_Status;
    }

    int main()
    {
      HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD...

    If you have no idea what recursion is you will not be
    able to understand what I am saying.


    No, YOU lack the understanding of what a program is.

    Your first problem is that function "DD" isn't a "program" by itself,
    but only becomes one when you include as part of it the code for HHH.
    And thus, the specific HHH that exists at this exact point IS HHH, and
    it can not be changed.

    HHH simulates to a point and then aborts for what you think are valid
    reason, but which have been shown to you to be incorrect.

    HHH1 simulates that exact same input, which calls the exact same HHH,
    and shows that HHH was wrong to say it doesn't halt. Your claim that DD
    needs to call HHH1 in that case is just a FRAUD, as DD was defined to
    call a particular HHH, and NOT "who ever is deciding me" as that isn't a
    valid program.

    The fact that you try to base your arguement on your FRAUDS just shows
    that you are nothing but a FRAUD yourself, and are totally ignorant of
    what you are talking about.

    Sorry, but those are the FACTS, which you can not argue, because they
    are based on core definitions of the field you claim to be talking
    about, and attempts to redefine them just prove the FRAUD.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sun Feb 9 17:50:03 2025
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> This treatment does not typically last very long and >>>>>>>>>>>>>>>>>>>>> will be immediately followed by a riskier fourth line >>>>>>>>>>>>>>>>>>>>> of treatment that has an initial success rate much >>>>>>>>>>>>>>>>>>>>> higher
    than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>

    Halting problem solved !


    The halting problem proof input does specify non-halting >>>>>>>>>>>>>>>>>>> behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language >>>>>>>>>>>>>>>>> sufficiently well (thus not confused by the unreachable >>>>>>>>>>>>>>>>> "if" statement) correctly understands that DD simulated >>>>>>>>>>>>>>>>> by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>>>>>>>

    And anyone that understand the halting problem knows >>>>>>>>>>>>>>>> that isn't the question being asked. The quesiton you >>>>>>>>>>>>>>>> NEED to ask is will the program described by the input >>>>>>>>>>>>>>>> halt when run?

    Since you start off with the wrong question, you logic >>>>>>>>>>>>>>>> is just faulty.


    Everyone that thinks my question is incorrect is wrong. >>>>>>>>>>>>>>> It has always been a mathematical mapping from finite >>>>>>>>>>>>>>> strings to behaviors. That people do not comprehend this >>>>>>>>>>>>>>> shows the shallowness of the depth of the learned-by-rote >>>>>>>>>>>>>>> (lack of) understanding.


    No, you are just incorreect as you don't know what you are >>>>>>>>>>>>>> talking about.

    Yes, it is a mapping of the string to the behavior, and >>>>>>>>>>>>>> that mapping is DEFINED to be the halting behavior of the >>>>>>>>>>>>>> program the string describes.


    No this is incorrect. The input finite string specifies >>>>>>>>>>>>> (not merely describes) non halting behavior to its decider. >>>>>>>>>>>>>

    No, since the definition of "Halting Behavior" is the
    behavior of the progran being run.


    It may seem that way to people that have learned-by-rote >>>>>>>>>>> as their only basis. It is actually nothing like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings
    specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior of >>>>>>>> running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The
    simulation aborts too soon on unsound grounds, one cycle before
    the normal termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally
    is a verified fact.


    Which proves that HHH fails to make a correct decision about DD's
    halting behaviour. All other methods (direct execution, simulation
    by a world class simulator, etc.) show that DD halts. But HHH fails
    to see it. Everyone with sufficient understanding of programming
    sees that HHH is not correctly programmed when it aborts one cycle
    before the simulation would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD...

    The execution trace only shows that HHH is unable to complete its
    simulation, because HHH is unable to simulate itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    The above code proves that HHH does simulate itself simulating DD.

    That you can't understand this code proves that you lack the
    technical basis to review my work.


    It turns out that Olcott does not even understand this simple proof that
    HHH produces false negatives. HHH is unable to simulate itself up to the
    normal termination.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Feb 9 12:04:29 2025
    On 2/9/25 10:08 AM, olcott wrote:
    On 2/8/2025 12:11 PM, joes wrote:
    Am Sat, 08 Feb 2025 08:59:11 -0600 schrieb olcott:
    On 2/8/2025 5:48 AM, Richard Damon wrote:
    On 2/8/25 12:53 AM, olcott wrote:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote:
    Am 05.02.2025 um 16:11 schrieb olcott:
    On 2/5/2025 1:44 AM, Bonita Montero wrote:
    Am 05.02.2025 um 04:38 schrieb olcott:

    The source-code of DD and HHH specifies that DD calls HHH in recursive
    simulation making it impossible for DD to terminate normally.
    https://github.com/plolcott/x86utm/blob/master/Halt7.c Disagreeing with
    source-code is not a smart thing to do.
    Ever heard of bugs?


    No one has ever pointed out any actual bug in
    my code in all of the years that it has been presented.


    Sure we have, and you ignored them.

    MORE LIES from the mouth of Peter Olcott.


    Your code doesn't even meet your own accepted requirement that the
    decider be a "pure function", so you start admitting you are just a
    blatant liar.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Feb 9 12:07:43 2025
    On 2/9/25 12:00 PM, olcott wrote:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically last very long and >>>>>>>>>>>>>>>>>>>>>>> will be immediately followed by a riskier fourth >>>>>>>>>>>>>>>>>>>>>>> line
    of treatment that has an initial success rate >>>>>>>>>>>>>>>>>>>>>>> much higher
    than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved !


    The halting problem proof input does specify non- >>>>>>>>>>>>>>>>>>>>> halting
    behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language >>>>>>>>>>>>>>>>>>> sufficiently well (thus not confused by the unreachable >>>>>>>>>>>>>>>>>>> "if" statement) correctly understands that DD simulated >>>>>>>>>>>>>>>>>>> by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>>>>>>>>>

    And anyone that understand the halting problem knows >>>>>>>>>>>>>>>>>> that isn't the question being asked. The quesiton you >>>>>>>>>>>>>>>>>> NEED to ask is will the program described by the input >>>>>>>>>>>>>>>>>> halt when run?

    Since you start off with the wrong question, you logic >>>>>>>>>>>>>>>>>> is just faulty.


    Everyone that thinks my question is incorrect is wrong. >>>>>>>>>>>>>>>>> It has always been a mathematical mapping from finite >>>>>>>>>>>>>>>>> strings to behaviors. That people do not comprehend this >>>>>>>>>>>>>>>>> shows the shallowness of the depth of the learned-by-rote >>>>>>>>>>>>>>>>> (lack of) understanding.


    No, you are just incorreect as you don't know what you >>>>>>>>>>>>>>>> are talking about.

    Yes, it is a mapping of the string to the behavior, and >>>>>>>>>>>>>>>> that mapping is DEFINED to be the halting behavior of >>>>>>>>>>>>>>>> the program the string describes.


    No this is incorrect. The input finite string specifies >>>>>>>>>>>>>>> (not merely describes) non halting behavior to its decider. >>>>>>>>>>>>>>>

    No, since the definition of "Halting Behavior" is the >>>>>>>>>>>>>> behavior of the progran being run.


    It may seem that way to people that have learned-by-rote >>>>>>>>>>>>> as their only basis. It is actually nothing like that. >>>>>>>>>>>>
    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings >>>>>>>>>>> specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior >>>>>>>>>> of running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The
    simulation aborts too soon on unsound grounds, one cycle before >>>>>>>> the normal termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally
    is a verified fact.


    Which proves that HHH fails to make a correct decision about DD's
    halting behaviour. All other methods (direct execution, simulation >>>>>> by a world class simulator, etc.) show that DD halts. But HHH
    fails to see it. Everyone with sufficient understanding of
    programming sees that HHH is not correctly programmed when it
    aborts one cycle before the simulation would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD...

    The execution trace only shows that HHH is unable to complete its
    simulation, because HHH is unable to simulate itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    The above code proves that HHH does simulate itself simulating DD.

    That you can't understand this code proves that you lack the
    technical basis to review my work.


    It turns out that Olcott does not even understand this simple proof
    that HHH produces false negatives. HHH is unable to simulate itself up
    to the normal termination.

    If you try to explain your view in terms of a line-by-line
    execution trace of DD simulated by HHH everyone will see that
    your claim has no actual basis what-so-ever and is merely
    utterly baseless rhetoric totally bereft of any supporting
    reasoning.


    You mean like the fact that when HHH simulates the Call HHH instuction,
    the normal trace you present doesn't show the instructions in HHH.

    And when you do, it shows that there all the conditional instructions
    within HHH that HHH ignores, so its logic is invalid.

    Sorry, you are just proved to be a liar.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sun Feb 9 19:54:07 2025
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote:
    On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically last very long and >>>>>>>>>>>>>>>>>>>>>>> will be immediately followed by a riskier fourth >>>>>>>>>>>>>>>>>>>>>>> line
    of treatment that has an initial success rate >>>>>>>>>>>>>>>>>>>>>>> much higher
    than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved !


    The halting problem proof input does specify non- >>>>>>>>>>>>>>>>>>>>> halting
    behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language >>>>>>>>>>>>>>>>>>> sufficiently well (thus not confused by the unreachable >>>>>>>>>>>>>>>>>>> "if" statement) correctly understands that DD simulated >>>>>>>>>>>>>>>>>>> by HHH cannot possibly reach its own return instruction. >>>>>>>>>>>>>>>>>>>

    And anyone that understand the halting problem knows >>>>>>>>>>>>>>>>>> that isn't the question being asked. The quesiton you >>>>>>>>>>>>>>>>>> NEED to ask is will the program described by the input >>>>>>>>>>>>>>>>>> halt when run?

    Since you start off with the wrong question, you logic >>>>>>>>>>>>>>>>>> is just faulty.


    Everyone that thinks my question is incorrect is wrong. >>>>>>>>>>>>>>>>> It has always been a mathematical mapping from finite >>>>>>>>>>>>>>>>> strings to behaviors. That people do not comprehend this >>>>>>>>>>>>>>>>> shows the shallowness of the depth of the learned-by-rote >>>>>>>>>>>>>>>>> (lack of) understanding.


    No, you are just incorreect as you don't know what you >>>>>>>>>>>>>>>> are talking about.

    Yes, it is a mapping of the string to the behavior, and >>>>>>>>>>>>>>>> that mapping is DEFINED to be the halting behavior of >>>>>>>>>>>>>>>> the program the string describes.


    No this is incorrect. The input finite string specifies >>>>>>>>>>>>>>> (not merely describes) non halting behavior to its decider. >>>>>>>>>>>>>>>

    No, since the definition of "Halting Behavior" is the >>>>>>>>>>>>>> behavior of the progran being run.


    It may seem that way to people that have learned-by-rote >>>>>>>>>>>>> as their only basis. It is actually nothing like that. >>>>>>>>>>>>
    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite
    strings to the actual behavior that these finite strings >>>>>>>>>>> specify. That this is not dead obvious to everyone here
    merely proves that learned-by-rote does not involve any
    actual comprehension.



    And the behavior the finite string specifies is the behavior >>>>>>>>>> of running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The
    simulation aborts too soon on unsound grounds, one cycle before >>>>>>>> the normal termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally
    is a verified fact.


    Which proves that HHH fails to make a correct decision about DD's
    halting behaviour. All other methods (direct execution, simulation >>>>>> by a world class simulator, etc.) show that DD halts. But HHH
    fails to see it. Everyone with sufficient understanding of
    programming sees that HHH is not correctly programmed when it
    aborts one cycle before the simulation would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD...

    The execution trace only shows that HHH is unable to complete its
    simulation, because HHH is unable to simulate itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    The above code proves that HHH does simulate itself simulating DD.

    That you can't understand this code proves that you lack the
    technical basis to review my work.


    It turns out that Olcott does not even understand this simple proof
    that HHH produces false negatives. HHH is unable to simulate itself up
    to the normal termination.

    If you try to explain your view in terms of a line-by-line
    execution trace of DD simulated by HHH everyone will see that
    your claim has no actual basis what-so-ever and is merely
    utterly baseless rhetoric totally bereft of any supporting
    reasoning.


    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
    int main() {
    return HHH(main);
    }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he tries to
    hide with a lot of irrelevant words.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sun Feb 9 20:33:32 2025
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote:
    On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically last very >>>>>>>>>>>>>>>>>>>>>>>>> long and
    will be immediately followed by a riskier >>>>>>>>>>>>>>>>>>>>>>>>> fourth line
    of treatment that has an initial success rate >>>>>>>>>>>>>>>>>>>>>>>>> much higher
    than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved !


    The halting problem proof input does specify non- >>>>>>>>>>>>>>>>>>>>>>> halting
    behavior to its decider.

    https://www.researchgate.net/
    publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language >>>>>>>>>>>>>>>>>>>>> sufficiently well (thus not confused by the >>>>>>>>>>>>>>>>>>>>> unreachable
    "if" statement) correctly understands that DD >>>>>>>>>>>>>>>>>>>>> simulated
    by HHH cannot possibly reach its own return >>>>>>>>>>>>>>>>>>>>> instruction.


    And anyone that understand the halting problem knows >>>>>>>>>>>>>>>>>>>> that isn't the question being asked. The quesiton >>>>>>>>>>>>>>>>>>>> you NEED to ask is will the program described by the >>>>>>>>>>>>>>>>>>>> input halt when run?

    Since you start off with the wrong question, you >>>>>>>>>>>>>>>>>>>> logic is just faulty.


    Everyone that thinks my question is incorrect is wrong. >>>>>>>>>>>>>>>>>>> It has always been a mathematical mapping from finite >>>>>>>>>>>>>>>>>>> strings to behaviors. That people do not comprehend this >>>>>>>>>>>>>>>>>>> shows the shallowness of the depth of the learned-by- >>>>>>>>>>>>>>>>>>> rote
    (lack of) understanding.


    No, you are just incorreect as you don't know what you >>>>>>>>>>>>>>>>>> are talking about.

    Yes, it is a mapping of the string to the behavior, >>>>>>>>>>>>>>>>>> and that mapping is DEFINED to be the halting behavior >>>>>>>>>>>>>>>>>> of the program the string describes.


    No this is incorrect. The input finite string specifies >>>>>>>>>>>>>>>>> (not merely describes) non halting behavior to its >>>>>>>>>>>>>>>>> decider.


    No, since the definition of "Halting Behavior" is the >>>>>>>>>>>>>>>> behavior of the progran being run.


    It may seem that way to people that have learned-by-rote >>>>>>>>>>>>>>> as their only basis. It is actually nothing like that. >>>>>>>>>>>>>>
    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite >>>>>>>>>>>>> strings to the actual behavior that these finite strings >>>>>>>>>>>>> specify. That this is not dead obvious to everyone here >>>>>>>>>>>>> merely proves that learned-by-rote does not involve any >>>>>>>>>>>>> actual comprehension.



    And the behavior the finite string specifies is the behavior >>>>>>>>>>>> of running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The
    simulation aborts too soon on unsound grounds, one cycle
    before the normal termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally
    is a verified fact.


    Which proves that HHH fails to make a correct decision about
    DD's halting behaviour. All other methods (direct execution,
    simulation by a world class simulator, etc.) show that DD halts. >>>>>>>> But HHH fails to see it. Everyone with sufficient understanding >>>>>>>> of programming sees that HHH is not correctly programmed when it >>>>>>>> aborts one cycle before the simulation would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD...

    The execution trace only shows that HHH is unable to complete its
    simulation, because HHH is unable to simulate itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    The above code proves that HHH does simulate itself simulating DD.

    That you can't understand this code proves that you lack the
    technical basis to review my work.


    It turns out that Olcott does not even understand this simple proof
    that HHH produces false negatives. HHH is unable to simulate itself
    up to the normal termination.

    If you try to explain your view in terms of a line-by-line
    execution trace of DD simulated by HHH everyone will see that
    your claim has no actual basis what-so-ever and is merely
    utterly baseless rhetoric totally bereft of any supporting
    reasoning.


    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {
              return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he tries
    to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself correctly. It produces false negatives. Such a failing HHH cannot be used for the
    halting problem.

    If you believe
    otherwise this merely proves that you do not understand
    what recursion is and how it works.


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Feb 9 18:05:18 2025
    On 2/9/25 2:54 PM, olcott wrote:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically last very >>>>>>>>>>>>>>>>>>>>>>>>>>> long and
    will be immediately followed by a riskier >>>>>>>>>>>>>>>>>>>>>>>>>>> fourth line
    of treatment that has an initial success rate >>>>>>>>>>>>>>>>>>>>>>>>>>> much higher
    than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved !


    The halting problem proof input does specify >>>>>>>>>>>>>>>>>>>>>>>>> non- halting
    behavior to its decider.

    https://www.researchgate.net/ >>>>>>>>>>>>>>>>>>>>>>>>> publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language >>>>>>>>>>>>>>>>>>>>>>> sufficiently well (thus not confused by the >>>>>>>>>>>>>>>>>>>>>>> unreachable
    "if" statement) correctly understands that DD >>>>>>>>>>>>>>>>>>>>>>> simulated
    by HHH cannot possibly reach its own return >>>>>>>>>>>>>>>>>>>>>>> instruction.


    And anyone that understand the halting problem >>>>>>>>>>>>>>>>>>>>>> knows that isn't the question being asked. The >>>>>>>>>>>>>>>>>>>>>> quesiton you NEED to ask is will the program >>>>>>>>>>>>>>>>>>>>>> described by the input halt when run? >>>>>>>>>>>>>>>>>>>>>>
    Since you start off with the wrong question, you >>>>>>>>>>>>>>>>>>>>>> logic is just faulty.


    Everyone that thinks my question is incorrect is >>>>>>>>>>>>>>>>>>>>> wrong.
    It has always been a mathematical mapping from finite >>>>>>>>>>>>>>>>>>>>> strings to behaviors. That people do not comprehend >>>>>>>>>>>>>>>>>>>>> this
    shows the shallowness of the depth of the learned- >>>>>>>>>>>>>>>>>>>>> by- rote
    (lack of) understanding.


    No, you are just incorreect as you don't know what >>>>>>>>>>>>>>>>>>>> you are talking about.

    Yes, it is a mapping of the string to the behavior, >>>>>>>>>>>>>>>>>>>> and that mapping is DEFINED to be the halting >>>>>>>>>>>>>>>>>>>> behavior of the program the string describes. >>>>>>>>>>>>>>>>>>>>

    No this is incorrect. The input finite string specifies >>>>>>>>>>>>>>>>>>> (not merely describes) non halting behavior to its >>>>>>>>>>>>>>>>>>> decider.


    No, since the definition of "Halting Behavior" is the >>>>>>>>>>>>>>>>>> behavior of the progran being run.


    It may seem that way to people that have learned-by-rote >>>>>>>>>>>>>>>>> as their only basis. It is actually nothing like that. >>>>>>>>>>>>>>>>
    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite >>>>>>>>>>>>>>> strings to the actual behavior that these finite strings >>>>>>>>>>>>>>> specify. That this is not dead obvious to everyone here >>>>>>>>>>>>>>> merely proves that learned-by-rote does not involve any >>>>>>>>>>>>>>> actual comprehension.



    And the behavior the finite string specifies is the >>>>>>>>>>>>>> behavior of running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The >>>>>>>>>>>> simulation aborts too soon on unsound grounds, one cycle >>>>>>>>>>>> before the normal termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally
    is a verified fact.


    Which proves that HHH fails to make a correct decision about >>>>>>>>>> DD's halting behaviour. All other methods (direct execution, >>>>>>>>>> simulation by a world class simulator, etc.) show that DD
    halts. But HHH fails to see it. Everyone with sufficient
    understanding of programming sees that HHH is not correctly >>>>>>>>>> programmed when it aborts one cycle before the simulation
    would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD...

    The execution trace only shows that HHH is unable to complete
    its simulation, because HHH is unable to simulate itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    The above code proves that HHH does simulate itself simulating DD. >>>>>>>
    That you can't understand this code proves that you lack the
    technical basis to review my work.


    It turns out that Olcott does not even understand this simple
    proof that HHH produces false negatives. HHH is unable to simulate >>>>>> itself up to the normal termination.

    If you try to explain your view in terms of a line-by-line
    execution trace of DD simulated by HHH everyone will see that
    your claim has no actual basis what-so-ever and is merely
    utterly baseless rhetoric totally bereft of any supporting
    reasoning.


    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {           return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he tries
    to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself correctly.

    If this was true then you could point out exactly where HHH
    is incorrect. Because this is not true and you don't hardly
    understand these things at all your rebuttals are mere dogmatic
    assertions with no basis in actual reasoning what-so-ever.


    Been there, done that, you just ignore the answer because you are just admitting to being a fraud.

    One version of your output doesn't make the call to HHH go into HHH.

    The other vesion claims that there were no conditional branch in the
    code, when there were, since all the code of the HHH that DD calls are
    part of the program DD.

    So, all you are doing is admitting to being a liar.


    Here is the code point out the (nonexistent) error: https://github.com/plolcott/x86utm/blob/master/Halt7.c

    How about the non-pure simulator, that detects the hidden input to
    decide if this is the "root" emulator.


    It produces false negatives. Such a failing HHH cannot be used for the
    halting problem.

    If you believe
    otherwise this merely proves that you do not understand
    what recursion is and how it works.





    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Mon Feb 10 09:22:38 2025
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically last very >>>>>>>>>>>>>>>>>>>>>>>>>>> long and
    will be immediately followed by a riskier >>>>>>>>>>>>>>>>>>>>>>>>>>> fourth line
    of treatment that has an initial success rate >>>>>>>>>>>>>>>>>>>>>>>>>>> much higher
    than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved !


    The halting problem proof input does specify >>>>>>>>>>>>>>>>>>>>>>>>> non- halting
    behavior to its decider.

    https://www.researchgate.net/ >>>>>>>>>>>>>>>>>>>>>>>>> publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language >>>>>>>>>>>>>>>>>>>>>>> sufficiently well (thus not confused by the >>>>>>>>>>>>>>>>>>>>>>> unreachable
    "if" statement) correctly understands that DD >>>>>>>>>>>>>>>>>>>>>>> simulated
    by HHH cannot possibly reach its own return >>>>>>>>>>>>>>>>>>>>>>> instruction.


    And anyone that understand the halting problem >>>>>>>>>>>>>>>>>>>>>> knows that isn't the question being asked. The >>>>>>>>>>>>>>>>>>>>>> quesiton you NEED to ask is will the program >>>>>>>>>>>>>>>>>>>>>> described by the input halt when run? >>>>>>>>>>>>>>>>>>>>>>
    Since you start off with the wrong question, you >>>>>>>>>>>>>>>>>>>>>> logic is just faulty.


    Everyone that thinks my question is incorrect is >>>>>>>>>>>>>>>>>>>>> wrong.
    It has always been a mathematical mapping from finite >>>>>>>>>>>>>>>>>>>>> strings to behaviors. That people do not comprehend >>>>>>>>>>>>>>>>>>>>> this
    shows the shallowness of the depth of the learned- >>>>>>>>>>>>>>>>>>>>> by- rote
    (lack of) understanding.


    No, you are just incorreect as you don't know what >>>>>>>>>>>>>>>>>>>> you are talking about.

    Yes, it is a mapping of the string to the behavior, >>>>>>>>>>>>>>>>>>>> and that mapping is DEFINED to be the halting >>>>>>>>>>>>>>>>>>>> behavior of the program the string describes. >>>>>>>>>>>>>>>>>>>>

    No this is incorrect. The input finite string specifies >>>>>>>>>>>>>>>>>>> (not merely describes) non halting behavior to its >>>>>>>>>>>>>>>>>>> decider.


    No, since the definition of "Halting Behavior" is the >>>>>>>>>>>>>>>>>> behavior of the progran being run.


    It may seem that way to people that have learned-by-rote >>>>>>>>>>>>>>>>> as their only basis. It is actually nothing like that. >>>>>>>>>>>>>>>>
    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite >>>>>>>>>>>>>>> strings to the actual behavior that these finite strings >>>>>>>>>>>>>>> specify. That this is not dead obvious to everyone here >>>>>>>>>>>>>>> merely proves that learned-by-rote does not involve any >>>>>>>>>>>>>>> actual comprehension.



    And the behavior the finite string specifies is the >>>>>>>>>>>>>> behavior of running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace
    than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The >>>>>>>>>>>> simulation aborts too soon on unsound grounds, one cycle >>>>>>>>>>>> before the normal termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally
    is a verified fact.


    Which proves that HHH fails to make a correct decision about >>>>>>>>>> DD's halting behaviour. All other methods (direct execution, >>>>>>>>>> simulation by a world class simulator, etc.) show that DD
    halts. But HHH fails to see it. Everyone with sufficient
    understanding of programming sees that HHH is not correctly >>>>>>>>>> programmed when it aborts one cycle before the simulation
    would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD...

    The execution trace only shows that HHH is unable to complete
    its simulation, because HHH is unable to simulate itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    The above code proves that HHH does simulate itself simulating DD. >>>>>>>
    That you can't understand this code proves that you lack the
    technical basis to review my work.


    It turns out that Olcott does not even understand this simple
    proof that HHH produces false negatives. HHH is unable to simulate >>>>>> itself up to the normal termination.

    If you try to explain your view in terms of a line-by-line
    execution trace of DD simulated by HHH everyone will see that
    your claim has no actual basis what-so-ever and is merely
    utterly baseless rhetoric totally bereft of any supporting
    reasoning.


    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {           return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he tries
    to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself correctly.

    If this was true then you could point out exactly where HHH
    is incorrect.

    It is true as a verified fact and has been pointed out to Olcott many
    times, but he refuses to learn. So, again:

    It is a verified fact that main halts, as is verified by the direct
    execution and bij many simulators. From this we know how many
    instructions are executed to reach the termination status.
    The HHH aborts the simulation long before this number of instructions
    have been simulated. Aborting a halting program halfway, of course, does
    not prove that it does not halt.
    So, to directly answer the point: HHH is incorrect by aborting the
    simulation of a halting program halfway.

    It seems that Olcott does not even understand such simple logic and
    keeps repeating false claims without and evidence.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Mon Feb 10 11:16:41 2025
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote:
    On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote:
    On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:


    Which proves that HHH fails to make a correct decision about >>>>>>>>>> DD's halting behaviour. All other methods (direct execution, >>>>>>>>>> simulation by a world class simulator, etc.) show that DD
    halts. But HHH fails to see it. Everyone with sufficient
    understanding of programming sees that HHH is not correctly >>>>>>>>>> programmed when it aborts one cycle before the simulation would >>>>>>>>>> end normally.

    The execution trace only shows that HHH is unable to complete its >>>>>>>> simulation, because HHH is unable to simulate itself.

    It turns out that Olcott does not even understand this simple proof >>>>>> that HHH produces false negatives. HHH is unable to simulate itself >>>>>> up to the normal termination.

    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {
              return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he tries
    to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly simulated
    by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself correctly.

    If this was true then you could point out exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and return the correct value.

    Here is the code point out the (nonexistent) error:
    https://github.com/plolcott/x86utm/blob/master/Halt7.c#L502

    --
    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 Mon Feb 10 13:14:44 2025
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically last very >>>>>>>>>>>>>>>>>>>>>>>>>>>>> long and
    will be immediately followed by a riskier >>>>>>>>>>>>>>>>>>>>>>>>>>>>> fourth line
    of treatment that has an initial success >>>>>>>>>>>>>>>>>>>>>>>>>>>>> rate much higher
    than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved ! >>>>>>>>>>>>>>>>>>>>>>>>>>>>

    The halting problem proof input does specify >>>>>>>>>>>>>>>>>>>>>>>>>>> non- halting
    behavior to its decider. >>>>>>>>>>>>>>>>>>>>>>>>>>>
    https://www.researchgate.net/ >>>>>>>>>>>>>>>>>>>>>>>>>>> publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming language >>>>>>>>>>>>>>>>>>>>>>>>> sufficiently well (thus not confused by the >>>>>>>>>>>>>>>>>>>>>>>>> unreachable
    "if" statement) correctly understands that DD >>>>>>>>>>>>>>>>>>>>>>>>> simulated
    by HHH cannot possibly reach its own return >>>>>>>>>>>>>>>>>>>>>>>>> instruction.


    And anyone that understand the halting problem >>>>>>>>>>>>>>>>>>>>>>>> knows that isn't the question being asked. The >>>>>>>>>>>>>>>>>>>>>>>> quesiton you NEED to ask is will the program >>>>>>>>>>>>>>>>>>>>>>>> described by the input halt when run? >>>>>>>>>>>>>>>>>>>>>>>>
    Since you start off with the wrong question, you >>>>>>>>>>>>>>>>>>>>>>>> logic is just faulty.


    Everyone that thinks my question is incorrect is >>>>>>>>>>>>>>>>>>>>>>> wrong.
    It has always been a mathematical mapping from >>>>>>>>>>>>>>>>>>>>>>> finite
    strings to behaviors. That people do not >>>>>>>>>>>>>>>>>>>>>>> comprehend this
    shows the shallowness of the depth of the >>>>>>>>>>>>>>>>>>>>>>> learned- by- rote
    (lack of) understanding.


    No, you are just incorreect as you don't know what >>>>>>>>>>>>>>>>>>>>>> you are talking about.

    Yes, it is a mapping of the string to the >>>>>>>>>>>>>>>>>>>>>> behavior, and that mapping is DEFINED to be the >>>>>>>>>>>>>>>>>>>>>> halting behavior of the program the string describes. >>>>>>>>>>>>>>>>>>>>>>

    No this is incorrect. The input finite string >>>>>>>>>>>>>>>>>>>>> specifies
    (not merely describes) non halting behavior to its >>>>>>>>>>>>>>>>>>>>> decider.


    No, since the definition of "Halting Behavior" is >>>>>>>>>>>>>>>>>>>> the behavior of the progran being run. >>>>>>>>>>>>>>>>>>>>

    It may seem that way to people that have learned-by-rote >>>>>>>>>>>>>>>>>>> as their only basis. It is actually nothing like that. >>>>>>>>>>>>>>>>>>
    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite >>>>>>>>>>>>>>>>> strings to the actual behavior that these finite strings >>>>>>>>>>>>>>>>> specify. That this is not dead obvious to everyone here >>>>>>>>>>>>>>>>> merely proves that learned-by-rote does not involve any >>>>>>>>>>>>>>>>> actual comprehension.



    And the behavior the finite string specifies is the >>>>>>>>>>>>>>>> behavior of running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace >>>>>>>>>>>>>>> than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The >>>>>>>>>>>>>> simulation aborts too soon on unsound grounds, one cycle >>>>>>>>>>>>>> before the normal termination of the program.


    This proves that you simply don't have sufficient
    understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally >>>>>>>>>>>>> is a verified fact.


    Which proves that HHH fails to make a correct decision about >>>>>>>>>>>> DD's halting behaviour. All other methods (direct execution, >>>>>>>>>>>> simulation by a world class simulator, etc.) show that DD >>>>>>>>>>>> halts. But HHH fails to see it. Everyone with sufficient >>>>>>>>>>>> understanding of programming sees that HHH is not correctly >>>>>>>>>>>> programmed when it aborts one cycle before the simulation >>>>>>>>>>>> would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD...

    The execution trace only shows that HHH is unable to complete >>>>>>>>>> its simulation, because HHH is unable to simulate itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    The above code proves that HHH does simulate itself simulating DD. >>>>>>>>>
    That you can't understand this code proves that you lack the >>>>>>>>> technical basis to review my work.


    It turns out that Olcott does not even understand this simple
    proof that HHH produces false negatives. HHH is unable to
    simulate itself up to the normal termination.

    If you try to explain your view in terms of a line-by-line
    execution trace of DD simulated by HHH everyone will see that
    your claim has no actual basis what-so-ever and is merely
    utterly baseless rhetoric totally bereft of any supporting
    reasoning.


    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {           return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he
    tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself correctly.

    If this was true then you could point out exactly where HHH
    is incorrect.

    It is true as a verified fact and has been pointed out to Olcott many
    times, but he refuses to learn. So, again:

    It is a verified fact that main halts,

    It is a verified fact that the input to HHH(main) cannot
    possibly terminate normally.

    No, the verified fact is that the input can terminatie normally and in
    fact it does when executed directly or simulated by a correct simulator. Another verified fact is that HHH cannot bring the simulation to a
    correct end, proving that HHH fails.


    The strawman error <is> an error.


    Indeed, Olcott produced a strawman error.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Feb 10 07:37:15 2025
    On 2/10/25 7:02 AM, olcott wrote:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:


    Which proves that HHH fails to make a correct decision about >>>>>>>>>>>> DD's halting behaviour. All other methods (direct execution, >>>>>>>>>>>> simulation by a world class simulator, etc.) show that DD >>>>>>>>>>>> halts. But HHH fails to see it. Everyone with sufficient >>>>>>>>>>>> understanding of programming sees that HHH is not correctly >>>>>>>>>>>> programmed when it aborts one cycle before the simulation would >>>>>>>>>>>> end normally.

    The execution trace only shows that HHH is unable to complete its >>>>>>>>>> simulation, because HHH is unable to simulate itself.

    It turns out that Olcott does not even understand this simple proof >>>>>>>> that HHH produces false negatives. HHH is unable to simulate itself >>>>>>>> up to the normal termination.

    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
             int main() {
               return HHH(main);
             }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he tries >>>>>> to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly simulated >>>>> by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself correctly.

    If this was true then you could point out exactly where HHH is
    incorrect.

    HHH is supposed to be a decider, i.e. halt and return the correct value.


    The directly executed HHH(DD) always halts and returns a correct
    value as soon as it correctly determines that its input cannot
    possibly terminate normally.

    But that answer ISN'T "correct" becuase the input when run DOES
    terminate normally.

    Your problem is you just don't know what TRUTH is. You claim you need a
    link to the truth-makers but instead you build your links to your lies.


    Here is the code point out the (nonexistent) error:
    https://github.com/plolcott/x86utm/blob/master/Halt7.c#L502




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Feb 10 07:44:53 2025
    On 2/10/25 7:27 AM, olcott wrote:

    The directly executed main IS NOT THE INPUT TO HHH.



    Then you admit that HHH is not a halt decider, or you gave it the wrong
    input.

    The input to a halt decider is the description of a program, and asks
    what it does when run.

    So, your claim is just admitting that you have been lying for years.

    Sorry, but that is what your forced ignorance of the topic has done to you.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Mon Feb 10 12:47:23 2025
    Am Mon, 10 Feb 2025 05:51:21 -0600 schrieb olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    And anyone that understand the halting problem >>>>>>>>>>>>>>>>>>>>>>>> knows that isn't the question being asked. The >>>>>>>>>>>>>>>>>>>>>>>> quesiton you NEED to ask is will the program >>>>>>>>>>>>>>>>>>>>>>>> described by the input halt when run? >>>>>>>>>>>>>>>>>>>>>>>>
    It has always been a mathematical mapping from >>>>>>>>>>>>>>>>>>>>>>> finite strings to behaviors.

    Yes, it is a mapping of the string to the behavior, >>>>>>>>>>>>>>>>>>>>>> and that mapping is DEFINED to be the halting >>>>>>>>>>>>>>>>>>>>>> behavior of the program the string describes. >>>>>>>>>>>>>>>>>>>>>>
    No this is incorrect. The input finite string >>>>>>>>>>>>>>>>>>>>> specifies (not merely describes) non halting >>>>>>>>>>>>>>>>>>>>> behavior to its decider.

    No, since the definition of "Halting Behavior" is the >>>>>>>>>>>>>>>>>>>> behavior of the progran being run.

    A termination analyzer computes the mapping from finite >>>>>>>>>>>>>>>>> strings to the actual behavior that these finite strings >>>>>>>>>>>>>>>>> specify.

    And the behavior the finite string specifies is the >>>>>>>>>>>>>>>> behavior of running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace than >>>>>>>>>>>>>>> the behavior that DD specifies to HHH.

    If so, then it proves the failure of the simulation. The >>>>>>>>>>>>>> simulation aborts too soon on unsound grounds, one cycle >>>>>>>>>>>>>> before the normal termination of the program.

    DD simulated by HHH cannot possibly terminate normally is a >>>>>>>>>>>>> verified fact.

    Which proves that HHH fails to make a correct decision about >>>>>>>>>>>> DD's halting behaviour. All other methods (direct execution, >>>>>>>>>>>> simulation by a world class simulator, etc.) show that DD >>>>>>>>>>>> halts. But HHH fails to see it. Everyone with sufficient >>>>>>>>>>>> understanding of programming sees that HHH is not correctly >>>>>>>>>>>> programmed when it aborts one cycle before the simulation >>>>>>>>>>>> would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);
    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }
    int main()
    {
       HHH(DD);
    }

    The execution trace only shows that HHH is unable to complete >>>>>>>>>> its simulation, because HHH is unable to simulate itself.

    https://github.com/plolcott/x86utm/blob/master/Halt7.c The above >>>>>>>>> code proves that HHH does simulate itself simulating DD.

    It turns out that Olcott does not even understand this simple
    proof that HHH produces false negatives. HHH is unable to
    simulate itself up to the normal termination.

    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {           return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he
    tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself correctly.

    If this was true then you could point out exactly where HHH is
    incorrect.

    It is true as a verified fact and has been pointed out to Olcott many
    times, but he refuses to learn. So, again:
    It is a verified fact that main halts,

    It is a verified fact that the input to HHH(main) cannot possibly
    terminate normally. The strawman error <is> an error.
    Yeah, if the input HHH doesn’t terminate, that is not a decider.

    --
    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 joes@21:1/5 to All on Mon Feb 10 12:52:06 2025
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote:
    On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote:
    On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote:
    On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    Which proves that HHH fails to make a correct decision about >>>>>>>>>>>> DD's halting behaviour. All other methods (direct execution, >>>>>>>>>>>> simulation by a world class simulator, etc.) show that DD >>>>>>>>>>>> halts. But HHH fails to see it. Everyone with sufficient >>>>>>>>>>>> understanding of programming sees that HHH is not correctly >>>>>>>>>>>> programmed when it aborts one cycle before the simulation >>>>>>>>>>>> would end normally.
    The execution trace only shows that HHH is unable to complete >>>>>>>>>> its simulation, because HHH is unable to simulate itself.
    It turns out that Olcott does not even understand this simple
    proof that HHH produces false negatives. HHH is unable to
    simulate itself up to the normal termination.
    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {
              return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he
    tries to hide with a lot of irrelevant words.
    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself correctly.
    If this was true then you could point out exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and return the correct
    value.
    The directly executed HHH(DD) always halts and returns a correct value
    as soon as it correctly determines that its input cannot possibly
    terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according
    to spec, so does the inner, because it is the same. Therefore
    it can’t report „non-halting” and be correct. If the inner HHH
    doesn’t halt, it is not a decider.

    Here is the code point out the (nonexistent) error:
    https://github.com/plolcott/x86utm/blob/master/Halt7.c#L502
    Look at it.

    --
    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 joes@21:1/5 to All on Mon Feb 10 12:59:49 2025
    Am Mon, 10 Feb 2025 06:27:33 -0600 schrieb olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself
    correctly.
    If this was true then you could point out exactly where HHH is
    incorrect.
    Line 502.

    It is true as a verified fact and has been pointed out to Olcott many
    times, but he refuses to learn. So, again:
    It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot possibly
    terminate normally.
    No, the verified fact is that the input can terminatie normally
    The directly executed main IS NOT THE INPUT TO HHH.
    It’s not? What if it were?

    --
    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 Mon Feb 10 19:41:49 2025
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically last >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> very long and
    will be immediately followed by a riskier >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> fourth line
    of treatment that has an initial success >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> rate much higher >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved ! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    The halting problem proof input does >>>>>>>>>>>>>>>>>>>>>>>>>>>>> specify non- halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>> behavior to its decider. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    https://www.researchgate.net/ >>>>>>>>>>>>>>>>>>>>>>>>>>>>> publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming >>>>>>>>>>>>>>>>>>>>>>>>>>> language
    sufficiently well (thus not confused by the >>>>>>>>>>>>>>>>>>>>>>>>>>> unreachable
    "if" statement) correctly understands that DD >>>>>>>>>>>>>>>>>>>>>>>>>>> simulated
    by HHH cannot possibly reach its own return >>>>>>>>>>>>>>>>>>>>>>>>>>> instruction.


    And anyone that understand the halting problem >>>>>>>>>>>>>>>>>>>>>>>>>> knows that isn't the question being asked. The >>>>>>>>>>>>>>>>>>>>>>>>>> quesiton you NEED to ask is will the program >>>>>>>>>>>>>>>>>>>>>>>>>> described by the input halt when run? >>>>>>>>>>>>>>>>>>>>>>>>>>
    Since you start off with the wrong question, >>>>>>>>>>>>>>>>>>>>>>>>>> you logic is just faulty.


    Everyone that thinks my question is incorrect >>>>>>>>>>>>>>>>>>>>>>>>> is wrong.
    It has always been a mathematical mapping from >>>>>>>>>>>>>>>>>>>>>>>>> finite
    strings to behaviors. That people do not >>>>>>>>>>>>>>>>>>>>>>>>> comprehend this
    shows the shallowness of the depth of the >>>>>>>>>>>>>>>>>>>>>>>>> learned- by- rote
    (lack of) understanding.


    No, you are just incorreect as you don't know >>>>>>>>>>>>>>>>>>>>>>>> what you are talking about.

    Yes, it is a mapping of the string to the >>>>>>>>>>>>>>>>>>>>>>>> behavior, and that mapping is DEFINED to be the >>>>>>>>>>>>>>>>>>>>>>>> halting behavior of the program the string >>>>>>>>>>>>>>>>>>>>>>>> describes.


    No this is incorrect. The input finite string >>>>>>>>>>>>>>>>>>>>>>> specifies
    (not merely describes) non halting behavior to >>>>>>>>>>>>>>>>>>>>>>> its decider.


    No, since the definition of "Halting Behavior" is >>>>>>>>>>>>>>>>>>>>>> the behavior of the progran being run. >>>>>>>>>>>>>>>>>>>>>>

    It may seem that way to people that have learned- >>>>>>>>>>>>>>>>>>>>> by- rote
    as their only basis. It is actually nothing like that. >>>>>>>>>>>>>>>>>>>>
    No, that *IS* the definition.


    A termination analyzer computes the mapping from finite >>>>>>>>>>>>>>>>>>> strings to the actual behavior that these finite strings >>>>>>>>>>>>>>>>>>> specify. That this is not dead obvious to everyone here >>>>>>>>>>>>>>>>>>> merely proves that learned-by-rote does not involve any >>>>>>>>>>>>>>>>>>> actual comprehension.



    And the behavior the finite string specifies is the >>>>>>>>>>>>>>>>>> behavior of running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace >>>>>>>>>>>>>>>>> than the behavior that DD specifies to HHH.


    If so, then it proves the failure of the simulation. The >>>>>>>>>>>>>>>> simulation aborts too soon on unsound grounds, one cycle >>>>>>>>>>>>>>>> before the normal termination of the program.


    This proves that you simply don't have sufficient >>>>>>>>>>>>>>> understanding of the C programming language.
    DD simulated by HHH cannot possibly terminate normally >>>>>>>>>>>>>>> is a verified fact.


    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>> about DD's halting behaviour. All other methods (direct >>>>>>>>>>>>>> execution, simulation by a world class simulator, etc.) >>>>>>>>>>>>>> show that DD halts. But HHH fails to see it. Everyone with >>>>>>>>>>>>>> sufficient understanding of programming sees that HHH is >>>>>>>>>>>>>> not correctly programmed when it aborts one cycle before >>>>>>>>>>>>>> the simulation would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD... >>>>>>>>>>>>
    The execution trace only shows that HHH is unable to
    complete its simulation, because HHH is unable to simulate >>>>>>>>>>>> itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c
    The above code proves that HHH does simulate itself
    simulating DD.

    That you can't understand this code proves that you lack the >>>>>>>>>>> technical basis to review my work.


    It turns out that Olcott does not even understand this simple >>>>>>>>>> proof that HHH produces false negatives. HHH is unable to
    simulate itself up to the normal termination.

    If you try to explain your view in terms of a line-by-line
    execution trace of DD simulated by HHH everyone will see that >>>>>>>>> your claim has no actual basis what-so-ever and is merely
    utterly baseless rhetoric totally bereft of any supporting
    reasoning.


    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {           return HHH(main); >>>>>>>>         }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>> tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself correctly. >>>>>
    If this was true then you could point out exactly where HHH
    is incorrect.

    It is true as a verified fact and has been pointed out to Olcott
    many times, but he refuses to learn. So, again:

    It is a verified fact that main halts,

    It is a verified fact that the input to HHH(main) cannot
    possibly terminate normally.

    No, the verified fact is that the input can terminatie normally

    The directly executed main IS NOT THE INPUT TO HHH.



    This main is a program that includes all functions called directly and indirectly, including HHH.
    This program has been proven to halt, e.g. by direct execution or in the simulation by many simulators.
    This unique finite string describes a program with one single behaviour:
    it halts. This property is independent of the system that interprets the
    finite string.
    This is exactly the same main that is passed to HHH. This is the input
    to HHH. This is the program HHH should decide about. If HHH decides
    about another imaginary program, than HHH is completely wrong,
    uninteresting and worthless.
    It seems that this is one of Olcott's basic errors. He does not
    understand that HHH is supposed to decide about its input, not about a imaginary non-input.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Mon Feb 10 20:48:39 2025
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>> about DD's halting behaviour. All other methods (direct >>>>>>>>>>>>>> execution,
    simulation by a world class simulator, etc.) show that DD >>>>>>>>>>>>>> halts. But HHH fails to see it. Everyone with sufficient >>>>>>>>>>>>>> understanding of programming sees that HHH is not correctly >>>>>>>>>>>>>> programmed when it aborts one cycle before the simulation >>>>>>>>>>>>>> would end normally.
    The execution trace only shows that HHH is unable to complete >>>>>>>>>>>> its simulation, because HHH is unable to simulate itself. >>>>>>>>>> It turns out that Olcott does not even understand this simple >>>>>>>>>> proof that HHH produces false negatives. HHH is unable to
    simulate itself up to the normal termination.
    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {
              return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>> tries to hide with a lot of irrelevant words.
    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself
    correctly.
    If this was true then you could point out exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and return the correct
    value.
    The directly executed HHH(DD) always halts and returns a correct value
    as soon as it correctly determines that its input cannot possibly
    terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according to
    spec, so does the inner, because it is the same. Therefore it can’t
    report „non-halting” and be correct. If the inner HHH doesn’t halt, it >> is not a decider.
    RSVP

    Here is the code point out the (nonexistent) error:
    https://github.com/plolcott/x86utm/blob/master/Halt7.c#L502
    Look at it.
    That is not an error.
    It is a verified fact that DD correctly simulated by HHH cannot possibly terminate normally. The line you referred to does not change that
    verified fact.
    You didn’t look at it.

    --
    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 Mon Feb 10 18:43:17 2025
    On 2/10/25 9:46 AM, olcott wrote:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote:
    On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote:
    On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    Which proves that HHH fails to make a correct decision about >>>>>>>>>>>>>> DD's halting behaviour. All other methods (direct execution, >>>>>>>>>>>>>> simulation by a world class simulator, etc.) show that DD >>>>>>>>>>>>>> halts. But HHH fails to see it. Everyone with sufficient >>>>>>>>>>>>>> understanding of programming sees that HHH is not correctly >>>>>>>>>>>>>> programmed when it aborts one cycle before the simulation >>>>>>>>>>>>>> would end normally.
    The execution trace only shows that HHH is unable to complete >>>>>>>>>>>> its simulation, because HHH is unable to simulate itself. >>>>>>>>>> It turns out that Olcott does not even understand this simple >>>>>>>>>> proof that HHH produces false negatives. HHH is unable to
    simulate itself up to the normal termination.
    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
              int main() {
                return HHH(main);
              }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>> tries to hide with a lot of irrelevant words.
    It is a verified fact that main cannot possibly be correctly
    simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself correctly. >>>>> If this was true then you could point out exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and return the correct
    value.
    The directly executed HHH(DD) always halts and returns a correct value
    as soon as it correctly determines that its input cannot possibly
    terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according
    to spec, so does the inner, because it is the same. Therefore
    it can’t report „non-halting” and be correct. If the inner HHH
    doesn’t halt, it is not a decider.

    Here is the code point out the (nonexistent) error:
    https://github.com/plolcott/x86utm/blob/master/Halt7.c#L502
    Look at it.


    That is not an error.
    It is a verified fact that DD correctly simulated by HHH cannot
    possibly terminate normally. The line you referred to does not
    change that verified fact.



    Nope, you have only verified that OTHER HHHs looking at OTHER DD get
    into an infinite loop when trying to simulate.

    Sorry, wrong problem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Feb 10 18:58:30 2025
    On 2/10/25 4:38 PM, olcott wrote:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>>>> about DD's halting behaviour. All other methods (direct >>>>>>>>>>>>>>>> execution,
    simulation by a world class simulator, etc.) show that DD >>>>>>>>>>>>>>>> halts. But HHH fails to see it. Everyone with sufficient >>>>>>>>>>>>>>>> understanding of programming sees that HHH is not correctly >>>>>>>>>>>>>>>> programmed when it aborts one cycle before the simulation >>>>>>>>>>>>>>>> would end normally.
    The execution trace only shows that HHH is unable to complete >>>>>>>>>>>>>> its simulation, because HHH is unable to simulate itself. >>>>>>>>>>>> It turns out that Olcott does not even understand this simple >>>>>>>>>>>> proof that HHH produces false negatives. HHH is unable to >>>>>>>>>>>> simulate itself up to the normal termination.
    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
               int main() {
                 return HHH(main);
               }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>>>> tries to hide with a lot of irrelevant words.
    It is a verified fact that main cannot possibly be correctly >>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself
    correctly.
    If this was true then you could point out exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and return the correct
    value.
    The directly executed HHH(DD) always halts and returns a correct value >>>>> as soon as it correctly determines that its input cannot possibly
    terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according to
    spec, so does the inner, because it is the same. Therefore it can’t
    report „non-halting” and be correct. If the inner HHH doesn’t halt, it
    is not a decider.
    RSVP

    Here is the code point out the (nonexistent) error:
    https://github.com/plolcott/x86utm/blob/master/Halt7.c#L502
    Look at it.
    That is not an error.
    It is a verified fact that DD correctly simulated by HHH cannot possibly >>> terminate normally. The line you referred to does not change that
    verified fact.

    You didn’t look at it.


    I did look at it and was pleased that you noticed the significance
    of this line-of-code. None-the-less it does not and cannot possibly
    alter the truism that DD simulated by HHH cannot possibly terminate
    normally.


    N o, you have FAILED to look at and correct the error that DISQUALIFIES
    HHH from being a decider, in part because to do so will fundamentally
    break parts of your needed operation of the program.

    This just shows that you are nothing but a FRAUD, and too stupid to
    understand your stupidity.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Tue Feb 11 07:28:53 2025
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {           return HHH(main); >>>>>>>>>>         }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>>>> tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly >>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself
    correctly.
    If this was true then you could point out exactly where HHH is
    incorrect.
    It is true as a verified fact and has been pointed out to Olcott
    many times, but he refuses to learn. So, again:
    It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot possibly
    terminate normally.
    No, the verified fact is that the input can terminatie normally
    The directly executed main IS NOT THE INPUT TO HHH.

    This main is a program that includes all functions called directly and
    indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot possibly terminate normally.
    The input to HHH, which is main(), terminates. HHH does not simulate that.

    The directly executed main() *IS NOT* the input to HHH(main)
    and *IS NOT* simulated by HHH.
    Do you not think you can pass a program to a simulator? What else do
    you think HHH is simulating.

    The security guard at the front door cannot even see the back door thus
    is not accountable for the back door.
    The guard should damn well be.

    HHH can see what its input does and that *IS ALL* that it is accountable
    for.
    No. HHH can see what itself does. If it did something different to the
    input, that would not change what the input does.

    --
    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 11 11:07:34 2025
    Op 10.feb.2025 om 21:36 schreef olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically last >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> very long and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> will be immediately followed by a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> riskier fourth line >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> of treatment that has an initial >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> success rate much higher >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved ! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    The halting problem proof input does >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> specify non- halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behavior to its decider. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    https://www.researchgate.net/ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming >>>>>>>>>>>>>>>>>>>>>>>>>>>>> language
    sufficiently well (thus not confused by the >>>>>>>>>>>>>>>>>>>>>>>>>>>>> unreachable
    "if" statement) correctly understands that >>>>>>>>>>>>>>>>>>>>>>>>>>>>> DD simulated
    by HHH cannot possibly reach its own return >>>>>>>>>>>>>>>>>>>>>>>>>>>>> instruction.


    And anyone that understand the halting >>>>>>>>>>>>>>>>>>>>>>>>>>>> problem knows that isn't the question being >>>>>>>>>>>>>>>>>>>>>>>>>>>> asked. The quesiton you NEED to ask is will >>>>>>>>>>>>>>>>>>>>>>>>>>>> the program described by the input halt when >>>>>>>>>>>>>>>>>>>>>>>>>>>> run?

    Since you start off with the wrong question, >>>>>>>>>>>>>>>>>>>>>>>>>>>> you logic is just faulty. >>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Everyone that thinks my question is incorrect >>>>>>>>>>>>>>>>>>>>>>>>>>> is wrong.
    It has always been a mathematical mapping >>>>>>>>>>>>>>>>>>>>>>>>>>> from finite
    strings to behaviors. That people do not >>>>>>>>>>>>>>>>>>>>>>>>>>> comprehend this
    shows the shallowness of the depth of the >>>>>>>>>>>>>>>>>>>>>>>>>>> learned- by- rote
    (lack of) understanding. >>>>>>>>>>>>>>>>>>>>>>>>>>>

    No, you are just incorreect as you don't know >>>>>>>>>>>>>>>>>>>>>>>>>> what you are talking about. >>>>>>>>>>>>>>>>>>>>>>>>>>
    Yes, it is a mapping of the string to the >>>>>>>>>>>>>>>>>>>>>>>>>> behavior, and that mapping is DEFINED to be >>>>>>>>>>>>>>>>>>>>>>>>>> the halting behavior of the program the string >>>>>>>>>>>>>>>>>>>>>>>>>> describes.


    No this is incorrect. The input finite string >>>>>>>>>>>>>>>>>>>>>>>>> specifies
    (not merely describes) non halting behavior to >>>>>>>>>>>>>>>>>>>>>>>>> its decider.


    No, since the definition of "Halting Behavior" >>>>>>>>>>>>>>>>>>>>>>>> is the behavior of the progran being run. >>>>>>>>>>>>>>>>>>>>>>>>

    It may seem that way to people that have learned- >>>>>>>>>>>>>>>>>>>>>>> by- rote
    as their only basis. It is actually nothing like >>>>>>>>>>>>>>>>>>>>>>> that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from >>>>>>>>>>>>>>>>>>>>> finite
    strings to the actual behavior that these finite >>>>>>>>>>>>>>>>>>>>> strings
    specify. That this is not dead obvious to everyone >>>>>>>>>>>>>>>>>>>>> here
    merely proves that learned-by-rote does not involve >>>>>>>>>>>>>>>>>>>>> any
    actual comprehension.



    And the behavior the finite string specifies is the >>>>>>>>>>>>>>>>>>>> behavior of running the program.

    That is verifiably factually incorrect.
    The running program has a different execution trace >>>>>>>>>>>>>>>>>>> than the behavior that DD specifies to HHH. >>>>>>>>>>>>>>>>>>>

    If so, then it proves the failure of the simulation. >>>>>>>>>>>>>>>>>> The simulation aborts too soon on unsound grounds, one >>>>>>>>>>>>>>>>>> cycle before the normal termination of the program. >>>>>>>>>>>>>>>>>>

    This proves that you simply don't have sufficient >>>>>>>>>>>>>>>>> understanding of the C programming language. >>>>>>>>>>>>>>>>> DD simulated by HHH cannot possibly terminate normally >>>>>>>>>>>>>>>>> is a verified fact.


    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>>>> about DD's halting behaviour. All other methods (direct >>>>>>>>>>>>>>>> execution, simulation by a world class simulator, etc.) >>>>>>>>>>>>>>>> show that DD halts. But HHH fails to see it. Everyone >>>>>>>>>>>>>>>> with sufficient understanding of programming sees that >>>>>>>>>>>>>>>> HHH is not correctly programmed when it aborts one cycle >>>>>>>>>>>>>>>> before the simulation would end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace
    of HHH simulating DD calling HHH(DD) simulating DD... >>>>>>>>>>>>>>
    The execution trace only shows that HHH is unable to >>>>>>>>>>>>>> complete its simulation, because HHH is unable to simulate >>>>>>>>>>>>>> itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c >>>>>>>>>>>>> The above code proves that HHH does simulate itself
    simulating DD.

    That you can't understand this code proves that you lack the >>>>>>>>>>>>> technical basis to review my work.


    It turns out that Olcott does not even understand this >>>>>>>>>>>> simple proof that HHH produces false negatives. HHH is >>>>>>>>>>>> unable to simulate itself up to the normal termination. >>>>>>>>>>>
    If you try to explain your view in terms of a line-by-line >>>>>>>>>>> execution trace of DD simulated by HHH everyone will see that >>>>>>>>>>> your claim has no actual basis what-so-ever and is merely >>>>>>>>>>> utterly baseless rhetoric totally bereft of any supporting >>>>>>>>>>> reasoning.


    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {           return HHH(main); >>>>>>>>>>         }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>>>> tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly >>>>>>>>> simulated by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself
    correctly.

    If this was true then you could point out exactly where HHH
    is incorrect.

    It is true as a verified fact and has been pointed out to Olcott
    many times, but he refuses to learn. So, again:

    It is a verified fact that main halts,

    It is a verified fact that the input to HHH(main) cannot
    possibly terminate normally.

    No, the verified fact is that the input can terminatie normally

    The directly executed main IS NOT THE INPUT TO HHH.



    This main is a program that includes all functions called directly and
    indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH
    cannot possibly terminate normally.

    Which proves that HHH fails, because the direct execution and many other simulators do execute it up to normal termination.
    This makes it a verified fact that HHH fails.


    The directly executed main() *IS NOT* the input to HHH(main)
    and  *IS NOT* simulated by HHH.

    Then HHH is given the wrong input. What is the response of HHH when it
    is given the same finite string that describes the main that is executed directly?


    The security guard at the front door cannot even see
    the back door thus is not accountable for the back door.

    But if it was known that the thief would enter the backdoor, then
    security guard guards the wrong door.


    HHH can see what its input does and that *IS ALL* that
    it is accountable for.

    If HHH is given the wrong input, then it is not HHH's error to give the
    wrong response, but it is the error of the programmer that gave HHH the
    wrong input.
    Why would Olcott change the input and analyse an unintersesting
    imaginairy input instead of the finite string we are discussing? It
    seems the most stupid thing to do.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Tue Feb 11 15:23:14 2025
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 06:53 schreef olcott:
    On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>>>> about DD's halting behaviour. All other methods (direct >>>>>>>>>>>>>>>> execution,
    simulation by a world class simulator, etc.) show that DD >>>>>>>>>>>>>>>> halts. But HHH fails to see it. Everyone with sufficient >>>>>>>>>>>>>>>> understanding of programming sees that HHH is not >>>>>>>>>>>>>>>> correctly programmed when it aborts one cycle before the >>>>>>>>>>>>>>>> simulation would end normally.
    The execution trace only shows that HHH is unable to >>>>>>>>>>>>>> complete its simulation, because HHH is unable to simulate >>>>>>>>>>>>>> itself.
    It turns out that Olcott does not even understand this simple >>>>>>>>>>>> proof that HHH produces false negatives. HHH is unable to >>>>>>>>>>>> simulate itself up to the normal termination.
    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {
              return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>>>> tries to hide with a lot of irrelevant words.
    It is a verified fact that main cannot possibly be correctly >>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself
    correctly.
    If this was true then you could point out exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and return the correct
    value.
    The directly executed HHH(DD) always halts and returns a correct
    value as soon as it correctly determines that its input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according to
    spec, so does the inner, because it is the same. Therefore it can’t
    report „non-halting” and be correct. If the inner HHH doesn’t halt, >>>> it is not a decider.
    RSVP
    Hello?

    Here is the code point out the (nonexistent) error:
    https://github.com/plolcott/x86utm/blob/master/Halt7.c#L502
    Look at it.
    That is not an error.
    It is a verified fact that DD correctly simulated by HHH cannot
    possibly terminate normally. The line you referred to does not change
    that verified fact.
    You didn’t look at it.
    I did look at it and was pleased that you noticed the significance of
    this line-of-code. None-the-less it does not and cannot possibly alter
    the truism that DD simulated by HHH cannot possibly terminate normally.
    The significance of that line is that it changes the halting behaviour
    of 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 11 17:10:51 2025
    Op 11.feb.2025 om 15:38 schreef olcott:
    On 2/11/2025 1:28 AM, joes wrote:
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
             int main() {           return HHH(main); >>>>>>>>>>>>          }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>>>>>> tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>> incorrect.
    It is true as a verified fact and has been pointed out to Olcott >>>>>>>> many times, but he refuses to learn. So, again:
    It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot possibly >>>>>>> terminate normally.
    No, the verified fact is that the input can terminatie normally
    The directly executed main IS NOT THE INPUT TO HHH.

    This main is a program that includes all functions called directly and >>>> indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot possibly
    terminate normally.

    The input to HHH, which is main(), terminates. HHH does not simulate
    that.


    The directly executed main() is not the same instance of
    main() that is input to HHH and simulated by HHH.

    The directly executed main() relies on HHH aborting
    the simulation of its input. HHH cannot rely on anything
    else aborting the simulation of its input.

    The simulating HHH should rely on the simulated HHH to abort. But HHH is
    not clever enough to see that the simulated HHH aborts. Therefore, the simulating HHH aborts one cycle before the simulated HHH would abort.


    Unless HHH does abort the simulation of its input HHH
    itself would never terminate normally. This by itself
    proves that that the input to HHH cannot possibly
    terminate normally.
    If the simulating HHH would not abort, then the simulated HHH would
    abort. But HHH is not programmed clever enough to see that the simulated
    HHH already aborts.

    In fact it is impossible to create an HHH that is clever enough. This is
    the halting theorem.
    So, Olcott does nothing else but proving the halting theorem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Tue Feb 11 17:04:52 2025
    Op 11.feb.2025 om 15:46 schreef olcott:
    On 2/11/2025 4:07 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 21:36 schreef olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> last very long and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> will be immediately followed by a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> riskier fourth line >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> of treatment that has an initial >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> success rate much higher >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved ! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    The halting problem proof input does >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> specify non- halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behavior to its decider. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    https://www.researchgate.net/ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> language
    sufficiently well (thus not confused by >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the unreachable
    "if" statement) correctly understands >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD simulated >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> by HHH cannot possibly reach its own >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> return instruction. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    And anyone that understand the halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> problem knows that isn't the question >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> being asked. The quesiton you NEED to ask >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is will the program described by the input >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> halt when run?

    Since you start off with the wrong >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> question, you logic is just faulty. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Everyone that thinks my question is >>>>>>>>>>>>>>>>>>>>>>>>>>>>> incorrect is wrong.
    It has always been a mathematical mapping >>>>>>>>>>>>>>>>>>>>>>>>>>>>> from finite
    strings to behaviors. That people do not >>>>>>>>>>>>>>>>>>>>>>>>>>>>> comprehend this
    shows the shallowness of the depth of the >>>>>>>>>>>>>>>>>>>>>>>>>>>>> learned- by- rote
    (lack of) understanding. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    No, you are just incorreect as you don't >>>>>>>>>>>>>>>>>>>>>>>>>>>> know what you are talking about. >>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Yes, it is a mapping of the string to the >>>>>>>>>>>>>>>>>>>>>>>>>>>> behavior, and that mapping is DEFINED to be >>>>>>>>>>>>>>>>>>>>>>>>>>>> the halting behavior of the program the >>>>>>>>>>>>>>>>>>>>>>>>>>>> string describes.


    No this is incorrect. The input finite string >>>>>>>>>>>>>>>>>>>>>>>>>>> specifies
    (not merely describes) non halting behavior >>>>>>>>>>>>>>>>>>>>>>>>>>> to its decider.


    No, since the definition of "Halting Behavior" >>>>>>>>>>>>>>>>>>>>>>>>>> is the behavior of the progran being run. >>>>>>>>>>>>>>>>>>>>>>>>>>

    It may seem that way to people that have >>>>>>>>>>>>>>>>>>>>>>>>> learned- by- rote
    as their only basis. It is actually nothing >>>>>>>>>>>>>>>>>>>>>>>>> like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from >>>>>>>>>>>>>>>>>>>>>>> finite
    strings to the actual behavior that these finite >>>>>>>>>>>>>>>>>>>>>>> strings
    specify. That this is not dead obvious to >>>>>>>>>>>>>>>>>>>>>>> everyone here
    merely proves that learned-by-rote does not >>>>>>>>>>>>>>>>>>>>>>> involve any
    actual comprehension.



    And the behavior the finite string specifies is >>>>>>>>>>>>>>>>>>>>>> the behavior of running the program. >>>>>>>>>>>>>>>>>>>>>
    That is verifiably factually incorrect. >>>>>>>>>>>>>>>>>>>>> The running program has a different execution trace >>>>>>>>>>>>>>>>>>>>> than the behavior that DD specifies to HHH. >>>>>>>>>>>>>>>>>>>>>

    If so, then it proves the failure of the simulation. >>>>>>>>>>>>>>>>>>>> The simulation aborts too soon on unsound grounds, >>>>>>>>>>>>>>>>>>>> one cycle before the normal termination of the program. >>>>>>>>>>>>>>>>>>>>

    This proves that you simply don't have sufficient >>>>>>>>>>>>>>>>>>> understanding of the C programming language. >>>>>>>>>>>>>>>>>>> DD simulated by HHH cannot possibly terminate normally >>>>>>>>>>>>>>>>>>> is a verified fact.


    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>>>>>> about DD's halting behaviour. All other methods >>>>>>>>>>>>>>>>>> (direct execution, simulation by a world class >>>>>>>>>>>>>>>>>> simulator, etc.) show that DD halts. But HHH fails to >>>>>>>>>>>>>>>>>> see it. Everyone with sufficient understanding of >>>>>>>>>>>>>>>>>> programming sees that HHH is not correctly programmed >>>>>>>>>>>>>>>>>> when it aborts one cycle before the simulation would >>>>>>>>>>>>>>>>>> end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace >>>>>>>>>>>>>>>>> of HHH simulating DD calling HHH(DD) simulating DD... >>>>>>>>>>>>>>>>
    The execution trace only shows that HHH is unable to >>>>>>>>>>>>>>>> complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>> simulate itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c >>>>>>>>>>>>>>> The above code proves that HHH does simulate itself >>>>>>>>>>>>>>> simulating DD.

    That you can't understand this code proves that you lack the >>>>>>>>>>>>>>> technical basis to review my work.


    It turns out that Olcott does not even understand this >>>>>>>>>>>>>> simple proof that HHH produces false negatives. HHH is >>>>>>>>>>>>>> unable to simulate itself up to the normal termination. >>>>>>>>>>>>>
    If you try to explain your view in terms of a line-by-line >>>>>>>>>>>>> execution trace of DD simulated by HHH everyone will see that >>>>>>>>>>>>> your claim has no actual basis what-so-ever and is merely >>>>>>>>>>>>> utterly baseless rhetoric totally bereft of any supporting >>>>>>>>>>>>> reasoning.


    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {           return HHH(main); >>>>>>>>>>>>         }
    but he denies it.
    He lacks the ability to accept simple verified facts, which >>>>>>>>>>>> he tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>> simulated by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>> correctly.

    If this was true then you could point out exactly where HHH
    is incorrect.

    It is true as a verified fact and has been pointed out to Olcott >>>>>>>> many times, but he refuses to learn. So, again:

    It is a verified fact that main halts,

    It is a verified fact that the input to HHH(main) cannot
    possibly terminate normally.

    No, the verified fact is that the input can terminatie normally

    The directly executed main IS NOT THE INPUT TO HHH.



    This main is a program that includes all functions called directly
    and indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH
    cannot possibly terminate normally.

    Which proves that HHH fails, because the direct execution and many
    other simulators do execute it up to normal termination.
    This makes it a verified fact that HHH fails.

    The code itself conclusively proves that I and the code are
    both correct. That you disagree with this code is ridiculous.

    That you can come up with an example that is more difficult
    for you to understand is not useful.

    DD simulated by HHH cannot possibly terminate normally. https://www.researchgate.net/ publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
    Why does Olcott keep denying verified facts? The finite string has been
    proven to describe a program that terminates normally, both by direct execution, as well as by simulation of many simulators.
    This finite string is the exact input that should be given to HHH.
    It either a, or b:
    a) If HHH is given another input, then the programmer is cheating.
    b) If HHH is given this same finite string, but it reports non-halting,
    then HHH is simply wrong.
    I suspect it is b. HHH has a bug in the detection of the 'special
    condition', so that it aborts one cycle before the simulation would halt
    by its own.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Tue Feb 11 17:44:30 2025
    Op 11.feb.2025 om 17:22 schreef olcott:
    On 2/11/2025 10:10 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 15:38 schreef olcott:
    On 2/11/2025 1:28 AM, joes wrote:
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Am 05.02.2025 um 04:38 schrieb olcott: >>>>
    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
             int main() {           return HHH(main);
             }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>> which he
    tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>>>> incorrect.
    It is true as a verified fact and has been pointed out to Olcott >>>>>>>>>> many times, but he refuses to learn. So, again:
    It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot possibly >>>>>>>>> terminate normally.
    No, the verified fact is that the input can terminatie normally >>>>>>> The directly executed main IS NOT THE INPUT TO HHH.

    This main is a program that includes all functions called directly >>>>>> and
    indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot possibly >>>>> terminate normally.

    The input to HHH, which is main(), terminates. HHH does not simulate
    that.


    The directly executed main() is not the same instance of
    main() that is input to HHH and simulated by HHH.

    The directly executed main() relies on HHH aborting
    the simulation of its input. HHH cannot rely on anything
    else aborting the simulation of its input.

    The simulating HHH should rely on the simulated HHH to abort.

    That cannot possibly work. The executed HHH always sees at least one
    more full execution trace than any inner HHH ever sees.


    Indeed, that is what I said, but Olcott deleted it in the citation.
    HHH cannot do what it should do. So, he proves the halting theorem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Tue Feb 11 20:05:32 2025
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>
    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>>>>>> about DD's halting behaviour. All other methods (direct >>>>>>>>>>>>>>>>>> execution,
    simulation by a world class simulator, etc.) show that >>>>>>>>>>>>>>>>>> DD halts. But HHH fails to see it. Everyone with >>>>>>>>>>>>>>>>>> sufficient understanding of programming sees that HHH >>>>>>>>>>>>>>>>>> is not correctly programmed when it aborts one cycle >>>>>>>>>>>>>>>>>> before the simulation would end normally.
    The execution trace only shows that HHH is unable to >>>>>>>>>>>>>>>> complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>> simulate itself.
    It turns out that Olcott does not even understand this >>>>>>>>>>>>>> simple proof that HHH produces false negatives. HHH is >>>>>>>>>>>>>> unable to simulate itself up to the normal termination. >>>>>>>>>>>> So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {
              return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which >>>>>>>>>>>> he tries to hide with a lot of irrelevant words.
    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. halt and return the correct >>>>>>>> value.
    The directly executed HHH(DD) always halts and returns a correct >>>>>>> value as soon as it correctly determines that its input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according to >>>>>> spec, so does the inner, because it is the same. Therefore it can’t >>>>>> report „non-halting” and be correct. If the inner HHH doesn’t halt,
    it is not a decider.
    RSVP
    Hello?
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections.

    Here is the code point out the (nonexistent) error:
    https://github.com/plolcott/x86utm/blob/master/Halt7.c#L502
    Look at it.
    That is not an error.
    It is a verified fact that DD correctly simulated by HHH cannot
    possibly terminate normally. The line you referred to does not
    change that verified fact.
    You didn’t look at it.
    I did look at it and was pleased that you noticed the significance of
    this line-of-code. None-the-less it does not and cannot possibly alter
    the truism that DD simulated by HHH cannot possibly terminate
    normally.
    The significance of that line is that it changes the halting behaviour
    of HHH.
    So you have a very hard time staying laser focused on the actual exact
    point that this line-of-code:
    HAS ABSOLUTELY NOTHING TO DO WITH THE FACT THAT DD SIMULATED BY HHH
    CANNOT POSSIBLY TERMINATE NORMALLY.
    Sure. If you changed that line, it could.

    --
    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 11 18:44:05 2025
    On 2/11/25 9:38 AM, olcott wrote:
    On 2/11/2025 1:28 AM, joes wrote:
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott:

    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
             int main() {           return HHH(main); >>>>>>>>>>>>          }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>>>>>> tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>> incorrect.
    It is true as a verified fact and has been pointed out to Olcott >>>>>>>> many times, but he refuses to learn. So, again:
    It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot possibly >>>>>>> terminate normally.
    No, the verified fact is that the input can terminatie normally
    The directly executed main IS NOT THE INPUT TO HHH.

    This main is a program that includes all functions called directly and >>>> indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot possibly
    terminate normally.

    The input to HHH, which is main(), terminates. HHH does not simulate
    that.


    The directly executed main() is not the same instance of
    main() that is input to HHH and simulated by HHH.

    The you gave it the wrong input.


    The directly executed main() relies on HHH aborting
    the simulation of its input. HHH cannot rely on anything
    else aborting the simulation of its input.

    HHH needs to rely on the actual behavior of the progrma describe by the
    input.

    It just makes a wrong guess.

    Sorry, you are just proving your stupidity.


    Unless HHH does abort the simulation of its input HHH
    itself would never terminate normally. This by itself
    proves that that the input to HHH cannot possibly
    terminate normally.

    But it does, as that is how it was programmed.

    YOu are just showing you don't know what you are talking about.

    Since UTM(DD) will Halt, since the HHH that DD calls will abort and
    return 0. And UTM(DD) is BY DEFINITION a correct simulatipion, it just
    shows that HHH doesn't do a correct simulation.


    The directly executed main() *IS NOT* the input to HHH(main)
    and  *IS NOT* simulated by HHH.
    Do you not think you can pass a program to a simulator? What else do
    you think HHH is simulating.

    The security guard at the front door cannot even see the back door thus
    is not accountable for the back door.
    The guard should damn well be.

    HHH can see what its input does and that *IS ALL* that it is accountable >>> for.
    No. HHH can see what itself does. If it did something different to the
    input, that would not change what the input does.




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Feb 11 18:45:45 2025
    On 2/11/25 11:22 AM, olcott wrote:
    On 2/11/2025 10:10 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 15:38 schreef olcott:
    On 2/11/2025 1:28 AM, joes wrote:
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Am 05.02.2025 um 04:38 schrieb olcott: >>>>
    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
             int main() {           return HHH(main);
             }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>> which he
    tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>>>> incorrect.
    It is true as a verified fact and has been pointed out to Olcott >>>>>>>>>> many times, but he refuses to learn. So, again:
    It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot possibly >>>>>>>>> terminate normally.
    No, the verified fact is that the input can terminatie normally >>>>>>> The directly executed main IS NOT THE INPUT TO HHH.

    This main is a program that includes all functions called directly >>>>>> and
    indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot possibly >>>>> terminate normally.

    The input to HHH, which is main(), terminates. HHH does not simulate
    that.


    The directly executed main() is not the same instance of
    main() that is input to HHH and simulated by HHH.

    The directly executed main() relies on HHH aborting
    the simulation of its input. HHH cannot rely on anything
    else aborting the simulation of its input.

    The simulating HHH should rely on the simulated HHH to abort.

    That cannot possibly work. The executed HHH always sees at least one
    more full execution trace than any inner HHH ever sees.


    No, the "inner" HHH's behavior goes on forever until it reaches an end.

    What you mean is that HHH needs to decide on the behavior of the HHH
    before it gets to the point where it makes the decision.

    You just don't understand the behavior that HHH is supposed to be
    looking at.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Feb 11 18:49:47 2025
    On 2/11/25 11:19 AM, olcott wrote:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>
    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>>>>>> about DD's halting behaviour. All other methods (direct >>>>>>>>>>>>>>>>>> execution,
    simulation by a world class simulator, etc.) show that DD >>>>>>>>>>>>>>>>>> halts. But HHH fails to see it. Everyone with sufficient >>>>>>>>>>>>>>>>>> understanding of programming sees that HHH is not >>>>>>>>>>>>>>>>>> correctly programmed when it aborts one cycle before the >>>>>>>>>>>>>>>>>> simulation would end normally.
    The execution trace only shows that HHH is unable to >>>>>>>>>>>>>>>> complete its simulation, because HHH is unable to simulate >>>>>>>>>>>>>>>> itself.
    It turns out that Olcott does not even understand this simple >>>>>>>>>>>>>> proof that HHH produces false negatives. HHH is unable to >>>>>>>>>>>>>> simulate itself up to the normal termination.
    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
                int main() {
                  return HHH(main);
                }
    but he denies it.
    He lacks the ability to accept simple verified facts, which he >>>>>>>>>>>> tries to hide with a lot of irrelevant words.
    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. halt and return the correct >>>>>>>> value.
    The directly executed HHH(DD) always halts and returns a correct >>>>>>> value as soon as it correctly determines that its input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according to >>>>>> spec, so does the inner, because it is the same. Therefore it can’t >>>>>> report „non-halting” and be correct. If the inner HHH doesn’t halt,
    it is not a decider.
    RSVP
    Hello?


    I am not going to ever talk about that.

    Here is the code point out the (nonexistent) error:
    https://github.com/plolcott/x86utm/blob/master/Halt7.c#L502
    Look at it.
    That is not an error.
    It is a verified fact that DD correctly simulated by HHH cannot
    possibly terminate normally. The line you referred to does not change >>>>> that verified fact.
    You didn’t look at it.
    I did look at it and was pleased that you noticed the significance of
    this line-of-code. None-the-less it does not and cannot possibly alter
    the truism that DD simulated by HHH cannot possibly terminate normally.

    The significance of that line is that it changes the halting behaviour
    of HHH.


    So you have a very hard time staying laser focused
    on the actual exact point that this line-of-code:

    HAS ABSOLUTELY NOTHING TO DO WITH THE FACT THAT DD
    SIMULATED BY HHH CANNOT POSSIBLY TERMINATE NORMALLY.


    And neither does the problem.

    THe problem says/asks NOTHING about the simulation of the input, only
    the behavior of the program described when run.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Feb 11 18:48:39 2025
    On 2/11/25 9:46 AM, olcott wrote:
    On 2/11/2025 4:07 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 21:36 schreef olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote:
    Op 08.feb.2025 om 15:47 schreef olcott:
    On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote:
    On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This treatment does not typically >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> last very long and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> will be immediately followed by a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> riskier fourth line >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> of treatment that has an initial >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> success rate much higher >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> than its non progression mortality rate. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Halting problem solved ! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    The halting problem proof input does >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> specify non- halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behavior to its decider. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    https://www.researchgate.net/ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D

    LOOOOOOOOL

    Anyone that understands the C programming >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> language
    sufficiently well (thus not confused by >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the unreachable
    "if" statement) correctly understands >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD simulated >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> by HHH cannot possibly reach its own >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> return instruction. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    And anyone that understand the halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> problem knows that isn't the question >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> being asked. The quesiton you NEED to ask >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is will the program described by the input >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> halt when run?

    Since you start off with the wrong >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> question, you logic is just faulty. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Everyone that thinks my question is >>>>>>>>>>>>>>>>>>>>>>>>>>>>> incorrect is wrong.
    It has always been a mathematical mapping >>>>>>>>>>>>>>>>>>>>>>>>>>>>> from finite
    strings to behaviors. That people do not >>>>>>>>>>>>>>>>>>>>>>>>>>>>> comprehend this
    shows the shallowness of the depth of the >>>>>>>>>>>>>>>>>>>>>>>>>>>>> learned- by- rote
    (lack of) understanding. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    No, you are just incorreect as you don't >>>>>>>>>>>>>>>>>>>>>>>>>>>> know what you are talking about. >>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Yes, it is a mapping of the string to the >>>>>>>>>>>>>>>>>>>>>>>>>>>> behavior, and that mapping is DEFINED to be >>>>>>>>>>>>>>>>>>>>>>>>>>>> the halting behavior of the program the >>>>>>>>>>>>>>>>>>>>>>>>>>>> string describes.


    No this is incorrect. The input finite string >>>>>>>>>>>>>>>>>>>>>>>>>>> specifies
    (not merely describes) non halting behavior >>>>>>>>>>>>>>>>>>>>>>>>>>> to its decider.


    No, since the definition of "Halting Behavior" >>>>>>>>>>>>>>>>>>>>>>>>>> is the behavior of the progran being run. >>>>>>>>>>>>>>>>>>>>>>>>>>

    It may seem that way to people that have >>>>>>>>>>>>>>>>>>>>>>>>> learned- by- rote
    as their only basis. It is actually nothing >>>>>>>>>>>>>>>>>>>>>>>>> like that.

    No, that *IS* the definition.


    A termination analyzer computes the mapping from >>>>>>>>>>>>>>>>>>>>>>> finite
    strings to the actual behavior that these finite >>>>>>>>>>>>>>>>>>>>>>> strings
    specify. That this is not dead obvious to >>>>>>>>>>>>>>>>>>>>>>> everyone here
    merely proves that learned-by-rote does not >>>>>>>>>>>>>>>>>>>>>>> involve any
    actual comprehension.



    And the behavior the finite string specifies is >>>>>>>>>>>>>>>>>>>>>> the behavior of running the program. >>>>>>>>>>>>>>>>>>>>>
    That is verifiably factually incorrect. >>>>>>>>>>>>>>>>>>>>> The running program has a different execution trace >>>>>>>>>>>>>>>>>>>>> than the behavior that DD specifies to HHH. >>>>>>>>>>>>>>>>>>>>>

    If so, then it proves the failure of the simulation. >>>>>>>>>>>>>>>>>>>> The simulation aborts too soon on unsound grounds, >>>>>>>>>>>>>>>>>>>> one cycle before the normal termination of the program. >>>>>>>>>>>>>>>>>>>>

    This proves that you simply don't have sufficient >>>>>>>>>>>>>>>>>>> understanding of the C programming language. >>>>>>>>>>>>>>>>>>> DD simulated by HHH cannot possibly terminate normally >>>>>>>>>>>>>>>>>>> is a verified fact.


    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>>>>>> about DD's halting behaviour. All other methods >>>>>>>>>>>>>>>>>> (direct execution, simulation by a world class >>>>>>>>>>>>>>>>>> simulator, etc.) show that DD halts. But HHH fails to >>>>>>>>>>>>>>>>>> see it. Everyone with sufficient understanding of >>>>>>>>>>>>>>>>>> programming sees that HHH is not correctly programmed >>>>>>>>>>>>>>>>>> when it aborts one cycle before the simulation would >>>>>>>>>>>>>>>>>> end normally.

    typedef void (*ptr)();
    int HHH(ptr P);

    int DD()
    {
       int Halt_Status = HHH(DD);
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    int main()
    {
       HHH(DD);
    }

    You lack the ability to do the execution trace >>>>>>>>>>>>>>>>> of HHH simulating DD calling HHH(DD) simulating DD... >>>>>>>>>>>>>>>>
    The execution trace only shows that HHH is unable to >>>>>>>>>>>>>>>> complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>> simulate itself.


    https://github.com/plolcott/x86utm/blob/master/Halt7.c >>>>>>>>>>>>>>> The above code proves that HHH does simulate itself >>>>>>>>>>>>>>> simulating DD.

    That you can't understand this code proves that you lack the >>>>>>>>>>>>>>> technical basis to review my work.


    It turns out that Olcott does not even understand this >>>>>>>>>>>>>> simple proof that HHH produces false negatives. HHH is >>>>>>>>>>>>>> unable to simulate itself up to the normal termination. >>>>>>>>>>>>>
    If you try to explain your view in terms of a line-by-line >>>>>>>>>>>>> execution trace of DD simulated by HHH everyone will see that >>>>>>>>>>>>> your claim has no actual basis what-so-ever and is merely >>>>>>>>>>>>> utterly baseless rhetoric totally bereft of any supporting >>>>>>>>>>>>> reasoning.


    So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {           return HHH(main); >>>>>>>>>>>>         }
    but he denies it.
    He lacks the ability to accept simple verified facts, which >>>>>>>>>>>> he tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>> simulated by HHH until its normal termination.

    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>> correctly.

    If this was true then you could point out exactly where HHH
    is incorrect.

    It is true as a verified fact and has been pointed out to Olcott >>>>>>>> many times, but he refuses to learn. So, again:

    It is a verified fact that main halts,

    It is a verified fact that the input to HHH(main) cannot
    possibly terminate normally.

    No, the verified fact is that the input can terminatie normally

    The directly executed main IS NOT THE INPUT TO HHH.



    This main is a program that includes all functions called directly
    and indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH
    cannot possibly terminate normally.

    Which proves that HHH fails, because the direct execution and many
    other simulators do execute it up to normal termination.
    This makes it a verified fact that HHH fails.

    The code itself conclusively proves that I and the code are
    both correct. That you disagree with this code is ridiculous.

    That you can come up with an example that is more difficult
    for you to understand is not useful.

    DD simulated by HHH cannot possibly terminate normally. https://www.researchgate.net/ publication/369971402_Simulating_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D






    No, the code conclusivly proves that DD() will Halt, and thus HHH(DD)
    should return 1, but it returns 0, so it is wrong.

    It also proves that you are just ignorantly stupid abpout what you are
    talking about, and are so stupid you can't see your error.

    And, you have admitted that this stupidity is self-inflicted, you don't
    want to learn what the requirements are, as then you would need to
    follow them per your complatint of "Learn-by-Rote", and your replace
    that with, Never Learned, so don't knpw or understand, because I made
    myself stupid.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Thu Feb 13 09:16:00 2025
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All other >>>>>>>>>>>>>>>>>>>> methods (direct execution,
    simulation by a world class simulator, etc.) show >>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see it. Everyone with >>>>>>>>>>>>>>>>>>>> sufficient understanding of programming sees that HHH >>>>>>>>>>>>>>>>>>>> is not correctly programmed when it aborts one cycle >>>>>>>>>>>>>>>>>>>> before the simulation would end normally. >>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is unable to >>>>>>>>>>>>>>>>>> complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>>>> simulate itself.
    It turns out that Olcott does not even understand this >>>>>>>>>>>>>>>> simple proof that HHH produces false negatives. HHH is >>>>>>>>>>>>>>>> unable to simulate itself up to the normal termination. >>>>>>>>>>>>>> So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
            int main() {
              return HHH(main);
            }
    but he denies it.
    He lacks the ability to accept simple verified facts, which >>>>>>>>>>>>>> he tries to hide with a lot of irrelevant words.
    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. halt and return the
    correct value.
    The directly executed HHH(DD) always halts and returns a correct >>>>>>>>> value as soon as it correctly determines that its input cannot >>>>>>>>> possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according >>>>>>>> to spec, so does the inner, because it is the same. Therefore it >>>>>>>> can’t report „non-halting” and be correct. If the inner HHH >>>>>>>> doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections.
    I reject infinite deflection away from the point. The absolute
    single-mined focus point is that DD correctly simulated by HHH cannot possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next month
    will kill me and this treatment is my only good chance I will totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.

    --
    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 Thu Feb 13 11:53:12 2025
    Op 13.feb.2025 om 05:12 schreef olcott:
    On 2/11/2025 10:44 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 17:22 schreef olcott:
    On 2/11/2025 10:10 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 15:38 schreef olcott:
    On 2/11/2025 1:28 AM, joes wrote:
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:

    So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>          int main() {           return HHH(main);
             }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>>>> which he
    tries to hide with a lot of irrelevant words.

    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>>>>>> incorrect.
    It is true as a verified fact and has been pointed out to >>>>>>>>>>>> Olcott
    many times, but he refuses to learn. So, again:
    It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot >>>>>>>>>>> possibly
    terminate normally.
    No, the verified fact is that the input can terminatie normally >>>>>>>>> The directly executed main IS NOT THE INPUT TO HHH.

    This main is a program that includes all functions called
    directly and
    indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot
    possibly
    terminate normally.

    The input to HHH, which is main(), terminates. HHH does not
    simulate that.


    The directly executed main() is not the same instance of
    main() that is input to HHH and simulated by HHH.

    The directly executed main() relies on HHH aborting
    the simulation of its input. HHH cannot rely on anything
    else aborting the simulation of its input.

    The simulating HHH should rely on the simulated HHH to abort.

    That cannot possibly work. The executed HHH always sees at least one
    more full execution trace than any inner HHH ever sees.


    Indeed, that is what I said, but Olcott deleted it in the citation.
    HHH cannot do what it should do. So, he proves the halting theorem.

    If the sentence it false it does not become true in some greater
    context.

    Indeed and since it is false that the simulated HHH would not abort, it
    makes no sense to claim that the simulating HHH must abort.
    The sentence that the finite string describe a non-halting program is
    false, as is proven by direct execution and many simulators. It does not
    become true in some greater context of HHH.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Thu Feb 13 07:17:47 2025
    On 2/12/25 11:18 PM, olcott wrote:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 07:10 schreef olcott:
    On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Am 05.02.2025 um 16:11 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Am 05.02.2025 um 04:38 schrieb olcott: >>>>>>>>>>
    Which proves that HHH fails to make a correct decision >>>>>>>>>>>>>>>>>>>> about DD's halting behaviour. All other methods (direct >>>>>>>>>>>>>>>>>>>> execution,
    simulation by a world class simulator, etc.) show that >>>>>>>>>>>>>>>>>>>> DD halts. But HHH fails to see it. Everyone with >>>>>>>>>>>>>>>>>>>> sufficient understanding of programming sees that HHH >>>>>>>>>>>>>>>>>>>> is not correctly programmed when it aborts one cycle >>>>>>>>>>>>>>>>>>>> before the simulation would end normally. >>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is unable to >>>>>>>>>>>>>>>>>> complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>>>> simulate itself.
    It turns out that Olcott does not even understand this >>>>>>>>>>>>>>>> simple proof that HHH produces false negatives. HHH is >>>>>>>>>>>>>>>> unable to simulate itself up to the normal termination. >>>>>>>>>>>>>> So, in other words, Olcott denies verified facts.
    HHH generates false negatives, as is verified in
                 int main() {
                   return HHH(main);
                 }
    but he denies it.
    He lacks the ability to accept simple verified facts, which >>>>>>>>>>>>>> he tries to hide with a lot of irrelevant words.
    It is a verified fact that main cannot possibly be correctly >>>>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. halt and return the correct >>>>>>>>>> value.
    The directly executed HHH(DD) always halts and returns a correct >>>>>>>>> value as soon as it correctly determines that its input cannot >>>>>>>>> possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according to >>>>>>>> spec, so does the inner, because it is the same. Therefore it can’t >>>>>>>> report „non-halting” and be correct. If the inner HHH doesn’t halt,
    it is not a decider.
    RSVP
    Hello?
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections.


    I reject infinite deflection away from the point.
    The absolute single-mined focus point is that
    DD correctly simulated by HHH cannot possible
    terminate normally.


    No, you deflect any statement that shows you are wrong, because your
    tiny mind can't handle it.

    Your problem is that you base your logic on contradictions and lies.

    Here the problem is that since your HHH doesn't correctly simulate its
    input, it doesn't matter what the not being used variant of the program
    would do, as we aren't using it.

    That you confuse the to, just proves you don't know the basic
    terminology of the system, and are too stupid to see your stupidity.


    Since there is a 5% chance that the treatment I will
    have next month will kill me and this treatment is
    my only good chance I will totally ignore anything
    that diverges from the point.


    No, you ignore and truth that shows that you are wrong, because you
    don't actually believe in the truth.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Thu Feb 13 15:47:42 2025
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All other >>>>>>>>>>>>>>>>>>>>>> methods (direct execution,
    simulation by a world class simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see it. Everyone with >>>>>>>>>>>>>>>>>>>>>> sufficient understanding of programming sees that HHH >>>>>>>>>>>>>>>>>>>>>> is not correctly programmed when it aborts one cycle >>>>>>>>>>>>>>>>>>>>>> before the simulation would end normally. >>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is unable to >>>>>>>>>>>>>>>>>>>> complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>>>>>> simulate itself.
    It turns out that Olcott does not even understand this >>>>>>>>>>>>>>>>>> simple proof that HHH produces false negatives. HHH is >>>>>>>>>>>>>>>>>> unable to simulate itself up to the normal termination. >>>>>>>>>>>>>>>> So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>               int main() {
                    return HHH(main); >>>>>>>>>>>>>>>>               }
    but he denies it.
    He lacks the ability to accept simple verified facts, which >>>>>>>>>>>>>>>> he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>> It is a verified fact that main cannot possibly be correctly >>>>>>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. halt and return the >>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts and returns a correct >>>>>>>>>>> value as soon as it correctly determines that its input cannot >>>>>>>>>>> possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according >>>>>>>>>> to spec, so does the inner, because it is the same. Therefore it >>>>>>>>>> can’t report „non-halting” and be correct. If the inner HHH >>>>>>>>>> doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections.
    I reject infinite deflection away from the point. The absolute
    single-mined focus point is that DD correctly simulated by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next month
    will kill me and this treatment is my only good chance I will totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows
    that DD correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot
    properly decide about its input, because it must abort the correct
    simulation before it sees that the correct simulation terminates normally.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Thu Feb 13 18:41:42 2025
    On 2/13/25 7:31 AM, olcott wrote:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 16:18 schreef olcott:
    On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All other >>>>>>>>>>>>>>>>>>>>>> methods (direct execution,
    simulation by a world class simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see it. Everyone with >>>>>>>>>>>>>>>>>>>>>> sufficient understanding of programming sees that HHH >>>>>>>>>>>>>>>>>>>>>> is not correctly programmed when it aborts one cycle >>>>>>>>>>>>>>>>>>>>>> before the simulation would end normally. >>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is unable to >>>>>>>>>>>>>>>>>>>> complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>>>>>> simulate itself.
    It turns out that Olcott does not even understand this >>>>>>>>>>>>>>>>>> simple proof that HHH produces false negatives. HHH is >>>>>>>>>>>>>>>>>> unable to simulate itself up to the normal termination. >>>>>>>>>>>>>>>> So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>               int main() {
                    return HHH(main); >>>>>>>>>>>>>>>>               }
    but he denies it.
    He lacks the ability to accept simple verified facts, which >>>>>>>>>>>>>>>> he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>> It is a verified fact that main cannot possibly be correctly >>>>>>>>>>>>>>> simulated by HHH until its normal termination.
    Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>>>>>> correctly.
    If this was true then you could point out exactly where HHH is >>>>>>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. halt and return the >>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts and returns a correct >>>>>>>>>>> value as soon as it correctly determines that its input cannot >>>>>>>>>>> possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts according >>>>>>>>>> to spec, so does the inner, because it is the same. Therefore it >>>>>>>>>> can’t report „non-halting” and be correct. If the inner HHH >>>>>>>>>> doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections.
    I reject infinite deflection away from the point. The absolute
    single-mined focus point is that DD correctly simulated by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next month
    will kill me and this treatment is my only good chance I will totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows
    that DD correctly simulated by HHH cannot possibly terminate normally.


    No, they know that your HHH doesn;t correct simulate its input.

    Also, per your definitions, NEITHER HHH or DD qualify as a "program" per Computation Theory, so your whole claim is a lie. (Neither of them, as
    you have specified them is a pure function of just its input).

    Sorry, you are just proving your are nothing but an ignorant lying fraud
    that doesn't care about the truth.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Thu Feb 13 22:15:41 2025
    On 2/13/25 7:09 PM, olcott wrote:
    On 2/13/2025 4:53 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 05:12 schreef olcott:
    On 2/11/2025 10:44 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 17:22 schreef olcott:
    On 2/11/2025 10:10 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 15:38 schreef olcott:
    On 2/11/2025 1:28 AM, joes wrote:
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:

    So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>          int main() {           return HHH(main);
             }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>>>>>> which he
    tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>>
    It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>> correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>>>>>>>> correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>> HHH is
    incorrect.
    It is true as a verified fact and has been pointed out to >>>>>>>>>>>>>> Olcott
    many times, but he refuses to learn. So, again:
    It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot >>>>>>>>>>>>> possibly
    terminate normally.
    No, the verified fact is that the input can terminatie normally >>>>>>>>>>> The directly executed main IS NOT THE INPUT TO HHH.

    This main is a program that includes all functions called
    directly and
    indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot >>>>>>>>> possibly
    terminate normally.

    The input to HHH, which is main(), terminates. HHH does not
    simulate that.


    The directly executed main() is not the same instance of
    main() that is input to HHH and simulated by HHH.

    The directly executed main() relies on HHH aborting
    the simulation of its input. HHH cannot rely on anything
    else aborting the simulation of its input.

    The simulating HHH should rely on the simulated HHH to abort.

    That cannot possibly work. The executed HHH always sees at least one >>>>> more full execution trace than any inner HHH ever sees.


    Indeed, that is what I said, but Olcott deleted it in the citation.
    HHH cannot do what it should do. So, he proves the halting theorem.

    If the sentence it false it does not become true in some greater
    context.

    Indeed and since it is false that the simulated HHH would not abort,

    This is simply beyond your skill level.
    Since each HHH is exactly the same unless the first
    one aborts none of them do.



    But the first one DOES abort, as that is how it was defined to be.

    And thus, the one that DD calls aborts.

    Remember, the problem statement for a Halt Decider says NOTHING about a
    need for the decider to simulate, and the results of any simulation it
    does is irrelevent. The only thing that matters is what the actual
    program the input represents does.

    Since the program you talk about as the input halts, that is the only
    right answer.

    The fact that you input doesn't fully specify that program, just means
    you have proved yourself too stupid to understand the problem.

    What you try to give as the input, isn't the representation of an actual program, as it is missing information, and that you don't understand
    that just proves your stupidity.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Fri Feb 14 09:36:59 2025
    Am Thu, 13 Feb 2025 18:12:52 -0600 schrieb olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote:

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution,
    simulation by a world class simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see it. Everyone >>>>>>>>>>>>>>>>>>>>>>>> with sufficient understanding of programming sees >>>>>>>>>>>>>>>>>>>>>>>> that HHH is not correctly programmed when it >>>>>>>>>>>>>>>>>>>>>>>> aborts one cycle before the simulation would end >>>>>>>>>>>>>>>>>>>>>>>> normally.
    The execution trace only shows that HHH is unable >>>>>>>>>>>>>>>>>>>>>> to complete its simulation, because HHH is unable >>>>>>>>>>>>>>>>>>>>>> to simulate itself.
    It turns out that Olcott does not even understand >>>>>>>>>>>>>>>>>>>> this simple proof that HHH produces false negatives. >>>>>>>>>>>>>>>>>>>> HHH is unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified facts. HHH >>>>>>>>>>>>>>>>>> generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>               int main() {
                    return HHH(main); >>>>>>>>>>>>>>>>>>               }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>>>>>> which he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>> It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>> correctly simulated by HHH until its normal termination. >>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to simulate >>>>>>>>>>>>>>>> itself correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>> HHH is incorrect.
    HHH is supposed to be a decider, i.e. halt and return the >>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts and returns a >>>>>>>>>>>>> correct value as soon as it correctly determines that its >>>>>>>>>>>>> input cannot possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts >>>>>>>>>>>> according to spec, so does the inner, because it is the same. >>>>>>>>>>>> Therefore it can’t report „non-halting” and be correct. If >>>>>>>>>>>> the inner HHH doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections. >>>>> I reject infinite deflection away from the point. The absolute
    single-mined focus point is that DD correctly simulated by HHH
    cannot possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next month >>>>> will kill me and this treatment is my only good chance I will
    totally ignore anything that diverges from the point.
    Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD
    correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot
    properly decide about its input, because  it must abort the correct
    simulation before it sees that the correct simulation terminates
    normally.

    The correct simulation is only the one that it sees by definition. it
    maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.
    All of the people that think it should map the behavior of a non-input
    have always been wrong.
    What is the non-input?
    The input is DD, and its behaviour is that it halts.
    HHH’s simulation is not correct by definition.

    --
    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 Fri Feb 14 10:53:11 2025
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott:
    On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 18:00 schreef olcott:
    On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution,
    simulation by a world class simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see it. Everyone >>>>>>>>>>>>>>>>>>>>>>>> with
    sufficient understanding of programming sees >>>>>>>>>>>>>>>>>>>>>>>> that HHH
    is not correctly programmed when it aborts one >>>>>>>>>>>>>>>>>>>>>>>> cycle
    before the simulation would end normally. >>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is unable to >>>>>>>>>>>>>>>>>>>>>> complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>>>>>>>> simulate itself.
    It turns out that Olcott does not even understand this >>>>>>>>>>>>>>>>>>>> simple proof that HHH produces false negatives. HHH is >>>>>>>>>>>>>>>>>>>> unable to simulate itself up to the normal termination. >>>>>>>>>>>>>>>>>> So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>               int main() {
                    return HHH(main); >>>>>>>>>>>>>>>>>>               }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>>>>>> which
    he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>> It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>> correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to simulate itself >>>>>>>>>>>>>>>> correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>> HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and return the >>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts and returns a >>>>>>>>>>>>> correct
    value as soon as it correctly determines that its input cannot >>>>>>>>>>>>> possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts >>>>>>>>>>>> according
    to spec, so does the inner, because it is the same.
    Therefore it
    can’t report „non-halting” and be correct. If the inner HHH >>>>>>>>>>>> doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections. >>>>> I reject infinite deflection away from the point. The absolute
    single-mined focus point is that DD correctly simulated by HHH cannot >>>>> possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next month >>>>> will kill me and this treatment is my only good chance I will totally >>>>> ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows
    that DD correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot
    properly decide about its input, because  it must abort the correct
    simulation before it sees that the correct simulation terminates
    normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.

    If I close my eyes, so that I do not see the accident, I cannot claim
    that the accident did not happen. That is the reasoning of a 2 years old
    child.
    Similarly, when HHH aborts the simulation, it closes its eyes for what
    happens in a correct simulation of DD.

    All of the people that think it should map the behavior
    of a non-input have always been wrong.


    It is a verified fact that the finite string given to HHH describes a
    program that halts.
    But olcott claims he does not use this input, but a non-input, a
    different program, as input to HHH. He does not understand that HHH
    should decide about the input described by the finite string that has
    been proven to halt.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Fri Feb 14 12:53:46 2025
    Am Thu, 13 Feb 2025 22:20:32 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:09 PM, olcott wrote:
    On 2/13/2025 4:53 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 05:12 schreef olcott:
    On 2/11/2025 10:44 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 17:22 schreef olcott:
    On 2/11/2025 10:10 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 15:38 schreef olcott:
    On 2/11/2025 1:28 AM, joes wrote:
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote:

    So, in other words, Olcott denies verified facts. HHH >>>>>>>>>>>>>>>>>>>> generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>          int main() {           return >>>>>>>>>>>>>>>>>>>>          HHH(main);
             }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>>>>>>>> which he tries to hide with a lot of irrelevant >>>>>>>>>>>>>>>>>>>> words.

    It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>>>> correctly simulated by HHH until its normal >>>>>>>>>>>>>>>>>>> termination.
    Indeed, which proves that HHH is unable to simulate >>>>>>>>>>>>>>>>>> itself correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>>>> HHH is incorrect.
    It is true as a verified fact and has been pointed out to >>>>>>>>>>>>>>>> Olcott many times, but he refuses to learn. So, again: >>>>>>>>>>>>>>>> It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot >>>>>>>>>>>>>>> possibly terminate normally.
    No, the verified fact is that the input can terminatie >>>>>>>>>>>>>> normally
    The directly executed main IS NOT THE INPUT TO HHH.

    This main is a program that includes all functions called >>>>>>>>>>>> directly and indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot >>>>>>>>>>> possibly terminate normally.

    The input to HHH, which is main(), terminates. HHH does not >>>>>>>>>> simulate that.


    The directly executed main() is not the same instance of main() >>>>>>>>> that is input to HHH and simulated by HHH.

    The directly executed main() relies on HHH aborting the
    simulation of its input. HHH cannot rely on anything else
    aborting the simulation of its input.

    The simulating HHH should rely on the simulated HHH to abort.

    That cannot possibly work. The executed HHH always sees at least >>>>>>> one more full execution trace than any inner HHH ever sees.


    Indeed, that is what I said, but Olcott deleted it in the citation. >>>>>> HHH cannot do what it should do. So, he proves the halting theorem. >>>>>
    If the sentence it false it does not become true in some greater
    context.

    Indeed and since it is false that the simulated HHH would not abort,

    This is simply beyond your skill level.
    Since each HHH is exactly the same unless the first one aborts none of
    them do.

    But the first one DOES abort, as that is how it was defined to be.

    And thus, the one that DD calls aborts.

    A program that is no longer being simulated DOES NOTHING

    Hey, let me prove all programs are no-ops, by NOT SIMULATING THEM MWAHAHA

    --
    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 joes@21:1/5 to All on Fri Feb 14 12:58:07 2025
    Am Fri, 14 Feb 2025 06:42:29 -0600 schrieb olcott:
    On 2/14/2025 3:36 AM, joes wrote:
    Am Thu, 13 Feb 2025 18:12:52 -0600 schrieb olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/6/25 10:02 PM, olcott wrote:

    Since there is a 5% chance that the treatment I will have next
    month will kill me and this treatment is my only good chance I
    will totally ignore anything that diverges from the point.
    Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD
    correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot
    properly decide about its input, because  it must abort the correct
    simulation before it sees that the correct simulation terminates
    normally.

    The correct simulation is only the one that it sees by definition. it
    maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.
    All of the people that think it should map the behavior of a non-input
    have always been wrong.
    What is the non-input?

    int main()
    {
    DD(); // Is not an input to HHH
    HHH(DD) // Is an input to HHH
    {
    Oh, but we’re not interested in the behaviour of HHH(HHH(DD)).

    The input is DD, and its behaviour is that it halts.
    HHH’s simulation is not correct by definition.
    --
    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 joes@21:1/5 to All on Fri Feb 14 13:02:17 2025
    Am Fri, 14 Feb 2025 06:48:31 -0600 schrieb olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote:


    Since there is a 5% chance that the treatment I will have next
    month will kill me and this treatment is my only good chance I
    will totally ignore anything that diverges from the point.
    Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD
    correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot
    properly decide about its input, because  it must abort the correct
    simulation before it sees that the correct simulation terminates
    normally.

    The correct simulation is only the one that it sees by definition. it
    maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.

    If I close my eyes, so that I do not see the accident, I cannot claim
    that the accident did not happen. That is the reasoning of a 2 years
    old child.
    Similarly, when HHH aborts the simulation, it closes its eyes for what
    happens in a correct simulation of DD.
    HHH(DD) maps the finite string input of DD to the behavior that it
    specifies.
    DD specifies halting behaviour, by only calling a „decider”, a program purported to halt.

    This behavior does include DD repeatedly calling HHH(DD) in
    recursive simulation that that cannot possibly terminate normally.
    If DD doesn’t halt, the outerHHH can’t be able to report on it;
    if the outer HHH halted, the inner one would do the same, because
    it IS the same.

    All of the people that think it should map the behavior of a non-input
    have always been wrong.
    It is a verified fact that the finite string given to HHH describes a
    program that halts.
    But olcott claims he does not use this input, but a non-input, a
    different program, as input to HHH. He does not understand that HHH
    should decide about the input described by the finite string that has
    been proven to halt.
    QFT

    --
    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 Fri Feb 14 08:25:41 2025
    On 2/13/25 11:20 PM, olcott wrote:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:09 PM, olcott wrote:
    On 2/13/2025 4:53 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 05:12 schreef olcott:
    On 2/11/2025 10:44 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 17:22 schreef olcott:
    On 2/11/2025 10:10 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 15:38 schreef olcott:
    On 2/11/2025 1:28 AM, joes wrote:
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 16:11 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/5/2025 1:44 AM, Bonita >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Montero wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am 05.02.2025 um 04:38 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:

    So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>          int main() {           return HHH(main);
             }
    but he denies it.
    He lacks the ability to accept simple verified >>>>>>>>>>>>>>>>>>>> facts, which he
    tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>>>>
    It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>>>> correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to simulate >>>>>>>>>>>>>>>>>> itself
    correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>>>> HHH is
    incorrect.
    It is true as a verified fact and has been pointed out >>>>>>>>>>>>>>>> to Olcott
    many times, but he refuses to learn. So, again: >>>>>>>>>>>>>>>> It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot >>>>>>>>>>>>>>> possibly
    terminate normally.
    No, the verified fact is that the input can terminatie >>>>>>>>>>>>>> normally
    The directly executed main IS NOT THE INPUT TO HHH.

    This main is a program that includes all functions called >>>>>>>>>>>> directly and
    indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot >>>>>>>>>>> possibly
    terminate normally.

    The input to HHH, which is main(), terminates. HHH does not >>>>>>>>>> simulate that.


    The directly executed main() is not the same instance of
    main() that is input to HHH and simulated by HHH.

    The directly executed main() relies on HHH aborting
    the simulation of its input. HHH cannot rely on anything
    else aborting the simulation of its input.

    The simulating HHH should rely on the simulated HHH to abort.

    That cannot possibly work. The executed HHH always sees at least one >>>>>>> more full execution trace than any inner HHH ever sees.


    Indeed, that is what I said, but Olcott deleted it in the citation. >>>>>> HHH cannot do what it should do. So, he proves the halting theorem. >>>>>
    If the sentence it false it does not become true in some greater
    context.

    Indeed and since it is false that the simulated HHH would not abort,

    This is simply beyond your skill level.
    Since each HHH is exactly the same unless the first
    one aborts none of them do.



    But the first one DOES abort, as that is how it was defined to be.

    And thus, the one that DD calls aborts.


    A program that is no longer being simulated DOES NOTHING


    A program's behavior is not based on it actually being run, but is a
    fixed property of its design.

    We aren't talking about "Program instances", we are talking about
    behavior of "Programs".

    That is the exact configuration of the instructions so defined, that is
    a program.

    "Partial Simulations" do not define the behavior of programs, only
    actual running or full simulation.

    You are just showing you fail to understand what you are talking about
    an just making up lies to cover up that fact.

    Sorry, you just proved your ignorance.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Fri Feb 14 08:35:51 2025
    On 2/14/25 7:42 AM, olcott wrote:
    On 2/14/2025 3:36 AM, joes wrote:
    Am Thu, 13 Feb 2025 18:12:52 -0600 schrieb olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote:

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see it. Everyone >>>>>>>>>>>>>>>>>>>>>>>>>> with sufficient understanding of programming sees >>>>>>>>>>>>>>>>>>>>>>>>>> that HHH is not correctly programmed when it >>>>>>>>>>>>>>>>>>>>>>>>>> aborts one cycle before the simulation would end >>>>>>>>>>>>>>>>>>>>>>>>>> normally.
    The execution trace only shows that HHH is unable >>>>>>>>>>>>>>>>>>>>>>>> to complete its simulation, because HHH is unable >>>>>>>>>>>>>>>>>>>>>>>> to simulate itself.
    It turns out that Olcott does not even understand >>>>>>>>>>>>>>>>>>>>>> this simple proof that HHH produces false negatives. >>>>>>>>>>>>>>>>>>>>>> HHH is unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified facts. HHH >>>>>>>>>>>>>>>>>>>> generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>                int main() { >>>>>>>>>>>>>>>>>>>>                  return HHH(main); >>>>>>>>>>>>>>>>>>>>                }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>>>>>>>> which he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>>>> correctly simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to simulate >>>>>>>>>>>>>>>>>> itself correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>>>> HHH is incorrect.
    HHH is supposed to be a decider, i.e. halt and return the >>>>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts and returns a >>>>>>>>>>>>>>> correct value as soon as it correctly determines that its >>>>>>>>>>>>>>> input cannot possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts >>>>>>>>>>>>>> according to spec, so does the inner, because it is the same. >>>>>>>>>>>>>> Therefore it can’t report „non-halting” and be correct. If >>>>>>>>>>>>>> the inner HHH doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections. >>>>>>> I reject infinite deflection away from the point. The absolute
    single-mined focus point is that DD correctly simulated by HHH
    cannot possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next month >>>>>>> will kill me and this treatment is my only good chance I will
    totally ignore anything that diverges from the point.
    Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD
    correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot
    properly decide about its input, because  it must abort the correct
    simulation before it sees that the correct simulation terminates
    normally.

    The correct simulation is only the one that it sees by definition. it
    maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.
    All of the people that think it should map the behavior of a non-input
    have always been wrong.
    What is the non-input?

    int main()
    {
      DD();    // Is not an input to HHH
      HHH(DD)  // Is an input to HHH
    {


    And the input needs to specify to HHH that it needs to respond about
    what you called "Not an input".

    Your problem is you don't know what you are talking about, a d just lie
    to everyone, even yourself

    The input is DD, and its behaviour is that it halts.
    HHH’s simulation is not correct by definition.




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Fri Feb 14 14:55:05 2025
    Op 14.feb.2025 om 13:42 schreef olcott:
    On 2/14/2025 3:36 AM, joes wrote:
    Am Thu, 13 Feb 2025 18:12:52 -0600 schrieb olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote:

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see it. Everyone >>>>>>>>>>>>>>>>>>>>>>>>>> with sufficient understanding of programming sees >>>>>>>>>>>>>>>>>>>>>>>>>> that HHH is not correctly programmed when it >>>>>>>>>>>>>>>>>>>>>>>>>> aborts one cycle before the simulation would end >>>>>>>>>>>>>>>>>>>>>>>>>> normally.
    The execution trace only shows that HHH is unable >>>>>>>>>>>>>>>>>>>>>>>> to complete its simulation, because HHH is unable >>>>>>>>>>>>>>>>>>>>>>>> to simulate itself.
    It turns out that Olcott does not even understand >>>>>>>>>>>>>>>>>>>>>> this simple proof that HHH produces false negatives. >>>>>>>>>>>>>>>>>>>>>> HHH is unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified facts. HHH >>>>>>>>>>>>>>>>>>>> generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>                int main() { >>>>>>>>>>>>>>>>>>>>                  return HHH(main); >>>>>>>>>>>>>>>>>>>>                }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>>>>>>>> which he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>>>> correctly simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to simulate >>>>>>>>>>>>>>>>>> itself correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>>>> HHH is incorrect.
    HHH is supposed to be a decider, i.e. halt and return the >>>>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts and returns a >>>>>>>>>>>>>>> correct value as soon as it correctly determines that its >>>>>>>>>>>>>>> input cannot possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts >>>>>>>>>>>>>> according to spec, so does the inner, because it is the same. >>>>>>>>>>>>>> Therefore it can’t report „non-halting” and be correct. If >>>>>>>>>>>>>> the inner HHH doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections. >>>>>>> I reject infinite deflection away from the point. The absolute
    single-mined focus point is that DD correctly simulated by HHH
    cannot possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next month >>>>>>> will kill me and this treatment is my only good chance I will
    totally ignore anything that diverges from the point.
    Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD
    correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot
    properly decide about its input, because  it must abort the correct
    simulation before it sees that the correct simulation terminates
    normally.

    The correct simulation is only the one that it sees by definition. it
    maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.
    All of the people that think it should map the behavior of a non-input
    have always been wrong.
    What is the non-input?

    int main()
    {
      DD();    // Is not an input to HHH
      HHH(DD)  // Is an input to HHH
    {

    The input is DD, and its behaviour is that it halts.
    HHH’s simulation is not correct by definition.




    What is the difference in the finite string that describes the first DD
    and the finite string that describes the second DD?
    You do not show a definition if DD, but there can be only one DD, so
    there is only one finite string which can have only one behaviour.
    That is the behaviour HHH should decide about. If HHH changes the
    behaviour of DD, then HHH is not a decider.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Fri Feb 14 15:01:29 2025
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott:
    On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:04 schreef olcott:
    On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita Montero >>>>>>
    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see it. >>>>>>>>>>>>>>>>>>>>>>>>>> Everyone with
    sufficient understanding of programming sees >>>>>>>>>>>>>>>>>>>>>>>>>> that HHH
    is not correctly programmed when it aborts one >>>>>>>>>>>>>>>>>>>>>>>>>> cycle
    before the simulation would end normally. >>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is >>>>>>>>>>>>>>>>>>>>>>>> unable to
    complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>> simulate itself.
    It turns out that Olcott does not even understand >>>>>>>>>>>>>>>>>>>>>> this
    simple proof that HHH produces false negatives. >>>>>>>>>>>>>>>>>>>>>> HHH is
    unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>               int main() { >>>>>>>>>>>>>>>>>>>>                 return HHH(main); >>>>>>>>>>>>>>>>>>>>               }
    but he denies it.
    He lacks the ability to accept simple verified >>>>>>>>>>>>>>>>>>>> facts, which
    he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>>>> correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to simulate >>>>>>>>>>>>>>>>>> itself
    correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>>>> HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and return the >>>>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts and returns a >>>>>>>>>>>>>>> correct
    value as soon as it correctly determines that its input >>>>>>>>>>>>>>> cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts >>>>>>>>>>>>>> according
    to spec, so does the inner, because it is the same. >>>>>>>>>>>>>> Therefore it
    can’t report „non-halting” and be correct. If the inner HHH
    doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject corrections. >>>>>>> I reject infinite deflection away from the point. The absolute
    single-mined focus point is that DD correctly simulated by HHH
    cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next month >>>>>>> will kill me and this treatment is my only good chance I will
    totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows
    that DD correctly simulated by HHH cannot possibly terminate normally. >>>>
    Indeed, which shows the limitation of HHH which makes that it cannot
    properly decide about its input, because  it must abort the correct
    simulation before it sees that the correct simulation terminates
    normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.

    If I close my eyes, so that I do not see the accident, I cannot claim
    that the accident did not happen. That is the reasoning of a 2 years
    old child.

    HHH(DD) maps the finite string input of DD to the behavior that it
    specifies. This behavior does include DD repeatedly calling HHH(DD)
    in recursive simulation that that cannot possibly terminate normally.

    Olcott is again dreaming of a HHH that does not abort. Dreams are no
    substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes and does not
    see that the simulated HHH also aborts so that the program terminates
    normally.

    Indeed, a simulator can not simulate itself up to a normal termination,
    but that is a limitation/failure of the simulator, not of the program
    being simulated.

    By saying that HHH cannot possibly terminate normally the simulation of
    a halting program, olcott adds evidence for the halting theorem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Fri Feb 14 19:38:29 2025
    On 2/14/25 6:30 PM, olcott wrote:
    On 2/14/2025 6:58 AM, joes wrote:
    Am Fri, 14 Feb 2025 06:42:29 -0600 schrieb olcott:
    On 2/14/2025 3:36 AM, joes wrote:
    Am Thu, 13 Feb 2025 18:12:52 -0600 schrieb olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/6/25 10:02 PM, olcott wrote:

    Since there is a 5% chance that the treatment I will have next >>>>>>>>> month will kill me and this treatment is my only good chance I >>>>>>>>> will totally ignore anything that diverges from the point.
    Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD >>>>>>> correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot >>>>>> properly decide about its input, because  it must abort the correct >>>>>> simulation before it sees that the correct simulation terminates
    normally.

    The correct simulation is only the one that it sees by definition. it >>>>> maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.
    All of the people that think it should map the behavior of a non-input >>>>> have always been wrong.
    What is the non-input?

    int main()
    {
        DD();    // Is not an input to HHH
        HHH(DD)  // Is an input to HHH
    {
    Oh, but we’re not interested in the behaviour of HHH(HHH(DD)).

    The input is DD, and its behaviour is that it halts.
    HHH’s simulation is not correct by definition.

    DD correctly simulated by HHH cannot possibly terminate normally.



    The problem is your HHH doesn't do that, so your are basing your logic
    on a LIE.

    You don't understand what a "Program" which just breaks all your logic,
    as you need HHH to be two different things at once, which is just the contradiction that blows up your logic.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sat Feb 15 09:10:03 2025
    Op 15.feb.2025 om 00:28 schreef olcott:
    On 2/14/2025 6:53 AM, joes wrote:
    Am Thu, 13 Feb 2025 22:20:32 -0600 schrieb olcott:
    On 2/13/2025 9:15 PM, Richard Damon wrote:
    On 2/13/25 7:09 PM, olcott wrote:
    On 2/13/2025 4:53 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 05:12 schreef olcott:
    On 2/11/2025 10:44 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 17:22 schreef olcott:
    On 2/11/2025 10:10 AM, Fred. Zwarts wrote:
    Op 11.feb.2025 om 15:38 schreef olcott:
    On 2/11/2025 1:28 AM, joes wrote:
    Am Mon, 10 Feb 2025 14:36:51 -0600 schrieb olcott:
    On 2/10/2025 12:41 PM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 13:27 schreef olcott:
    On 2/10/2025 6:14 AM, Fred. Zwarts wrote:
    Op 10.feb.2025 om 12:51 schreef olcott:
    On 2/10/2025 2:22 AM, Fred. Zwarts wrote:
    Op 09.feb.2025 om 20:54 schreef olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote:

    So, in other words, Olcott denies verified facts. HHH >>>>>>>>>>>>>>>>>>>>>> generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>>>           int main() {           return
              HHH(main);
              }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>>>>>>>>>> which he tries to hide with a lot of irrelevant >>>>>>>>>>>>>>>>>>>>>> words.

    It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>>>>>> correctly simulated by HHH until its normal >>>>>>>>>>>>>>>>>>>>> termination.
    Indeed, which proves that HHH is unable to simulate >>>>>>>>>>>>>>>>>>>> itself correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>>>>>> HHH is incorrect.
    It is true as a verified fact and has been pointed out to >>>>>>>>>>>>>>>>>> Olcott many times, but he refuses to learn. So, again: >>>>>>>>>>>>>>>>>> It is a verified fact that main halts,
    It is a verified fact that the input to HHH(main) cannot >>>>>>>>>>>>>>>>> possibly terminate normally.
    No, the verified fact is that the input can terminatie >>>>>>>>>>>>>>>> normally
    The directly executed main IS NOT THE INPUT TO HHH. >>>>>>>>>>>>>>>
    This main is a program that includes all functions called >>>>>>>>>>>>>> directly and indirectly, including HHH.

    The input to HHH(main) when correctly simulated by HHH cannot >>>>>>>>>>>>> possibly terminate normally.

    The input to HHH, which is main(), terminates. HHH does not >>>>>>>>>>>> simulate that.


    The directly executed main() is not the same instance of main() >>>>>>>>>>> that is input to HHH and simulated by HHH.

    The directly executed main() relies on HHH aborting the
    simulation of its input. HHH cannot rely on anything else >>>>>>>>>>> aborting the simulation of its input.

    The simulating HHH should rely on the simulated HHH to abort. >>>>>>>>>
    That cannot possibly work. The executed HHH always sees at least >>>>>>>>> one more full execution trace than any inner HHH ever sees.


    Indeed, that is what I said, but Olcott deleted it in the citation. >>>>>>>> HHH cannot do what it should do. So, he proves the halting theorem. >>>>>>>
    If the sentence it false it does not become true in some greater >>>>>>> context.

    Indeed and since it is false that the simulated HHH would not abort, >>>>>
    This is simply beyond your skill level.
    Since each HHH is exactly the same unless the first one aborts none of >>>>> them do.

    But the first one DOES abort, as that is how it was defined to be.

    And thus, the one that DD calls aborts.

    A program that is no longer being simulated DOES NOTHING

    Hey, let me prove all programs are no-ops, by NOT SIMULATING THEM MWAHAHA


    DD correctly simulated  by HHH cannot possibly terminate normally.

    But HHH aborts and an aborting program is also a halting program. The simulation of an aborting program should see that. This is the failure
    of HHH, that it does not see that the aborting simulated program halts.
    It does not even notice that the simulating program aborts.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sat Feb 15 09:11:03 2025
    Op 15.feb.2025 om 00:30 schreef olcott:
    On 2/14/2025 6:58 AM, joes wrote:
    Am Fri, 14 Feb 2025 06:42:29 -0600 schrieb olcott:
    On 2/14/2025 3:36 AM, joes wrote:
    Am Thu, 13 Feb 2025 18:12:52 -0600 schrieb olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/6/25 10:02 PM, olcott wrote:

    Since there is a 5% chance that the treatment I will have next >>>>>>>>> month will kill me and this treatment is my only good chance I >>>>>>>>> will totally ignore anything that diverges from the point.
    Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD >>>>>>> correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot >>>>>> properly decide about its input, because  it must abort the correct >>>>>> simulation before it sees that the correct simulation terminates
    normally.

    The correct simulation is only the one that it sees by definition. it >>>>> maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.
    All of the people that think it should map the behavior of a non-input >>>>> have always been wrong.
    What is the non-input?

    int main()
    {
        DD();    // Is not an input to HHH
        HHH(DD)  // Is an input to HHH
    {
    Oh, but we’re not interested in the behaviour of HHH(HHH(DD)).

    The input is DD, and its behaviour is that it halts.
    HHH’s simulation is not correct by definition.

    DD correctly simulated by HHH cannot possibly terminate normally.


    Proving the failure to decide by simulation.


    --
    Paradoxes in the relation between Creator and creature. <http://www.wirholt.nl/English>.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sat Feb 15 09:06:25 2025
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Montero

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All >>>>>>>>>>>>>>>>>>>>>>>>>>>> other
    methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, etc.) >>>>>>>>>>>>>>>>>>>>>>>>>>>> show
    that DD halts. But HHH fails to see it. >>>>>>>>>>>>>>>>>>>>>>>>>>>> Everyone with
    sufficient understanding of programming sees >>>>>>>>>>>>>>>>>>>>>>>>>>>> that HHH
    is not correctly programmed when it aborts >>>>>>>>>>>>>>>>>>>>>>>>>>>> one cycle
    before the simulation would end normally. >>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is >>>>>>>>>>>>>>>>>>>>>>>>>> unable to
    complete its simulation, because HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself.
    It turns out that Olcott does not even >>>>>>>>>>>>>>>>>>>>>>>> understand this
    simple proof that HHH produces false negatives. >>>>>>>>>>>>>>>>>>>>>>>> HHH is
    unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>>>               int main() { >>>>>>>>>>>>>>>>>>>>>>                 return HHH(main); >>>>>>>>>>>>>>>>>>>>>>               }
    but he denies it.
    He lacks the ability to accept simple verified >>>>>>>>>>>>>>>>>>>>>> facts, which
    he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>>>>>> correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to simulate >>>>>>>>>>>>>>>>>>>> itself
    correctly.
    If this was true then you could point out exactly >>>>>>>>>>>>>>>>>>> where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and return the >>>>>>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts and returns >>>>>>>>>>>>>>>>> a correct
    value as soon as it correctly determines that its input >>>>>>>>>>>>>>>>> cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts >>>>>>>>>>>>>>>> according
    to spec, so does the inner, because it is the same. >>>>>>>>>>>>>>>> Therefore it
    can’t report „non-halting” and be correct. If the inner HHH
    doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject
    corrections.
    I reject infinite deflection away from the point. The absolute >>>>>>>>> single-mined focus point is that DD correctly simulated by HHH >>>>>>>>> cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next >>>>>>>>> month
    will kill me and this treatment is my only good chance I will >>>>>>>>> totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows
    that DD correctly simulated by HHH cannot possibly terminate
    normally.

    Indeed, which shows the limitation of HHH which makes that it
    cannot properly decide about its input, because  it must abort the >>>>>> correct simulation before it sees that the correct simulation
    terminates normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.

    If I close my eyes, so that I do not see the accident, I cannot
    claim that the accident did not happen. That is the reasoning of a 2
    years old child.

    HHH(DD) maps the finite string input of DD to the behavior that it
    specifies. This behavior does include DD repeatedly calling HHH(DD)
    in recursive simulation that that cannot possibly terminate normally.

    Olcott is again dreaming of a HHH that does not abort. Dreams are no
    substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes and does not
    see that the simulated HHH also aborts so that the program terminates
    normally.


    It is only your lack of technical competence that makes it seem that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not see that the simulated HHH would also abort, so that the simulating HHH does not need
    to abort. But, HHH cannot do so. This limitation of HHH makes that it
    cannot possibly complete its task correctly.
    Olcott seems to be stuck in his idea that HHH must be correct, because
    there is no other correct way. This is, of course, unsound logic.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sat Feb 15 09:14:19 2025
    Op 15.feb.2025 om 00:54 schreef olcott:
    On 2/14/2025 7:55 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:42 schreef olcott:
    On 2/14/2025 3:36 AM, joes wrote:
    Am Thu, 13 Feb 2025 18:12:52 -0600 schrieb olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott:
    On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/6/25 10:02 PM, olcott wrote:

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All >>>>>>>>>>>>>>>>>>>>>>>>>>>> other
    methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, etc.) >>>>>>>>>>>>>>>>>>>>>>>>>>>> show
    that DD halts. But HHH fails to see it. >>>>>>>>>>>>>>>>>>>>>>>>>>>> Everyone
    with sufficient understanding of programming >>>>>>>>>>>>>>>>>>>>>>>>>>>> sees
    that HHH is not correctly programmed when it >>>>>>>>>>>>>>>>>>>>>>>>>>>> aborts one cycle before the simulation would >>>>>>>>>>>>>>>>>>>>>>>>>>>> end
    normally.
    The execution trace only shows that HHH is unable >>>>>>>>>>>>>>>>>>>>>>>>>> to complete its simulation, because HHH is unable >>>>>>>>>>>>>>>>>>>>>>>>>> to simulate itself.
    It turns out that Olcott does not even understand >>>>>>>>>>>>>>>>>>>>>>>> this simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>> negatives.
    HHH is unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified facts. HHH >>>>>>>>>>>>>>>>>>>>>> generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>>>                int main() { >>>>>>>>>>>>>>>>>>>>>>                  return HHH(main); >>>>>>>>>>>>>>>>>>>>>>                }
    but he denies it.
    He lacks the ability to accept simple verified facts, >>>>>>>>>>>>>>>>>>>>>> which he tries to hide with a lot of irrelevant >>>>>>>>>>>>>>>>>>>>>> words.
    It is a verified fact that main cannot possibly be >>>>>>>>>>>>>>>>>>>>> correctly simulated by HHH until its normal >>>>>>>>>>>>>>>>>>>>> termination.
    Indeed, which proves that HHH is unable to simulate >>>>>>>>>>>>>>>>>>>> itself correctly.
    If this was true then you could point out exactly where >>>>>>>>>>>>>>>>>>> HHH is incorrect.
    HHH is supposed to be a decider, i.e. halt and return the >>>>>>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts and returns a >>>>>>>>>>>>>>>>> correct value as soon as it correctly determines that its >>>>>>>>>>>>>>>>> input cannot possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts >>>>>>>>>>>>>>>> according to spec, so does the inner, because it is the >>>>>>>>>>>>>>>> same.
    Therefore it can’t report „non-halting” and be correct. If
    the inner HHH doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject
    corrections.
    I reject infinite deflection away from the point. The absolute >>>>>>>>> single-mined focus point is that DD correctly simulated by HHH >>>>>>>>> cannot possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have next >>>>>>>>> month
    will kill me and this treatment is my only good chance I will >>>>>>>>> totally ignore anything that diverges from the point.
    Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD >>>>>>> correctly simulated by HHH cannot possibly terminate normally.

    Indeed, which shows the limitation of HHH which makes that it cannot >>>>>> properly decide about its input, because  it must abort the correct >>>>>> simulation before it sees that the correct simulation terminates
    normally.

    The correct simulation is only the one that it sees by definition. it >>>>> maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.
    All of the people that think it should map the behavior of a non-input >>>>> have always been wrong.
    What is the non-input?

    int main()
    {
       DD();    // Is not an input to HHH
       HHH(DD)  // Is an input to HHH
    {

    The input is DD, and its behaviour is that it halts.
    HHH’s simulation is not correct by definition.




    What is the difference in the finite string that describes the first
    DD and the finite string that describes the second DD?

    The directly executed DD only halts because HHH aborts its
    simulated DD.

    DD correctly simulated  by HHH cannot possibly terminate normally.



    No answer to the question, which probably means that there is no
    difference. There is only one finite string, which describes a halting
    program (proven by direct execution and many simulators), but HHH does
    an incorrect analysis of this finite string. It incorrectly thinks it
    cannot terminate normally and then incorrectly aborts the simulation.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Feb 15 20:38:16 2025
    On 2/15/25 2:21 PM, olcott wrote:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Montero

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> other
    methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> etc.) show
    that DD halts. But HHH fails to see it. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Everyone with
    sufficient understanding of programming >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sees that HHH
    is not correctly programmed when it aborts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> one cycle
    before the simulation would end normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to
    complete its simulation, because HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to
    simulate itself.
    It turns out that Olcott does not even >>>>>>>>>>>>>>>>>>>>>>>>>> understand this
    simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>>>> negatives. HHH is
    unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>>>>>               int main() { >>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main); >>>>>>>>>>>>>>>>>>>>>>>>               }
    but he denies it.
    He lacks the ability to accept simple verified >>>>>>>>>>>>>>>>>>>>>>>> facts, which
    he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot possibly >>>>>>>>>>>>>>>>>>>>>>> be correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to >>>>>>>>>>>>>>>>>>>>>> simulate itself
    correctly.
    If this was true then you could point out exactly >>>>>>>>>>>>>>>>>>>>> where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and >>>>>>>>>>>>>>>>>>>> return the
    correct value.
    The directly executed HHH(DD) always halts and >>>>>>>>>>>>>>>>>>> returns a correct
    value as soon as it correctly determines that its >>>>>>>>>>>>>>>>>>> input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts >>>>>>>>>>>>>>>>>> according
    to spec, so does the inner, because it is the same. >>>>>>>>>>>>>>>>>> Therefore it
    can’t report „non-halting” and be correct. If the >>>>>>>>>>>>>>>>>> inner HHH
    doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject >>>>>>>>>>>> corrections.
    I reject infinite deflection away from the point. The absolute >>>>>>>>>>> single-mined focus point is that DD correctly simulated by >>>>>>>>>>> HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have >>>>>>>>>>> next month
    will kill me and this treatment is my only good chance I will >>>>>>>>>>> totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows
    that DD correctly simulated by HHH cannot possibly terminate >>>>>>>>> normally.

    Indeed, which shows the limitation of HHH which makes that it
    cannot properly decide about its input, because  it must abort >>>>>>>> the correct simulation before it sees that the correct
    simulation terminates normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.

    If I close my eyes, so that I do not see the accident, I cannot
    claim that the accident did not happen. That is the reasoning of a >>>>>> 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior that it
    specifies. This behavior does include DD repeatedly calling HHH(DD)
    in recursive simulation that that cannot possibly terminate normally. >>>>>
    Olcott is again dreaming of a HHH that does not abort. Dreams are no
    substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes and does
    not see that the simulated HHH also aborts so that the program
    terminates normally.


    It is only your lack of technical competence that makes it seem that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not see that
    the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly
    get to the point where it sees that it needs to abort because it
    is aborted before it gets to this point.

    You don't seem to understand that the simulated machine's behavior
    continues after the simulation is stopped.

    You are talking about the behavior shown in the simulation, which is
    something different, and just a strawman for the problem.


    Unless the outermost HHH aborts before any inner HHH sees that
    it needs  to abort no HHH ever aborts. You simply do not understand
    these things well enough to verify the actual facts.


    And since the outermost HHH aborts, it meens the CORRECT simulation, and
    actual behavior of the"inner" HHH is to halt.

    You are just proving that you are nothing but an ignorant pathological
    liar that doesn't understand what he is talking about, and who refuses
    to learn, because it lying is pathological and based on a need to be
    "right" even if it requires fraud.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sun Feb 16 10:40:20 2025
    Op 16.feb.2025 om 04:29 schreef olcott:
    On 2/15/2025 2:11 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 00:30 schreef olcott:
    On 2/14/2025 6:58 AM, joes wrote:
    Am Fri, 14 Feb 2025 06:42:29 -0600 schrieb olcott:
    On 2/14/2025 3:36 AM, joes wrote:
    Am Thu, 13 Feb 2025 18:12:52 -0600 schrieb olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote:

    Since there is a 5% chance that the treatment I will have next >>>>>>>>>>> month will kill me and this treatment is my only good chance I >>>>>>>>>>> will totally ignore anything that diverges from the point. >>>>>>>>>> Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD >>>>>>>>> correctly simulated by HHH cannot possibly terminate normally. >>>>>>>>
    Indeed, which shows the limitation of HHH which makes that it
    cannot
    properly decide about its input, because  it must abort the correct >>>>>>>> simulation before it sees that the correct simulation terminates >>>>>>>> normally.

    The correct simulation is only the one that it sees by
    definition. it
    maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.
    All of the people that think it should map the behavior of a non- >>>>>>> input
    have always been wrong.
    What is the non-input?

    int main()
    {
        DD();    // Is not an input to HHH
        HHH(DD)  // Is an input to HHH
    {
    Oh, but we’re not interested in the behaviour of HHH(HHH(DD)).

    The input is DD, and its behaviour is that it halts.
    HHH’s simulation is not correct by definition.

    DD correctly simulated by HHH cannot possibly terminate normally.


    Proving the failure to decide by simulation.



    That would be isomorphic to saying that cows prove that
    mammals do not exist.


    Claiming that it is isomorphic is counter factual.
    It has been shown before that olcott does not understand what isomorphic is.
    It has been proven that olcott's HHH claims non-halting for a finite
    string that describes a halting program and therefore fails.
    He seems to be desperate and starts to use words he does not understand
    to try to rescue his claim.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sun Feb 16 10:44:19 2025
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, Bonita >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Montero

    Which proves that HHH fails to make a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting behaviour. All >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> other
    methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> etc.) show
    that DD halts. But HHH fails to see it. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Everyone with
    sufficient understanding of programming >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sees that HHH
    is not correctly programmed when it aborts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> one cycle
    before the simulation would end normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to
    complete its simulation, because HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to
    simulate itself.
    It turns out that Olcott does not even >>>>>>>>>>>>>>>>>>>>>>>>>> understand this
    simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>>>> negatives. HHH is
    unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>>>>>               int main() { >>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main); >>>>>>>>>>>>>>>>>>>>>>>>               }
    but he denies it.
    He lacks the ability to accept simple verified >>>>>>>>>>>>>>>>>>>>>>>> facts, which
    he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot possibly >>>>>>>>>>>>>>>>>>>>>>> be correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to >>>>>>>>>>>>>>>>>>>>>> simulate itself
    correctly.
    If this was true then you could point out exactly >>>>>>>>>>>>>>>>>>>>> where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and >>>>>>>>>>>>>>>>>>>> return the
    correct value.
    The directly executed HHH(DD) always halts and >>>>>>>>>>>>>>>>>>> returns a correct
    value as soon as it correctly determines that its >>>>>>>>>>>>>>>>>>> input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH halts >>>>>>>>>>>>>>>>>> according
    to spec, so does the inner, because it is the same. >>>>>>>>>>>>>>>>>> Therefore it
    can’t report „non-halting” and be correct. If the >>>>>>>>>>>>>>>>>> inner HHH
    doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject >>>>>>>>>>>> corrections.
    I reject infinite deflection away from the point. The absolute >>>>>>>>>>> single-mined focus point is that DD correctly simulated by >>>>>>>>>>> HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH.

    Since there is a 5% chance that the treatment I will have >>>>>>>>>>> next month
    will kill me and this treatment is my only good chance I will >>>>>>>>>>> totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows
    that DD correctly simulated by HHH cannot possibly terminate >>>>>>>>> normally.

    Indeed, which shows the limitation of HHH which makes that it
    cannot properly decide about its input, because  it must abort >>>>>>>> the correct simulation before it sees that the correct
    simulation terminates normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.

    If I close my eyes, so that I do not see the accident, I cannot
    claim that the accident did not happen. That is the reasoning of a >>>>>> 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior that it
    specifies. This behavior does include DD repeatedly calling HHH(DD)
    in recursive simulation that that cannot possibly terminate normally. >>>>>
    Olcott is again dreaming of a HHH that does not abort. Dreams are no
    substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes and does
    not see that the simulated HHH also aborts so that the program
    terminates normally.


    It is only your lack of technical competence that makes it seem that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not see that
    the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly
    get to the point where it sees that it needs to abort because it
    is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point where the
    simulated HHH aborts and halts. The simulating misses in this way
    relevant details of the program given in its input. That is the reason
    why it fails. It is unable to see the whole input, because it gets stuck
    in recursive simulation of itself.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Feb 16 07:11:17 2025
    On 2/15/25 10:29 PM, olcott wrote:
    On 2/15/2025 2:11 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 00:30 schreef olcott:
    On 2/14/2025 6:58 AM, joes wrote:
    Am Fri, 14 Feb 2025 06:42:29 -0600 schrieb olcott:
    On 2/14/2025 3:36 AM, joes wrote:
    Am Thu, 13 Feb 2025 18:12:52 -0600 schrieb olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote:

    Since there is a 5% chance that the treatment I will have next >>>>>>>>>>> month will kill me and this treatment is my only good chance I >>>>>>>>>>> will totally ignore anything that diverges from the point. >>>>>>>>>> Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD >>>>>>>>> correctly simulated by HHH cannot possibly terminate normally. >>>>>>>>
    Indeed, which shows the limitation of HHH which makes that it
    cannot
    properly decide about its input, because  it must abort the correct >>>>>>>> simulation before it sees that the correct simulation terminates >>>>>>>> normally.

    The correct simulation is only the one that it sees by
    definition. it
    maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.
    All of the people that think it should map the behavior of a non- >>>>>>> input
    have always been wrong.
    What is the non-input?

    int main()
    {
        DD();    // Is not an input to HHH
        HHH(DD)  // Is an input to HHH
    {
    Oh, but we’re not interested in the behaviour of HHH(HHH(DD)).

    The input is DD, and its behaviour is that it halts.
    HHH’s simulation is not correct by definition.

    DD correctly simulated by HHH cannot possibly terminate normally.


    Proving the failure to decide by simulation.



    That would be isomorphic to saying that cows prove that
    mammals do not exist.


    Try to show that morpic.

    You are famous for bad analogies.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Sun Feb 16 12:50:21 2025
    Am Sat, 15 Feb 2025 13:21:10 -0600 schrieb olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott:
    On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon


    Since there is a 5% chance that the treatment I will have next >>>>>>>>>>> month will kill me and this treatment is my only good chance I >>>>>>>>>>> will totally ignore anything that diverges from the point. >>>>>>>>>> Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD >>>>>>>>> correctly simulated by HHH cannot possibly terminate normally. >>>>>>>>
    Indeed, which shows the limitation of HHH which makes that it
    cannot properly decide about its input, because  it must abort >>>>>>>> the correct simulation before it sees that the correct simulation >>>>>>>> terminates normally.

    The correct simulation is only the one that it sees by definition. >>>>>>> it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.

    If I close my eyes, so that I do not see the accident, I cannot
    claim that the accident did not happen. That is the reasoning of a >>>>>> 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior that it
    specifies. This behavior does include DD repeatedly calling HHH(DD)
    in recursive simulation that that cannot possibly terminate
    normally.

    Olcott is again dreaming of a HHH that does not abort. Dreams are no
    substitute for reasoning.
    The simulating HHH aborts the simulation, closes its eyes and does
    not see that the simulated HHH also aborts so that the program
    terminates normally.

    It is only your lack of technical competence that makes it seem that
    (a) The simulated HHH aborts its simulation after itself is no longer
    being simulated.

    (b) Either the outermost HHH aborts its simulation of none of them do.
    Which does not change the fact that simulating HHH does not see that
    the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly get to
    the point where it sees that it needs to abort because it is aborted
    before it gets to this point.
    Yes, but why does it need to be stopped before it halts?

    Unless the outermost HHH aborts before any inner HHH sees that it needs
    to abort no HHH ever aborts.
    True. No HHH should ever 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 Sun Feb 16 13:39:36 2025
    On 2/16/25 8:18 AM, olcott wrote:
    On 2/16/2025 6:50 AM, joes wrote:
    Am Sat, 15 Feb 2025 13:21:10 -0600 schrieb olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon


    Since there is a 5% chance that the treatment I will have next >>>>>>>>>>>>> month will kill me and this treatment is my only good chance I >>>>>>>>>>>>> will totally ignore anything that diverges from the point. >>>>>>>>>>>> Ok, I will wait a month then.

    Anyone that knows the C language sufficiently well knows that DD >>>>>>>>>>> correctly simulated by HHH cannot possibly terminate normally. >>>>>>>>>>
    Indeed, which shows the limitation of HHH which makes that it >>>>>>>>>> cannot properly decide about its input, because  it must abort >>>>>>>>>> the correct simulation before it sees that the correct simulation >>>>>>>>>> terminates normally.

    The correct simulation is only the one that it sees by definition. >>>>>>>>> it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT.

    If I close my eyes, so that I do not see the accident, I cannot >>>>>>>> claim that the accident did not happen. That is the reasoning of a >>>>>>>> 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior that it >>>>>>> specifies. This behavior does include DD repeatedly calling HHH(DD) >>>>>>> in recursive simulation that that cannot possibly terminate
    normally.

    Olcott is again dreaming of a HHH that does not abort. Dreams are no >>>>>> substitute for reasoning.
    The simulating HHH aborts the simulation, closes its eyes and does >>>>>> not see that the simulated HHH also aborts so that the program
    terminates normally.

    It is only your lack of technical competence that makes it seem that >>>>> (a) The simulated HHH aborts its simulation after itself is no longer >>>>> being simulated.

    (b) Either the outermost HHH aborts its simulation of none of them do. >>>> Which does not change the fact that simulating HHH does not see that
    the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly get to >>> the point where it sees that it needs to abort because it is aborted
    before it gets to this point.

    Yes, but why does it need to be stopped before it halts?
    I had to rewrite this reply five times because Thunderbird
    kept screwing up. I forgot my original words.

    No DD simulated by any corresponding HHH can possibly ever terminate
    normally if you disagree that only proves that you don't know C well
    enough.

    So?

    We aren't looking at templates, we are looking at programs.

    Any DD that calls an HHH that aborts its simulation of DD, and returns
    0, creates a PROGRAM that Halts, since it does so when correctly run or simulated.

    The fact that its HHH aborted its simulation based on invalid logic,
    doesn't make its answer "correct", it makes the logic incorrect and the
    answer wrong.

    Of course, since you just don't understand the fundamental nature of
    Truth, you don't care that you are working from your own lies, you think anything you say must be correct, but that is just you lying to yourself.

    Of course, you know what happens to liars, so you can't afford to look
    closely at your own words, or you would know your fate.



    Unless the outermost HHH aborts before any inner HHH sees that it needs
    to abort no HHH ever aborts.
    True. No HHH should ever abort.





    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Sun Feb 16 21:16:18 2025
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott:
    On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote:
    Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Bonita Montero

    Which proves that HHH fails to make a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correct
    decision about DD's halting behaviour. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> All other
    methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> etc.) show
    that DD halts. But HHH fails to see it. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Everyone with
    sufficient understanding of programming >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sees that HHH
    is not correctly programmed when it >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would end normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to
    complete its simulation, because HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to
    simulate itself.
    It turns out that Olcott does not even >>>>>>>>>>>>>>>>>>>>>>>>>>>> understand this
    simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>>>>>> negatives. HHH is
    unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified facts. >>>>>>>>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is verified in >>>>>>>>>>>>>>>>>>>>>>>>>>               int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main); >>>>>>>>>>>>>>>>>>>>>>>>>>               } >>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it.
    He lacks the ability to accept simple verified >>>>>>>>>>>>>>>>>>>>>>>>>> facts, which
    he tries to hide with a lot of irrelevant words. >>>>>>>>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot possibly >>>>>>>>>>>>>>>>>>>>>>>>> be correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>> simulate itself
    correctly.
    If this was true then you could point out exactly >>>>>>>>>>>>>>>>>>>>>>> where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and >>>>>>>>>>>>>>>>>>>>>> return the
    correct value.
    The directly executed HHH(DD) always halts and >>>>>>>>>>>>>>>>>>>>> returns a correct
    value as soon as it correctly determines that its >>>>>>>>>>>>>>>>>>>>> input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH >>>>>>>>>>>>>>>>>>>> halts according
    to spec, so does the inner, because it is the same. >>>>>>>>>>>>>>>>>>>> Therefore it
    can’t report „non-halting” and be correct. If the >>>>>>>>>>>>>>>>>>>> inner HHH
    doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject >>>>>>>>>>>>>> corrections.
    I reject infinite deflection away from the point. The absolute >>>>>>>>>>>>> single-mined focus point is that DD correctly simulated by >>>>>>>>>>>>> HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH. >>>>>>>>>>>>
    Since there is a 5% chance that the treatment I will have >>>>>>>>>>>>> next month
    will kill me and this treatment is my only good chance I >>>>>>>>>>>>> will totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows >>>>>>>>>>> that DD correctly simulated by HHH cannot possibly terminate >>>>>>>>>>> normally.

    Indeed, which shows the limitation of HHH which makes that it >>>>>>>>>> cannot properly decide about its input, because  it must abort >>>>>>>>>> the correct simulation before it sees that the correct
    simulation terminates normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT. >>>>>>>>
    If I close my eyes, so that I do not see the accident, I cannot >>>>>>>> claim that the accident did not happen. That is the reasoning of >>>>>>>> a 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior that
    it specifies. This behavior does include DD repeatedly calling
    HHH(DD)
    in recursive simulation that that cannot possibly terminate
    normally.

    Olcott is again dreaming of a HHH that does not abort. Dreams are
    no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes and does >>>>>> not see that the simulated HHH also aborts so that the program
    terminates normally.


    It is only your lack of technical competence that makes it seem that >>>>> (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not see that
    the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly
    get to the point where it sees that it needs to abort because it
    is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point where the
    simulated HHH aborts and halts. The simulating misses in this way
    relevant details of the program given in its input. That is the reason
    why it fails. It is unable to see the whole input, because it gets
    stuck in recursive simulation of itself.


    This is all moot because the executed HHH recognizes this
    pattern and correctly reports that its input cannot possibly
    terminate normally.


    It only reports that the simulation was aborted. Not more, not less.
    Since it saw only the start of the program, it misses the fact that the
    program described with the infinite string is a halting program, proven
    by direct execution and many simulators. HHH did not analyse the
    remainder of the program that follows when HHH returns to DD.
    A better simulation would be to replace the call to HHH with the return
    value of HHH (which is known to HHH) and then continue the simulation of
    the remainder of DD. In that way HHH would analyse the whole input
    instead of only the first few instructions. The first few instructions
    that do not tell anything about the halting behaviour of the program.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Feb 16 20:08:09 2025
    On 2/16/25 5:00 PM, olcott wrote:
    On 2/16/2025 2:16 PM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Bonita Montero

    Which proves that HHH fails to make a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correct
    decision about DD's halting behaviour. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> All other
    methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> it. Everyone with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sufficient understanding of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> programming sees that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is not correctly programmed when it >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would end normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is unable to
    complete its simulation, because HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to
    simulate itself. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It turns out that Olcott does not even >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> understand this
    simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> negatives. HHH is
    unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified >>>>>>>>>>>>>>>>>>>>>>>>>>>> facts.
    HHH generates false negatives, as is >>>>>>>>>>>>>>>>>>>>>>>>>>>> verified in
                  int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main); >>>>>>>>>>>>>>>>>>>>>>>>>>>>               } >>>>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it.
    He lacks the ability to accept simple >>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts, which
    he tries to hide with a lot of irrelevant >>>>>>>>>>>>>>>>>>>>>>>>>>>> words.
    It is a verified fact that main cannot >>>>>>>>>>>>>>>>>>>>>>>>>>> possibly be correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself
    correctly.
    If this was true then you could point out >>>>>>>>>>>>>>>>>>>>>>>>> exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and >>>>>>>>>>>>>>>>>>>>>>>> return the
    correct value.
    The directly executed HHH(DD) always halts and >>>>>>>>>>>>>>>>>>>>>>> returns a correct
    value as soon as it correctly determines that its >>>>>>>>>>>>>>>>>>>>>>> input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH >>>>>>>>>>>>>>>>>>>>>> halts according
    to spec, so does the inner, because it is the >>>>>>>>>>>>>>>>>>>>>> same. Therefore it
    can’t report „non-halting” and be correct. If the >>>>>>>>>>>>>>>>>>>>>> inner HHH
    doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject >>>>>>>>>>>>>>>> corrections.
    I reject infinite deflection away from the point. The >>>>>>>>>>>>>>> absolute
    single-mined focus point is that DD correctly simulated >>>>>>>>>>>>>>> by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH. >>>>>>>>>>>>>>
    Since there is a 5% chance that the treatment I will have >>>>>>>>>>>>>>> next month
    will kill me and this treatment is my only good chance I >>>>>>>>>>>>>>> will totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows >>>>>>>>>>>>> that DD correctly simulated by HHH cannot possibly
    terminate normally.

    Indeed, which shows the limitation of HHH which makes that >>>>>>>>>>>> it cannot properly decide about its input, because  it must >>>>>>>>>>>> abort the correct simulation before it sees that the correct >>>>>>>>>>>> simulation terminates normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT. >>>>>>>>>>
    If I close my eyes, so that I do not see the accident, I
    cannot claim that the accident did not happen. That is the >>>>>>>>>> reasoning of a 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior that >>>>>>>>> it specifies. This behavior does include DD repeatedly calling >>>>>>>>> HHH(DD)
    in recursive simulation that that cannot possibly terminate
    normally.

    Olcott is again dreaming of a HHH that does not abort. Dreams
    are no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes and
    does not see that the simulated HHH also aborts so that the
    program terminates normally.


    It is only your lack of technical competence that makes it seem that >>>>>>> (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not see
    that the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly
    get to the point where it sees that it needs to abort because it
    is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point where the
    simulated HHH aborts and halts. The simulating misses in this way
    relevant details of the program given in its input. That is the
    reason why it fails. It is unable to see the whole input, because it
    gets stuck in recursive simulation of itself.


    This is all moot because the executed HHH recognizes this
    pattern and correctly reports that its input cannot possibly
    terminate normally.


    It only reports that the simulation was aborted. Not more, not less.

    That you do not understand the term: "terminates normally"
    is far less than no rebuttal at all.


    That you don't understand that computation can only "terminate normally"
    and your whole argument is just a shell game to hide your lies.

    Sorry, but since you clearly don't know the meaning of what you are
    talking about, you are just proving that you are too stupid to matter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Mon Feb 17 09:59:16 2025
    Op 16.feb.2025 om 23:00 schreef olcott:
    On 2/16/2025 2:16 PM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott: >>>>>>>>>>>>>>> On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote:
    Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Bonita Montero

    Which proves that HHH fails to make a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correct
    decision about DD's halting behaviour. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> All other
    methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class simulator, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> it. Everyone with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sufficient understanding of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> programming sees that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is not correctly programmed when it >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would end normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is unable to
    complete its simulation, because HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to
    simulate itself. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It turns out that Olcott does not even >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> understand this
    simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> negatives. HHH is
    unable to simulate itself up to the normal >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> termination.
    So, in other words, Olcott denies verified >>>>>>>>>>>>>>>>>>>>>>>>>>>> facts.
    HHH generates false negatives, as is >>>>>>>>>>>>>>>>>>>>>>>>>>>> verified in
                  int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main); >>>>>>>>>>>>>>>>>>>>>>>>>>>>               } >>>>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it.
    He lacks the ability to accept simple >>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts, which
    he tries to hide with a lot of irrelevant >>>>>>>>>>>>>>>>>>>>>>>>>>>> words.
    It is a verified fact that main cannot >>>>>>>>>>>>>>>>>>>>>>>>>>> possibly be correctly
    simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself
    correctly.
    If this was true then you could point out >>>>>>>>>>>>>>>>>>>>>>>>> exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and >>>>>>>>>>>>>>>>>>>>>>>> return the
    correct value.
    The directly executed HHH(DD) always halts and >>>>>>>>>>>>>>>>>>>>>>> returns a correct
    value as soon as it correctly determines that its >>>>>>>>>>>>>>>>>>>>>>> input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH >>>>>>>>>>>>>>>>>>>>>> halts according
    to spec, so does the inner, because it is the >>>>>>>>>>>>>>>>>>>>>> same. Therefore it
    can’t report „non-halting” and be correct. If the >>>>>>>>>>>>>>>>>>>>>> inner HHH
    doesn’t halt, it is not a decider.
    I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject >>>>>>>>>>>>>>>> corrections.
    I reject infinite deflection away from the point. The >>>>>>>>>>>>>>> absolute
    single-mined focus point is that DD correctly simulated >>>>>>>>>>>>>>> by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH. >>>>>>>>>>>>>>
    Since there is a 5% chance that the treatment I will have >>>>>>>>>>>>>>> next month
    will kill me and this treatment is my only good chance I >>>>>>>>>>>>>>> will totally
    ignore anything that diverges from the point.
    Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows >>>>>>>>>>>>> that DD correctly simulated by HHH cannot possibly
    terminate normally.

    Indeed, which shows the limitation of HHH which makes that >>>>>>>>>>>> it cannot properly decide about its input, because  it must >>>>>>>>>>>> abort the correct simulation before it sees that the correct >>>>>>>>>>>> simulation terminates normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS INPUT. >>>>>>>>>>
    If I close my eyes, so that I do not see the accident, I
    cannot claim that the accident did not happen. That is the >>>>>>>>>> reasoning of a 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior that >>>>>>>>> it specifies. This behavior does include DD repeatedly calling >>>>>>>>> HHH(DD)
    in recursive simulation that that cannot possibly terminate
    normally.

    Olcott is again dreaming of a HHH that does not abort. Dreams
    are no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes and
    does not see that the simulated HHH also aborts so that the
    program terminates normally.


    It is only your lack of technical competence that makes it seem that >>>>>>> (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not see
    that the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly
    get to the point where it sees that it needs to abort because it
    is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point where the
    simulated HHH aborts and halts. The simulating misses in this way
    relevant details of the program given in its input. That is the
    reason why it fails. It is unable to see the whole input, because it
    gets stuck in recursive simulation of itself.


    This is all moot because the executed HHH recognizes this
    pattern and correctly reports that its input cannot possibly
    terminate normally.


    It only reports that the simulation was aborted. Not more, not less.

    That you do not understand the term: "terminates normally"
    is far less than no rebuttal at all.


    So we (Olcott and me) agree that HHH cannot possibly simulate up to the
    normal termination of the program described by the finite string.
    However, Olcott fails to see that it is a failure of HHH to be unable to simulate a halting program up to the end.

    In his citation he deleted my suggestion to change his simulator.
    Instead of aborting the simulation at the call to HHH, he could replace
    this call with the correct return value of HHH (which he seems to know)
    and then continue the simulation of DD. This avoids the recursion
    introduced by the simulator.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Mon Feb 17 16:43:43 2025
    Op 17.feb.2025 om 15:06 schreef olcott:
    On 2/17/2025 2:59 AM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 23:00 schreef olcott:
    On 2/16/2025 2:16 PM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Bonita Montero >>>>>>>>>>>>>>>>
    Which proves that HHH fails to make >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> it. Everyone with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sufficient understanding of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> programming sees that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is not correctly programmed when it >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would end >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> complete its simulation, because HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It turns out that Olcott does not even >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> understand this >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> negatives. HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to simulate itself up to the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So, in other words, Olcott denies verified >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> facts.
    HHH generates false negatives, as is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified in
                  int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main); >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>               } >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it.
    He lacks the ability to accept simple >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts, which >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> he tries to hide with a lot of irrelevant >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> words.
    It is a verified fact that main cannot >>>>>>>>>>>>>>>>>>>>>>>>>>>>> possibly be correctly >>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself
    correctly.
    If this was true then you could point out >>>>>>>>>>>>>>>>>>>>>>>>>>> exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and >>>>>>>>>>>>>>>>>>>>>>>>>> return the
    correct value.
    The directly executed HHH(DD) always halts and >>>>>>>>>>>>>>>>>>>>>>>>> returns a correct
    value as soon as it correctly determines that >>>>>>>>>>>>>>>>>>>>>>>>> its input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH >>>>>>>>>>>>>>>>>>>>>>>> halts according
    to spec, so does the inner, because it is the >>>>>>>>>>>>>>>>>>>>>>>> same. Therefore it
    can’t report „non-halting” and be correct. If >>>>>>>>>>>>>>>>>>>>>>>> the inner HHH
    doesn’t halt, it is not a decider. >>>>>>>>>>>>>>>>>>> I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject >>>>>>>>>>>>>>>>>> corrections.
    I reject infinite deflection away from the point. The >>>>>>>>>>>>>>>>> absolute
    single-mined focus point is that DD correctly simulated >>>>>>>>>>>>>>>>> by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH. >>>>>>>>>>>>>>>>
    Since there is a 5% chance that the treatment I will >>>>>>>>>>>>>>>>> have next month
    will kill me and this treatment is my only good chance >>>>>>>>>>>>>>>>> I will totally
    ignore anything that diverges from the point. >>>>>>>>>>>>>>>> Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows >>>>>>>>>>>>>>> that DD correctly simulated by HHH cannot possibly >>>>>>>>>>>>>>> terminate normally.

    Indeed, which shows the limitation of HHH which makes that >>>>>>>>>>>>>> it cannot properly decide about its input, because  it >>>>>>>>>>>>>> must abort the correct simulation before it sees that the >>>>>>>>>>>>>> correct simulation terminates normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS >>>>>>>>>>>>> INPUT.

    If I close my eyes, so that I do not see the accident, I >>>>>>>>>>>> cannot claim that the accident did not happen. That is the >>>>>>>>>>>> reasoning of a 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior >>>>>>>>>>> that it specifies. This behavior does include DD repeatedly >>>>>>>>>>> calling HHH(DD)
    in recursive simulation that that cannot possibly terminate >>>>>>>>>>> normally.

    Olcott is again dreaming of a HHH that does not abort. Dreams >>>>>>>>>> are no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes and >>>>>>>>>> does not see that the simulated HHH also aborts so that the >>>>>>>>>> program terminates normally.


    It is only your lack of technical competence that makes it seem >>>>>>>>> that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not see >>>>>>>> that the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly >>>>>>> get to the point where it sees that it needs to abort because it >>>>>>> is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point where the
    simulated HHH aborts and halts. The simulating misses in this way
    relevant details of the program given in its input. That is the
    reason why it fails. It is unable to see the whole input, because
    it gets stuck in recursive simulation of itself.


    This is all moot because the executed HHH recognizes this
    pattern and correctly reports that its input cannot possibly
    terminate normally.


    It only reports that the simulation was aborted. Not more, not less.

    That you do not understand the term: "terminates normally"
    is far less than no rebuttal at all.


    So we (Olcott and me) agree that HHH cannot possibly simulate up to
    the normal termination of the program described by the finite string.

    Good.

    However, Olcott fails to see that it is a failure of HHH to be unable
    to simulate a halting program up to the end.


    What most everyone fails to understand is that the inability to
    accomplish the logically impossible is never any actual sort of failure.

    Olcott fails to see that, even the logically impossible is impossible.
    He thinks that he can claim that it is possible by changing the definitions.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Mon Feb 17 21:16:46 2025
    Op 17.feb.2025 om 18:11 schreef olcott:
    On 2/17/2025 9:43 AM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 15:06 schreef olcott:
    On 2/17/2025 2:59 AM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 23:00 schreef olcott:
    On 2/16/2025 2:16 PM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 5:16 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Bonita Montero >>>>>>>>>>>>>>>>>>
    Which proves that HHH fails to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> make a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> see it. Everyone with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sufficient understanding of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> programming sees that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is not correctly programmed when >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> it aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would end >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> complete its simulation, because HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It turns out that Olcott does not even >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> understand this >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> negatives. HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to simulate itself up to the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So, in other words, Olcott denies >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified in
                  int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main);
                  } >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> He lacks the ability to accept simple >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts, which >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> he tries to hide with a lot of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> irrelevant words. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> possibly be correctly >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulated by HHH until its normal >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> termination.
    Indeed, which proves that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself
    correctly.
    If this was true then you could point out >>>>>>>>>>>>>>>>>>>>>>>>>>>>> exactly where HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. halt >>>>>>>>>>>>>>>>>>>>>>>>>>>> and return the
    correct value.
    The directly executed HHH(DD) always halts >>>>>>>>>>>>>>>>>>>>>>>>>>> and returns a correct
    value as soon as it correctly determines that >>>>>>>>>>>>>>>>>>>>>>>>>>> its input cannot
    possibly terminate normally. >>>>>>>>>>>>>>>>>>>>>>>>>> We were talking about HHH(HHH). If the outer >>>>>>>>>>>>>>>>>>>>>>>>>> HHH halts according
    to spec, so does the inner, because it is the >>>>>>>>>>>>>>>>>>>>>>>>>> same. Therefore it
    can’t report „non-halting” and be correct. If >>>>>>>>>>>>>>>>>>>>>>>>>> the inner HHH
    doesn’t halt, it is not a decider. >>>>>>>>>>>>>>>>>>>>> I am not going to ever talk about that. >>>>>>>>>>>>>>>>>>>> Oh goody, you’re never getting anywhere if you >>>>>>>>>>>>>>>>>>>> reject corrections.
    I reject infinite deflection away from the point. The >>>>>>>>>>>>>>>>>>> absolute
    single-mined focus point is that DD correctly >>>>>>>>>>>>>>>>>>> simulated by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH. >>>>>>>>>>>>>>>>>>
    Since there is a 5% chance that the treatment I will >>>>>>>>>>>>>>>>>>> have next month
    will kill me and this treatment is my only good >>>>>>>>>>>>>>>>>>> chance I will totally
    ignore anything that diverges from the point. >>>>>>>>>>>>>>>>>> Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows >>>>>>>>>>>>>>>>> that DD correctly simulated by HHH cannot possibly >>>>>>>>>>>>>>>>> terminate normally.

    Indeed, which shows the limitation of HHH which makes >>>>>>>>>>>>>>>> that it cannot properly decide about its input, because >>>>>>>>>>>>>>>> it must abort the correct simulation before it sees that >>>>>>>>>>>>>>>> the correct simulation terminates normally.


    The correct simulation is only the one that it sees >>>>>>>>>>>>>>> by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS >>>>>>>>>>>>>>> INPUT.

    If I close my eyes, so that I do not see the accident, I >>>>>>>>>>>>>> cannot claim that the accident did not happen. That is the >>>>>>>>>>>>>> reasoning of a 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior >>>>>>>>>>>>> that it specifies. This behavior does include DD repeatedly >>>>>>>>>>>>> calling HHH(DD)
    in recursive simulation that that cannot possibly terminate >>>>>>>>>>>>> normally.

    Olcott is again dreaming of a HHH that does not abort. >>>>>>>>>>>> Dreams are no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes >>>>>>>>>>>> and does not see that the simulated HHH also aborts so that >>>>>>>>>>>> the program terminates normally.


    It is only your lack of technical competence that makes it >>>>>>>>>>> seem that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not >>>>>>>>>> see that the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly >>>>>>>>> get to the point where it sees that it needs to abort because it >>>>>>>>> is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point where
    the simulated HHH aborts and halts. The simulating misses in
    this way relevant details of the program given in its input.
    That is the reason why it fails. It is unable to see the whole >>>>>>>> input, because it gets stuck in recursive simulation of itself. >>>>>>>>

    This is all moot because the executed HHH recognizes this
    pattern and correctly reports that its input cannot possibly
    terminate normally.


    It only reports that the simulation was aborted. Not more, not less. >>>>>
    That you do not understand the term: "terminates normally"
    is far less than no rebuttal at all.


    So we (Olcott and me) agree that HHH cannot possibly simulate up to
    the normal termination of the program described by the finite string.

    Good.

    However, Olcott fails to see that it is a failure of HHH to be
    unable to simulate a halting program up to the end.


    What most everyone fails to understand is that the inability to
    accomplish the logically impossible is never any actual sort of failure. >>>
    Olcott fails to see that, even the logically impossible is impossible.
    He thinks that he can claim that it is possible by changing the
    definitions.

    When the problem definition is specify the algorithm
    for correctly encoding a correct geometric square circle
    then rejecting the original problem definition is the only
    correct option.

    The inability to correctly encode such as algorithm
    places no actual limit on computation.


    So, Olcott thinks that by changing the definitions he can create an
    algorithm to encode a correct geometric square circle and that in this
    way he solved the problem.

    The proven halting theorem tells that it is logically impossible to
    create a decider. Olcott thinks that by changing the definitions he can
    create such a decider.

    See the isomorphism?

    What is wrong with proving that something is logically impossible?
    Does olcott have an allergy against things that are logically impossible?

    Of course logically impossible things cause limitations. One limit is
    that the surface of a square circle cannot be computed.
    That a halting decider is logically impossible creates the limit that
    not every halting question is computable.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Feb 17 19:50:08 2025
    On 2/17/25 9:06 AM, olcott wrote:
    On 2/17/2025 2:59 AM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 23:00 schreef olcott:
    On 2/16/2025 2:16 PM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott: >>>>>>>>>>>>>>>>> On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote:
    Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote:
    Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 6:52 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 5:16 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Bonita Montero >>>>>>>>>>>>>>>>
    Which proves that HHH fails to make >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to see >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> it. Everyone with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sufficient understanding of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> programming sees that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is not correctly programmed when it >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would end >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows that >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> complete its simulation, because HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It turns out that Olcott does not even >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> understand this >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> negatives. HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to simulate itself up to the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So, in other words, Olcott denies verified >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> facts.
    HHH generates false negatives, as is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified in
                  int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main); >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>               } >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it.
    He lacks the ability to accept simple >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts, which >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> he tries to hide with a lot of irrelevant >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> words.
    It is a verified fact that main cannot >>>>>>>>>>>>>>>>>>>>>>>>>>>>> possibly be correctly >>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulated by HHH until its normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself
    correctly.
    If this was true then you could point out >>>>>>>>>>>>>>>>>>>>>>>>>>> exactly where HHH is
    incorrect.
    HHH is supposed to be a decider, i.e. halt and >>>>>>>>>>>>>>>>>>>>>>>>>> return the
    correct value.
    The directly executed HHH(DD) always halts and >>>>>>>>>>>>>>>>>>>>>>>>> returns a correct
    value as soon as it correctly determines that >>>>>>>>>>>>>>>>>>>>>>>>> its input cannot
    possibly terminate normally.
    We were talking about HHH(HHH). If the outer HHH >>>>>>>>>>>>>>>>>>>>>>>> halts according
    to spec, so does the inner, because it is the >>>>>>>>>>>>>>>>>>>>>>>> same. Therefore it
    can’t report „non-halting” and be correct. If >>>>>>>>>>>>>>>>>>>>>>>> the inner HHH
    doesn’t halt, it is not a decider. >>>>>>>>>>>>>>>>>>> I am not going to ever talk about that.
    Oh goody, you’re never getting anywhere if you reject >>>>>>>>>>>>>>>>>> corrections.
    I reject infinite deflection away from the point. The >>>>>>>>>>>>>>>>> absolute
    single-mined focus point is that DD correctly simulated >>>>>>>>>>>>>>>>> by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH. >>>>>>>>>>>>>>>>
    Since there is a 5% chance that the treatment I will >>>>>>>>>>>>>>>>> have next month
    will kill me and this treatment is my only good chance >>>>>>>>>>>>>>>>> I will totally
    ignore anything that diverges from the point. >>>>>>>>>>>>>>>> Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows >>>>>>>>>>>>>>> that DD correctly simulated by HHH cannot possibly >>>>>>>>>>>>>>> terminate normally.

    Indeed, which shows the limitation of HHH which makes that >>>>>>>>>>>>>> it cannot properly decide about its input, because  it >>>>>>>>>>>>>> must abort the correct simulation before it sees that the >>>>>>>>>>>>>> correct simulation terminates normally.


    The correct simulation is only the one that it sees
    by definition. it maps ITS INPUT TO THE BEHAVIOR OF THIS >>>>>>>>>>>>> INPUT.

    If I close my eyes, so that I do not see the accident, I >>>>>>>>>>>> cannot claim that the accident did not happen. That is the >>>>>>>>>>>> reasoning of a 2 years old child.

    HHH(DD) maps the finite string input of DD to the behavior >>>>>>>>>>> that it specifies. This behavior does include DD repeatedly >>>>>>>>>>> calling HHH(DD)
    in recursive simulation that that cannot possibly terminate >>>>>>>>>>> normally.

    Olcott is again dreaming of a HHH that does not abort. Dreams >>>>>>>>>> are no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes and >>>>>>>>>> does not see that the simulated HHH also aborts so that the >>>>>>>>>> program terminates normally.


    It is only your lack of technical competence that makes it seem >>>>>>>>> that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not see >>>>>>>> that the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't possibly >>>>>>> get to the point where it sees that it needs to abort because it >>>>>>> is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point where the
    simulated HHH aborts and halts. The simulating misses in this way
    relevant details of the program given in its input. That is the
    reason why it fails. It is unable to see the whole input, because
    it gets stuck in recursive simulation of itself.


    This is all moot because the executed HHH recognizes this
    pattern and correctly reports that its input cannot possibly
    terminate normally.


    It only reports that the simulation was aborted. Not more, not less.

    That you do not understand the term: "terminates normally"
    is far less than no rebuttal at all.


    So we (Olcott and me) agree that HHH cannot possibly simulate up to
    the normal termination of the program described by the finite string.

    Good.

    However, Olcott fails to see that it is a failure of HHH to be unable
    to simulate a halting program up to the end.


    What most everyone fails to understand is that the inability to
    accomplish the logically impossible is never any actual sort of failure.

    Except to claims that it was possible to do.


    In his citation he deleted my suggestion to change his simulator.

    To the best of my knowledge any change would be erroneous.

    Then why do you do it.

    HHH aborts its simulation.

    Thus, DD calls the HHH that aborts, and thus WILL return 0 to DD if
    simulated correctly.

    And thus DD can not be correctly determined to not halt.

    The fact that HHH makes an error and this that its decision was correct, doesn't make it correct.


    Instead of aborting the simulation at the call to HHH, he could
    replace this call with the correct return value of HHH

    If you understand this code then you can see that this is is not what
    the code itself specifies.

    Which isn't a full specification of DD, until you include the full
    definition of HHH,


    int DD()
    {
      int Halt_Status = HHH(DD);
      if (Halt_Status)
        HERE: goto HERE;
      return Halt_Status;
    }

    int main()
    {
      HHH(DD);
    }

    HHH[0] simulates DD[0]
    that calls HHH[1] on its line 1 to simulate DD[1]
    that calls HHH[2] on its line 1 to simulate DD[2]
    that calls HHH[3] on its line 1 to simulate DD[3]...

    ANd if that is what happens, then HHH will NEVER abort its simulation,
    and thus never returns an answer and fails to be a decider.

    HHH can't be two different programs at once.


    (which he seems to know) and then continue the simulation of DD. This
    avoids the recursion introduced by the simulator.

    We cannot simply ignore the call to HHH(DD) from DD
    and replace this call with different code and construe
    this as a correct simulation.

    Right, and that call will do exactly what the top level HHH(DD) does, so
    if the top level HHH(DD) aborts and returns, then the CORRECT simulation
    of the call to HHH(DD) will also do that, so HHH is just incorrect to
    presume that it won't.

    *THAT* is the presumption that this call does something different that
    what it does.


    *Here is what you seem to be saying, HHH changes this code*
    int DD()
    {
      int Halt_Status = HHH(DD);
      if (Halt_Status)
        HERE: goto HERE;
      return Halt_Status;
    }

    *To this code*
    int DD()
    {
      return 1;
      if (Halt_Status)
        HERE: goto HERE;
      return Halt_Status;
    }



    No, but if HHH(DD) returns 0, then the code woould be isomorphic in
    behavior to your second (with the 1 changed to a 0).

    The fact that HHH can't do the correct simulation, because it was
    programmed to abort (incorrectly) at that point, isn't the fault of DD,
    but just shows that the programmer of HHH didn't know what they were doing.

    Sorry, you are just proving your total ignorance of the basic of
    computer science.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Feb 17 19:51:20 2025
    On 2/17/25 3:25 PM, olcott wrote:
    On 2/17/2025 2:16 PM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 18:11 schreef olcott:
    On 2/17/2025 9:43 AM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 15:06 schreef olcott:
    On 2/17/2025 2:59 AM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 23:00 schreef olcott:
    On 2/16/2025 2:16 PM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote:
    Op 13.feb.2025 om 13:31 schreef olcott:
    On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>> On 2/11/2025 2:05 PM, joes wrote:
    Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 6:52 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 5:16 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Sun, 09 Feb 2025 13:54:39 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Op 09.feb.2025 om 16:18 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>
    Which proves that HHH fails to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> make a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> see it. Everyone with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sufficient understanding of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> programming sees that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is not correctly programmed when >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> it aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would end >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> complete its simulation, because >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It turns out that Olcott does not >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> even understand this >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simple proof that HHH produces false >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> negatives. HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to simulate itself up to the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So, in other words, Olcott denies >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified in >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>               int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main);
                  } >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> He lacks the ability to accept simple >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts, which >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> he tries to hide with a lot of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> irrelevant words. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> possibly be correctly >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulated by HHH until its normal >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> termination.
    Indeed, which proves that HHH is unable >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> to simulate itself >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correctly.
    If this was true then you could point out >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> exactly where HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. halt >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> and return the
    correct value.
    The directly executed HHH(DD) always halts >>>>>>>>>>>>>>>>>>>>>>>>>>>>> and returns a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>> value as soon as it correctly determines >>>>>>>>>>>>>>>>>>>>>>>>>>>>> that its input cannot >>>>>>>>>>>>>>>>>>>>>>>>>>>>> possibly terminate normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>> We were talking about HHH(HHH). If the outer >>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH halts according
    to spec, so does the inner, because it is >>>>>>>>>>>>>>>>>>>>>>>>>>>> the same. Therefore it >>>>>>>>>>>>>>>>>>>>>>>>>>>> can’t report „non-halting” and be correct. >>>>>>>>>>>>>>>>>>>>>>>>>>>> If the inner HHH
    doesn’t halt, it is not a decider. >>>>>>>>>>>>>>>>>>>>>>> I am not going to ever talk about that. >>>>>>>>>>>>>>>>>>>>>> Oh goody, you’re never getting anywhere if you >>>>>>>>>>>>>>>>>>>>>> reject corrections.
    I reject infinite deflection away from the point. >>>>>>>>>>>>>>>>>>>>> The absolute
    single-mined focus point is that DD correctly >>>>>>>>>>>>>>>>>>>>> simulated by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH. >>>>>>>>>>>>>>>>>>>>
    Since there is a 5% chance that the treatment I >>>>>>>>>>>>>>>>>>>>> will have next month
    will kill me and this treatment is my only good >>>>>>>>>>>>>>>>>>>>> chance I will totally
    ignore anything that diverges from the point. >>>>>>>>>>>>>>>>>>>> Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well knows >>>>>>>>>>>>>>>>>>> that DD correctly simulated by HHH cannot possibly >>>>>>>>>>>>>>>>>>> terminate normally.

    Indeed, which shows the limitation of HHH which makes >>>>>>>>>>>>>>>>>> that it cannot properly decide about its input, >>>>>>>>>>>>>>>>>> because it must abort the correct simulation before it >>>>>>>>>>>>>>>>>> sees that the correct simulation terminates normally. >>>>>>>>>>>>>>>>>>

    The correct simulation is only the one that it sees >>>>>>>>>>>>>>>>> by definition. it maps ITS INPUT TO THE BEHAVIOR OF >>>>>>>>>>>>>>>>> THIS INPUT.

    If I close my eyes, so that I do not see the accident, I >>>>>>>>>>>>>>>> cannot claim that the accident did not happen. That is >>>>>>>>>>>>>>>> the reasoning of a 2 years old child.

    HHH(DD) maps the finite string input of DD to the >>>>>>>>>>>>>>> behavior that it specifies. This behavior does include DD >>>>>>>>>>>>>>> repeatedly calling HHH(DD)
    in recursive simulation that that cannot possibly >>>>>>>>>>>>>>> terminate normally.

    Olcott is again dreaming of a HHH that does not abort. >>>>>>>>>>>>>> Dreams are no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes >>>>>>>>>>>>>> and does not see that the simulated HHH also aborts so >>>>>>>>>>>>>> that the program terminates normally.


    It is only your lack of technical competence that makes it >>>>>>>>>>>>> seem that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation
    of none of them do.
    Which does not change the fact that simulating HHH does not >>>>>>>>>>>> see that the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't >>>>>>>>>>> possibly
    get to the point where it sees that it needs to abort because it >>>>>>>>>>> is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point where >>>>>>>>>> the simulated HHH aborts and halts. The simulating misses in >>>>>>>>>> this way relevant details of the program given in its input. >>>>>>>>>> That is the reason why it fails. It is unable to see the whole >>>>>>>>>> input, because it gets stuck in recursive simulation of itself. >>>>>>>>>>

    This is all moot because the executed HHH recognizes this
    pattern and correctly reports that its input cannot possibly >>>>>>>>> terminate normally.


    It only reports that the simulation was aborted. Not more, not >>>>>>>> less.

    That you do not understand the term: "terminates normally"
    is far less than no rebuttal at all.


    So we (Olcott and me) agree that HHH cannot possibly simulate up
    to the normal termination of the program described by the finite
    string.

    Good.

    However, Olcott fails to see that it is a failure of HHH to be
    unable to simulate a halting program up to the end.


    What most everyone fails to understand is that the inability to
    accomplish the logically impossible is never any actual sort of
    failure.

    Olcott fails to see that, even the logically impossible is
    impossible. He thinks that he can claim that it is possible by
    changing the definitions.

    When the problem definition is specify the algorithm
    for correctly encoding a correct geometric square circle
    then rejecting the original problem definition is the only
    correct option.

    The inability to correctly encode such as algorithm
    places no actual limit on computation.


    So, Olcott thinks that by changing the definitions he can create an
    algorithm to encode a correct geometric square circle

    *I didn't say anything like that*
    That you said that did does not seem like any honest mistake.


    But it is just as isomorphic to what you said as your "termination
    analyzer" is to the Halting Problem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Feb 17 23:16:09 2025
    On 2/17/25 10:54 PM, olcott wrote:
    On 2/17/2025 6:51 PM, Richard Damon wrote:
    On 2/17/25 3:25 PM, olcott wrote:
    On 2/17/2025 2:16 PM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 18:11 schreef olcott:
    On 2/17/2025 9:43 AM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 15:06 schreef olcott:
    On 2/17/2025 2:59 AM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 23:00 schreef olcott:
    On 2/16/2025 2:16 PM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 13.feb.2025 om 13:31 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/11/2025 2:05 PM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 2:48 PM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 6:52 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 5:16 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Sun, 09 Feb 2025 13:54:39 -0600 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>
    Which proves that HHH fails to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> make a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> to see it. Everyone with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sufficient understanding of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> programming sees that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is not correctly programmed >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> when it aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> end normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> complete its simulation, because >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It turns out that Olcott does not >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> even understand this >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simple proof that HHH produces >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> false negatives. HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to simulate itself up to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So, in other words, Olcott denies >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified in >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>               int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main);
                  } >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> He lacks the ability to accept >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simple verified facts, which >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> he tries to hide with a lot of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> irrelevant words. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It is a verified fact that main >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> cannot possibly be correctly >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulated by HHH until its normal >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to simulate itself >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correctly.
    If this was true then you could point >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> out exactly where HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> halt and return the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> halts and returns a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> value as soon as it correctly determines >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that its input cannot >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> possibly terminate normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> We were talking about HHH(HHH). If the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> outer HHH halts according >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> to spec, so does the inner, because it is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the same. Therefore it >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> can’t report „non-halting” and be correct. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> If the inner HHH
    doesn’t halt, it is not a decider. >>>>>>>>>>>>>>>>>>>>>>>>> I am not going to ever talk about that. >>>>>>>>>>>>>>>>>>>>>>>> Oh goody, you’re never getting anywhere if you >>>>>>>>>>>>>>>>>>>>>>>> reject corrections.
    I reject infinite deflection away from the point. >>>>>>>>>>>>>>>>>>>>>>> The absolute
    single-mined focus point is that DD correctly >>>>>>>>>>>>>>>>>>>>>>> simulated by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call >>>>>>>>>>>>>>>>>>>>>> HHH.

    Since there is a 5% chance that the treatment I >>>>>>>>>>>>>>>>>>>>>>> will have next month
    will kill me and this treatment is my only good >>>>>>>>>>>>>>>>>>>>>>> chance I will totally
    ignore anything that diverges from the point. >>>>>>>>>>>>>>>>>>>>>> Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well >>>>>>>>>>>>>>>>>>>>> knows
    that DD correctly simulated by HHH cannot possibly >>>>>>>>>>>>>>>>>>>>> terminate normally.

    Indeed, which shows the limitation of HHH which >>>>>>>>>>>>>>>>>>>> makes that it cannot properly decide about its >>>>>>>>>>>>>>>>>>>> input, because it must abort the correct simulation >>>>>>>>>>>>>>>>>>>> before it sees that the correct simulation >>>>>>>>>>>>>>>>>>>> terminates normally.


    The correct simulation is only the one that it sees >>>>>>>>>>>>>>>>>>> by definition. it maps ITS INPUT TO THE BEHAVIOR OF >>>>>>>>>>>>>>>>>>> THIS INPUT.

    If I close my eyes, so that I do not see the accident, >>>>>>>>>>>>>>>>>> I cannot claim that the accident did not happen. That >>>>>>>>>>>>>>>>>> is the reasoning of a 2 years old child.

    HHH(DD) maps the finite string input of DD to the >>>>>>>>>>>>>>>>> behavior that it specifies. This behavior does include >>>>>>>>>>>>>>>>> DD repeatedly calling HHH(DD)
    in recursive simulation that that cannot possibly >>>>>>>>>>>>>>>>> terminate normally.

    Olcott is again dreaming of a HHH that does not abort. >>>>>>>>>>>>>>>> Dreams are no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its >>>>>>>>>>>>>>>> eyes and does not see that the simulated HHH also aborts >>>>>>>>>>>>>>>> so that the program terminates normally.


    It is only your lack of technical competence that makes >>>>>>>>>>>>>>> it seem that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation >>>>>>>>>>>>>>> of none of them do.
    Which does not change the fact that simulating HHH does >>>>>>>>>>>>>> not see that the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't >>>>>>>>>>>>> possibly
    get to the point where it sees that it needs to abort >>>>>>>>>>>>> because it
    is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point >>>>>>>>>>>> where the simulated HHH aborts and halts. The simulating >>>>>>>>>>>> misses in this way relevant details of the program given in >>>>>>>>>>>> its input. That is the reason why it fails. It is unable to >>>>>>>>>>>> see the whole input, because it gets stuck in recursive >>>>>>>>>>>> simulation of itself.


    This is all moot because the executed HHH recognizes this >>>>>>>>>>> pattern and correctly reports that its input cannot possibly >>>>>>>>>>> terminate normally.


    It only reports that the simulation was aborted. Not more, not >>>>>>>>>> less.

    That you do not understand the term: "terminates normally"
    is far less than no rebuttal at all.


    So we (Olcott and me) agree that HHH cannot possibly simulate up >>>>>>>> to the normal termination of the program described by the finite >>>>>>>> string.

    Good.

    However, Olcott fails to see that it is a failure of HHH to be >>>>>>>> unable to simulate a halting program up to the end.


    What most everyone fails to understand is that the inability to
    accomplish the logically impossible is never any actual sort of
    failure.

    Olcott fails to see that, even the logically impossible is
    impossible. He thinks that he can claim that it is possible by
    changing the definitions.

    When the problem definition is specify the algorithm
    for correctly encoding a correct geometric square circle
    then rejecting the original problem definition is the only
    correct option.

    The inability to correctly encode such as algorithm
    places no actual limit on computation.


    So, Olcott thinks that by changing the definitions he can create an
    algorithm to encode a correct geometric square circle

    *I didn't say anything like that*
    That you said that did does not seem like any honest mistake.


    But it is just as isomorphic to what you said as your "termination
    analyzer" is to the Halting Problem.

    THAT IS NOT THE TOPIC OF THE ABOVE REPLY.



    Of course it is, YOU claim he is wrong because you didn't say what he
    said you implied, but your statement *IS* Isomorphic to it in a sense.

    Your problem is you are just admitting that you "logic" is build on bad analogies and claiming things to be isomorphic to something they are not acutally really like.

    Thus, your claims actually ARE isomorphic to a lot of clearly bad statement.

    THe fact that they don't see so to you, is just the evidence that you
    just flat out don't understand what you are talking about, and don't
    realizer how much you are just admitting to your ignorance, and that
    your claims really are just a FRAUD that you may have even perpetrated
    on yourself.

    The fact you can't see the problems, just agian highlights your stupidity.

    THe fact that you have given up even trying to defend your statements
    with things from actual sources just proves that you understand you have
    no grounds for you claim, but think that by claiming them often enough
    you can make them seem true.

    This again, just highlights how bad your logic is.

    At one point I thought that maybe you had a shread of something behind
    your ideas, but it seems that I was mistaken on that, and you just have
    POOP in your brains, with no really meaning.

    Sorry, but you HAVE destroyed your life and seem to have doomed your
    reputation to that of just being a stupid crank.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Tue Feb 18 10:13:01 2025
    Op 18.feb.2025 om 04:54 schreef olcott:
    On 2/17/2025 6:51 PM, Richard Damon wrote:
    On 2/17/25 3:25 PM, olcott wrote:
    On 2/17/2025 2:16 PM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 18:11 schreef olcott:
    On 2/17/2025 9:43 AM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 15:06 schreef olcott:
    On 2/17/2025 2:59 AM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 23:00 schreef olcott:
    On 2/16/2025 2:16 PM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>> Op 13.feb.2025 om 13:31 schreef olcott: >>>>>>>>>>>>>>>>>>>>> On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>> On 2/11/2025 2:05 PM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>> Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 2:48 PM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 6:52 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 5:16 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Sun, 09 Feb 2025 13:54:39 -0600 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
    Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> PM, Richard Damon >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>>
    Which proves that HHH fails to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> make a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> to see it. Everyone with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sufficient understanding of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> programming sees that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is not correctly programmed >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> when it aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> end normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> complete its simulation, because >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It turns out that Olcott does not >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> even understand this >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simple proof that HHH produces >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> false negatives. HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to simulate itself up to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So, in other words, Olcott denies >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified in >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>               int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main);
                  } >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> He lacks the ability to accept >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simple verified facts, which >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> he tries to hide with a lot of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> irrelevant words. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It is a verified fact that main >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> cannot possibly be correctly >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulated by HHH until its normal >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to simulate itself >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correctly.
    If this was true then you could point >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> out exactly where HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> halt and return the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> halts and returns a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> value as soon as it correctly determines >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that its input cannot >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> possibly terminate normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> We were talking about HHH(HHH). If the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> outer HHH halts according >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> to spec, so does the inner, because it is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the same. Therefore it >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> can’t report „non-halting” and be correct. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> If the inner HHH
    doesn’t halt, it is not a decider. >>>>>>>>>>>>>>>>>>>>>>>>> I am not going to ever talk about that. >>>>>>>>>>>>>>>>>>>>>>>> Oh goody, you’re never getting anywhere if you >>>>>>>>>>>>>>>>>>>>>>>> reject corrections.
    I reject infinite deflection away from the point. >>>>>>>>>>>>>>>>>>>>>>> The absolute
    single-mined focus point is that DD correctly >>>>>>>>>>>>>>>>>>>>>>> simulated by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call >>>>>>>>>>>>>>>>>>>>>> HHH.

    Since there is a 5% chance that the treatment I >>>>>>>>>>>>>>>>>>>>>>> will have next month
    will kill me and this treatment is my only good >>>>>>>>>>>>>>>>>>>>>>> chance I will totally
    ignore anything that diverges from the point. >>>>>>>>>>>>>>>>>>>>>> Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well >>>>>>>>>>>>>>>>>>>>> knows
    that DD correctly simulated by HHH cannot possibly >>>>>>>>>>>>>>>>>>>>> terminate normally.

    Indeed, which shows the limitation of HHH which >>>>>>>>>>>>>>>>>>>> makes that it cannot properly decide about its >>>>>>>>>>>>>>>>>>>> input, because it must abort the correct simulation >>>>>>>>>>>>>>>>>>>> before it sees that the correct simulation >>>>>>>>>>>>>>>>>>>> terminates normally.


    The correct simulation is only the one that it sees >>>>>>>>>>>>>>>>>>> by definition. it maps ITS INPUT TO THE BEHAVIOR OF >>>>>>>>>>>>>>>>>>> THIS INPUT.

    If I close my eyes, so that I do not see the accident, >>>>>>>>>>>>>>>>>> I cannot claim that the accident did not happen. That >>>>>>>>>>>>>>>>>> is the reasoning of a 2 years old child.

    HHH(DD) maps the finite string input of DD to the >>>>>>>>>>>>>>>>> behavior that it specifies. This behavior does include >>>>>>>>>>>>>>>>> DD repeatedly calling HHH(DD)
    in recursive simulation that that cannot possibly >>>>>>>>>>>>>>>>> terminate normally.

    Olcott is again dreaming of a HHH that does not abort. >>>>>>>>>>>>>>>> Dreams are no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its >>>>>>>>>>>>>>>> eyes and does not see that the simulated HHH also aborts >>>>>>>>>>>>>>>> so that the program terminates normally.


    It is only your lack of technical competence that makes >>>>>>>>>>>>>>> it seem that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation >>>>>>>>>>>>>>> of none of them do.
    Which does not change the fact that simulating HHH does >>>>>>>>>>>>>> not see that the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't >>>>>>>>>>>>> possibly
    get to the point where it sees that it needs to abort >>>>>>>>>>>>> because it
    is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point >>>>>>>>>>>> where the simulated HHH aborts and halts. The simulating >>>>>>>>>>>> misses in this way relevant details of the program given in >>>>>>>>>>>> its input. That is the reason why it fails. It is unable to >>>>>>>>>>>> see the whole input, because it gets stuck in recursive >>>>>>>>>>>> simulation of itself.


    This is all moot because the executed HHH recognizes this >>>>>>>>>>> pattern and correctly reports that its input cannot possibly >>>>>>>>>>> terminate normally.


    It only reports that the simulation was aborted. Not more, not >>>>>>>>>> less.

    That you do not understand the term: "terminates normally"
    is far less than no rebuttal at all.


    So we (Olcott and me) agree that HHH cannot possibly simulate up >>>>>>>> to the normal termination of the program described by the finite >>>>>>>> string.

    Good.

    However, Olcott fails to see that it is a failure of HHH to be >>>>>>>> unable to simulate a halting program up to the end.


    What most everyone fails to understand is that the inability to
    accomplish the logically impossible is never any actual sort of
    failure.

    Olcott fails to see that, even the logically impossible is
    impossible. He thinks that he can claim that it is possible by
    changing the definitions.

    When the problem definition is specify the algorithm
    for correctly encoding a correct geometric square circle
    then rejecting the original problem definition is the only
    correct option.

    The inability to correctly encode such as algorithm
    places no actual limit on computation.


    So, Olcott thinks that by changing the definitions he can create an
    algorithm to encode a correct geometric square circle

    *I didn't say anything like that*
    That you said that did does not seem like any honest mistake.


    But it is just as isomorphic to what you said as your "termination
    analyzer" is to the Halting Problem.

    THAT IS NOT THE TOPIC OF THE ABOVE REPLY.
    Yes it is, but Olcott removed most of my reply in his citation, where I described how they are isomorphic.
    Is is stupid or dishonest to remove important words from a reply and
    then claim that it is not the topic of the reply?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Tue Feb 18 10:08:22 2025
    Op 18.feb.2025 om 01:51 schreef Richard Damon:
    On 2/17/25 3:25 PM, olcott wrote:
    On 2/17/2025 2:16 PM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 18:11 schreef olcott:
    On 2/17/2025 9:43 AM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 15:06 schreef olcott:
    On 2/17/2025 2:59 AM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 23:00 schreef olcott:
    On 2/16/2025 2:16 PM, Fred. Zwarts wrote:
    Op 16.feb.2025 om 13:58 schreef olcott:
    On 2/16/2025 3:44 AM, Fred. Zwarts wrote:
    Op 15.feb.2025 om 20:21 schreef olcott:
    On 2/15/2025 2:06 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 22:18 schreef olcott:
    On 2/14/2025 8:01 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 13:48 schreef olcott:
    On 2/14/2025 3:53 AM, Fred. Zwarts wrote:
    Op 14.feb.2025 om 01:12 schreef olcott:
    On 2/13/2025 8:47 AM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>> Op 13.feb.2025 om 13:31 schreef olcott: >>>>>>>>>>>>>>>>>>>> On 2/13/2025 3:16 AM, joes wrote:
    Am Wed, 12 Feb 2025 22:18:32 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>> On 2/11/2025 2:05 PM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>> Am Tue, 11 Feb 2025 10:19:11 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>> On 2/11/2025 9:23 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 15:38:37 -0600 schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>> On 2/10/2025 2:48 PM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 08:46:21 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 6:52 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Mon, 10 Feb 2025 06:02:48 -0600 schrieb >>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott:
    On 2/10/2025 5:16 AM, joes wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Am Sun, 09 Feb 2025 13:54:39 -0600 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schrieb olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 1:33 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 20:04 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 12:54 PM, Fred. Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 18:00 schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 10:50 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 16:18 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/9/2025 2:13 AM, Fred. Zwarts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 09.feb.2025 om 07:10 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:54 PM, Fred. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 15:47 schreef >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/8/2025 3:57 AM, Fred. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Zwarts wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Op 08.feb.2025 om 06:53 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schreef olcott: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 7:27 PM, Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 8:12 PM, olcott >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 5:56 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/25 11:26 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/7/2025 6:20 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 10:02 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 8:21 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 5:18 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 1:51 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Damon wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/25 1:26 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> olcott wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 2/6/2025 10:52 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> AM, Bonita Montero >>>>>>>>>>>>>>>>>>>>>
    Which proves that HHH fails to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> make a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> decision about DD's halting >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> behaviour. All other >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> methods (direct execution, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulation by a world class >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulator, etc.) show >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that DD halts. But HHH fails to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> see it. Everyone with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sufficient understanding of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> programming sees that HHH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is not correctly programmed >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> when it aborts one cycle >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before the simulation would end >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The execution trace only shows >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> complete its simulation, because >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH is unable to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulate itself. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It turns out that Olcott does not >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> even understand this >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simple proof that HHH produces >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> false negatives. HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> unable to simulate itself up to the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> normal termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So, in other words, Olcott denies >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HHH generates false negatives, as is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified in >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>               int main() { >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>                 return HHH(main);
                  } >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> but he denies it. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> He lacks the ability to accept simple >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> verified facts, which >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> he tries to hide with a lot of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> irrelevant words. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> It is a verified fact that main cannot >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> possibly be correctly >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> simulated by HHH until its normal >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> termination. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Indeed, which proves that HHH is unable >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> to simulate itself >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correctly.
    If this was true then you could point >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> out exactly where HHH is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> incorrect.
    HHH is supposed to be a decider, i.e. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> halt and return the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> correct value.
    The directly executed HHH(DD) always halts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> and returns a correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> value as soon as it correctly determines >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that its input cannot >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> possibly terminate normally. >>>>>>>>>>>>>>>>>>>>>>>>>>>>> We were talking about HHH(HHH). If the >>>>>>>>>>>>>>>>>>>>>>>>>>>>> outer HHH halts according >>>>>>>>>>>>>>>>>>>>>>>>>>>>> to spec, so does the inner, because it is >>>>>>>>>>>>>>>>>>>>>>>>>>>>> the same. Therefore it >>>>>>>>>>>>>>>>>>>>>>>>>>>>> can’t report „non-halting” and be correct. >>>>>>>>>>>>>>>>>>>>>>>>>>>>> If the inner HHH
    doesn’t halt, it is not a decider. >>>>>>>>>>>>>>>>>>>>>>>> I am not going to ever talk about that. >>>>>>>>>>>>>>>>>>>>>>> Oh goody, you’re never getting anywhere if you >>>>>>>>>>>>>>>>>>>>>>> reject corrections.
    I reject infinite deflection away from the point. >>>>>>>>>>>>>>>>>>>>>> The absolute
    single-mined focus point is that DD correctly >>>>>>>>>>>>>>>>>>>>>> simulated by HHH cannot
    possible terminate normally.
    That IS the point. DD does nothing else than call HHH. >>>>>>>>>>>>>>>>>>>>>
    Since there is a 5% chance that the treatment I >>>>>>>>>>>>>>>>>>>>>> will have next month
    will kill me and this treatment is my only good >>>>>>>>>>>>>>>>>>>>>> chance I will totally
    ignore anything that diverges from the point. >>>>>>>>>>>>>>>>>>>>> Ok, I will wait a month then.


    Anyone that knows the C language sufficiently well >>>>>>>>>>>>>>>>>>>> knows
    that DD correctly simulated by HHH cannot possibly >>>>>>>>>>>>>>>>>>>> terminate normally.

    Indeed, which shows the limitation of HHH which makes >>>>>>>>>>>>>>>>>>> that it cannot properly decide about its input, >>>>>>>>>>>>>>>>>>> because it must abort the correct simulation before >>>>>>>>>>>>>>>>>>> it sees that the correct simulation terminates normally. >>>>>>>>>>>>>>>>>>>

    The correct simulation is only the one that it sees >>>>>>>>>>>>>>>>>> by definition. it maps ITS INPUT TO THE BEHAVIOR OF >>>>>>>>>>>>>>>>>> THIS INPUT.

    If I close my eyes, so that I do not see the accident, >>>>>>>>>>>>>>>>> I cannot claim that the accident did not happen. That >>>>>>>>>>>>>>>>> is the reasoning of a 2 years old child.

    HHH(DD) maps the finite string input of DD to the >>>>>>>>>>>>>>>> behavior that it specifies. This behavior does include >>>>>>>>>>>>>>>> DD repeatedly calling HHH(DD)
    in recursive simulation that that cannot possibly >>>>>>>>>>>>>>>> terminate normally.

    Olcott is again dreaming of a HHH that does not abort. >>>>>>>>>>>>>>> Dreams are no substitute for reasoning.

    The simulating HHH aborts the simulation, closes its eyes >>>>>>>>>>>>>>> and does not see that the simulated HHH also aborts so >>>>>>>>>>>>>>> that the program terminates normally.


    It is only your lack of technical competence that makes it >>>>>>>>>>>>>> seem that
    (a) The simulated HHH aborts its simulation
    after itself is no longer being simulated.

    (b) Either the outermost HHH aborts its simulation >>>>>>>>>>>>>> of none of them do.
    Which does not change the fact that simulating HHH does not >>>>>>>>>>>>> see that the simulated HHH would also abort,

    The simulated HHH cannot possibly abort because it can't >>>>>>>>>>>> possibly
    get to the point where it sees that it needs to abort
    because it
    is aborted before it gets to this point.

    Exactly! So the simulating HHH fails to reach the point where >>>>>>>>>>> the simulated HHH aborts and halts. The simulating misses in >>>>>>>>>>> this way relevant details of the program given in its input. >>>>>>>>>>> That is the reason why it fails. It is unable to see the >>>>>>>>>>> whole input, because it gets stuck in recursive simulation of >>>>>>>>>>> itself.


    This is all moot because the executed HHH recognizes this
    pattern and correctly reports that its input cannot possibly >>>>>>>>>> terminate normally.


    It only reports that the simulation was aborted. Not more, not >>>>>>>>> less.

    That you do not understand the term: "terminates normally"
    is far less than no rebuttal at all.


    So we (Olcott and me) agree that HHH cannot possibly simulate up >>>>>>> to the normal termination of the program described by the finite >>>>>>> string.

    Good.

    However, Olcott fails to see that it is a failure of HHH to be
    unable to simulate a halting program up to the end.


    What most everyone fails to understand is that the inability to
    accomplish the logically impossible is never any actual sort of
    failure.

    Olcott fails to see that, even the logically impossible is
    impossible. He thinks that he can claim that it is possible by
    changing the definitions.

    When the problem definition is specify the algorithm
    for correctly encoding a correct geometric square circle
    then rejecting the original problem definition is the only
    correct option.

    The inability to correctly encode such as algorithm
    places no actual limit on computation.


    So, Olcott thinks that by changing the definitions he can create an
    algorithm to encode a correct geometric square circle

    *I didn't say anything like that*
    That you said that did does not seem like any honest mistake.


    But it is just as isomorphic to what you said as your "termination
    analyzer" is to the Halting Problem.

    Indeed, that is what I said in other words. That is not obvious from the
    above, because Olcott removed most of the words I said from his
    citation, so that my words are now out of context.
    Is that stupid or dishonest?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Feb 18 07:25:15 2025
    On 2/18/25 12:04 AM, olcott wrote:
    On 2/17/2025 10:16 PM, Richard Damon wrote:
    On 2/17/25 10:54 PM, olcott wrote:
    On 2/17/2025 6:51 PM, Richard Damon wrote:
    On 2/17/25 3:25 PM, olcott wrote:
    On 2/17/2025 2:16 PM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 18:11 schreef olcott:
    On 2/17/2025 9:43 AM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 15:06 schreef olcott:

    When the problem definition is specify the algorithm
    for correctly encoding a correct geometric square circle
    then rejecting the original problem definition is the only
    correct option.

    The inability to correctly encode such as algorithm
    places no actual limit on computation.


    So, Olcott thinks that by changing the definitions he can create
    an algorithm to encode a correct geometric square circle

    *I didn't say anything like that*
    That you said that did does not seem like any honest mistake.


    But it is just as isomorphic to what you said as your "termination
    analyzer" is to the Halting Problem.

    THAT IS NOT THE TOPIC OF THE ABOVE REPLY.



    Of course it is, YOU claim he is wrong because you didn't say what he
    said you implied, but your statement *IS* Isomorphic to it in a sense.


    I did not even use the term isomorphic in the above.
    I will start trimming the posts much more.

    No, you complianed about someone else using it to mock your misuse of it elsewhere.

    The problem is your initial statement was based on erroneous
    presumptions, which was being pointed out.


    *Stay within the precise context of my exact reply*

    If it HAD a percise meaning.

    Your problem is you misuse so many words, your statement are often just nonsense.


    The problem of defining the algorithm to encode an actual
    square circle can only be correctly rejected as nonsense.


    But the arguement is in error if the problem was to draw a square with
    the same area as a circle, the classical "Squaring the Circle" problem.

    Your ignorance of what you talk about doesn't make your erroneous
    "isomorphism" (that aren't) valid. It just shows how stupid you are.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Tue Feb 18 13:53:45 2025
    Am Tue, 18 Feb 2025 07:29:55 -0600 schrieb olcott:
    On 2/18/2025 6:25 AM, Richard Damon wrote:
    On 2/18/25 6:22 AM, olcott wrote:

    I am talking about the impossibility of defining an Algorithm to
    correctly encode square circles not placing any limit on computation.

    And who cares about that.

    It is generally the case that problems that are defined to be impossible
    DO NOT EVER ACTUALLY LIMIT COMPUTATION.
    Impossible problems, like halting deciders. Asking for one makes no sense
    the same way that asking for square circles does. Sure, you may be able
    to decide on the halting of infinitely many programs, but there will
    always be inf. many you cannot, among them everything that calls the
    supposed „decider”.

    --
    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 joes@21:1/5 to All on Tue Feb 18 16:51:45 2025
    Am Tue, 18 Feb 2025 10:41:57 -0600 schrieb olcott:
    On 2/18/2025 7:53 AM, joes wrote:
    Am Tue, 18 Feb 2025 07:29:55 -0600 schrieb olcott:
    On 2/18/2025 6:25 AM, Richard Damon wrote:
    On 2/18/25 6:22 AM, olcott wrote:

    I am talking about the impossibility of defining an Algorithm to
    correctly encode square circles not placing any limit on
    computation.

    And who cares about that.

    It is generally the case that problems that are defined to be
    impossible DO NOT EVER ACTUALLY LIMIT COMPUTATION.
    Impossible problems, like halting deciders. Asking for one makes no
    sense the same way that asking for square circles does. Sure, you may
    be able to decide on the halting of infinitely many programs, but there
    will always be inf. many you cannot, among them everything that calls
    the supposed „decider”.

    What no one has ever bothered to notice is that impossible problems do
    not place any actual real limit on computation.
    Well, only if you unfathomably *wanted* a decider.

    --
    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 18 18:37:43 2025
    On 2/18/25 8:27 AM, olcott wrote:
    On 2/18/2025 6:25 AM, Richard Damon wrote:
    On 2/18/25 12:04 AM, olcott wrote:
    On 2/17/2025 10:16 PM, Richard Damon wrote:
    On 2/17/25 10:54 PM, olcott wrote:
    On 2/17/2025 6:51 PM, Richard Damon wrote:
    On 2/17/25 3:25 PM, olcott wrote:
    On 2/17/2025 2:16 PM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 18:11 schreef olcott:
    On 2/17/2025 9:43 AM, Fred. Zwarts wrote:
    Op 17.feb.2025 om 15:06 schreef olcott:

    When the problem definition is specify the algorithm
    for correctly encoding a correct geometric square circle
    then rejecting the original problem definition is the only
    correct option.

    The inability to correctly encode such as algorithm
    places no actual limit on computation.


    So, Olcott thinks that by changing the definitions he can create >>>>>>>> an algorithm to encode a correct geometric square circle

    *I didn't say anything like that*
    That you said that did does not seem like any honest mistake.


    But it is just as isomorphic to what you said as your "termination >>>>>> analyzer" is to the Halting Problem.

    THAT IS NOT THE TOPIC OF THE ABOVE REPLY.



    Of course it is, YOU claim he is wrong because you didn't say what
    he said you implied, but your statement *IS* Isomorphic to it in a
    sense.


    I did not even use the term isomorphic in the above.
    I will start trimming the posts much more.

    No, you complianed about someone else using it to mock your misuse of
    it elsewhere.

    The problem is your initial statement was based on erroneous
    presumptions, which was being pointed out.


    *Stay within the precise context of my exact reply*

    If it HAD a percise meaning.

    Your problem is you misuse so many words, your statement are often
    just nonsense.


    The problem of defining the algorithm to encode an actual
    square circle can only be correctly rejected as nonsense.


    But the arguement is in error if the problem was to draw a square with
    the same area as a circle, the classical "Squaring the Circle" problem.


    I didn't say anything like that either.


    Sure you did, or implied it.

    Or, are you admitting that the Halting Problem isn't based on a nonsense definition.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Feb 18 18:38:34 2025
    On 2/18/25 8:29 AM, olcott wrote:
    On 2/18/2025 6:25 AM, Richard Damon wrote:
    On 2/18/25 6:22 AM, olcott wrote:

    I am talking about the impossibility of defining an Algorithm to
    correctly encode square circles not placing any limit on computation.


    And who cares about that.


    It is generally the case that problems that are defined to be impossible
    DO NOT EVER ACTUALLY LIMIT COMPUTATION.


    Sure they do, they show some things that could never have been computed,
    which is knowledge that wasn't know before the impossibility was known.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Wed Feb 19 07:14:03 2025
    On 2/18/25 11:06 PM, olcott wrote:
    On 2/18/2025 10:51 AM, joes wrote:
    Am Tue, 18 Feb 2025 10:41:57 -0600 schrieb olcott:
    On 2/18/2025 7:53 AM, joes wrote:
    Am Tue, 18 Feb 2025 07:29:55 -0600 schrieb olcott:
    On 2/18/2025 6:25 AM, Richard Damon wrote:
    On 2/18/25 6:22 AM, olcott wrote:

    I am talking about the impossibility of defining an Algorithm to >>>>>>> correctly encode square circles not placing any limit on
    computation.

    And who cares about that.

    It is generally the case that problems that are defined to be
    impossible DO NOT EVER ACTUALLY LIMIT COMPUTATION.
    Impossible problems, like halting deciders. Asking for one makes no
    sense the same way that asking for square circles does. Sure, you may
    be able to decide on the halting of infinitely many programs, but there >>>> will always be inf. many you cannot, among them everything that calls
    the supposed „decider”.
    i
    What no one has ever bothered to notice is that impossible problems do
    not place any actual real limit on computation.
    Well, only if you unfathomably *wanted* a decider.


    Isomorphic to "wanting" a square circle, thus equally ridiculous.


    So, you think wanting a decider is ridiculous?

    I guess you don't want answers, only your lies.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Wed Feb 19 07:12:57 2025
    On 2/18/25 11:41 AM, olcott wrote:
    On 2/18/2025 7:53 AM, joes wrote:
    Am Tue, 18 Feb 2025 07:29:55 -0600 schrieb olcott:
    On 2/18/2025 6:25 AM, Richard Damon wrote:
    On 2/18/25 6:22 AM, olcott wrote:

    I am talking about the impossibility of defining an Algorithm to
    correctly encode square circles not placing any limit on computation. >>>>>
    And who cares about that.

    It is generally the case that problems that are defined to be impossible >>> DO NOT EVER ACTUALLY LIMIT COMPUTATION.
    Impossible problems, like halting deciders. Asking for one makes no sense
    the same way that asking for square circles does. Sure, you may be able
    to decide on the halting of infinitely many programs, but there will
    always be inf. many you cannot, among them everything that calls the
    supposed „decider”.


    What no one has ever bothered to notice is that impossible
    problems do not place any actual real limit on computation.


    Except to add to the knowledge of what can be done.

    As you have been told, but refuse to learn, the Halting Problem was not "designed" to be impossible, but in fact comes out of a chain of ideas
    that would show that logic and mathematics were a complete system, one
    where EVERY true statement could be proven.

    Great minds worked hard to try to prove that, until Turing found this
    simple and obvious (in hindsight) proof that it could not be done.

    So, your premise that the halting problem was designed to be impossible
    is just another of your LIES to support your FRAUD.

    But, you can't look at history, as it shows you are wrong, and you seem
    to think that being ignorant of your error is better than knowing you
    are wrong, because you just can't face the truth. Truth being something
    you just don't understand.

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