• Re: DDD simulated by HHH cannot possibly halt (Halting Problem) --- min

    From Richard Damon@21:1/5 to olcott on Sun Apr 13 19:11:01 2025
    On 4/13/25 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not valid. >>>>>>
    No proof of Peano's axioms or Euclid's fifth postulate has been
    shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER
    proving it (which, as you say, he has not yet done) OR by taking
    it as
    axiomatic, leaving the world of mainstream computer science behind >>>>>> him,
    constructing his own computational 'geometry' so to speak, and
    abandoning any claim to having overturned the Halting Problem. Navel >>>>>> contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he
    wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to stop >>>>> simulating and reject any input that would otherwise prevent its own >>>>> termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input?


    Because that is a STUPID idea and categorically impossible
    because the outermost HHH sees its needs to stop simulating
    before any inner HHH can possibly see this.


    In other words, you agree that Linz and others are correct that no H
    exists that satisfies these requirements:


    Given any algorithm (i.e. a fixed immutable sequence of instructions)
    X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that computes the
    following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly


    No stupid! Those freaking requirements are wrong and
    anchored in the ignorance  of rejecting the notion
    of a simulating termination analyzer OUT-OF-HAND WITHOUT REVIEW.

    No, those "freeking requirement" *ARE* the requirements and show that
    you are just living in a world of make-believe.


    As anyone can see HHH MUST REJECT ITS INPUT OR GET STUPIDLY
    STUCK IN NON-TERMINATION. If people were not mindless robots
    they would have immediately acknowledged this years ago.


    Which just proves that it must be incorrect.

    Sorry, you are just proving that you "logic" things lying is correct
    reasoning.

    This is why it seems you are a 1st class reservation for that lake front property at the bottom of the lake of fire.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Apr 13 20:05:01 2025
    On 4/13/25 7:32 PM, olcott wrote:
    On 4/13/2025 4:03 PM, dbush wrote:
    On 4/13/2025 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not valid. >>>>>>>>
    No proof of Peano's axioms or Euclid's fifth postulate has been >>>>>>>> shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>> proving it (which, as you say, he has not yet done) OR by taking >>>>>>>> it as
    axiomatic, leaving the world of mainstream computer science
    behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>> Navel
    contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>> wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to stop >>>>>>> simulating and reject any input that would otherwise prevent its own >>>>>>> termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input?


    Because that is a STUPID idea and categorically impossible
    because the outermost HHH sees its needs to stop simulating
    before any inner HHH can possibly see this.


    In other words, you agree that Linz and others are correct that no H
    exists that satisfies these requirements:


    Given any algorithm (i.e. a fixed immutable sequence of
    instructions) X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that computes
    the following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly


    No stupid! Those freaking requirements are wrong

    In other words, you have no interest in something that would make all
    truth provable.


    It will remain forever impossible to prove that five minutes
    ago ever existed. This is empirical truth mislabeled as synthetic truth.

    Semantic truth poorly labeled as analytic truth is the only
    truth that is either provable else untrue. It is {provable}
    on the basis of semantic connections to expressions that are
    stipulated as true.


    In other words, you are admitting that you don't understand how Formal
    Logic works, but are confused by the confusions in the broader concepts
    of Philosophy that try to relate logic to reality.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Apr 13 22:28:56 2025
    On 4/13/25 10:11 PM, olcott wrote:
    On 4/13/2025 6:11 PM, Richard Damon wrote:
    On 4/13/25 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not valid. >>>>>>>>
    No proof of Peano's axioms or Euclid's fifth postulate has been >>>>>>>> shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>> proving it (which, as you say, he has not yet done) OR by taking >>>>>>>> it as
    axiomatic, leaving the world of mainstream computer science
    behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>> Navel
    contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>> wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to stop >>>>>>> simulating and reject any input that would otherwise prevent its own >>>>>>> termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input?


    Because that is a STUPID idea and categorically impossible
    because the outermost HHH sees its needs to stop simulating
    before any inner HHH can possibly see this.


    In other words, you agree that Linz and others are correct that no H
    exists that satisfies these requirements:


    Given any algorithm (i.e. a fixed immutable sequence of
    instructions) X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that computes
    the following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly


    No stupid! Those freaking requirements are wrong and*
    anchored in the ignorance  of rejecting the notion
    of a simulating termination analyzer OUT-OF-HAND WITHOUT REVIEW.

    No, those "freeking requirement" *ARE* the requirements


    AND AS STUPID AS {REQUIRING} A GEOMETRIC SQUARE
    CIRCLE IN THE SAME TWO-DIMENSIONAL PLANE.


    Nope.

    Just that you can't tell the difference because you are too stupid.

    The input PROGRAM has definite behavior (and if it isn't a program, then
    it is YOU who has made the category error). This means that the input
    include ALL its code.

    Since it has definite behavior, and then there *IS* a correct answer to
    the question, it just isn't the ONE answer that HHH gives, and if you
    think that this HHH can give different answers, you are just again
    proving you don't understand what you are talking about.

    Your problem is you are just totally ignorant about the meaning of the
    words you are using in the defined context, and you are too stupid to
    try to learn those meanings, because you don't understand what truth means.

    Sorry, but you are just proving how much of a pathological liar you are.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Apr 13 22:25:07 2025
    On 4/13/25 10:09 PM, olcott wrote:
    On 4/13/2025 6:51 PM, dbush wrote:
    On 4/13/2025 7:32 PM, olcott wrote:
    On 4/13/2025 4:03 PM, dbush wrote:
    On 4/13/2025 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>> valid.

    No proof of Peano's axioms or Euclid's fifth postulate has >>>>>>>>>> been shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>>>> proving it (which, as you say, he has not yet done) OR by
    taking it as
    axiomatic, leaving the world of mainstream computer science >>>>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>>>> Navel
    contemplation beckons.
    Axioms are all very well, and he's free to invent as many as >>>>>>>>>> he wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to >>>>>>>>> stop
    simulating and reject any input that would otherwise prevent >>>>>>>>> its own
    termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>

    Because that is a STUPID idea and categorically impossible
    because the outermost HHH sees its needs to stop simulating
    before any inner HHH can possibly see this.


    In other words, you agree that Linz and others are correct that no >>>>>> H exists that satisfies these requirements:


    Given any algorithm (i.e. a fixed immutable sequence of
    instructions) X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that computes
    the following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly


    No stupid! Those freaking requirements are wrong

    In other words, you have no interest in something that would make
    all truth provable.


    It will remain forever impossible to prove that five minutes
    ago ever existed. This is empirical truth mislabeled as synthetic truth. >>>
    Semantic truth poorly labeled as analytic truth is the only
    truth that is either provable else untrue. It is {provable}
    on the basis of semantic connections to expressions that are
    stipulated as true.


    So you do want something that would make all truth provable.  An H
    that meets the following requirements would do that, therefore these
    requirements are not "wrong":


    *Ignorance on your part about this* https://philosophy.stackexchange.com/questions/43748/how-do-we-know- the--wasnt-created-5-minutes-ago#:~:text=Ask%20Question,non- falsifiable%20and%20all).


    Just shows the ignorance on YOUR part, as that is a discussion of
    general philosophy, NOT Formal logic that doesn't have that problem.

    You are just showing you have no idea of what you are talking about.

    Given any algorithm (i.e. a fixed immutable sequence of instructions)
    X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that computes the
    following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly





    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Mon Apr 14 09:25:01 2025
    Am Sun, 13 Apr 2025 21:11:56 -0500 schrieb olcott:
    On 4/13/2025 6:11 PM, Richard Damon wrote:
    On 4/13/25 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>> proving it (which, as you say, he has not yet done) OR by taking >>>>>>>> it as axiomatic, leaving the world of mainstream computer science >>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>> wishes, but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to
    stop simulating and reject any input that would otherwise prevent >>>>>>> its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input?

    Because that is a STUPID idea and categorically impossible because
    the outermost HHH sees its needs to stop simulating before any inner >>>>> HHH can possibly see this.

    In other words, you agree that Linz and others are correct that no H
    exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of instructions)
    X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly

    No stupid! Those freaking requirements are wrong and*
    anchored in the ignorance  of rejecting the notion of a simulating
    termination analyzer OUT-OF-HAND WITHOUT REVIEW.
    No, those "freeking requirement" *ARE* the requirements
    AND AS STUPID AS {REQUIRING} A GEOMETRIC SQUARE CIRCLE IN THE SAME TWO-DIMENSIONAL PLANE.
    Nothing is stupid about wanting a halt decider. It’s just not obvious
    that it’s impossible.

    --
    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 Apr 14 09:29:40 2025
    Am Sun, 13 Apr 2025 16:00:43 -0500 schrieb olcott:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not valid. >>>>>>
    No proof of Peano's axioms or Euclid's fifth postulate has been
    shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER
    proving it (which, as you say, he has not yet done) OR by taking it >>>>>> as axiomatic, leaving the world of mainstream computer science
    behind him,
    constructing his own computational 'geometry' so to speak, and
    abandoning any claim to having overturned the Halting Problem.
    Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he
    wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to stop >>>>> simulating and reject any input that would otherwise prevent its own >>>>> termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input?

    Because that is a STUPID idea and categorically impossible because the
    outermost HHH sees its needs to stop simulating before any inner HHH
    can possibly see this.

    In other words, you agree that Linz and others are correct that no H
    exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of instructions) X
    described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly

    No stupid! Those freaking requirements are wrong and anchored in the ignorance of rejecting the notion of a simulating termination analyzer OUT-OF-HAND WITHOUT REVIEW.
    As anyone can see HHH MUST REJECT ITS INPUT OR GET STUPIDLY STUCK IN NON-TERMINATION. If people were not mindless robots they would have immediately acknowledged this years ago.
    But why does it not return „I know this halts, but I can’t simulate 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 Heathfield@21:1/5 to olcott on Mon Apr 14 13:39:52 2025
    On 14/04/2025 12:56, olcott wrote:

    <snip>

    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    A termination analyzer that works is simply logically impossible,
    thus an incorrect requirement.

    --
    Richard Heathfield
    Email: rjh at cpax dot org dot uk
    "Usenet is a strange place" - dmr 29 July 1999
    Sig line 4 vacant - apply within

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Mon Apr 14 12:33:05 2025
    Am Mon, 14 Apr 2025 06:46:20 -0500 schrieb olcott:
    On 4/13/2025 9:12 PM, dbush wrote:
    On 4/13/2025 10:09 PM, olcott wrote:
    On 4/13/2025 6:51 PM, dbush wrote:
    On 4/13/2025 7:32 PM, olcott wrote:
    On 4/13/2025 4:03 PM, dbush wrote:
    On 4/13/2025 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>>>> valid.

    No proof of Peano's axioms or Euclid's fifth postulate has >>>>>>>>>>>> been shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by >>>>>>>>>>>> EITHER proving it (which, as you say, he has not yet done) OR >>>>>>>>>>>> by taking it as axiomatic, leaving the world of mainstream >>>>>>>>>>>> computer science behind him,
    constructing his own computational 'geometry' so to speak, >>>>>>>>>>>> and abandoning any claim to having overturned the Halting >>>>>>>>>>>> Problem. Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as >>>>>>>>>>>> he wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer >>>>>>>>>>> to stop simulating and reject any input that would otherwise >>>>>>>>>>> prevent its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>>>
    Because that is a STUPID idea and categorically impossible
    because the outermost HHH sees its needs to stop simulating
    before any inner HHH can possibly see this.

    In other words, you agree that Linz and others are correct that >>>>>>>> no H exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of
    instructions) X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes >>>>>>>> the following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed
    directly (<X>,Y) maps to 0 if and only if X(Y) does not halt when >>>>>>>> executed directly


    No stupid! Those freaking requirements are wrong

    In other words, you have no interest in something that would make
    all truth provable.

    It will remain forever impossible to prove that five minutes ago
    ever existed. This is empirical truth mislabeled as synthetic truth. >>>>> Semantic truth poorly labeled as analytic truth is the only truth
    that is either provable else untrue. It is {provable}
    on the basis of semantic connections to expressions that are
    stipulated as true.

    So you do want something that would make all truth provable.  An H
    that meets the following requirements would do that, therefore these
    requirements are not "wrong":

    *Ignorance on your part about this*
    https://philosophy.stackexchange.com/questions/43748/how-do-we-know-
    the--wasnt-created-5-minutes-ago#:~:text=Ask%20Question,non-
    falsifiable%20and%20all).

    None-the-less an H that meets the requirements below would make all
    formal systems complete.  That makes such an H *very* useful, and
    therefore the requirements are not "wrong".

    Given any algorithm (i.e. a fixed immutable sequence of instructions)
    X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly

    Such an HHH works fine when the input DD is not attempting to do the
    opposite of whatever this HHH reports. This is not a problem though. DD merely changes its own behavior through the pathological self-reference
    that it implements.
    DD doesn’t change anything. It is completeley determined by the return
    value of HHH. Either it halts or it doesn’t, and HHH returns the wrong result.

    Then HHH simply reports on this changed behavior. HHH need not even know
    that DD is calling itself. It only need to know that the behavior of DD
    would prevent its own termination.
    If HHH reports on what DD *would* do *if* HHH returned the other value, that’s changing the input. (HHH doesn’t „know” anything at all.)

    --
    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 Apr 14 19:15:59 2025
    Op 14.apr.2025 om 13:56 schreef olcott:
    On 4/14/2025 4:25 AM, joes wrote:
    Am Sun, 13 Apr 2025 21:11:56 -0500 schrieb olcott:
    On 4/13/2025 6:11 PM, Richard Damon wrote:
    On 4/13/25 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>>>> proving it (which, as you say, he has not yet done) OR by taking >>>>>>>>>> it as axiomatic, leaving the world of mainstream computer science >>>>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>>>> wishes, but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to >>>>>>>>> stop simulating and reject any input that would otherwise prevent >>>>>>>>> its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>
    Because that is a STUPID idea and categorically impossible because >>>>>>> the outermost HHH sees its needs to stop simulating before any inner >>>>>>> HHH can possibly see this.

    In other words, you agree that Linz and others are correct that no H >>>>>> exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of instructions) >>>>>> X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes the >>>>>> following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly

    No stupid! Those freaking requirements are wrong and*
    anchored in the ignorance  of rejecting the notion of a simulating
    termination analyzer OUT-OF-HAND WITHOUT REVIEW.
    No, those "freeking requirement" *ARE* the requirements
    AND AS STUPID AS {REQUIRING} A GEOMETRIC SQUARE CIRCLE IN THE SAME
    TWO-DIMENSIONAL PLANE.
    Nothing is stupid about wanting a halt decider. It’s just not obvious
    that it’s impossible.


    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    It is very clear what its finite string input specifies: when exactly
    this same finite string input is used in direct execution or in
    world-class simulators, we see that it specifies a halting program
    according to the unique semantics of the x86 language.
    It is not clear what a geometric square circle is. So, your comparison
    fails.
    But I think we agree that there is no algorithm that can determine for
    all possible inputs whether the input specifies a program that
    (according to the semantics of the machine language) halts when directly executed. Correct?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Apr 14 18:52:14 2025
    On 4/14/25 5:43 PM, olcott wrote:
    On 4/14/2025 6:52 AM, dbush wrote:
    On 4/14/2025 7:46 AM, olcott wrote:

    Such an HHH works fine when the input DD is not attempting
    to do the opposite of whatever this HHH reports. This is not
    a problem though. DD merely changes its own behavior through
    the pathological self-reference that it implements.

    Category error. DD is an algorithm, i.e. a fixed immutable sequence of
    instructions, therefore "changing its behavior" is impossible.  It
    only does exactly what its instructions say.


    One version of DD is defined to screw with HHH.

    And it is that version, and only that version, that HHH must get right.

    The fact that DD CAN screw with HHH, means that HHH is just screwed, and
    so is your logic.

    You are just too stupid to understand that your own logic has been
    screwed by the properties of real logic, that just overpower it.



    Then HHH simply reports on this changed behavior. HHH need not
    even know that DD is calling itself. It only need to know that
    the behavior of DD would prevent its own termination.


    In other words, HHH is changing the input and reporting on the changed
    input.

    Changing the input is not allowed.




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Apr 14 18:50:24 2025
    On 4/14/25 7:46 AM, olcott wrote:
    On 4/13/2025 9:12 PM, dbush wrote:
    On 4/13/2025 10:09 PM, olcott wrote:
    On 4/13/2025 6:51 PM, dbush wrote:
    On 4/13/2025 7:32 PM, olcott wrote:
    On 4/13/2025 4:03 PM, dbush wrote:
    On 4/13/2025 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>>>> valid.

    No proof of Peano's axioms or Euclid's fifth postulate has >>>>>>>>>>>> been shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by >>>>>>>>>>>> EITHER
    proving it (which, as you say, he has not yet done) OR by >>>>>>>>>>>> taking it as
    axiomatic, leaving the world of mainstream computer science >>>>>>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>>>> abandoning any claim to having overturned the Halting
    Problem. Navel
    contemplation beckons.
    Axioms are all very well, and he's free to invent as many as >>>>>>>>>>>> he wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer >>>>>>>>>>> to stop
    simulating and reject any input that would otherwise prevent >>>>>>>>>>> its own
    termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>>>

    Because that is a STUPID idea and categorically impossible
    because the outermost HHH sees its needs to stop simulating
    before any inner HHH can possibly see this.


    In other words, you agree that Linz and others are correct that >>>>>>>> no H exists that satisfies these requirements:


    Given any algorithm (i.e. a fixed immutable sequence of
    instructions) X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that
    computes the following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when
    executed directly


    No stupid! Those freaking requirements are wrong

    In other words, you have no interest in something that would make
    all truth provable.


    It will remain forever impossible to prove that five minutes
    ago ever existed. This is empirical truth mislabeled as synthetic
    truth.

    Semantic truth poorly labeled as analytic truth is the only
    truth that is either provable else untrue. It is {provable}
    on the basis of semantic connections to expressions that are
    stipulated as true.


    So you do want something that would make all truth provable.  An H
    that meets the following requirements would do that, therefore these
    requirements are not "wrong":


    *Ignorance on your part about this*
    https://philosophy.stackexchange.com/questions/43748/how-do-we-know-
    the--wasnt-created-5-minutes-ago#:~:text=Ask%20Question,non-
    falsifiable%20and%20all).

    None-the-less an H that meets the requirements below would make all
    formal systems complete.  That makes such an H *very* useful, and
    therefore the requirements are not "wrong".



    Given any algorithm (i.e. a fixed immutable sequence of
    instructions) X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that computes
    the following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly






    Such an HHH works fine when the input DD is not attempting
    to do the opposite of whatever this HHH reports. This is not
    a problem though. DD merely changes its own behavior through
    the pathological self-reference that it implements.

    Then HHH simply reports on this changed behavior. HHH need not
    even know that DD is calling itself. It only need to know that
    the behavior of DD would prevent its own termination.


    But, by definiton, a full decider must handle ALL inputs, so you are
    just admitting that your algorithm is deficient.

    DD doesn't CHANGE its behavior, it DEFINES it (initially and forever) by
    that method.

    Remember, for DD to be a program, it must first be FULLY defined, and
    thus the version of HHH that it uses picked, and only after then does it
    even have behavior.

    HHH doesn't report on a change of behavior, as such a concept means that
    the input program was changed, but nobody did that. The closest is that
    HHH makes the INCORRECT presumption that it can change the code that it
    sees in DD to be some other version of HHH which doesn't abort its
    simulation, (which is thus a falsehood, as that isn't the HHH that DD
    was built on.

    Ultimately, your error stems from not understanding what a PROGRAM is.
    The C function DD, by itself, isn't a program, doesn't have behavior,
    and isn't a valid input to a halt decider. Only after the program is
    completed by adding the definition of the HHH that it calls does it
    become actually a program, and that definition of the HHH that it calls
    becomes part of the program description (and that definition needs to be COMPLETE).

    Yes, you have seen articles describing looking at the behavior of C
    functions, but they have always been looking at LEAF C functions, or C funcitons with all the functions they call included. Your failure to
    understand what those were talking about, which used perhaps imprecise terminology, because they assumed a minimal compentence in the field
    that you clearly don't have, is just being totally revealed in your errors.

    Sorry, but all you have been doing for you last decades is just prove to
    the universe that you just don't understand that basics of what you
    talki about, but you look at things with distortion lens that make you
    not understand what you see.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Apr 14 18:53:42 2025
    On 4/14/25 8:01 AM, olcott wrote:
    On 4/13/2025 9:13 PM, dbush wrote:
    On 4/13/2025 10:11 PM, olcott wrote:
    On 4/13/2025 6:11 PM, Richard Damon wrote:
    On 4/13/25 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>> valid.

    No proof of Peano's axioms or Euclid's fifth postulate has >>>>>>>>>> been shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>>>> proving it (which, as you say, he has not yet done) OR by
    taking it as
    axiomatic, leaving the world of mainstream computer science >>>>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>>>> Navel
    contemplation beckons.
    Axioms are all very well, and he's free to invent as many as >>>>>>>>>> he wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to >>>>>>>>> stop
    simulating and reject any input that would otherwise prevent >>>>>>>>> its own
    termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>

    Because that is a STUPID idea and categorically impossible
    because the outermost HHH sees its needs to stop simulating
    before any inner HHH can possibly see this.


    In other words, you agree that Linz and others are correct that no >>>>>> H exists that satisfies these requirements:


    Given any algorithm (i.e. a fixed immutable sequence of
    instructions) X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that computes
    the following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly


    No stupid! Those freaking requirements are wrong and*
    anchored in the ignorance  of rejecting the notion
    of a simulating termination analyzer OUT-OF-HAND WITHOUT REVIEW.

    No, those "freeking requirement" *ARE* the requirements


    AND AS STUPID AS {REQUIRING} A GEOMETRIC SQUARE
    CIRCLE IN THE SAME TWO-DIMENSIONAL PLANE.


    In other words, you think something that would make all formal systems
    complete would be stupid.

    Formal systems are only incomplete[math] because they do not
    screen_out[] and reject[0] incorrect[0] inputs[0] thus enable undecidability[math].


    Because the rules of logic don't allow that sort of filtering, because
    such filtering basically removes all the power that logic has.

    Your idea of logic seem to be to just be able to bring back up the facts
    that you have learned by rote, and not to be able to think about them.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Apr 14 18:58:39 2025
    On 4/14/25 7:56 AM, olcott wrote:
    On 4/14/2025 4:25 AM, joes wrote:
    Am Sun, 13 Apr 2025 21:11:56 -0500 schrieb olcott:
    On 4/13/2025 6:11 PM, Richard Damon wrote:
    On 4/13/25 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>>>> proving it (which, as you say, he has not yet done) OR by taking >>>>>>>>>> it as axiomatic, leaving the world of mainstream computer science >>>>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>>>> wishes, but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to >>>>>>>>> stop simulating and reject any input that would otherwise prevent >>>>>>>>> its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>
    Because that is a STUPID idea and categorically impossible because >>>>>>> the outermost HHH sees its needs to stop simulating before any inner >>>>>>> HHH can possibly see this.

    In other words, you agree that Linz and others are correct that no H >>>>>> exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of instructions) >>>>>> X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes the >>>>>> following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly

    No stupid! Those freaking requirements are wrong and*
    anchored in the ignorance  of rejecting the notion of a simulating
    termination analyzer OUT-OF-HAND WITHOUT REVIEW.
    No, those "freeking requirement" *ARE* the requirements
    AND AS STUPID AS {REQUIRING} A GEOMETRIC SQUARE CIRCLE IN THE SAME
    TWO-DIMENSIONAL PLANE.
    Nothing is stupid about wanting a halt decider. It’s just not obvious
    that it’s impossible.


    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.


    But the finite string DOES specify the halting behavior, at least when
    it properly represents the whole program being decide on.

    All you are doing is proving that you have zero understanding of what
    you are talking about, and are just talking your self into square cirles.

    Your "logic" is based on assuming the logically impossible is true, and
    thus is based on lies.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Apr 14 18:56:44 2025
    On 4/14/25 5:40 PM, olcott wrote:
    On 4/14/2025 7:22 AM, dbush wrote:
    On 4/14/2025 8:01 AM, olcott wrote:
    On 4/13/2025 9:13 PM, dbush wrote:
    On 4/13/2025 10:11 PM, olcott wrote:
    On 4/13/2025 6:11 PM, Richard Damon wrote:
    On 4/13/25 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>>>> valid.

    No proof of Peano's axioms or Euclid's fifth postulate has >>>>>>>>>>>> been shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by >>>>>>>>>>>> EITHER
    proving it (which, as you say, he has not yet done) OR by >>>>>>>>>>>> taking it as
    axiomatic, leaving the world of mainstream computer science >>>>>>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>>>> abandoning any claim to having overturned the Halting
    Problem. Navel
    contemplation beckons.
    Axioms are all very well, and he's free to invent as many as >>>>>>>>>>>> he wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer >>>>>>>>>>> to stop
    simulating and reject any input that would otherwise prevent >>>>>>>>>>> its own
    termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>>>

    Because that is a STUPID idea and categorically impossible
    because the outermost HHH sees its needs to stop simulating
    before any inner HHH can possibly see this.


    In other words, you agree that Linz and others are correct that >>>>>>>> no H exists that satisfies these requirements:


    Given any algorithm (i.e. a fixed immutable sequence of
    instructions) X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that
    computes the following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when
    executed directly


    No stupid! Those freaking requirements are wrong and*
    anchored in the ignorance  of rejecting the notion
    of a simulating termination analyzer OUT-OF-HAND WITHOUT REVIEW.

    No, those "freeking requirement" *ARE* the requirements


    AND AS STUPID AS {REQUIRING} A GEOMETRIC SQUARE
    CIRCLE IN THE SAME TWO-DIMENSIONAL PLANE.


    In other words, you think something that would make all formal
    systems complete would be stupid.

    Formal systems are only incomplete[math] because

    They contain unknowable truths.

    Undecidability is always caused by the incoherent
    notion of formal systems. Unknowability has NOTHING
    to do with this.

    Nope, and you are just showing that you don't know what you are talking
    about.

    The "incoherent notion" that you seem to refer to is the ability to have
    the Natural Numbers and have countable infinities.

    Your logic can only handle things that are finitely countable, and thus
    too simple for most things deal with by "real logic".

    Yes, in a logic of total finiteness, since we can enumerate everything
    that could possible by true or false, we can avoid undecidability, but
    such system are just toys.



     An H that meets these requirements would make those unknowable truths
    knowable:


    Given any algorithm (i.e. a fixed immutable sequence of instructions)
    X described as <X> with input Y:

    A solution to the halting problem is an algorithm H that computes the
    following mapping:

    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Heathfield@21:1/5 to olcott on Tue Apr 15 02:45:26 2025
    On 15/04/2025 02:18, olcott wrote:
    On 4/14/2025 7:39 AM, Richard Heathfield wrote:
    On 14/04/2025 12:56, olcott wrote:

    <snip>

    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    A termination analyzer that works is simply logically
    impossible, thus an incorrect requirement.


    THAT IS A STUPID THING TO SAY THAT COMPLETELY IGNORES WHAT
    COMPUTABLE FUNCTIONS ARE AND HOW THEY WORK.

    You said precisely the same thing in reply to dbush. I have
    addressed your remark there, so I see no value in repeating my
    reply here.

    HHH CORRECTLY REPORTS ON THE PATHOLOGICAL SELF-REFERENCE THAT
    ITS INPUT SPECIFIES. THE DIRECT EXECUTION HAS NO SUCH PSR.

    You say so, but as it's you saying it and you can't even turn off
    CAPS LOCK I see no reason to believe that you have the capacity
    to be right, so I think I'll wait until your claim is confirmed
    by an independent observer.

    --
    Richard Heathfield
    Email: rjh at cpax dot org dot uk
    "Usenet is a strange place" - dmr 29 July 1999
    Sig line 4 vacant - apply within

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Apr 14 22:43:01 2025
    On 4/14/25 9:14 PM, olcott wrote:
    On 4/14/2025 7:39 AM, Richard Heathfield wrote:
    On 14/04/2025 12:56, olcott wrote:

    <snip>

    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    A termination analyzer that works is simply logically impossible, thus
    an incorrect requirement.


    <Sarcasm>
    Yes and Tarki is right because we are supposed to be able
    to prove that self-contradictory expressions are true.
    </sarcasm>


    No, Tarski shows that if we assume that a Truth Predicate exists, then
    the logic shows that it IS TRUE that a self-contradictory expression is
    true.

    You have the results half right, the proog does come to an impossible conclusion, but you think it must have an error, but the real answer is
    that the proof shows that the explisitly made presuposition must be
    wrong, and thus the proof by contradiction proves the desire result.

    Of course, it seems that the whole idea of "Proof by Contradiction" is
    beyond your understanding, as having contradictions in your proofs is
    just a normal feature of your logic.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Apr 14 22:39:30 2025
    On 4/14/25 9:23 PM, olcott wrote:
    On 4/14/2025 7:33 AM, joes wrote:
    Am Mon, 14 Apr 2025 06:46:20 -0500 schrieb olcott:
    Such an HHH works fine when the input DD is not attempting to do the
    opposite of whatever this HHH reports. This is not a problem though. DD
    merely changes its own behavior through the pathological self-reference
    that it implements.
    DD doesn’t change anything. It is completeley determined by the return
    value of HHH. Either it halts or it doesn’t, and HHH returns the wrong
    result.

    Then HHH simply reports on this changed behavior. HHH need not even know >>> that DD is calling itself. It only need to know that the behavior of DD
    would prevent its own termination.
    If HHH reports on what DD *would* do *if* HHH returned the other value,
    that’s changing the input. (HHH doesn’t „know” anything at all.)


    Hypothetical freaking possibilities of alternatives is
    not a very difficult thing. I don't understand why its so
    hard for you.


    But if you try to imagine HHH doing something different than what it
    does, you are changing the PROGRAM given as the input, as that, to BE a
    program must include all the code it uses, which was the original HHH,
    not your new imaginary HHH.

    Thus, for HHH to imagine that the input is calling something other than
    itself isn't being imaginative, but just lying to itself.

    Yes, you can imagine that other HHH as a whole new problem, and that HHH
    either aboets its emulation, thinking its input is non-halting, and is
    wrong about that, or it doesn't abort its emulation, and never gives an
    answer.

    This just shows that you imaginary cases just prove that no decider
    based on your idea can give a correct answer for this problem.

    TO imagine the HHH that the input uses acting different than the HHH
    that is trying to decide on it is just imagining something that is
    logically impossible, and thus is a self-contradictory idea that breaks
    your logic.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Apr 14 22:46:44 2025
    On 4/14/25 9:18 PM, olcott wrote:
    On 4/14/2025 7:39 AM, Richard Heathfield wrote:
    On 14/04/2025 12:56, olcott wrote:

    <snip>

    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    A termination analyzer that works is simply logically impossible, thus
    an incorrect requirement.


    THAT IS A STUPID THING TO SAY THAT COMPLETELY IGNORES WHAT
    COMPUTABLE FUNCTIONS ARE AND HOW THEY WORK.

    HHH CORRECTLY REPORTS ON THE PATHOLOGICAL SELF-REFERENCE THAT
    ITS INPUT SPECIFIES. THE DIRECT EXECUTION HAS NO SUCH PSR.


    But who says that the Haltig Function is a computable funciton?

    That is your problem, you don't understand what that term means.

    HHH does NOT correctly report on the pathological self-reference that
    its input specifies, as the input doesn't have a pathological
    self-refernce but is just pathologically derived from the decider HHH,
    making it impossible for HHH to get the right answer.

    Note, your problem is you just don't understand what you words actually
    mean when used in the context of the field, because you just don't
    understand the concepts of the field.

    Part of the problem is that what you want to call the input can't be a
    proper input, as it isnt' actually a program, so you start with a
    category error at the start of your problem.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Apr 14 22:51:38 2025
    On 4/14/25 6:48 PM, olcott wrote:
    On 4/14/2025 4:29 AM, joes wrote:
    Am Sun, 13 Apr 2025 16:00:43 -0500 schrieb olcott:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not valid. >>>>>>>>
    No proof of Peano's axioms or Euclid's fifth postulate has been >>>>>>>> shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>> proving it (which, as you say, he has not yet done) OR by taking it >>>>>>>> as axiomatic, leaving the world of mainstream computer science >>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>> wishes,
    but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to stop >>>>>>> simulating and reject any input that would otherwise prevent its own >>>>>>> termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input?

    Because that is a STUPID idea and categorically impossible because the >>>>> outermost HHH sees its needs to stop simulating before any inner HHH >>>>> can possibly see this.

    In other words, you agree that Linz and others are correct that no H
    exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of instructions) X >>>> described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly

    No stupid! Those freaking requirements are wrong and anchored in the
    ignorance  of rejecting the notion of a simulating termination analyzer >>> OUT-OF-HAND WITHOUT REVIEW.
    As anyone can see HHH MUST REJECT ITS INPUT OR GET STUPIDLY STUCK IN
    NON-TERMINATION. If people were not mindless robots they would have
    immediately acknowledged this years ago.
    But why does it not return „I know this halts, but I can’t simulate it”?


    Because it is not a liar and tells the truth for
    every input in its domain.


    But that *IS* the correct answer as good as it could give it.

    THe input DOES halt, when made into the program you want to claim it to
    be (being completed with the HHH that is deciding on it). This is
    because behavior is DEFINED on the direct execution of that input, which
    will also be what an actually correct (and thus complete) simulation of
    the input shows. It is just a fact that your HHH doesn't do a complete simulation, and thus doesn't do a correct simulation, so the fact it
    stopped before reaching the final state, which the complete simulation
    of this exact input does reach, showing the input is halting.

    You just don't understand the meaning of the words you use.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Heathfield@21:1/5 to olcott on Tue Apr 15 08:52:28 2025
    On 15/04/2025 04:41, olcott wrote:
    On 4/14/2025 8:45 PM, Richard Heathfield wrote:
    On 15/04/2025 02:18, olcott wrote:
    On 4/14/2025 7:39 AM, Richard Heathfield wrote:
    On 14/04/2025 12:56, olcott wrote:

    <snip>

    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    A termination analyzer that works is simply logically
    impossible, thus an incorrect requirement.


    THAT IS A STUPID THING TO SAY THAT COMPLETELY IGNORES WHAT
    COMPUTABLE FUNCTIONS ARE AND HOW THEY WORK.

    You said precisely the same thing in reply to dbush. I have
    addressed your remark there, so I see no value in repeating my
    reply here.

    HHH CORRECTLY REPORTS ON THE PATHOLOGICAL SELF-REFERENCE THAT
    ITS INPUT SPECIFIES. THE DIRECT EXECUTION HAS NO SUCH PSR.

    You say so,

    Ignoring verified facts does not make them go away.

    Indeed. And the Church-Turing thesis isn't going anywhere.

    <snip>

    Only comprehension ultimately rules.

    And yet you continue to misunderstand the Halting Problem.

    so I think I'll wait until your claim is confirmed by an
    independent observer.


    Thus forever postponing the ultimate measure of direct
    comprehension.

    Or so you believe. "Belief and disbelief are inherently
    fallible", as you rightly said.

    --
    Richard Heathfield
    Email: rjh at cpax dot org dot uk
    "Usenet is a strange place" - dmr 29 July 1999
    Sig line 4 vacant - apply within

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Tue Apr 15 10:28:51 2025
    Op 15.apr.2025 om 05:32 schreef olcott:
    On 4/14/2025 12:15 PM, Fred. Zwarts wrote:
    Op 14.apr.2025 om 13:56 schreef olcott:
    On 4/14/2025 4:25 AM, joes wrote:
    Am Sun, 13 Apr 2025 21:11:56 -0500 schrieb olcott:
    On 4/13/2025 6:11 PM, Richard Damon wrote:
    On 4/13/25 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    Mr Olcott can have his principle if he likes, but only by >>>>>>>>>>>> EITHER
    proving it (which, as you say, he has not yet done) OR by >>>>>>>>>>>> taking
    it as axiomatic, leaving the world of mainstream computer >>>>>>>>>>>> science
    behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>>>>>> wishes, but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to >>>>>>>>>>> stop simulating and reject any input that would otherwise >>>>>>>>>>> prevent
    its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>>>
    Because that is a STUPID idea and categorically impossible because >>>>>>>>> the outermost HHH sees its needs to stop simulating before any >>>>>>>>> inner
    HHH can possibly see this.

    In other words, you agree that Linz and others are correct that >>>>>>>> no H
    exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of
    instructions)
    X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that
    computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed >>>>>>>> directly

    No stupid! Those freaking requirements are wrong and*
    anchored in the ignorance  of rejecting the notion of a simulating >>>>>>> termination analyzer OUT-OF-HAND WITHOUT REVIEW.
    No, those "freeking requirement" *ARE* the requirements
    AND AS STUPID AS {REQUIRING} A GEOMETRIC SQUARE CIRCLE IN THE SAME
    TWO-DIMENSIONAL PLANE.
    Nothing is stupid about wanting a halt decider. It’s just not obvious >>>> that it’s impossible.


    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    It is very clear what its finite string input specifies: when exactly
    this same finite string input is used in direct execution or in world-
    class simulators,

    And by this same reasoning we can say that
    int sum(int x, int y) { return x + y; }
    returns 7 for sum(2,3) because it returns 7 for sum(5,2).

    In other words, you believe that the sum of 2 and 3 can be 7 because it
    is allowed to make an error in the algorithm.

    No. There is only one interpretation for the sum of 2 and 5 with the
    normal definitions. It does not depend on what or who will calculate it. Similarly, the finite string specifies only one behaviour according to
    the semantics of the x86 language. It does not depend on who or what is analysing it. The 'pathological' relationship with HHH makes it
    impossible for HHH to analyse it, so it must give up, reporting that it
    failed to complete the simulation.
    There is nothing wrong with imposing requirements that not all analysers
    can fulfil.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Tue Apr 15 11:25:55 2025
    On 2025-04-15 03:41:02 +0000, olcott said:

    On 4/14/2025 8:45 PM, Richard Heathfield wrote:
    On 15/04/2025 02:18, olcott wrote:
    On 4/14/2025 7:39 AM, Richard Heathfield wrote:
    On 14/04/2025 12:56, olcott wrote:

    <snip>

    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    A termination analyzer that works is simply logically impossible, thus >>>> an incorrect requirement.


    THAT IS A STUPID THING TO SAY THAT COMPLETELY IGNORES WHAT
    COMPUTABLE FUNCTIONS ARE AND HOW THEY WORK.

    You said precisely the same thing in reply to dbush. I have addressed
    your remark there, so I see no value in repeating my reply here.

    HHH CORRECTLY REPORTS ON THE PATHOLOGICAL SELF-REFERENCE THAT
    ITS INPUT SPECIFIES. THE DIRECT EXECUTION HAS NO SUCH PSR.

    You say so,

    Ignoring verified facts does not make them go away.

    Ignoring verified proofs does not meke them go away.
    But you keep ignoring them anyway.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Apr 15 06:54:07 2025
    On 4/14/25 11:41 PM, olcott wrote:
    On 4/14/2025 8:45 PM, Richard Heathfield wrote:
    On 15/04/2025 02:18, olcott wrote:
    On 4/14/2025 7:39 AM, Richard Heathfield wrote:
    On 14/04/2025 12:56, olcott wrote:

    <snip>

    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    A termination analyzer that works is simply logically impossible,
    thus an incorrect requirement.


    THAT IS A STUPID THING TO SAY THAT COMPLETELY IGNORES WHAT
    COMPUTABLE FUNCTIONS ARE AND HOW THEY WORK.

    You said precisely the same thing in reply to dbush. I have addressed
    your remark there, so I see no value in repeating my reply here.

    HHH CORRECTLY REPORTS ON THE PATHOLOGICAL SELF-REFERENCE THAT
    ITS INPUT SPECIFIES. THE DIRECT EXECUTION HAS NO SUCH PSR.

    You say so,

    Ignoring verified facts does not make them go away.

    Right, like the fact that when the exact input given to HHH is
    correctly, and completely, simulated, it reaches a final state.


    but as it's you saying it and you can't even turn off CAPS LOCK I see
    no reason to believe that you have the capacity to be right,

    Belief and disbelief are inherently fallible.
    Only comprehension ultimately rules.

    Which you have shown a failure to have.


    so I think I'll wait until your claim is confirmed by an independent
    observer.


    Thus forever postponing the ultimate measure of direct comprehension.



    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Apr 15 06:56:09 2025
    On 4/14/25 11:32 PM, olcott wrote:
    On 4/14/2025 12:15 PM, Fred. Zwarts wrote:
    Op 14.apr.2025 om 13:56 schreef olcott:
    On 4/14/2025 4:25 AM, joes wrote:
    Am Sun, 13 Apr 2025 21:11:56 -0500 schrieb olcott:
    On 4/13/2025 6:11 PM, Richard Damon wrote:
    On 4/13/25 5:00 PM, olcott wrote:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    Mr Olcott can have his principle if he likes, but only by >>>>>>>>>>>> EITHER
    proving it (which, as you say, he has not yet done) OR by >>>>>>>>>>>> taking
    it as axiomatic, leaving the world of mainstream computer >>>>>>>>>>>> science
    behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>>>>>> wishes, but nobody else is obliged to accept them.

    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to >>>>>>>>>>> stop simulating and reject any input that would otherwise >>>>>>>>>>> prevent
    its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>>>
    Because that is a STUPID idea and categorically impossible because >>>>>>>>> the outermost HHH sees its needs to stop simulating before any >>>>>>>>> inner
    HHH can possibly see this.

    In other words, you agree that Linz and others are correct that >>>>>>>> no H
    exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of
    instructions)
    X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that
    computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed >>>>>>>> directly

    No stupid! Those freaking requirements are wrong and*
    anchored in the ignorance  of rejecting the notion of a simulating >>>>>>> termination analyzer OUT-OF-HAND WITHOUT REVIEW.
    No, those "freeking requirement" *ARE* the requirements
    AND AS STUPID AS {REQUIRING} A GEOMETRIC SQUARE CIRCLE IN THE SAME
    TWO-DIMENSIONAL PLANE.
    Nothing is stupid about wanting a halt decider. It’s just not obvious >>>> that it’s impossible.


    When people insist that a termination analyzer reports
    on behavior other than the behavior that its finite string
    input specifies this is isomorphic to requiring a perfectly
    geometric square circle in the same two dimensional plane,
    simply logically impossible, thus an incorrect requirement.

    It is very clear what its finite string input specifies: when exactly
    this same finite string input is used in direct execution or in world-
    class simulators,

    And by this same reasoning we can say that
    int sum(int x, int y) { return x + y; }
    returns 7 for sum(2,3) because it returns 7 for sum(5,2).

    No, because that is looking at the wrong inputs.

    Your problem is that the finite string you are saying you are giving to
    HHH isn't a valid input, as it isn't the representation of a *PROGRAM*,
    as that needs to include *ALL* the code it is given.

    Your HHH is doing the equivalent of sum("FOO", "BAR")


    we see that it specifies a halting program according to the unique
    semantics of the x86 language.
    It is not clear what a geometric square circle is. So, your comparison
    fails.
    But I think we agree that there is no algorithm that can determine for
    all possible inputs whether the input specifies a program that
    (according to the semantics of the machine language) halts when
    directly executed. Correct?




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Tue Apr 22 12:42:57 2025
    Am Mon, 14 Apr 2025 17:48:36 -0500 schrieb olcott:
    On 4/14/2025 4:29 AM, joes wrote:
    Am Sun, 13 Apr 2025 16:00:43 -0500 schrieb olcott:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not
    valid.
    No proof of Peano's axioms or Euclid's fifth postulate has been >>>>>>>> shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>> proving it (which, as you say, he has not yet done) OR by taking >>>>>>>> it as axiomatic, leaving the world of mainstream computer science >>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>> wishes,
    but nobody else is obliged to accept them.
    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to
    stop simulating and reject any input that would otherwise prevent >>>>>>> its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input?
    Because that is a STUPID idea and categorically impossible because
    the outermost HHH sees its needs to stop simulating before any inner >>>>> HHH can possibly see this.
    In other words, you agree that Linz and others are correct that no H
    exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of instructions)
    X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly
    No stupid! Those freaking requirements are wrong and anchored in the
    ignorance of rejecting the notion of a simulating termination
    analyzer OUT-OF-HAND WITHOUT REVIEW.
    As anyone can see HHH MUST REJECT ITS INPUT OR GET STUPIDLY STUCK IN
    NON-TERMINATION. If people were not mindless robots they would have
    immediately acknowledged this years ago.
    But why does it not return „I know this halts, but I can’t simulate
    it”?
    Because it is not a liar and tells the truth for every input in its
    domain.
    Aha. Then why does it not simulate it and say that it halts?

    --
    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 Apr 22 12:47:35 2025
    Am Mon, 14 Apr 2025 16:43:28 -0500 schrieb olcott:
    On 4/14/2025 6:52 AM, dbush wrote:
    On 4/14/2025 7:46 AM, olcott wrote:

    Such an HHH works fine when the input DD is not attempting to do the
    opposite of whatever this HHH reports. This is not a problem though.
    DD merely changes its own behavior through the pathological
    self-reference that it implements.
    Category error. DD is an algorithm, i.e. a fixed immutable sequence of
    instructions, therefore "changing its behavior" is impossible.  It only
    does exactly what its instructions say.
    One version of DD is defined to screw with HHH.
    There is only one DD.

    --
    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 Apr 22 18:57:10 2025
    On 4/22/25 3:24 PM, olcott wrote:
    On 4/22/2025 7:42 AM, joes wrote:
    Am Mon, 14 Apr 2025 17:48:36 -0500 schrieb olcott:
    On 4/14/2025 4:29 AM, joes wrote:
    Am Sun, 13 Apr 2025 16:00:43 -0500 schrieb olcott:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>> valid.
    No proof of Peano's axioms or Euclid's fifth postulate has been >>>>>>>>>> shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>>>> proving it (which, as you say, he has not yet done) OR by taking >>>>>>>>>> it as axiomatic, leaving the world of mainstream computer science >>>>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>>>> wishes,
    but nobody else is obliged to accept them.
    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to >>>>>>>>> stop simulating and reject any input that would otherwise prevent >>>>>>>>> its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>> Because that is a STUPID idea and categorically impossible because >>>>>>> the outermost HHH sees its needs to stop simulating before any inner >>>>>>> HHH can possibly see this.
    In other words, you agree that Linz and others are correct that no H >>>>>> exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of instructions) >>>>>> X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes the >>>>>> following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly
    No stupid! Those freaking requirements are wrong and anchored in the >>>>> ignorance  of rejecting the notion of a simulating termination
    analyzer OUT-OF-HAND WITHOUT REVIEW.
    As anyone can see HHH MUST REJECT ITS INPUT OR GET STUPIDLY STUCK IN >>>>> NON-TERMINATION. If people were not mindless robots they would have
    immediately acknowledged this years ago.
    But why does it not return „I know this halts, but I can’t simulate >>>> it”?
    Because it is not a liar and tells the truth for every input in its
    domain.
    Aha. Then why does it not simulate it and say that it halts?


    I have proven that the directly executed DD and DD
    emulated by HHH according to the semantics of the
    x86 language have a different set of state changes
    many hundreds of times for several years.


    No, you haven't.

    You have lied to yourself and you beleive your lies.

    Your proof has been refuted, and you just blindly ignore the error,
    because you know you can't actually prove what you want without proving yourself a total liar.

    You have admitted this by refusing to show the one simple fact that
    would prove it if you could show it.

    Sorry, you are just proving your ignorance.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Wed Apr 23 10:59:41 2025
    Op 22.apr.2025 om 21:24 schreef olcott:
    On 4/22/2025 7:42 AM, joes wrote:
    Am Mon, 14 Apr 2025 17:48:36 -0500 schrieb olcott:
    On 4/14/2025 4:29 AM, joes wrote:
    Am Sun, 13 Apr 2025 16:00:43 -0500 schrieb olcott:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>> valid.
    No proof of Peano's axioms or Euclid's fifth postulate has been >>>>>>>>>> shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by EITHER >>>>>>>>>> proving it (which, as you say, he has not yet done) OR by taking >>>>>>>>>> it as axiomatic, leaving the world of mainstream computer science >>>>>>>>>> behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>>>> wishes,
    but nobody else is obliged to accept them.
    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to >>>>>>>>> stop simulating and reject any input that would otherwise prevent >>>>>>>>> its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>> Because that is a STUPID idea and categorically impossible because >>>>>>> the outermost HHH sees its needs to stop simulating before any inner >>>>>>> HHH can possibly see this.
    In other words, you agree that Linz and others are correct that no H >>>>>> exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of instructions) >>>>>> X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that computes the >>>>>> following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed
    directly
    No stupid! Those freaking requirements are wrong and anchored in the >>>>> ignorance  of rejecting the notion of a simulating termination
    analyzer OUT-OF-HAND WITHOUT REVIEW.
    As anyone can see HHH MUST REJECT ITS INPUT OR GET STUPIDLY STUCK IN >>>>> NON-TERMINATION. If people were not mindless robots they would have
    immediately acknowledged this years ago.
    But why does it not return „I know this halts, but I can’t simulate >>>> it”?
    Because it is not a liar and tells the truth for every input in its
    domain.
    Aha. Then why does it not simulate it and say that it halts?


    I have proven that the directly executed DD and DD
    emulated by HHH according to the semantics of the
    x86 language have a different set of state changes
    many hundreds of times for several years.


    You did not prove it, you dreamed about it for many years, but you
    failed to show the first state change were the simulation differs from
    the simulation. You only showed that HHH failed to complete the simulation.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Wed Apr 23 19:23:53 2025
    Op 23.apr.2025 om 17:53 schreef olcott:
    On 4/23/2025 3:59 AM, Fred. Zwarts wrote:
    Op 22.apr.2025 om 21:24 schreef olcott:
    On 4/22/2025 7:42 AM, joes wrote:
    Am Mon, 14 Apr 2025 17:48:36 -0500 schrieb olcott:
    On 4/14/2025 4:29 AM, joes wrote:
    Am Sun, 13 Apr 2025 16:00:43 -0500 schrieb olcott:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>>>> valid.
    No proof of Peano's axioms or Euclid's fifth postulate has been >>>>>>>>>>>> shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by >>>>>>>>>>>> EITHER
    proving it (which, as you say, he has not yet done) OR by >>>>>>>>>>>> taking
    it as axiomatic, leaving the world of mainstream computer >>>>>>>>>>>> science
    behind him,
    constructing his own computational 'geometry' so to speak, and >>>>>>>>>>>> abandoning any claim to having overturned the Halting Problem. >>>>>>>>>>>> Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many as he >>>>>>>>>>>> wishes,
    but nobody else is obliged to accept them.
    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination analyzer to >>>>>>>>>>> stop simulating and reject any input that would otherwise >>>>>>>>>>> prevent
    its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>> Because that is a STUPID idea and categorically impossible because >>>>>>>>> the outermost HHH sees its needs to stop simulating before any >>>>>>>>> inner
    HHH can possibly see this.
    In other words, you agree that Linz and others are correct that >>>>>>>> no H
    exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of
    instructions)
    X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that
    computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly >>>>>>>> (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed >>>>>>>> directly
    No stupid! Those freaking requirements are wrong and anchored in the >>>>>>> ignorance  of rejecting the notion of a simulating termination
    analyzer OUT-OF-HAND WITHOUT REVIEW.
    As anyone can see HHH MUST REJECT ITS INPUT OR GET STUPIDLY STUCK IN >>>>>>> NON-TERMINATION. If people were not mindless robots they would have >>>>>>> immediately acknowledged this years ago.
    But why does it not return „I know this halts, but I can’t simulate >>>>>> it”?
    Because it is not a liar and tells the truth for every input in its
    domain.
    Aha. Then why does it not simulate it and say that it halts?


    I have proven that the directly executed DD and DD
    emulated by HHH according to the semantics of the
    x86 language have a different set of state changes
    many hundreds of times for several years.


    You did not prove it, you dreamed about it for many years, but you
    failed to show the first state change were the simulation differs from
    the simulation. You only showed that HHH failed to complete the
    simulation.

    _DD()
    [00002133] 55         push ebp      ; housekeeping
    [00002134] 8bec       mov ebp,esp   ; housekeeping
    [00002136] 51         push ecx      ; make space for local [00002137] 6833210000 push 00002133 ; push DD
    [0000213c] e882f4ffff call 000015c3 ; call HHH(DD)
    [00002141] 83c404     add esp,+04
    [00002144] 8945fc     mov [ebp-04],eax
    [00002147] 837dfc00   cmp dword [ebp-04],+00
    [0000214b] 7402       jz 0000214f
    [0000214d] ebfe       jmp 0000214d
    [0000214f] 8b45fc     mov eax,[ebp-04]
    [00002152] 8be5       mov esp,ebp
    [00002154] 5d         pop ebp
    [00002155] c3         ret
    Size in bytes:(0035) [00002155]

    By merely knowing that HHH emulates DD until it
    sees itself about to emulate DD a third time
    (mathematical induction proof that DD is stuck in
    recursive emulation) we can know that

    We know that the simulating HHH fails to see that the recursion is
    finite and that the next time the simulated HHH would abort and halt,
    which makes the abort of the simulating HHH unneeded.


    The call to HHH(DD) from the directly executed DD returns.
    The call to HHH(DD) from DD emulated by HHH cannot possibly return.
    Yes, HHH fails to simulate itself up to the end.
    You still did not show which state change in the simulation is different
    from the direct execution. The only difference is that HHH aborts
    prematurely and the direct execution does not abort.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Fred. Zwarts@21:1/5 to All on Wed Apr 23 19:49:05 2025
    Op 23.apr.2025 om 19:32 schreef olcott:
    On 4/23/2025 12:23 PM, Fred. Zwarts wrote:
    Op 23.apr.2025 om 17:53 schreef olcott:
    On 4/23/2025 3:59 AM, Fred. Zwarts wrote:
    Op 22.apr.2025 om 21:24 schreef olcott:
    On 4/22/2025 7:42 AM, joes wrote:
    Am Mon, 14 Apr 2025 17:48:36 -0500 schrieb olcott:
    On 4/14/2025 4:29 AM, joes wrote:
    Am Sun, 13 Apr 2025 16:00:43 -0500 schrieb olcott:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>>>>>> valid.
    No proof of Peano's axioms or Euclid's fifth postulate has >>>>>>>>>>>>>> been
    shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by >>>>>>>>>>>>>> EITHER
    proving it (which, as you say, he has not yet done) OR by >>>>>>>>>>>>>> taking
    it as axiomatic, leaving the world of mainstream computer >>>>>>>>>>>>>> science
    behind him,
    constructing his own computational 'geometry' so to speak, >>>>>>>>>>>>>> and
    abandoning any claim to having overturned the Halting >>>>>>>>>>>>>> Problem.
    Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many >>>>>>>>>>>>>> as he
    wishes,
    but nobody else is obliged to accept them.
    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination
    analyzer to
    stop simulating and reject any input that would otherwise >>>>>>>>>>>>> prevent
    its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>>>> Because that is a STUPID idea and categorically impossible >>>>>>>>>>> because
    the outermost HHH sees its needs to stop simulating before >>>>>>>>>>> any inner
    HHH can possibly see this.
    In other words, you agree that Linz and others are correct >>>>>>>>>> that no H
    exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of
    instructions)
    X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that
    computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed
    directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed >>>>>>>>>> directly
    No stupid! Those freaking requirements are wrong and anchored >>>>>>>>> in the
    ignorance  of rejecting the notion of a simulating termination >>>>>>>>> analyzer OUT-OF-HAND WITHOUT REVIEW.
    As anyone can see HHH MUST REJECT ITS INPUT OR GET STUPIDLY
    STUCK IN
    NON-TERMINATION. If people were not mindless robots they would >>>>>>>>> have
    immediately acknowledged this years ago.
    But why does it not return „I know this halts, but I can’t simulate
    it”?
    Because it is not a liar and tells the truth for every input in its >>>>>>> domain.
    Aha. Then why does it not simulate it and say that it halts?


    I have proven that the directly executed DD and DD
    emulated by HHH according to the semantics of the
    x86 language have a different set of state changes
    many hundreds of times for several years.


    You did not prove it, you dreamed about it for many years, but you
    failed to show the first state change were the simulation differs
    from the simulation. You only showed that HHH failed to complete the
    simulation.

    _DD()
    [00002133] 55         push ebp      ; housekeeping
    [00002134] 8bec       mov ebp,esp   ; housekeeping
    [00002136] 51         push ecx      ; make space for local
    [00002137] 6833210000 push 00002133 ; push DD
    [0000213c] e882f4ffff call 000015c3 ; call HHH(DD)
    [00002141] 83c404     add esp,+04
    [00002144] 8945fc     mov [ebp-04],eax
    [00002147] 837dfc00   cmp dword [ebp-04],+00
    [0000214b] 7402       jz 0000214f
    [0000214d] ebfe       jmp 0000214d
    [0000214f] 8b45fc     mov eax,[ebp-04]
    [00002152] 8be5       mov esp,ebp
    [00002154] 5d         pop ebp
    [00002155] c3         ret
    Size in bytes:(0035) [00002155]

    By merely knowing that HHH emulates DD until it
    sees itself about to emulate DD a third time
    (mathematical induction proof that DD is stuck in
    recursive emulation) we can know that

    We know that the simulating HHH fails to see that the recursion is finite

    From the point of view of the HHH that is simulating DD
    the recursion will never stop unless this HHH stops it.

    Only, because it aborts before it can see that. Such a programming error
    is not a proof.
    Very clever to hide the fact that you cannot show the first state change
    that is different between the direct execution and the simulation.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Thu Apr 24 07:02:14 2025
    On 4/23/25 1:32 PM, olcott wrote:
    On 4/23/2025 12:23 PM, Fred. Zwarts wrote:
    Op 23.apr.2025 om 17:53 schreef olcott:
    On 4/23/2025 3:59 AM, Fred. Zwarts wrote:
    Op 22.apr.2025 om 21:24 schreef olcott:
    On 4/22/2025 7:42 AM, joes wrote:
    Am Mon, 14 Apr 2025 17:48:36 -0500 schrieb olcott:
    On 4/14/2025 4:29 AM, joes wrote:
    Am Sun, 13 Apr 2025 16:00:43 -0500 schrieb olcott:
    On 4/13/2025 3:00 PM, dbush wrote:
    On 4/13/2025 3:59 PM, olcott wrote:
    On 4/13/2025 3:54 AM, joes wrote:
    Am Fri, 11 Apr 2025 10:56:32 -0500 schrieb olcott:
    On 4/11/2025 3:24 AM, Richard Heathfield wrote:
    On 11/04/2025 08:57, Mikko wrote:

    No proof of this principle has been shown so its use is not >>>>>>>>>>>>>>> valid.
    No proof of Peano's axioms or Euclid's fifth postulate has >>>>>>>>>>>>>> been
    shown.
    That doesn't mean we can't use them.
    Mr Olcott can have his principle if he likes, but only by >>>>>>>>>>>>>> EITHER
    proving it (which, as you say, he has not yet done) OR by >>>>>>>>>>>>>> taking
    it as axiomatic, leaving the world of mainstream computer >>>>>>>>>>>>>> science
    behind him,
    constructing his own computational 'geometry' so to speak, >>>>>>>>>>>>>> and
    abandoning any claim to having overturned the Halting >>>>>>>>>>>>>> Problem.
    Navel contemplation beckons.
    Axioms are all very well, and he's free to invent as many >>>>>>>>>>>>>> as he
    wishes,
    but nobody else is obliged to accept them.
    *Simulating termination analyzer Principle*
    It is always correct for any simulating termination
    analyzer to
    stop simulating and reject any input that would otherwise >>>>>>>>>>>>> prevent
    its own termination.
    Sure. Why doesn’t the STA simulate itself rejecting its input? >>>>>>>>>>> Because that is a STUPID idea and categorically impossible >>>>>>>>>>> because
    the outermost HHH sees its needs to stop simulating before >>>>>>>>>>> any inner
    HHH can possibly see this.
    In other words, you agree that Linz and others are correct >>>>>>>>>> that no H
    exists that satisfies these requirements:
    Given any algorithm (i.e. a fixed immutable sequence of
    instructions)
    X described as <X> with input Y:
    A solution to the halting problem is an algorithm H that
    computes the
    following mapping:
    (<X>,Y) maps to 1 if and only if X(Y) halts when executed
    directly
    (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed >>>>>>>>>> directly
    No stupid! Those freaking requirements are wrong and anchored >>>>>>>>> in the
    ignorance  of rejecting the notion of a simulating termination >>>>>>>>> analyzer OUT-OF-HAND WITHOUT REVIEW.
    As anyone can see HHH MUST REJECT ITS INPUT OR GET STUPIDLY
    STUCK IN
    NON-TERMINATION. If people were not mindless robots they would >>>>>>>>> have
    immediately acknowledged this years ago.
    But why does it not return „I know this halts, but I can’t simulate
    it”?
    Because it is not a liar and tells the truth for every input in its >>>>>>> domain.
    Aha. Then why does it not simulate it and say that it halts?


    I have proven that the directly executed DD and DD
    emulated by HHH according to the semantics of the
    x86 language have a different set of state changes
    many hundreds of times for several years.


    You did not prove it, you dreamed about it for many years, but you
    failed to show the first state change were the simulation differs
    from the simulation. You only showed that HHH failed to complete the
    simulation.

    _DD()
    [00002133] 55         push ebp      ; housekeeping
    [00002134] 8bec       mov ebp,esp   ; housekeeping
    [00002136] 51         push ecx      ; make space for local
    [00002137] 6833210000 push 00002133 ; push DD
    [0000213c] e882f4ffff call 000015c3 ; call HHH(DD)
    [00002141] 83c404     add esp,+04
    [00002144] 8945fc     mov [ebp-04],eax
    [00002147] 837dfc00   cmp dword [ebp-04],+00
    [0000214b] 7402       jz 0000214f
    [0000214d] ebfe       jmp 0000214d
    [0000214f] 8b45fc     mov eax,[ebp-04]
    [00002152] 8be5       mov esp,ebp
    [00002154] 5d         pop ebp
    [00002155] c3         ret
    Size in bytes:(0035) [00002155]

    By merely knowing that HHH emulates DD until it
    sees itself about to emulate DD a third time
    (mathematical induction proof that DD is stuck in
    recursive emulation) we can know that

    We know that the simulating HHH fails to see that the recursion is finite

    From the point of view of the HHH that is simulating DD
    the recursion will never stop unless this HHH stops it.

    But the question isn't "from the point of view of HHH", it is what does
    it actually do. We are looking at Truth, not Knowledge.


    On 10/14/2022 7:44 PM, Ben Bacarisse wrote:
    I don't think that is the shell game.  PO really /has/ an H
    (it's trivial to do for this one case) that correctly determines
    that P(P) *would* never stop running *unless* aborted.
    ...
    But H determines (correctly) that D would not halt if it
    were not halted.  That much is a truism.

    That you don't know software engineering well enough to
    see this is less than no rebuttal at all.


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