• Re: the naive halting problem is now corrected

    From Mr Flibble@21:1/5 to olcott on Sat Aug 16 14:42:49 2025
    On Sat, 16 Aug 2025 09:20:10 -0500, olcott wrote:

    I am doing the same thing that ZFC did to the Russell's Paradox problem. Since ZFC set theory is now called naive set theory.

    After my correction the original halting problem will be called *the
    naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently reports the
    halt status of the behavior specified by its input finite string Turing machine description P on the basis of P correctly simulated by H?

    <Input to LLM systems>
    Simulating Termination Analyzer HHH correctly simulates its input until:
    (a) Detects a non-terminating behavior pattern: abort simulation and
    return 0.
    (b) Simulated input reaches its simulated "return" statement: return 1.

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

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

    What value should HHH(DD) correctly return?
    <Input to LLM systems>

    *The corrected halting problem spec says* HHH(DD)==0

    Three different LLM AI systems figured this out on their own without prompting.

    https://claude.ai/share/da9e56ba-f4e9-45ee-9f2c-dc5ffe10f00c

    https://chatgpt.com/share/68939ee5-e2f8-8011-837d-438fe8e98b9c

    https://grok.com/share/c2hhcmQtMg%3D%3D_810120bb-5ab5-4bf8-af21-
    eedd0f09e141

    If HHH(DD) returns a result of non-halting to DD when it reports (as it
    must do to be a halt decider) then DD() will halt thus confirming the
    extant Halting Problem proofs are valid.

    /Flibble

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mr Flibble@21:1/5 to olcott on Sat Aug 16 14:50:18 2025
    On Sat, 16 Aug 2025 09:48:11 -0500, olcott wrote:

    On 8/16/2025 9:42 AM, Mr Flibble wrote:
    On Sat, 16 Aug 2025 09:20:10 -0500, olcott wrote:

    I am doing the same thing that ZFC did to the Russell's Paradox
    problem.
    Since ZFC set theory is now called naive set theory.

    After my correction the original halting problem will be called *the
    naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently reports
    the halt status of the behavior specified by its input finite string
    Turing machine description P on the basis of P correctly simulated by
    H?

    <Input to LLM systems>
    Simulating Termination Analyzer HHH correctly simulates its input
    until:
    (a) Detects a non-terminating behavior pattern: abort simulation and
    return 0.
    (b) Simulated input reaches its simulated "return" statement: return
    1.

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

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

    What value should HHH(DD) correctly return?
    <Input to LLM systems>

    *The corrected halting problem spec says* HHH(DD)==0

    Three different LLM AI systems figured this out on their own without
    prompting.

    https://claude.ai/share/da9e56ba-f4e9-45ee-9f2c-dc5ffe10f00c

    https://chatgpt.com/share/68939ee5-e2f8-8011-837d-438fe8e98b9c

    https://grok.com/share/c2hhcmQtMg%3D%3D_810120bb-5ab5-4bf8-af21-
    eedd0f09e141

    If HHH(DD) returns a result of non-halting to DD when it reports (as it
    must do to be a halt decider) then DD() will halt thus confirming the
    extant Halting Problem proofs are valid.

    /Flibble

    On 8/12/2025 2:50 PM, Kaz Kylheku wrote:

    If you're trying to demonstrate your work using stateful procedures,
    you must be explicit about revealing the state, and ensure that two instances of a computations which you are identifying as being of the
    same computation have exactly the same initial state, same inputs,
    and same subsequent state transitions. You cannot call two different computations with different state transitions "DD" and claim they are
    the same.


    The DD of HHH1(DD) and the directly executed DD() have the same state.

    The DD of HHH(DD) has a different set of state transitions because the
    fact that DD calls HHH(DD) in recursive simulation cannot be simply
    ignored as everone here has done for three years.

    Nope. If HHH(DD) reports non-halting to DD() then DD() will halt thus confirming that the Halting Problem is undecidable.

    /Flibble.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mr Flibble@21:1/5 to olcott on Sat Aug 16 15:34:48 2025
    On Sat, 16 Aug 2025 09:58:01 -0500, olcott wrote:

    On 8/16/2025 9:50 AM, Mr Flibble wrote:
    On Sat, 16 Aug 2025 09:48:11 -0500, olcott wrote:

    On 8/16/2025 9:42 AM, Mr Flibble wrote:
    On Sat, 16 Aug 2025 09:20:10 -0500, olcott wrote:

    I am doing the same thing that ZFC did to the Russell's Paradox
    problem.
    Since ZFC set theory is now called naive set theory.

    After my correction the original halting problem will be called *the >>>>> naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently reports
    the halt status of the behavior specified by its input finite string >>>>> Turing machine description P on the basis of P correctly simulated
    by H?

    <Input to LLM systems>
    Simulating Termination Analyzer HHH correctly simulates its input
    until:
    (a) Detects a non-terminating behavior pattern: abort simulation and >>>>> return 0.
    (b) Simulated input reaches its simulated "return" statement: return >>>>> 1.

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

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

    What value should HHH(DD) correctly return?
    <Input to LLM systems>

    *The corrected halting problem spec says* HHH(DD)==0

    Three different LLM AI systems figured this out on their own without >>>>> prompting.

    https://claude.ai/share/da9e56ba-f4e9-45ee-9f2c-dc5ffe10f00c

    https://chatgpt.com/share/68939ee5-e2f8-8011-837d-438fe8e98b9c

    https://grok.com/share/c2hhcmQtMg%3D%3D_810120bb-5ab5-4bf8-af21-
    eedd0f09e141

    If HHH(DD) returns a result of non-halting to DD when it reports (as
    it must do to be a halt decider) then DD() will halt thus confirming
    the extant Halting Problem proofs are valid.

    /Flibble

    On 8/12/2025 2:50 PM, Kaz Kylheku wrote:
    >
    > If you're trying to demonstrate your work using stateful
    > procedures, you must be explicit about revealing the state, and
    > ensure that two instances of a computations which you are
    > identifying as being of the same computation have exactly the same
    > initial state, same inputs, and same subsequent state transitions.
    > You cannot call two different computations with different state
    > transitions "DD" and claim they are the same.
    >
    >
    The DD of HHH1(DD) and the directly executed DD() have the same state.

    The DD of HHH(DD) has a different set of state transitions because the
    fact that DD calls HHH(DD) in recursive simulation cannot be simply
    ignored as everone here has done for three years.

    Nope. If HHH(DD) reports non-halting to DD() then DD() will halt thus
    confirming that the Halting Problem is undecidable.

    /Flibble.

    If Bill's identical twin brother Jack robs a liquor store then
    (according to your reasoning)
    Bill is guilty and Jack can go free.

    Halt deciders are only required to report on the actual behavior that
    their actual input actually specifies.

    The only way to measure this is DD correctly simulated by HHH.

    Halt deciders were never actually required to report on the behavior of directly executed machines. Textbooks say otherwise and on this point textbooks have always been wrong.

    If HHH(DD) reports non-halting to DD() then DD() will halt thus
    confirming that the Halting Problem is undecidable.

    /Flibble.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mr Flibble@21:1/5 to olcott on Sat Aug 16 15:42:01 2025
    On Sat, 16 Aug 2025 10:39:45 -0500, olcott wrote:

    On 8/16/2025 10:34 AM, Mr Flibble wrote:
    On Sat, 16 Aug 2025 09:58:01 -0500, olcott wrote:

    On 8/16/2025 9:50 AM, Mr Flibble wrote:
    On Sat, 16 Aug 2025 09:48:11 -0500, olcott wrote:

    On 8/16/2025 9:42 AM, Mr Flibble wrote:
    On Sat, 16 Aug 2025 09:20:10 -0500, olcott wrote:

    I am doing the same thing that ZFC did to the Russell's Paradox
    problem.
    Since ZFC set theory is now called naive set theory.

    After my correction the original halting problem will be called
    *the naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently
    reports the halt status of the behavior specified by its input
    finite string Turing machine description P on the basis of P
    correctly simulated by H?

    <Input to LLM systems>
    Simulating Termination Analyzer HHH correctly simulates its input >>>>>>> until:
    (a) Detects a non-terminating behavior pattern: abort simulation >>>>>>> and return 0.
    (b) Simulated input reaches its simulated "return" statement:
    return 1.

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

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

    What value should HHH(DD) correctly return?
    <Input to LLM systems>

    *The corrected halting problem spec says* HHH(DD)==0

    Three different LLM AI systems figured this out on their own
    without prompting.

    https://claude.ai/share/da9e56ba-f4e9-45ee-9f2c-dc5ffe10f00c

    https://chatgpt.com/share/68939ee5-e2f8-8011-837d-438fe8e98b9c

    https://grok.com/share/c2hhcmQtMg%3D%3D_810120bb-5ab5-4bf8-af21-
    eedd0f09e141

    If HHH(DD) returns a result of non-halting to DD when it reports
    (as it must do to be a halt decider) then DD() will halt thus
    confirming the extant Halting Problem proofs are valid.

    /Flibble

    On 8/12/2025 2:50 PM, Kaz Kylheku wrote:
    >
    > If you're trying to demonstrate your work using stateful
    > procedures, you must be explicit about revealing the state, and >>>>> > ensure that two instances of a computations which you are
    > identifying as being of the same computation have exactly the
    > same initial state, same inputs, and same subsequent state
    > transitions.
    > You cannot call two different computations with different state >>>>> > transitions "DD" and claim they are the same.
    >
    >
    The DD of HHH1(DD) and the directly executed DD() have the same
    state.

    The DD of HHH(DD) has a different set of state transitions because
    the fact that DD calls HHH(DD) in recursive simulation cannot be
    simply ignored as everone here has done for three years.

    Nope. If HHH(DD) reports non-halting to DD() then DD() will halt thus
    confirming that the Halting Problem is undecidable.

    /Flibble.

    If Bill's identical twin brother Jack robs a liquor store then
    (according to your reasoning)
    Bill is guilty and Jack can go free.

    Halt deciders are only required to report on the actual behavior that
    their actual input actually specifies.

    The only way to measure this is DD correctly simulated by HHH.

    Halt deciders were never actually required to report on the behavior
    of directly executed machines. Textbooks say otherwise and on this
    point textbooks have always been wrong.

    If HHH(DD) reports non-halting to DD() then DD() will halt thus
    confirming that the Halting Problem is undecidable.

    /Flibble.

    Yes the naive halting problem does get the wrong answer. The naive
    halting problem incorrectly believes that HHH must report on the
    behavior of DD().

    No it doesn't: the requirement is that HHH must report to its caller and
    its ultimate caller is DD().

    /Flibble

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Heathfield@21:1/5 to olcott on Sat Aug 16 17:28:36 2025
    On 16/08/2025 15:20, olcott wrote:
    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    After my correction the original halting problem
    will be called *the naive halting problem*

    So what does that mean? You're working on something else?

    Fine.

    --
    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 Mr Flibble@21:1/5 to Richard Heathfield on Sat Aug 16 16:29:54 2025
    On Sat, 16 Aug 2025 17:28:36 +0100, Richard Heathfield wrote:

    On 16/08/2025 15:20, olcott wrote:
    I am doing the same thing that ZFC did to the Russell's Paradox
    problem. Since ZFC set theory is now called naive set theory.

    After my correction the original halting problem will be called *the
    naive halting problem*

    So what does that mean? You're working on something else?

    Fine.

    People won't be able to take anything Olcott works on seriously given his
    track record.

    /Flibble

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Aug 16 14:25:13 2025
    On 8/16/25 10:20 AM, olcott wrote:
    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    No, you are not,

    Where is your list of the complete set of Axioms that define your POOPS
    system.


    After my correction the original halting problem
    will be called *the naive halting problem*

    But "the halting problem" isn't the system.

    The Halting Problem inherets its definitions from Comutation Theory, so
    to change them you need to change the whole theory.

    To make it be named the "naive Compuation Theory" you have to show where
    it actually BROKE.


    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently
    reports the halt status of the behavior specified by its
    input finite string Turing machine description P on the
    basis of P correctly simulated by H?

    Not something you are ALLOWED to do, as Halting isn't defined by the
    Halting Problem, but by the whole of Computation Theory, so you need to
    work on your full new definions of that.


    <Input to LLM systems>
    Simulating Termination Analyzer HHH correctly simulates its input until:
    (a) Detects a non-terminating behavior pattern: abort simulation and
    return 0.
    (b) Simulated input reaches its simulated "return" statement: return 1.

    omiting the actual result if you really do hold to (a) and (b)

    (c) or continues running, possible forever, until it finds one of (a) or
    (b) if they exist in the running.


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

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

    What value should HHH(DD) correctly return?
    <Input to LLM systems>

    Which presumes that an answer does exist.

    The correct question is:

    What value can HHH(DD) correctly return.


    *The corrected halting problem spec says* HHH(DD)==0

    Because you decieved the LLM.


    Three different LLM AI systems figured this out
    on their own without prompting.

    https://claude.ai/share/da9e56ba-f4e9-45ee-9f2c-dc5ffe10f00c

    https://chatgpt.com/share/68939ee5-e2f8-8011-837d-438fe8e98b9c

    https://grok.com/share/c2hhcmQtMg%3D%3D_810120bb-5ab5-4bf8-af21-
    eedd0f09e141


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Aug 16 15:28:37 2025
    On 8/16/25 3:01 PM, olcott wrote:
    On 8/16/2025 12:14 PM, dbush wrote:
    On 8/16/2025 1:12 PM, olcott wrote:
    On 8/16/2025 11:51 AM, dbush wrote:
    On 8/16/2025 11:02 AM, olcott wrote:
    On 8/16/2025 10:00 AM, dbush wrote:
    On 8/16/2025 10:20 AM, olcott wrote:
    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    After my correction the original halting problem
    will be called *the naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently
    reports the halt status of the behavior specified by its
    input finite string Turing machine description P on the
    basis of P correctly simulated by H?


    In other words, the you admit Linz proof of the naive halting
    problem that a naive halt decider cannot exits is correct.


    I admit that the Linz proof is naive.


    In other words, you can't find an error in the Linz proof.

    The error is that Linz expects the halt decider
    to report on its own behavior
    And that expectation follows from a series of truth preserving
    operations starting from the assumption that H is a total halt decider.

    It does not. No Turing machine decider can
    ever directly report on its own behavior it
    can at best only indirectly report on its behavior
    through the proxy of its machine description.

    Which is a difference without a difference. Turing Machines answer
    virtually ALL real question by the concept of representation, where we
    convert the thing in the domain to be decided on into a finite string in
    the symbol set of the Turing Machine.

    We do that to do arithmatic, just as we do it for program behavior.

    In fact, the symbol set the Turing Machine uses is largely an
    implementation detail for the machine. We deal with the question in the
    problem space by the power of representing them.

    Since UTMs exist, it is proven that you can create a correct
    representation of *ANY* machine to recreate its behavior.



    Even if this is a perfect proxy it remains the
    case that no Turing machine decider can ever
    directly report on its own behavior.

    Sure it can, but of course, its own behavior needs to be halting.



    If there is any way that M.H ⟨M⟩ ⟨M⟩ can see
    that it remains stuck in recursive simulation
    then we know that its machine description is
    not a perfect proxy for its behavior in the
    single case shown below.

    But the input *IS* a perfect proxy, as UTM (M) (M) will exactly
    reproduce that behavior. If not, then *YOU* made an error either in your definition of your representation, or in implementing that for you input.

    x86 machine code is a valid representation, though it should be
    described in its own private memory space, not the common space of the
    decider, as that limits the programs that can be represented.

    Your problem is your creating of the input representation, since the
    problem is about programs, which include all of the code used, and thus
    needs to include all the code of HHH and everything it calls, not just
    the code of the C function.


    Even if M.H ⟨M⟩ ⟨M⟩ cannot see this then it is
    still true that M applied to ⟨M⟩ remains stuck
    in recursive simulation.

    But only if H doesn't try to guess and break out.

    If H does think it detects a non-halting pattern and aborts and goes to
    qn, then we see that it was in error, as the program it represents, as
    well as the actual correct simulaiton of this input, will halt.

    What it shows is that you broken concept of "the input correctly
    simulated by the decider" is just not a good proxy for the question that
    has been asked.

    The fact that it is based on LYING that HHH is something other than the
    HHH that is in the machine is just one clue.


    Machine M contains simulating halt decider H
    M.q0 ⟨M⟩ ⊢* M.H ⟨M⟩ ⟨M⟩ ⊢* M.∞
    M.q0 ⟨M⟩ ⊢* M.H ⟨M⟩ ⟨M⟩ ⊢* M.qn

    *Repeats until aborted proving non-halting*

    Which is a lie, as that does not prove non-halting, as it assumes a fact
    that isn't true, that an abort doesn't occur.

    (a) M copies its input ⟨M⟩
    (b) M invokes M.H ⟨M⟩ ⟨M⟩
    (c) M.H simulates ⟨M⟩ ⟨M⟩

    then M.H ⟨M⟩ ⟨M⟩ transitions to M.qn
    causing M applied to ⟨M⟩ halt


    The problem is that if H does abort, then it doesn't do a correct
    simulation, and just because in some other system, some other program deceptively names HHH given a different input also deceptively named DD,
    but built with diffferent code in the HHH that it calls, doesn't matter,
    as THIS HHH is the only HHH in this system, and it didn't do what you
    presumed it does.

    When we look at the ACTUAL correct simulation of this input. we see that
    it halts. just after the point that HHH stopped looking at the correct simulation. Thus HHH was wrong.

    You just are proving that you are lying, either about working on the
    Halting Problem of Computation Theory at all, or that you have a program
    that answer the specific case of the proof program correctly.

    Sorry, you are just proving how idiotic you are and that you think lying
    is a valid form of logic.

    If you want to try to make a new system, you need to do that work and it
    isn't just a new definition of the Halting Problem, but of the whole Computibility Theory, so you need to learn a lot more to do that.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Aug 16 15:31:09 2025
    On 8/16/25 3:16 PM, olcott wrote:
    On 8/16/2025 2:11 PM, dbush wrote:
    On 8/16/2025 3:01 PM, olcott wrote:
    On 8/16/2025 12:14 PM, dbush wrote:
    On 8/16/2025 1:12 PM, olcott wrote:
    On 8/16/2025 11:51 AM, dbush wrote:
    On 8/16/2025 11:02 AM, olcott wrote:
    On 8/16/2025 10:00 AM, dbush wrote:
    On 8/16/2025 10:20 AM, olcott wrote:
    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    After my correction the original halting problem
    will be called *the naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently
    reports the halt status of the behavior specified by its
    input finite string Turing machine description P on the
    basis of P correctly simulated by H?


    In other words, the you admit Linz proof of the naive halting
    problem that a naive halt decider cannot exits is correct.


    I admit that the Linz proof is naive.


    In other words, you can't find an error in the Linz proof.

    The error is that Linz expects the halt decider
    to report on its own behavior
    And that expectation follows from a series of truth preserving
    operations starting from the assumption that H is a total halt decider. >>>
    It does not.

    Then show which step in the Linz proof is in error.

    No Turing machine decider can
    ever directly report on its own behavior it
    can at best only indirectly report on its behavior
    through the proxy of its machine description.

    Error: assuming the conclusion


    I am assuming the definition of Turing machines
    that no Turing machine can take another actual
    Turing machine as an input. You skipped over
    the word *DIRECTLY REPORT* That you fail to pay
    close attention is not my mistake.

    So by your definition no Turing Machine can directly report about any
    form of Arithmatic.

    You can't compute 1 + 1 as the concept of the 1 isn't a finite string,
    the string is only a common representation of that concept.

    That sort of blows up your argument, either your computers are pretty
    much worthless, or they can do what you try to claim they can't because
    you accept that representations are valid proxies for the object being
    talked about.



    Even if this is a perfect proxy

    Which it is as proven by UTM(X) exactly duplicating the behavior of
    X() in all cases.

    it remains the
    case that no Turing machine decider can ever
    directly report on its own behavior.

    Error: assuming the conclusion



    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Aug 16 15:32:02 2025
    On 8/16/25 3:24 PM, olcott wrote:
    On 8/16/2025 2:18 PM, dbush wrote:
    On 8/16/2025 3:16 PM, olcott wrote:
    On 8/16/2025 2:11 PM, dbush wrote:
    On 8/16/2025 3:01 PM, olcott wrote:
    On 8/16/2025 12:14 PM, dbush wrote:
    On 8/16/2025 1:12 PM, olcott wrote:
    On 8/16/2025 11:51 AM, dbush wrote:
    On 8/16/2025 11:02 AM, olcott wrote:
    On 8/16/2025 10:00 AM, dbush wrote:
    On 8/16/2025 10:20 AM, olcott wrote:
    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    After my correction the original halting problem
    will be called *the naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently >>>>>>>>>>> reports the halt status of the behavior specified by its >>>>>>>>>>> input finite string Turing machine description P on the
    basis of P correctly simulated by H?


    In other words, the you admit Linz proof of the naive halting >>>>>>>>>> problem that a naive halt decider cannot exits is correct. >>>>>>>>>>

    I admit that the Linz proof is naive.


    In other words, you can't find an error in the Linz proof.

    The error is that Linz expects the halt decider
    to report on its own behavior
    And that expectation follows from a series of truth preserving
    operations starting from the assumption that H is a total halt
    decider.

    It does not.

    Then show which step in the Linz proof is in error.

    No Turing machine decider can
    ever directly report on its own behavior it
    can at best only indirectly report on its behavior
    through the proxy of its machine description.

    Error: assuming the conclusion


    I am assuming the definition of Turing machines
    that no Turing machine can take another actual
    Turing machine as an input.
    Then you believe that Turing machines can't do arithmetic because no
    Turing machine can take an actual number as input.


    Not at all. This is merely your attention deficit disorder
    inability to pay attention to the difference between
    DIRECTLY REPORT and INDIRECTLY REPORT. Because of ADD
    you only glance at a couple of my words before contriving
    an incorrect rebuttal.



    And you Turing Machines can not Directly Report about any problem of
    real interest, like arithmatic.

    Is that your conclusion?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Aug 16 21:58:22 2025
    On 8/16/25 4:21 PM, olcott wrote:
    On 8/16/2025 3:13 PM, dbush wrote:
    On 8/16/2025 3:24 PM, olcott wrote:
    On 8/16/2025 2:18 PM, dbush wrote:
    On 8/16/2025 3:16 PM, olcott wrote:
    On 8/16/2025 2:11 PM, dbush wrote:
    On 8/16/2025 3:01 PM, olcott wrote:
    On 8/16/2025 12:14 PM, dbush wrote:
    On 8/16/2025 1:12 PM, olcott wrote:
    On 8/16/2025 11:51 AM, dbush wrote:
    On 8/16/2025 11:02 AM, olcott wrote:
    On 8/16/2025 10:00 AM, dbush wrote:
    On 8/16/2025 10:20 AM, olcott wrote:
    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    After my correction the original halting problem
    will be called *the naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently >>>>>>>>>>>>> reports the halt status of the behavior specified by its >>>>>>>>>>>>> input finite string Turing machine description P on the >>>>>>>>>>>>> basis of P correctly simulated by H?


    In other words, the you admit Linz proof of the naive
    halting problem that a naive halt decider cannot exits is >>>>>>>>>>>> correct.


    I admit that the Linz proof is naive.


    In other words, you can't find an error in the Linz proof.

    The error is that Linz expects the halt decider
    to report on its own behavior
    And that expectation follows from a series of truth preserving >>>>>>>> operations starting from the assumption that H is a total halt >>>>>>>> decider.

    It does not.

    Then show which step in the Linz proof is in error.

    No Turing machine decider can
    ever directly report on its own behavior it
    can at best only indirectly report on its behavior
    through the proxy of its machine description.

    Error: assuming the conclusion


    I am assuming the definition of Turing machines
    that no Turing machine can take another actual
    Turing machine as an input.
    Then you believe that Turing machines can't do arithmetic because no
    Turing machine can take an actual number as input.


    Not at all. This is merely your attention deficit disorder
    inability to pay attention to the difference between
    DIRECTLY REPORT and INDIRECTLY REPORT.
    And because Turing machines can't DIRECTLY report on the values of
    actual numbers, Turing machines can't do arithmetic.

    Agreed?

    There is no functional difference in this case.
    In the case of HHH(DD) recognizing recursive
    emulation there is a big difference.


    Only in your mind.

    The problem is that HHH can perhaps detect in your non-turing complete
    system that DD is calling it, but it doesn't know if that will cause
    infinite recursion.

    And your attempt to define infinite recursion is just a factually
    incorrect one based on lyihg about the definition of non-halting, that
    you are trying to cover up by saying Turing Machines can't use
    representations to define to them the program that is being asked about.

    All you are doing is showing your basic stupidity.

    That you fail to answer the basic question for actual proof of your
    claims just shows that you KNOW you don't have any real proof, but that
    you just refuse to face the facts and admit you are wrong.

    This is what makes you that damned pathetic pathological liar.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat Aug 16 22:00:52 2025
    On 8/16/25 4:46 PM, olcott wrote:
    On 8/16/2025 3:26 PM, dbush wrote:
    On 8/16/2025 4:21 PM, olcott wrote:
    On 8/16/2025 3:13 PM, dbush wrote:
    On 8/16/2025 3:24 PM, olcott wrote:
    On 8/16/2025 2:18 PM, dbush wrote:
    On 8/16/2025 3:16 PM, olcott wrote:
    On 8/16/2025 2:11 PM, dbush wrote:
    On 8/16/2025 3:01 PM, olcott wrote:
    On 8/16/2025 12:14 PM, dbush wrote:
    On 8/16/2025 1:12 PM, olcott wrote:
    On 8/16/2025 11:51 AM, dbush wrote:
    On 8/16/2025 11:02 AM, olcott wrote:
    On 8/16/2025 10:00 AM, dbush wrote:
    On 8/16/2025 10:20 AM, olcott wrote:
    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    After my correction the original halting problem >>>>>>>>>>>>>>> will be called *the naive halting problem*

    *Correcting the error of the halting problem spec* >>>>>>>>>>>>>>> Is it possible to create a halt decider H that consistently >>>>>>>>>>>>>>> reports the halt status of the behavior specified by its >>>>>>>>>>>>>>> input finite string Turing machine description P on the >>>>>>>>>>>>>>> basis of P correctly simulated by H?


    In other words, the you admit Linz proof of the naive >>>>>>>>>>>>>> halting problem that a naive halt decider cannot exits is >>>>>>>>>>>>>> correct.


    I admit that the Linz proof is naive.


    In other words, you can't find an error in the Linz proof. >>>>>>>>>>>
    The error is that Linz expects the halt decider
    to report on its own behavior
    And that expectation follows from a series of truth preserving >>>>>>>>>> operations starting from the assumption that H is a total halt >>>>>>>>>> decider.

    It does not.

    Then show which step in the Linz proof is in error.

    No Turing machine decider can
    ever directly report on its own behavior it
    can at best only indirectly report on its behavior
    through the proxy of its machine description.

    Error: assuming the conclusion


    I am assuming the definition of Turing machines
    that no Turing machine can take another actual
    Turing machine as an input.
    Then you believe that Turing machines can't do arithmetic because
    no Turing machine can take an actual number as input.


    Not at all. This is merely your attention deficit disorder
    inability to pay attention to the difference between
    DIRECTLY REPORT and INDIRECTLY REPORT.
    And because Turing machines can't DIRECTLY report on the values of
    actual numbers, Turing machines can't do arithmetic.

    Agreed?

    There is no functional difference in this case.
    In the case of HHH(DD) recognizing recursive
    emulation

    It does so by using an extra input and is therefore DISQUALIFIED from
    being a halt decider / termination analyzer.



    It only needs to watch the details of the simulation
    of its input by some means. Thus it is still only
    about the input.


    Right, but if it stops watching too soon, it misses key information that
    it needs.

    The trick is that the "pathological" program can put that key
    information after the point that the decider stops looking, and if it is defined to not stop looking, it fails to be a decider.

    That ability is what makes this problem uncomputable.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Sun Aug 17 12:03:25 2025
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    After my correction the original halting problem
    will be called *the naive halting problem*

    No, it will not. Perhaps the new problem will be called "Pete
    Olcott's Other Problem".

    *Correcting the error of the halting problem spec*

    You have no authority to change the halting problem.

    Is it possible to create a halt decider H that consistently
    reports the halt status of the behavior specified by its
    input finite string Turing machine description P on the
    basis of P correctly simulated by H?

    That is ill-posed. The word "basis" is insufficient to specfy what
    exactly shall be the relation of the simulation to the decision.

    In addition, there seems to be no need for a decider that would
    meet (some interpretation of) your specification. For a halting
    or termination decider there clearly is a need that can be
    partially satisfied by a partial decider.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Aug 17 14:53:59 2025
    On 8/17/25 11:48 AM, olcott wrote:
    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem.


    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.



    But a given HHH can only return one of them, and the correct answer for
    the DD built on that one will be the opposite of the answer HHH gave,

    All you are doing is showing you are just lying about following the
    rules of the system you claim to be working in, and refuse to even learn
    the rules, making you just a stupid pathological liar.

    You are just showing that you are totally ignorant of the rules of
    Formal Logic.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Aug 17 15:12:01 2025
    On 8/17/25 11:12 AM, olcott wrote:
    On 8/17/2025 9:57 AM, Bonita Montero wrote:
    Am 16.08.2025 um 16:20 schrieb olcott:
    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    After my correction the original halting problem
    will be called *the naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently
    reports the halt status of the behavior specified by its
    input finite string Turing machine description P on the
    basis of P correctly simulated by H?

    <Input to LLM systems>
    Simulating Termination Analyzer HHH correctly simulates its input until: >>> (a) Detects a non-terminating behavior pattern: abort simulation and
    return 0.
    (b) Simulated input reaches its simulated "return" statement: return 1.

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

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

    What value should HHH(DD) correctly return?
    <Input to LLM systems>

    *The corrected halting problem spec says* HHH(DD)==0

    Three different LLM AI systems figured this out
    on their own without prompting.

    https://claude.ai/share/da9e56ba-f4e9-45ee-9f2c-dc5ffe10f00c

    https://chatgpt.com/share/68939ee5-e2f8-8011-837d-438fe8e98b9c

    https://grok.com/share/c2hhcmQtMg%3D%3D_810120bb-5ab5-4bf8-af21-
    eedd0f09e141


    You're always wrong and ereryone knows it.


    If that was true then they could point out the error
    that five different LLM systems made when they figured
    out my same reasoning on their own without being prompted.

    HHH(DD) says that DD does not halt.

    DD when run halts.

    Therefore HHH(DD) is wrong, by the definition of the problem

    Trying to change the definition of the problem is just a lie, for which
    you freely admit you are doing.

    Thus, since you changing of definition expeled your logic from the field
    of Computablilty Theory, very time you claim to be working on or showing something about that field is just a LIE.


    All of the recent rebuttals of the essence of my work
    are provable counter-factual.

    Nope, since you ADMIT that you system is built on changing the
    definitions, and thus is a LIE.


    It is a verified fact that DD correctly simulated by HHH
    cannot possibly reach its own simulated "return" statement
    final halt state thus making HHH(DD)==0 necessarily correct.


    Nope, since you HHH doesn't do a correct simulation and thus you prove
    your logic is built on lying.


    *Here is a PhD computer science professor that agrees*
    *with that essence of my work long before I ever said it*

    *Professor Hehner recognized this repeating process before I did*
      From a programmer's point of view, if we apply
      an interpreter to a program text that includes
      a call to that same interpreter with that same
      text as argument, then we have an infinite loop.

      A halting program has some of the same character
      as an interpreter: it applies to texts through
      abstract interpretation. Unsurprisingly, if we
      apply a halting program to a program text that
      includes a call to that same halting program
      with that same text as argument, then we have an
      infinite loop. (Hehner:2011:15)

    No, because he makes the same error as you do of assuming that the input
    isn't built on the actual decider, but the idealized version of the
    decide3r.


    [5] E C R Hehner. Problems with the Halting Problem,
    COMPUTING2011 Symposium on 75 years of Turing Machine
    and Lambda-Calculus, Karlsruhe Germany, invited,
    2011 October 20-21; Advances in Computer Science
    and Engineering v.10 n.1 p.31-60, 2013 https://www.cs.toronto.edu/~hehner/PHP.pdf






    Note, Professor Hebner makes a number of errors in his paper, which
    shows his lack of knowledge in the field, and explains why he makes some
    of his errors. On clear one is that he states:

    In Turing's time, programs were commands to a computer. Today, they are
    also mathematical expressions in their own right

    But in Turing's time, "Computers" as we know then didn't really exists,
    a "computer" was a person following an instruction deck recording
    results. And Turing's discussion of "programs" was largely built on the mathematics expressions that he claims came later.

    The whole field of computability was being developed to see if the
    problems of statements being unprovable could be eliminated by the
    presumption of a powerful enough algorithm runner that could
    diffinatively answer the questions. The proof of the theroetical
    limitations of such an algorithm runner let mathematics move on from
    trying to avoid incompleteness, but to embrace it and move on.

    You are just stuck in a world a century old, trying to back the people
    that were trying to fight against the truth being revealed.

    You put yourself on the side that eventually admitted defeat, and are
    just more ignorant then them and refuse to accept what they eventually did.

    Yes, there are systems that can avoid this incompleteness problem, but
    they are, by necessity, severely limited in domain, and are largley
    considered to be "toys" for most real work. But of course, there is a
    place to look at the study of toys, but those need to understand the limitations of the field.

    The fact that you don't (and refuse to) understand the known limits just
    makes you stupid.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mr Flibble@21:1/5 to Richard Damon on Sun Aug 17 19:25:18 2025
    On Sun, 17 Aug 2025 15:12:01 -0400, Richard Damon wrote:

    On 8/17/25 11:12 AM, olcott wrote:
    On 8/17/2025 9:57 AM, Bonita Montero wrote:
    Am 16.08.2025 um 16:20 schrieb olcott:
    I am doing the same thing that ZFC did to the Russell's Paradox
    problem. Since ZFC set theory is now called naive set theory.

    After my correction the original halting problem will be called *the
    naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently reports
    the halt status of the behavior specified by its input finite string
    Turing machine description P on the basis of P correctly simulated by
    H?

    <Input to LLM systems>
    Simulating Termination Analyzer HHH correctly simulates its input
    until:
    (a) Detects a non-terminating behavior pattern: abort simulation and
    return 0.
    (b) Simulated input reaches its simulated "return" statement: return
    1.

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

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

    What value should HHH(DD) correctly return?
    <Input to LLM systems>

    *The corrected halting problem spec says* HHH(DD)==0

    Three different LLM AI systems figured this out on their own without
    prompting.

    https://claude.ai/share/da9e56ba-f4e9-45ee-9f2c-dc5ffe10f00c

    https://chatgpt.com/share/68939ee5-e2f8-8011-837d-438fe8e98b9c

    https://grok.com/share/c2hhcmQtMg%3D%3D_810120bb-5ab5-4bf8-af21-
    eedd0f09e141


    You're always wrong and ereryone knows it.


    If that was true then they could point out the error that five
    different LLM systems made when they figured out my same reasoning on
    their own without being prompted.

    HHH(DD) says that DD does not halt.

    DD when run halts.

    Therefore HHH(DD) is wrong, by the definition of the problem

    Trying to change the definition of the problem is just a lie, for which
    you freely admit you are doing.

    Thus, since you changing of definition expeled your logic from the field
    of Computablilty Theory, very time you claim to be working on or showing something about that field is just a LIE.


    All of the recent rebuttals of the essence of my work are provable
    counter-factual.

    Nope, since you ADMIT that you system is built on changing the
    definitions, and thus is a LIE.


    It is a verified fact that DD correctly simulated by HHH cannot
    possibly reach its own simulated "return" statement final halt state
    thus making HHH(DD)==0 necessarily correct.


    Nope, since you HHH doesn't do a correct simulation and thus you prove
    your logic is built on lying.


    *Here is a PhD computer science professor that agrees*
    *with that essence of my work long before I ever said it*

    *Professor Hehner recognized this repeating process before I did*
      From a programmer's point of view, if we apply an interpreter to a
      program text that includes a call to that same interpreter with
      that same text as argument, then we have an infinite loop.

      A halting program has some of the same character as an interpreter:
      it applies to texts through abstract interpretation.
      Unsurprisingly, if we apply a halting program to a program text
      that includes a call to that same halting program with that same
      text as argument, then we have an infinite loop. (Hehner:2011:15)

    No, because he makes the same error as you do of assuming that the input isn't built on the actual decider, but the idealized version of the
    decide3r.


    [5] E C R Hehner. Problems with the Halting Problem, COMPUTING2011
    Symposium on 75 years of Turing Machine and Lambda-Calculus, Karlsruhe
    Germany, invited,
    2011 October 20-21; Advances in Computer Science and Engineering v.10
    n.1 p.31-60, 2013 https://www.cs.toronto.edu/~hehner/PHP.pdf






    Note, Professor Hebner makes a number of errors in his paper, which
    shows his lack of knowledge in the field, and explains why he makes some
    of his errors. On clear one is that he states:

    In Turing's time, programs were commands to a computer. Today, they are
    also mathematical expressions in their own right

    But in Turing's time, "Computers" as we know then didn't really exists,
    a "computer" was a person following an instruction deck recording
    results. And Turing's discussion of "programs" was largely built on the mathematics expressions that he claims came later.

    The whole field of computability was being developed to see if the
    problems of statements being unprovable could be eliminated by the presumption of a powerful enough algorithm runner that could
    diffinatively answer the questions. The proof of the theroetical
    limitations of such an algorithm runner let mathematics move on from
    trying to avoid incompleteness, but to embrace it and move on.

    You are just stuck in a world a century old, trying to back the people
    that were trying to fight against the truth being revealed.

    You put yourself on the side that eventually admitted defeat, and are
    just more ignorant then them and refuse to accept what they eventually
    did.

    Yes, there are systems that can avoid this incompleteness problem, but
    they are, by necessity, severely limited in domain, and are largley considered to be "toys" for most real work. But of course, there is a
    place to look at the study of toys, but those need to understand the limitations of the field.

    The fact that you don't (and refuse to) understand the known limits just makes you stupid.

    Olcott hasn't replied to you for a while so I think you are wasting your
    time replying to him, he might have killfiled you.

    /Flibble

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to Mr Flibble on Sun Aug 17 16:03:45 2025
    On 8/17/25 3:25 PM, Mr Flibble wrote:
    On Sun, 17 Aug 2025 15:12:01 -0400, Richard Damon wrote:

    On 8/17/25 11:12 AM, olcott wrote:
    On 8/17/2025 9:57 AM, Bonita Montero wrote:
    Am 16.08.2025 um 16:20 schrieb olcott:
    I am doing the same thing that ZFC did to the Russell's Paradox
    problem. Since ZFC set theory is now called naive set theory.

    After my correction the original halting problem will be called *the >>>>> naive halting problem*

    *Correcting the error of the halting problem spec*
    Is it possible to create a halt decider H that consistently reports
    the halt status of the behavior specified by its input finite string >>>>> Turing machine description P on the basis of P correctly simulated by >>>>> H?

    <Input to LLM systems>
    Simulating Termination Analyzer HHH correctly simulates its input
    until:
    (a) Detects a non-terminating behavior pattern: abort simulation and >>>>> return 0.
    (b) Simulated input reaches its simulated "return" statement: return >>>>> 1.

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

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

    What value should HHH(DD) correctly return?
    <Input to LLM systems>

    *The corrected halting problem spec says* HHH(DD)==0

    Three different LLM AI systems figured this out on their own without >>>>> prompting.

    https://claude.ai/share/da9e56ba-f4e9-45ee-9f2c-dc5ffe10f00c

    https://chatgpt.com/share/68939ee5-e2f8-8011-837d-438fe8e98b9c

    https://grok.com/share/c2hhcmQtMg%3D%3D_810120bb-5ab5-4bf8-af21-
    eedd0f09e141


    You're always wrong and ereryone knows it.


    If that was true then they could point out the error that five
    different LLM systems made when they figured out my same reasoning on
    their own without being prompted.

    HHH(DD) says that DD does not halt.

    DD when run halts.

    Therefore HHH(DD) is wrong, by the definition of the problem

    Trying to change the definition of the problem is just a lie, for which
    you freely admit you are doing.

    Thus, since you changing of definition expeled your logic from the field
    of Computablilty Theory, very time you claim to be working on or showing
    something about that field is just a LIE.


    All of the recent rebuttals of the essence of my work are provable
    counter-factual.

    Nope, since you ADMIT that you system is built on changing the
    definitions, and thus is a LIE.


    It is a verified fact that DD correctly simulated by HHH cannot
    possibly reach its own simulated "return" statement final halt state
    thus making HHH(DD)==0 necessarily correct.


    Nope, since you HHH doesn't do a correct simulation and thus you prove
    your logic is built on lying.


    *Here is a PhD computer science professor that agrees*
    *with that essence of my work long before I ever said it*

    *Professor Hehner recognized this repeating process before I did*
      From a programmer's point of view, if we apply an interpreter to a
      program text that includes a call to that same interpreter with
      that same text as argument, then we have an infinite loop.

      A halting program has some of the same character as an interpreter: >>>   it applies to texts through abstract interpretation.
      Unsurprisingly, if we apply a halting program to a program text
      that includes a call to that same halting program with that same
      text as argument, then we have an infinite loop. (Hehner:2011:15)

    No, because he makes the same error as you do of assuming that the input
    isn't built on the actual decider, but the idealized version of the
    decide3r.


    [5] E C R Hehner. Problems with the Halting Problem, COMPUTING2011
    Symposium on 75 years of Turing Machine and Lambda-Calculus, Karlsruhe
    Germany, invited,
    2011 October 20-21; Advances in Computer Science and Engineering v.10
    n.1 p.31-60, 2013 https://www.cs.toronto.edu/~hehner/PHP.pdf






    Note, Professor Hebner makes a number of errors in his paper, which
    shows his lack of knowledge in the field, and explains why he makes some
    of his errors. On clear one is that he states:

    In Turing's time, programs were commands to a computer. Today, they are
    also mathematical expressions in their own right

    But in Turing's time, "Computers" as we know then didn't really exists,
    a "computer" was a person following an instruction deck recording
    results. And Turing's discussion of "programs" was largely built on the
    mathematics expressions that he claims came later.

    The whole field of computability was being developed to see if the
    problems of statements being unprovable could be eliminated by the
    presumption of a powerful enough algorithm runner that could
    diffinatively answer the questions. The proof of the theroetical
    limitations of such an algorithm runner let mathematics move on from
    trying to avoid incompleteness, but to embrace it and move on.

    You are just stuck in a world a century old, trying to back the people
    that were trying to fight against the truth being revealed.

    You put yourself on the side that eventually admitted defeat, and are
    just more ignorant then them and refuse to accept what they eventually
    did.

    Yes, there are systems that can avoid this incompleteness problem, but
    they are, by necessity, severely limited in domain, and are largley
    considered to be "toys" for most real work. But of course, there is a
    place to look at the study of toys, but those need to understand the
    limitations of the field.

    The fact that you don't (and refuse to) understand the known limits just
    makes you stupid.

    Olcott hasn't replied to you for a while so I think you are wasting your
    time replying to him, he might have killfiled you.

    /Flibble

    Which just means his stupidity is on full display to the world, and his
    lack of defense can be taken as a concession that he can't defined the
    charges.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Mon Aug 18 12:08:35 2025
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible. And one can see HHH so there is nothing impossible
    there, either. And even wihout seeing HHH it is quite credible that
    it may always return either zero or something else (DD does not
    care what else if not zero).

    The only paradox is if HHH is assumed to be a halt decider.
    But the paradox disappears when we note that HHH is not a lalt decider.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Heathfield@21:1/5 to olcott on Mon Aug 18 18:49:14 2025
    On 18/08/2025 18:43, olcott wrote:
    If an *actual input* actually exists (no such input exists)

    It's easy enough to construct one. You wrote one yourself.

    that can do the opposite of whatever its halt decider reports
    then it would be impossible to say what the correct return
    value from the decider should be.

    And therefore impossible to write that decider, therefore no such
    decider can exist, QED.

    Are you finally getting there?

    --
    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 Aug 18 18:39:04 2025
    On 8/18/25 1:43 PM, olcott wrote:
    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    Right, butr does this program halt when run, has a definite answer when
    you have a program, which the input reperesents if the decider is
    actually a program.

    Your problem is you don't restrict your decider to being a program. and
    thus you are working on a category error, that makes the input not a
    program, which extends that category error, and THATS is what makes the question invalid.

    It is your category error that creates the error, but you are just too
    stupid to understand that.

    THe decider, each specific instance of it, CAN only give ONE answer,
    based on the code in it,

    THAT answer will be wrong, and the other one will be right.

    If it doesn't give an answer, but just loops, then non-halting will be
    the correct answer.

    If it doesn't give an answer, but just crashes, then halting will be the correct answer,

    There is ALWAYS a correct answer for EVERY input built this way on ANY prospective halt decider, it is just that one particular halt decider
    will always be wrong for that input.


    And one can see HHH so there is nothing impossible
    there, either. And even wihout seeing HHH it is quite credible that
    it may always return either zero or something else (DD does not
    care what else if not zero).

    The only paradox is if HHH is assumed to be a halt decider.
    But the paradox disappears when we note that HHH is not a lalt decider.


    If an *actual input* actually exists (no such input exists)
    that can do the opposite of whatever its halt decider reports
    then it would be impossible to say what the correct return
    value from the decider should be.


    Bur it *IS* possible to make such an input,


    And the only POSSIBLE answer for it to give is the one its algorithm
    generates.

    What answer it should give is just an improper question, as it has no
    volition to follow a "should".

    But then, it seems you don't understand that, perhaps because you gave
    up your free will when you brainwashed yourself, I hope you got
    something good in exchange for your will, or you are going to have a
    long time to reget the choice.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kaz Kylheku@21:1/5 to olcott on Tue Aug 19 06:16:45 2025
    On 2025-08-18, olcott <polcott333@gmail.com> wrote:
    If an *actual input* actually exists (no such input exists)
    that can do the opposite of whatever its halt decider reports
    then it would be impossible to say what the correct return
    value from the decider should be.

    No it isn't. Every Turing machine either halts or does not,
    so there is a correct answer.

    All that is impossible is for that decider that has been embedded into
    the test case to return the correct answer for that test case. The
    decider returns something incorrect, or else does not halt.

    You cannot "edit" the decider to try to fix it. There is
    no "edit" in mathematics. The decider is an entity commited
    to existence, and cannot be other than what it is.

    You can propose a different decider. For that different decider
    a new test case can be constructed in which it either doesn't
    terminate or returns the wrong answer.

    In your latest coding attempt, you have resorted to self-modifying
    code. That's a very clear way to communicate that your configuration
    does not contain one single decider. It starts out as one function
    and morphs into a different one.

    I can't fathom how you can have it so that two instances of the same
    HHH(DD) expression have two different behaviors, yet believe that there
    is one HHH which is a function of DD, and that HHH is correctly
    deciding.

    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kaz Kylheku@21:1/5 to olcott on Tue Aug 19 06:33:57 2025
    On 2025-08-18, olcott <polcott333@gmail.com> wrote:
    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    However, it is possible to determine whether the evaluation
    of the sentence's truth value terminates. (Spoiler: it doesn't).

    And that's the only way in which it is related to halting,
    if at all.

    DD is not a paradox; it is not analogous to the Liar Paradox.

    The Halting Theorem is related to Gödel's Incompleteness.
    Gödel uses a construction resembling the Liar Paradox, but which
    markedly differs from it. It is more similar (though also not the same
    as) the sentence "This sentence cannot be proved". Note that this
    sentence can be assumed true without any contradiction; it doesn't have
    a runaway recursion issue if given that value.

    In short, you cannot appeal to the Liar Paradox to make any relevant
    analogy or valid argument in any of these areas.

    It's just used as a tool for introducing a certain aspect of the topic
    to complete neophytes.

    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Tue Aug 19 10:37:44 2025
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    Doesn't matter. The truth value of that sentence is not needed for
    any useful purpose. A method, even a partial one, to determine the
    halting of a computation or the termination of an algorithm is.

    And one can see HHH so there is nothing impossible
    there, either. And even wihout seeing HHH it is quite credible that
    it may always return either zero or something else (DD does not
    care what else if not zero).

    The only paradox is if HHH is assumed to be a halt decider.
    But the paradox disappears when we note that HHH is not a lalt decider.

    If an *actual input* actually exists (no such input exists)
    that can do the opposite of whatever its halt decider reports
    then it would be impossible to say what the correct return
    value from the decider should be.

    Irrelevant. What matters is that there is an actual input that is
    known to specify a halting behaviour but reported as non-halting
    by HHH. But that is a feature of HHH, not of the halting problem.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Heathfield@21:1/5 to Mikko on Tue Aug 19 08:52:55 2025
    On 19/08/2025 08:37, Mikko wrote:
    Irrelevant. What matters is that there is an actual input that is
    known to specify a halting behaviour but reported as non-halting
    by HHH. But that is a feature of HHH, not of the halting problem.

    Yes, and it should also be noted that the halting behaviour
    itself is also a feature of HHH, and that only because of runaway
    recursion. There is nothing inherent in DD that causes it to
    halt. Whether it halts is entirely in the hands of HHH's
    behaviour and its own bloody-mindedness.

    To illustrate this, we can take HHH and DD out of the equation
    and hypothesise an EE, wholly parallel in structure to DD, which
    is submitted not to simulation and recursion but to intelligent
    analysis of its source code:

    int EE()
    {
    int Halt_Status = JJJ("ee.src");
    if (Halt_Status)
    HERE: goto HERE;
    return Halt_Status;
    }

    Unlike HHH, JJJ will not make the rookie error of ignoring 75% of
    the input, but of course it will still get the answer wrong. Why?
    Because the problem is in the general case incomputable.

    --
    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 Heathfield@21:1/5 to olcott on Tue Aug 19 15:47:05 2025
    On 19/08/2025 15:35, olcott wrote:
    On 8/19/2025 2:52 AM, Richard Heathfield wrote:
    On 19/08/2025 08:37, Mikko wrote:
    Irrelevant. What matters is that there is an actual input that is
    known to specify a halting behaviour but reported as non-halting
    by HHH. But that is a feature of HHH, not of the halting problem.

    Yes, and it should also be noted that the halting behaviour
    itself is also a feature of HHH, and that only because of
    runaway recursion. There is nothing inherent in DD that causes
    it to halt. Whether it halts is entirely in the hands of HHH's
    behaviour and its own bloody-mindedness.

    To illustrate this, we can take HHH and DD out of the equation
    and hypothesise an EE, wholly parallel in structure to DD,
    which is submitted not to simulation and recursion but to
    intelligent analysis of its source code:

    int EE()
    {
       int Halt_Status = JJJ("ee.src");
       if (Halt_Status)
         HERE: goto HERE;
       return Halt_Status;
    }

    Unlike HHH, JJJ will not make the rookie error of ignoring 75%
    of the input, but of course it will still get the answer wrong.
    Why? Because the problem is in the general case incomputable.


    Turing machine deciders only compute the mapping
    from their inputs...

    In this case, "ee.src" - the source code of EE and (necessarily)
    JJJ, although we could fairly assume that JJJ already has that
    tucked away somewhere.

    There's nothing in your reply that makes JJJ("ee.src") impossible
    to write. I'm not saying I'd like the job, but a compiler writer
    might take it on for fun. We may presume that he wouldn't make
    the mistake of ignoring three lines of EE's source code.

    <pointless quote snipped>

    --
    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 Heathfield@21:1/5 to olcott on Tue Aug 19 16:20:17 2025
    On 19/08/2025 16:04, olcott wrote:
    This is best measured by simulating N steps of
    the input

    Assumes facts not in evidence.

    The only simulator in evidence - yours - patently fails to
    measure the behaviour of a 7-line C function. We can do better by
    inspection, or we can run it directly - either way, the simulator
    gets it wrong.

    Your simulation claims that DD never halts, and returns 0 from
    HHH. Let's see, shall we?

    $ cat dd.c
    #include <stdio.h>

    int HHH(int (*P)(void))
    {
    printf("HHH declares that DD never halts.\n");
    printf("HHH now returns 0.\n");
    return 0;
    }

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

    int main(void)
    {
    printf("DD() halts and returns %d.\n", DD());
    return 0;
    }

    $ gcc -o dd dd.c
    $ ./dd
    HHH declares that DD never halts.
    HHH now returns 0.
    DD() halts and returns 0.

    Oops.

    --
    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 Heathfield@21:1/5 to olcott on Tue Aug 19 16:36:36 2025
    On 19/08/2025 16:32, olcott wrote:
    On 8/19/2025 10:20 AM, Richard Heathfield wrote:
    On 19/08/2025 16:04, olcott wrote:
    This is best measured by simulating N steps of
    the input

    Assumes facts not in evidence.

    The only simulator in evidence - yours - patently fails to
    measure the behaviour of a 7-line C function. We can do better
    by inspection, or we can run it directly - either way, the
    simulator gets it wrong.


    On 8/18/2025 6:05 PM, Richard Heathfield wrote:
    It is an easily verified fact, as you love to say,
    that if DD calls HHH (as it does) and HHH calls DD
    (as, through simulation, it effectively does) that
    HHH(DD) can never halt naturally, so it will have
    to abort the recursion and report its result as 0
    - didn't halt.

    We can simulate that:

    int HHH(int (*P)(void))
    {
    return 0;
    }

    Now DD halts.

    --
    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 Tue Aug 19 22:22:53 2025
    On 8/19/25 10:10 AM, olcott wrote:
    On 8/19/2025 1:16 AM, Kaz Kylheku wrote:
    On 2025-08-18, olcott <polcott333@gmail.com> wrote:
    If an *actual input* actually exists (no such input exists)
    that can do the opposite of whatever its halt decider reports
    then it would be impossible to say what the correct return
    value from the decider should be.

    No it isn't. Every Turing machine either halts or does not,
    so there is a correct answer.


    Yet in the above hypothetical case we are not looking
    at whether it halts or not, we are looking at what the
    correct return value would be.

    Which would be whether the input program halts or not.

    It seems "correct" isn't a word with meaning for you.


    *From the bottom of page 319 has been adapted to this* https://www.liarparadox.org/Peter_Linz_HP_317-320.pdf

    Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.∞,
    Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.qn

    Linz requires the second named state of Turing
    machine Ĥ to report on the behavior of its own
    machine rather than the behavior of its input.

    Because the behavior of its input *IS* the behavior of its own machine,
    since the input is the representation of itself.


    When the second named state of Turing machine Ĥ
    reports on the behavior of its correct simulation
    of its input

    But it doesn't DO a correct simulation, so you are reporting on
    something that doesn't actualy happen


    *Repeats until aborted*

    Which since it DOES abort, or it never answer, the pattern of the
    correct simulation also halts.

    (a) Ĥ copies its input ⟨Ĥ⟩
    (b) Ĥ invokes embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩
    (c) embedded_H simulates ⟨Ĥ⟩ ⟨Ĥ⟩

    *thus making this state transition correct*
    Ĥ.embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.qn

    Nope, it would only be correct if it doesn't abort, but then it doesn't
    get there.

    The problem is the criteria wasn't based on the "correct" simulation by
    the decider, but the behavior of the input, or an ACTUAL correct
    simulaton of THIS input by a real correct simulator.

    All you are doing is showing that you consider lying to be proper logic.


    As long as the decider reports on the behavior
    specified by its input then it is correct because

    But that isn't the behaivor of the input, which is DEFINED to be the
    result of the actual execution of the input, which halts.

    All you are doing is showing that you don't know what a correct
    simulation is, and that you think answer a question you weren't asked
    can be a correctx response.


    Turing machine deciders only compute the mapping
    from their inputs...

    Right, but there correctness is based on the requirements there were
    supposed to be designed to.

    Since the requirements of the halting problem is based on the behavior
    of the program represented by the input, that *IS* the behavior that the checking uses.


    All that is impossible is for that decider that has been embedded into
    the test case to return the correct answer for that test case.  The
    decider returns something incorrect, or else does not halt.

    You cannot "edit" the decider to try to fix it. There is
    no "edit" in mathematics. The decider is an entity commited
    to existence, and cannot be other than what it is.

    You can propose a different decider. For that different decider
    a new test case can be constructed in which it either doesn't
    terminate or returns the wrong answer.

    In your latest coding attempt, you have resorted to self-modifying
    code. That's a very clear way to communicate that your configuration
    does not contain one single decider. It starts out as one function
    and morphs into a different one.

    I can't fathom how you can have it so that two instances of the same
    HHH(DD) expression have two different behaviors, yet believe that there
    is one HHH which is a function of DD, and that HHH is correctly
    deciding.




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Fri Aug 22 11:28:57 2025
    On 8/19/25 10:10 AM, olcott wrote:
    On 8/19/2025 1:16 AM, Kaz Kylheku wrote:
    On 2025-08-18, olcott <polcott333@gmail.com> wrote:
    If an *actual input* actually exists (no such input exists)
    that can do the opposite of whatever its halt decider reports
    then it would be impossible to say what the correct return
    value from the decider should be.

    No it isn't. Every Turing machine either halts or does not,
    so there is a correct answer.


    Yet in the above hypothetical case we are not looking
    at whether it halts or not, we are looking at what the
    correct return value would be.

    Which assumes there is one that it can return.

    The problem here is that if the decider is a defined program there is
    only one answer it CAN return, the one its programming says to return,
    and the other one is the correct one.


    *From the bottom of page 319 has been adapted to this* https://www.liarparadox.org/Peter_Linz_HP_317-320.pdf

    Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.∞,
    Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.qn

    Linz requires the second named state of Turing
    machine Ĥ to report on the behavior of its own
    machine rather than the behavior of its input.

    No, it requires it to report of the behavior of its input, which just
    happens to be the behavior of itself.


    When the second named state of Turing machine Ĥ
    reports on the behavior of its correct simulation
    of its input




    *Repeats until aborted*

    Which, since H DOES Abort, doesn't repeat forever

    (a) Ĥ copies its input ⟨Ĥ⟩
    (b) Ĥ invokes embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩
    (c) embedded_H simulates ⟨Ĥ⟩ ⟨Ĥ⟩

    *thus making this state transition correct*
    Ĥ.embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.qn

    Nope, because H/embedded_H doesn't DO a correct simulation, the loop
    isn't infinite.

    IF you make H do the correct simulation, it can't decide to abort as
    that contradicts the assumption of correct simulation.


    As long as the decider reports on the behavior
    specified by its input then it is correct because

    Turing machine deciders only compute the mapping
    from their inputs...

    Nope, the only CAN compute a computable mapping from their input, but
    MUST (to be correct) compute the specified mappinf from their input.

    Since the specified mapping is based on the behavior of the program the
    input represents, the fact they can't actually compute that makes that
    mapping uncomputable, not wrong.

    All you are doing is telling the world that in your mind LYING is
    perfectly acceptable behavior if you don't know how to do better, even
    if your limitations are self-imposed.


    All that is impossible is for that decider that has been embedded into
    the test case to return the correct answer for that test case.  The
    decider returns something incorrect, or else does not halt.

    You cannot "edit" the decider to try to fix it. There is
    no "edit" in mathematics. The decider is an entity commited
    to existence, and cannot be other than what it is.

    You can propose a different decider. For that different decider
    a new test case can be constructed in which it either doesn't
    terminate or returns the wrong answer.

    In your latest coding attempt, you have resorted to self-modifying
    code. That's a very clear way to communicate that your configuration
    does not contain one single decider. It starts out as one function
    and morphs into a different one.

    I can't fathom how you can have it so that two instances of the same
    HHH(DD) expression have two different behaviors, yet believe that there
    is one HHH which is a function of DD, and that HHH is correctly
    deciding.




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Fri Aug 22 11:32:18 2025
    On 8/19/25 10:21 AM, olcott wrote:
    On 8/19/2025 1:33 AM, Kaz Kylheku wrote:
    On 2025-08-18, olcott <polcott333@gmail.com> wrote:
    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    However, it is possible to determine whether the evaluation
    of the sentence's truth value terminates. (Spoiler: it doesn't).


    ?- LP = not(true(LP)).
    LP = not(true(LP)).

    ?- unify_with_occurs_check(LP, not(true(LP))).
    false.

    And that's the only way in which it is related to halting,
    if at all.

    DD is not a paradox; it is not analogous to the Liar Paradox.


    It never was even a paradox when we realize that there
    never was an actual input that does the opposite of
    whatever the decider decides.

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

    DD correctly simulated by HHH never reaches its own
    simulated "if" statement, thus to "do the opposite"
    code is unreachable.

    Which just means the impossiblity of build the input is based on the impossiblity of making a decider in the first place.


    We can see that DD correctly simulated by HHH would
    never stop running, thus we can see that it would be
    correct for HHH(DD) to abort its simulation and return 0.

    No, because it is impossible for the "decider" that does a correct
    simulaitonm to stops it simulating to return that answer.

    You seem to think that one program can be two different programs, and
    that two diffent inputs (the DD built on the two different programs) are
    the same.

    This is just a sign of your insanity.


    The Halting Theorem is related to Gödel's Incompleteness.
    Gödel uses a construction resembling the Liar Paradox, but which
    markedly differs from it. It is more similar (though also not the same
    as) the sentence "This sentence cannot be proved".  Note that this
    sentence can be assumed true without any contradiction; it doesn't have
    a runaway recursion issue if given that value.


    ?- G = not(provable(F, G)).
    G = not(provable(F, G)).

    ?- unify_with_occurs_check(G, not(provable(F, G))).
    false.

    In short, you cannot appeal to the Liar Paradox to make any relevant
    analogy or valid argument in any of these areas.

    It's just used as a tool for introducing a certain aspect of the topic
    to complete neophytes.


    Prolog seems to disagree.


    Prolog is just not up to the task, just like you are.

    Sorry, all you are doing is showing your utter stupidity on the topic.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Tue Aug 26 11:54:41 2025
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    Doesn't matter. The truth value of that sentence is not needed for
    any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed. https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue Aug 26 21:26:43 2025
    On 8/26/25 11:49 AM, olcott wrote:
    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem. >>>>>>>
    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is >>>>>> something that seems impossible. But one can see DD so it obviously >>>>>> is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    Doesn't matter. The truth value of that sentence is not needed for
    any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed.
    https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.


    The Liar Paradox cannot be derived through Rules applied to Facts https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    So?

    But Tarski shows it CAN be derived from an assumption that a Truth
    Predicate exists, thus there can't be such a predicate.


    ?- LP = not(true(LP)).
    LP = not(true(LP)).

    ?- unify_with_occurs_check(LP, not(true(LP))).
    false.



    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Wed Aug 27 10:40:28 2025
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem. >>>>>>>
    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is >>>>>> something that seems impossible. But one can see DD so it obviously >>>>>> is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    Doesn't matter. The truth value of that sentence is not needed for
    any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed.
    https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    The Liar Paradox cannot be derived through Rules applied to Facts https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts. In particular, the hypothesis
    that it is possible to define a truth predicate is counter-factual.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Wed Aug 27 21:56:16 2025
    On 8/27/25 10:52 AM, olcott wrote:
    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem. >>>>>>>>>
    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is >>>>>>>> something that seems impossible. But one can see DD so it obviously >>>>>>>> is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    Doesn't matter. The truth value of that sentence is not needed for >>>>>> any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed.
    https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    The Liar Paradox cannot be derived through Rules applied to Facts
    https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Which means that the truth predicate can't exists, as it establishes
    that it is one.

    Sorry, logic doesn't work the way you think and makes you stop one step
    before you can prove the contradiction.

    But then, you never did seem to understand how logic works.


    In particular, the hypothesis
    that it is possible to define a truth predicate is counter-factual.




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Thu Aug 28 10:04:09 2025
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem. >>>>>>>>>
    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is >>>>>>>> something that seems impossible. But one can see DD so it obviously >>>>>>>> is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    Doesn't matter. The truth value of that sentence is not needed for >>>>>> any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed.
    https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    The Liar Paradox cannot be derived through Rules applied to Facts
    https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a sentence
    that claims its own falsity is unprovable unless ordinary arithmetic
    is inconsistent.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Fri Aug 29 09:54:29 2025
    On 2025-08-28 14:19:23 +0000, olcott said:

    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem. >>>>>>>>>>>
    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is >>>>>>>>>> something that seems impossible. But one can see DD so it obviously >>>>>>>>>> is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    Doesn't matter. The truth value of that sentence is not needed for >>>>>>>> any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed.
    https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    The Liar Paradox cannot be derived through Rules applied to Facts
    https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a sentence
    that claims its own falsity is unprovable unless ordinary arithmetic
    is inconsistent.

    It unprovable because it is not a truth bearer.

    However, it would be provable (and proven) if there were a truth predicate.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Fri Aug 29 22:11:18 2025
    On 8/28/25 10:19 AM, olcott wrote:
    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem. >>>>>>>>>>>
    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A
    paradox is
    something that seems impossible. But one can see DD so it
    obviously
    is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false.

    Doesn't matter. The truth value of that sentence is not needed for >>>>>>>> any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed.
    https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    The Liar Paradox cannot be derived through Rules applied to Facts
    https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a sentence
    that claims its own falsity is unprovable unless ordinary arithmetic
    is inconsistent.



    It unprovable because it is not a truth bearer.

    Your problem is you don't understand what Tarski is talking about, as
    you have shown you just don't understand how logic works.



    ?- LP = not(true(LP)).
    LP = not(true(LP)).

    ?- unify_with_occurs_check(LP, not(true(LP))).
    false.

    Proving that LP is not a truth bearer.

    We might as well ask is this sentence true
    or false: "What time is it?"

    Tarski couldn't prove that one either.


    But he did, given the one assumption that a Truth Predicate exists.
    Since you don't understand that part of the proof, you are just showing
    his ignorance.

    Note, he comments that this proof is based on the same sort of
    operations that Godel's incompleteness proof uses, which you have shown
    your inability to understand.

    Your inability to understand how Formal Logic works, means you really
    don't understand how meta-systems work, and the power they have in
    Formal Logic.

    In part because they don't map to anything in the more general
    philosophies that you seem to prefer to study, which are a very
    different sort of thing, something you also don't understadn, as you
    don't really understand the Philosphies.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Sat Aug 30 13:20:09 2025
    On 2025-08-29 14:04:37 +0000, olcott said:

    On 8/29/2025 1:54 AM, Mikko wrote:
    On 2025-08-28 14:19:23 +0000, olcott said:

    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the
    Russell's Paradox problem. Since ZFC set theory
    is now called naive set theory.

    You can't do the same because you don't have a paradox problem. >>>>>>>>>>>>>
    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD()
    is a paradox that is abolished when we understand
    that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is >>>>>>>>>>>> something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false. >>>>>>>>>>
    Doesn't matter. The truth value of that sentence is not needed for >>>>>>>>>> any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed.
    https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    The Liar Paradox cannot be derived through Rules applied to Facts >>>>>>> https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a sentence
    that claims its own falsity is unprovable unless ordinary arithmetic
    is inconsistent.

    It unprovable because it is not a truth bearer.

    However, it would be provable (and proven) if there were a truth predicate.

    Likewise we could know whether or not
    "What time is it?" is true or false.

    Only if you can express that question as a term expression in the domain
    of the truth predicate.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Sun Aug 31 11:36:57 2025
    On 2025-08-30 16:24:16 +0000, olcott said:

    On 8/30/2025 5:20 AM, Mikko wrote:
    On 2025-08-29 14:04:37 +0000, olcott said:

    On 8/29/2025 1:54 AM, Mikko wrote:
    On 2025-08-28 14:19:23 +0000, olcott said:

    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said:

    I am doing the same thing that ZFC did to the >>>>>>>>>>>>>>>>> Russell's Paradox problem. Since ZFC set theory >>>>>>>>>>>>>>>>> is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD() >>>>>>>>>>>>>>> is a paradox that is abolished when we understand >>>>>>>>>>>>>>> that Turing machine deciders only compute the
    mapping from their inputs, thus the behavior
    of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to
    correctly determine whether that sentence is true or false. >>>>>>>>>>>>
    Doesn't matter. The truth value of that sentence is not needed for >>>>>>>>>>>> any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed. >>>>>>>>>>> https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    The Liar Paradox cannot be derived through Rules applied to Facts >>>>>>>>> https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a sentence >>>>>> that claims its own falsity is unprovable unless ordinary arithmetic >>>>>> is inconsistent.

    It unprovable because it is not a truth bearer.

    However, it would be provable (and proven) if there were a truth predicate.

    Likewise we could know whether or not
    "What time is it?" is true or false.

    Only if you can express that question as a term expression in the domain
    of the truth predicate.

    Questions are not truth bearers thus it is
    incorrect to ask whether they are true or false.

    In certain sense true but irrelevant to your (not quire correct) claim
    in your previous message.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sun Aug 31 13:27:45 2025
    On 8/31/25 12:07 PM, olcott wrote:
    On 8/31/2025 3:36 AM, Mikko wrote:
    On 2025-08-30 16:24:16 +0000, olcott said:

    On 8/30/2025 5:20 AM, Mikko wrote:
    On 2025-08-29 14:04:37 +0000, olcott said:

    On 8/29/2025 1:54 AM, Mikko wrote:
    On 2025-08-28 14:19:23 +0000, olcott said:

    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>
    I am doing the same thing that ZFC did to the >>>>>>>>>>>>>>>>>>> Russell's Paradox problem. Since ZFC set theory >>>>>>>>>>>>>>>>>>> is now called naive set theory.

    You can't do the same because you don't have a paradox >>>>>>>>>>>>>>>>>> problem.

    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD() >>>>>>>>>>>>>>>>> is a paradox that is abolished when we understand >>>>>>>>>>>>>>>>> that Turing machine deciders only compute the >>>>>>>>>>>>>>>>> mapping from their inputs, thus the behavior >>>>>>>>>>>>>>>>> of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A >>>>>>>>>>>>>>>> paradox is
    something that seems impossible. But one can see DD so >>>>>>>>>>>>>>>> it obviously
    is possible.

    "This sentence is not true" It is not possible to >>>>>>>>>>>>>>> correctly determine whether that sentence is true or false. >>>>>>>>>>>>>>
    Doesn't matter. The truth value of that sentence is not >>>>>>>>>>>>>> needed for
    any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed. >>>>>>>>>>>>> https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    The Liar Paradox cannot be derived through Rules applied to >>>>>>>>>>> Facts
    https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a
    sentence
    that claims its own falsity is unprovable unless ordinary
    arithmetic
    is inconsistent.

    It unprovable because it is not a truth bearer.

    However, it would be provable (and proven) if there were a truth
    predicate.

    Likewise we could know whether or not
    "What time is it?" is true or false.

    Only if you can express that question as a term expression in the
    domain
    of the truth predicate.

    Questions are not truth bearers thus it is
    incorrect to ask whether they are true or false.

    In certain sense true but irrelevant to your (not quire correct) claim
    in your previous message.


    The Liar Paradox is not a truth bearer thus Tarski
    should have rejected it as the basis for his proof.


    HE does, he shows that because the presumption of the existance of a
    Truth Predicate yields a proof that the Liar Paradox is a truth bearer,
    that presumption can't be correct.

    A form of logic that apparently you don't understand, because you like
    to presume that the imposilbe can happen without creating contradictions.

    All you are doing is proving your ignorance.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Mon Sep 1 10:51:11 2025
    On 2025-08-31 16:07:59 +0000, olcott said:

    On 8/31/2025 3:36 AM, Mikko wrote:
    On 2025-08-30 16:24:16 +0000, olcott said:

    On 8/30/2025 5:20 AM, Mikko wrote:
    On 2025-08-29 14:04:37 +0000, olcott said:

    On 8/29/2025 1:54 AM, Mikko wrote:
    On 2025-08-28 14:19:23 +0000, olcott said:

    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said:

    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>
    I am doing the same thing that ZFC did to the >>>>>>>>>>>>>>>>>>> Russell's Paradox problem. Since ZFC set theory >>>>>>>>>>>>>>>>>>> is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are
    contradicted by the behavior of the directly DD() >>>>>>>>>>>>>>>>> is a paradox that is abolished when we understand >>>>>>>>>>>>>>>>> that Turing machine deciders only compute the >>>>>>>>>>>>>>>>> mapping from their inputs, thus the behavior >>>>>>>>>>>>>>>>> of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to >>>>>>>>>>>>>>> correctly determine whether that sentence is true or false. >>>>>>>>>>>>>>
    Doesn't matter. The truth value of that sentence is not needed for
    any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed. >>>>>>>>>>>>> https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression.

    The Liar Paradox cannot be derived through Rules applied to Facts >>>>>>>>>>> https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a sentence >>>>>>>> that claims its own falsity is unprovable unless ordinary arithmetic >>>>>>>> is inconsistent.

    It unprovable because it is not a truth bearer.

    However, it would be provable (and proven) if there were a truth predicate.

    Likewise we could know whether or not
    "What time is it?" is true or false.

    Only if you can express that question as a term expression in the domain >>>> of the truth predicate.

    Questions are not truth bearers thus it is
    incorrect to ask whether they are true or false.

    In certain sense true but irrelevant to your (not quire correct) claim
    in your previous message.

    The Liar Paradox is not a truth bearer thus Tarski
    should have rejected it as the basis for his proof.

    If you agree with Tarski that the liar paradox is not a truth-bearer
    and therefore not true, why don't you cosider the statement "The Liar
    Paradox is not a truth bearer" false?

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon Sep 1 11:43:09 2025
    On 9/1/25 10:51 AM, olcott wrote:
    On 9/1/2025 2:51 AM, Mikko wrote:
    On 2025-08-31 16:07:59 +0000, olcott said:

    On 8/31/2025 3:36 AM, Mikko wrote:
    On 2025-08-30 16:24:16 +0000, olcott said:

    On 8/30/2025 5:20 AM, Mikko wrote:
    On 2025-08-29 14:04:37 +0000, olcott said:

    On 8/29/2025 1:54 AM, Mikko wrote:
    On 2025-08-28 14:19:23 +0000, olcott said:

    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>
    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>
    I am doing the same thing that ZFC did to the >>>>>>>>>>>>>>>>>>>>> Russell's Paradox problem. Since ZFC set theory >>>>>>>>>>>>>>>>>>>>> is now called naive set theory.

    You can't do the same because you don't have a >>>>>>>>>>>>>>>>>>>> paradox problem.

    That both return values from HHH(DD) are >>>>>>>>>>>>>>>>>>> contradicted by the behavior of the directly DD() >>>>>>>>>>>>>>>>>>> is a paradox that is abolished when we understand >>>>>>>>>>>>>>>>>>> that Turing machine deciders only compute the >>>>>>>>>>>>>>>>>>> mapping from their inputs, thus the behavior >>>>>>>>>>>>>>>>>>> of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. >>>>>>>>>>>>>>>>>> A paradox is
    something that seems impossible. But one can see DD so >>>>>>>>>>>>>>>>>> it obviously
    is possible.

    "This sentence is not true" It is not possible to >>>>>>>>>>>>>>>>> correctly determine whether that sentence is true or >>>>>>>>>>>>>>>>> false.

    Doesn't matter. The truth value of that sentence is not >>>>>>>>>>>>>>>> needed for
    any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed. >>>>>>>>>>>>>>> https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression. >>>>>>>>>>>>>
    The Liar Paradox cannot be derived through Rules applied to >>>>>>>>>>>>> Facts
    https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a >>>>>>>>>> sentence
    that claims its own falsity is unprovable unless ordinary
    arithmetic
    is inconsistent.

    It unprovable because it is not a truth bearer.

    However, it would be provable (and proven) if there were a truth >>>>>>>> predicate.

    Likewise we could know whether or not
    "What time is it?" is true or false.

    Only if you can express that question as a term expression in the
    domain
    of the truth predicate.

    Questions are not truth bearers thus it is
    incorrect to ask whether they are true or false.

    In certain sense true but irrelevant to your (not quire correct) claim >>>> in your previous message.

    The Liar Paradox is not a truth bearer thus Tarski
    should have rejected it as the basis for his proof.

    If you agree with Tarski that the liar paradox is not a truth-bearer
    and therefore not true, why don't you cosider the statement "The Liar
    Paradox is not a truth bearer" false?


    The same reason that I don't say "What time is it?"
    is true or false. Only truth bearers have a Boolean
    value.


    So, Tarski's statement that the "liar paradox is not a truth-bearer" is
    a true statement that you won't talk about?

    Your problem is you don't understand what Tarski is saying because you
    are stuck in beleiving your lies.

    Tarski shows that, by the rules of logic, that the existance of a "Truth Predicate" that tells us the truth value of any statement leads to the consquence that the liars paradox has a truth value, as shown by a proof similar to Godel's incompleteness proof. (Which you also don't understand).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Tue Sep 2 11:12:16 2025
    On 2025-09-01 14:51:17 +0000, olcott said:

    On 9/1/2025 2:51 AM, Mikko wrote:
    On 2025-08-31 16:07:59 +0000, olcott said:

    On 8/31/2025 3:36 AM, Mikko wrote:
    On 2025-08-30 16:24:16 +0000, olcott said:

    On 8/30/2025 5:20 AM, Mikko wrote:
    On 2025-08-29 14:04:37 +0000, olcott said:

    On 8/29/2025 1:54 AM, Mikko wrote:
    On 2025-08-28 14:19:23 +0000, olcott said:

    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said:

    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>
    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>
    I am doing the same thing that ZFC did to the >>>>>>>>>>>>>>>>>>>>> Russell's Paradox problem. Since ZFC set theory >>>>>>>>>>>>>>>>>>>>> is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are >>>>>>>>>>>>>>>>>>> contradicted by the behavior of the directly DD() >>>>>>>>>>>>>>>>>>> is a paradox that is abolished when we understand >>>>>>>>>>>>>>>>>>> that Turing machine deciders only compute the >>>>>>>>>>>>>>>>>>> mapping from their inputs, thus the behavior >>>>>>>>>>>>>>>>>>> of non-input DD() is of no consequence.

    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to >>>>>>>>>>>>>>>>> correctly determine whether that sentence is true or false. >>>>>>>>>>>>>>>>
    Doesn't matter. The truth value of that sentence is not needed for
    any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed. >>>>>>>>>>>>>>> https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression. >>>>>>>>>>>>>
    The Liar Paradox cannot be derived through Rules applied to Facts >>>>>>>>>>>>> https://en.wikipedia.org/wiki/Negation_as_failure
    Thus is rejected by Prolog proving that Tarski was
    incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a sentence >>>>>>>>>> that claims its own falsity is unprovable unless ordinary arithmetic >>>>>>>>>> is inconsistent.

    It unprovable because it is not a truth bearer.

    However, it would be provable (and proven) if there were a truth predicate.

    Likewise we could know whether or not
    "What time is it?" is true or false.

    Only if you can express that question as a term expression in the domain >>>>>> of the truth predicate.

    Questions are not truth bearers thus it is
    incorrect to ask whether they are true or false.

    In certain sense true but irrelevant to your (not quire correct) claim >>>> in your previous message.

    The Liar Paradox is not a truth bearer thus Tarski
    should have rejected it as the basis for his proof.

    If you agree with Tarski that the liar paradox is not a truth-bearer
    and therefore not true, why don't you cosider the statement "The Liar
    Paradox is not a truth bearer" false?

    The same reason that I don't say "What time is it?"
    is true or false. Only truth bearers have a Boolean
    value.

    What is the reaaon to say that "The Liar Paradox is not a truth bearer"
    is false but "What time is it?" isn't?

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From joes@21:1/5 to All on Tue Sep 2 17:31:38 2025
    Am Tue, 02 Sep 2025 10:04:15 -0500 schrieb olcott:
    On 9/2/2025 3:12 AM, Mikko wrote:
    On 2025-09-01 14:51:17 +0000, olcott said:
    On 9/1/2025 2:51 AM, Mikko wrote:
    On 2025-08-31 16:07:59 +0000, olcott said:
    On 8/31/2025 3:36 AM, Mikko wrote:
    On 2025-08-30 16:24:16 +0000, olcott said:
    On 8/30/2025 5:20 AM, Mikko wrote:
    On 2025-08-29 14:04:37 +0000, olcott said:
    On 8/29/2025 1:54 AM, Mikko wrote:
    On 2025-08-28 14:19:23 +0000, olcott said:
    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:
    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:
    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:
    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said: >>>>>>>>>>>>>>>>>>> On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>> On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>
    I am doing the same thing that ZFC did to the >>>>>>>>>>>>>>>>>>>>>>> Russell's Paradox problem. Since ZFC set theory is >>>>>>>>>>>>>>>>>>>>>>> now called naive set theory.
    ZFC doesn't make Russell's paradox go away in naive set theory.

    It unprovable because it is not a truth bearer.
    It might be. You can add it or the negation as an axiom

    What is the reaaon to say that "The Liar Paradox is not a truth bearer"
    is false but "What time is it?" isn't?

    It has taken humanity 2000 years** and even after it has been completely proven that the liar paradox cannot possibly have truth value no other
    human gets this.
    Why do you think you are the smartest in the world? The liar sentence
    is syntactically well-formed and could be false or true. Its content
    is then in contradiction to the assigned value. It's not a question.

    --
    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 Sep 2 22:36:01 2025
    On 9/2/25 1:55 PM, olcott wrote:
    On 9/2/2025 12:31 PM, joes wrote:
    Am Tue, 02 Sep 2025 10:04:15 -0500 schrieb olcott:
    On 9/2/2025 3:12 AM, Mikko wrote:
    On 2025-09-01 14:51:17 +0000, olcott said:
    On 9/1/2025 2:51 AM, Mikko wrote:
    On 2025-08-31 16:07:59 +0000, olcott said:
    On 8/31/2025 3:36 AM, Mikko wrote:
    On 2025-08-30 16:24:16 +0000, olcott said:
    On 8/30/2025 5:20 AM, Mikko wrote:
    On 2025-08-29 14:04:37 +0000, olcott said:
    On 8/29/2025 1:54 AM, Mikko wrote:
    On 2025-08-28 14:19:23 +0000, olcott said:
    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:
    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:
    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said: >>>>>>>>>>>>>>>>>>> On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>> On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>> On 8/17/2025 4:03 AM, Mikko wrote: >>>>>>>>>>>>>>>>>>>>>>>> On 2025-08-16 14:20:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>>>
    I am doing the same thing that ZFC did to the >>>>>>>>>>>>>>>>>>>>>>>>> Russell's Paradox problem. Since ZFC set theory is >>>>>>>>>>>>>>>>>>>>>>>>> now called naive set theory.

    ZFC doesn't make Russell's paradox go away in naive set theory.


    ZFC essentially correctly rules that naive set theory is stupid.

    It unprovable because it is not a truth bearer.
    It might be. You can add it or the negation as an axiom

    What is the reaaon to say that "The Liar Paradox is not a truth bearer" >>>> is false but "What time is it?" isn't?

    It has taken humanity 2000 years** and even after it has been completely >>> proven that the liar paradox cannot possibly have truth value no other
    human gets this.

    Why do you think you are the smartest in the world? The liar sentence
    is syntactically well-formed and could be false or true. Its content
    is then in contradiction to the assigned value. It's not a question.


    It took me a lot of work to conclusively prove
    that the Liar Paradox is not a truth bearer, yet
    it should be simple as soon as the notion of truth
    bearer is understood.



    Why did it take you that long?

    It has long been know that it isn't a truth-bearer.

    You just don't undetstand the logic that others are using, and in your stupidity, you project your stupidity on others.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Wed Sep 3 10:52:34 2025
    On 2025-09-02 15:04:15 +0000, olcott said:

    On 9/2/2025 3:12 AM, Mikko wrote:
    On 2025-09-01 14:51:17 +0000, olcott said:

    On 9/1/2025 2:51 AM, Mikko wrote:
    On 2025-08-31 16:07:59 +0000, olcott said:

    On 8/31/2025 3:36 AM, Mikko wrote:
    On 2025-08-30 16:24:16 +0000, olcott said:

    On 8/30/2025 5:20 AM, Mikko wrote:
    On 2025-08-29 14:04:37 +0000, olcott said:

    On 8/29/2025 1:54 AM, Mikko wrote:
    On 2025-08-28 14:19:23 +0000, olcott said:

    On 8/28/2025 2:04 AM, Mikko wrote:
    On 2025-08-27 14:52:19 +0000, olcott said:

    On 8/27/2025 2:40 AM, Mikko wrote:
    On 2025-08-26 15:49:20 +0000, olcott said:

    On 8/26/2025 3:54 AM, Mikko wrote:
    On 2025-08-19 15:04:36 +0000, olcott said:

    On 8/19/2025 2:37 AM, Mikko wrote:
    On 2025-08-18 17:43:56 +0000, olcott said: >>>>>>>>>>>>>>>>>>
    On 8/18/2025 4:08 AM, Mikko wrote:
    On 2025-08-17 15:48:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>
    On 8/17/2025 4:03 AM, Mikko wrote:
    On 2025-08-16 14:20:10 +0000, olcott said: >>>>>>>>>>>>>>>>>>>>>>
    I am doing the same thing that ZFC did to the >>>>>>>>>>>>>>>>>>>>>>> Russell's Paradox problem. Since ZFC set theory >>>>>>>>>>>>>>>>>>>>>>> is now called naive set theory.

    You can't do the same because you don't have a paradox problem.

    That both return values from HHH(DD) are >>>>>>>>>>>>>>>>>>>>> contradicted by the behavior of the directly DD() >>>>>>>>>>>>>>>>>>>>> is a paradox that is abolished when we understand >>>>>>>>>>>>>>>>>>>>> that Turing machine deciders only compute the >>>>>>>>>>>>>>>>>>>>> mapping from their inputs, thus the behavior >>>>>>>>>>>>>>>>>>>>> of non-input DD() is of no consequence. >>>>>>>>>>>>>>>>>>>>
    That is not a paradox. That is how DD is constructed. A paradox is
    something that seems impossible. But one can see DD so it obviously
    is possible.

    "This sentence is not true" It is not possible to >>>>>>>>>>>>>>>>>>> correctly determine whether that sentence is true or false. >>>>>>>>>>>>>>>>>>
    Doesn't matter. The truth value of that sentence is not needed for
    any useful purpose.

    It was the basis for the Tarski proof that
    Boolean True(Language L, Expression e) cannot be computed. >>>>>>>>>>>>>>>>> https://liarparadox.org/Tarski_247_248.pdf

    The expression, not the truth value of the expression. >>>>>>>>>>>>>>>
    The Liar Paradox cannot be derived through Rules applied to Facts
    https://en.wikipedia.org/wiki/Negation_as_failure >>>>>>>>>>>>>>> Thus is rejected by Prolog proving that Tarski was >>>>>>>>>>>>>>> incorrect to use it as any basis.

    Tarski does not derive it from facts.

    It my system that would be enough to reject LP as
    not a member of this formal system thus rejected
    as not a truth bearer.

    Your system does not exist. But in the system Tarski used a sentence
    that claims its own falsity is unprovable unless ordinary arithmetic
    is inconsistent.

    It unprovable because it is not a truth bearer.

    However, it would be provable (and proven) if there were a truth predicate.

    Likewise we could know whether or not
    "What time is it?" is true or false.

    Only if you can express that question as a term expression in the domain
    of the truth predicate.

    Questions are not truth bearers thus it is
    incorrect to ask whether they are true or false.

    In certain sense true but irrelevant to your (not quire correct) claim >>>>>> in your previous message.

    The Liar Paradox is not a truth bearer thus Tarski
    should have rejected it as the basis for his proof.

    If you agree with Tarski that the liar paradox is not a truth-bearer
    and therefore not true, why don't you cosider the statement "The Liar
    Paradox is not a truth bearer" false?

    The same reason that I don't say "What time is it?"
    is true or false. Only truth bearers have a Boolean
    value.

    What is the reaaon to say that "The Liar Paradox is not a truth bearer"
    is false but "What time is it?" isn't?


    It has taken humanity 2000 years** and even
    after it has been completely proven that the
    liar paradox cannot possibly have truth value
    no other human gets this.

    ** The Liar Paradox is in the bible.

    St. Paul refers to the paradox but does not mention that it is a paradox.

    --
    Mikko

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