• Re: Category error [ HEAD GAMES ] (smart honest people would agree)[ Be

    From olcott@21:1/5 to Ben on Fri May 20 15:33:57 2022
    XPost: comp.theory, sci.logic

    On 5/20/2022 11:41 AM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    On 5/20/2022 11:26 AM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    On 5/20/2022 10:12 AM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    On 5/20/2022 6:25 AM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    On 5/19/2022 7:53 PM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    ONE CAN VERIFY THAT THE EXECUTION TRACE IS CORRECT ON THE BASIS THAT >>>>>>>>>> THE EXECUTION TRACE OF THE INPUT TO H(P,P) CORRESPONDS TO
    THE BEHAVIOR SPECIFIED BY THE X86 SOURCE-CODE OF P
    WHERE H(P,P) CORRECTLY EMULATES ITS INPUT
    THAT CALLS H(P,P) THAT CORRECTLY EMULATES ITS INPUT

    Rather than shouting, you could either publish an honest, un-edited >>>>>>>>> execution trace,

    If you can't understand that a single page already proves that >>>>>>>> H(p,P)==0 is correct it is certainly the case that providing 237-fold >>>>>>>> more details [would not help].
    (Your correction added)

    Your traces are edited. No one will believe them until you post the >>>>>>> real trace, and even then you will have some work to do to convince >>>>>>> people you are being honest about the output.

    I can simply upgrade to smarter people that don't lie.

    I don't lie. Your trace does not show what you claim H is doing.

    That is either a lie or you are very stupid and I do not believe that
    you are very stupid.
    I really don't care. The trace of a nested emulation would not look
    like your trace.

    This <is> the trace of the nested emulation of the input to H(P,P)

    So you say. But there are no signs of anything but an edited sequence
    of function calls. No emulation code appears at all. You may have
    removed the evidence that you are right, but that would an absurd thing
    to do.


    NONE-THE-LESS WHEN WE REVERSE ENGINEER WHAT THE CORRECT NESTED
    SIMULATION OF THE INPUT TO H(P,P) WOULD BE IT EXACTLY MATCHES THE TRACE
    THAT IS PROVIDED THUS CONCLUSIVELY PROVING THAT THE TRACE PROVIDED IS
    CORRECT.

    You will be exposed as a liar when you try to show any error in the
    execution trace of the nested simulation of the input to H(P,P).

    Post H and I'll gladly explain. We know that H is not a halt decider,
    but we don't know exactly what silly thing it really is deciding because
    you post only edited execution traces.



    --
    Copyright 2022 Pete Olcott

    "Talent hits a target no one else can hit;
    Genius hits a target no one else can see."
    Arthur Schopenhauer

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Fri May 20 17:14:09 2022
    XPost: comp.theory, sci.logic

    On 5/20/22 4:33 PM, olcott wrote:
    On 5/20/2022 11:41 AM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    On 5/20/2022 11:26 AM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    On 5/20/2022 10:12 AM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    On 5/20/2022 6:25 AM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    On 5/19/2022 7:53 PM, Ben wrote:
    olcott <NoOne@NoWhere.com> writes:

    ONE CAN VERIFY THAT THE EXECUTION TRACE IS CORRECT ON THE >>>>>>>>>>> BASIS THAT
    THE EXECUTION TRACE OF THE INPUT TO H(P,P) CORRESPONDS TO >>>>>>>>>>> THE BEHAVIOR SPECIFIED BY THE X86 SOURCE-CODE OF P
    WHERE H(P,P) CORRECTLY EMULATES ITS INPUT
    THAT CALLS H(P,P) THAT CORRECTLY EMULATES ITS INPUT

    Rather than shouting, you could either publish an honest,
    un-edited
    execution trace,

    If you can't understand that a single page already proves that >>>>>>>>> H(p,P)==0 is correct it is certainly the case that providing >>>>>>>>> 237-fold
    more details [would not help].
    (Your correction added)

    Your traces are edited.  No one will believe them until you post >>>>>>>> the
    real trace, and even then you will have some work to do to convince >>>>>>>> people you are being honest about the output.

    I can simply upgrade to smarter people that don't lie.

    I don't lie.  Your trace does not show what you claim H is doing.

    That is either a lie or you are very stupid and I do not believe that >>>>> you are very stupid.
    I really don't care.  The trace of a nested emulation would not look
    like your trace.

    This <is> the trace of the nested emulation of the input to H(P,P)

    So you say.  But there are no signs of anything but an edited sequence
    of function calls.  No emulation code appears at all.  You may have
    removed the evidence that you are right, but that would an absurd thing
    to do.


    NONE-THE-LESS WHEN WE REVERSE ENGINEER WHAT THE CORRECT NESTED
    SIMULATION OF THE INPUT TO H(P,P) WOULD BE IT EXACTLY MATCHES THE TRACE
    THAT IS PROVIDED THUS CONCLUSIVELY PROVING THAT THE TRACE PROVIDED IS CORRECT.


    Nope.

    You will be exposed as a liar when you try to show any error in the
    execution trace of the nested simulation of the input to H(P,P).

    Post H and I'll gladly explain.  We know that H is not a halt decider,
    but we don't know exactly what silly thing it really is deciding because
    you post only edited execution traces.




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