1. Forum
  2. Usenet
  3. COMP.THEORY

  • Re: Repetitive posting [ Was: Incorrect requirements --- Computing the

    From Fred. Zwarts@21:1/5 to All on Sat May 10 16:57:58 2025
    Op 10.mei.2025 om 16:30 schreef olcott:
    On 5/10/2025 5:21 AM, Alan Mackenzie wrote:
    olcott <polcott333@gmail.com> wrote:

    [ .... ]

    Do I have to repeat this 1000 times before you ever notice
    that I said it once?

    Most of what you write, you have written many, many times.  Reading your
    posts is dull, dull, dull.  Whenever I look at your posts and see yet one >> more x86 instruction sequence, or yet one more C fragment, I just
    subconsciously skim over it.  You must have posted these literally 1000
    times and more.

    Why can't you post something original and fresh, for a change?

    [ .... ]

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


    *I only came up with this in the last month*

    And this irrelevant text has been posted already many times.


    _DDD()
    [00002172] 55         push ebp      ; housekeeping
    [00002173] 8bec       mov ebp,esp   ; housekeeping
    [00002175] 6872210000 push 00002172 ; push DDD
    [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD)
    [0000217f] 83c404     add esp,+04
    [00002182] 5d         pop ebp
    [00002183] c3         ret
    Size in bytes:(0018) [00002183]

    HHH(DDD) is only allowed to compute the mapping from
    its input finite string to the behavior that this
    input finite string actually. This is measured by HHH
    emulating DDD according to the rules of the x86 language.


    Since this strings includes the conditional abort, it specifies a
    halting program, but hHH computes another mapping, which makes it
    incorrect. That HHH is blind for the specified behaviour does not mean
    that the behaviour is not specified. It only proves that there are bugs
    in HHH, because it violates the semantics of the x86 language.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Sat May 10 15:21:21 2025
    On 5/10/25 10:30 AM, olcott wrote:
    On 5/10/2025 5:21 AM, Alan Mackenzie wrote:
    olcott <polcott333@gmail.com> wrote:

    [ .... ]

    Do I have to repeat this 1000 times before you ever notice
    that I said it once?

    Most of what you write, you have written many, many times.  Reading your
    posts is dull, dull, dull.  Whenever I look at your posts and see yet one >> more x86 instruction sequence, or yet one more C fragment, I just
    subconsciously skim over it.  You must have posted these literally 1000
    times and more.

    Why can't you post something original and fresh, for a change?

    [ .... ]

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


    *I only came up with this in the last month*

    _DDD()
    [00002172] 55         push ebp      ; housekeeping
    [00002173] 8bec       mov ebp,esp   ; housekeeping
    [00002175] 6872210000 push 00002172 ; push DDD
    [0000217a] e853f4ffff call 000015d2 ; call HHH(DDD)
    [0000217f] 83c404     add esp,+04
    [00002182] 5d         pop ebp
    [00002183] c3         ret
    Size in bytes:(0018) [00002183]

    HHH(DDD) is only allowed to compute the mapping from
    its input finite string to the behavior that this
    input finite string actually. This is measured by HHH
    emulating DDD according to the rules of the x86 language.


    Right, the mapping that HHH computes must be by those rules, but since
    it breaks its rules, it doesn't get the right answer. Any HHH that
    reports an answer needed to break the correct emulation rule by doing
    ony a partial emulation.

    The mapping that it must compute to be CORRECT does not need to be a
    computable result.

    That mapping is based on the correct emulation of the input, not
    restricted to being by HHH (and in fact, it can't be, since any HHH that
    gives an answer can't have followed the rules).

    This mapping will see that any of your HHH that answer, will abort their emulation when they have been called by DDD, and return to that DDD
    which will halt.

    Thus, the mapping of ANY DDD that calls an HHH(DDD) that returns an
    answer will halt, so that HHH would have needed to return a 1 to have
    been correct.

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