• Re: Five different LLM systems agree with my rebuttal of the HPproofs --- Ben

    From olcott@polcott333@gmail.com to comp.theory on Wed Sep 10 21:16:19 2025
    From Newsgroup: comp.theory

    On 9/10/2025 7:45 PM, Ben Bacarisse wrote:
    Richard Heathfield <rjh@cpax.org.uk> writes:

    On 06/09/2025 14:36, Ben Bacarisse wrote:

    <snip>

    My point has nothing to do with his (or your) consistency
    of use. My aim was to encourage use consistent with all the published
    work on the subject.

    Naturally you won't find me unco-operative, but it does seem to imply that, >> having redefined "reject" as "decide it doesn't halt", we need a new word
    to cover the concept of turning down a program for being ungrammatical or
    asyntactical or whatever.

    Decision problems are usually stated so that accept/reject is all you
    need. In the case of halting one might state that inputs that are
    accepted are those that represent halting TM/input pairs.

    That is the very subtle fallacy of equivocation error
    that has been perpetuated by every textbook on the subject.

    All deciders only compute the mapping from their
    input finite strings...

    It is not the behavior of some machine somewhere
    else that is "represented" by the finite string.
    It is the behavior that the finite string INPUT
    SPECIFIES to its decider.

    When simulating halt deciders are considered then
    we see that DD does call HHH(DD) in recursive
    simulation that cannot possibly reach its own
    simulated final halt state. The same applies to
    the Linz Ĥ.embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩.

    To expound on some notions in Rice's theorem
    deciders accept or reject input finite strings
    on the basis of a semantic or syntactic property
    [of their input].

    Everything
    else would be rejected. In that context "rejection" would include
    inputs that don't represent valid TM/input pairs.

    Obviously one could choose to have many reasons for rejecting an input
    as not a member of the set being decided, but there's no theoretical advantage in making the decider tell you about them. If, for some
    reason, you really want to complicate the theory with these details then
    the decider could have several rejecting states, each for a different
    reason to reject an input. Or one could switch the model and have the decider signal membership or non-membership by leaving some specific
    result on the tape. But none of the these do anything so simplify the theorems or their proofs.

    [Sorry for the delay. I'm not really keeping up with all the group. It seems to be an endless re-hash of the same material from decades ago.]


    Unless you pay very close attention.
    --
    Copyright 2025 Olcott "Talent hits a target no one else can hit; Genius
    hits a target no one else can see." Arthur Schopenhauer
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From dbush@dbush.mobile@gmail.com to comp.theory on Wed Sep 10 22:25:27 2025
    From Newsgroup: comp.theory

    On 9/10/2025 10:16 PM, olcott wrote:
    It is not the behavior of some machine somewhere
    else that is "represented" by the finite string.

    Yes it is, because we want to know if any arbitrary Turing machine X
    with input Y will halt when executed, and it would be very useful to
    have a Turing machine that could tell us that in *all* possible cases.
    --- Synchronet 3.21a-Linux NewsLink 1.2