Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: olcott <polcott333@gmail.com>
Newsgroups: comp.theory
Subject: Re: Incorrect requirements --- Computing the mapping from the input
 to HHH(DD)
Date: Mon, 12 May 2025 11:19:50 -0500
Organization: A noiseless patient Spider
Lines: 35
Message-ID: <vvt736$14pca$16@dont-email.me>
References: <vv97ft$3fg66$1@dont-email.me> <vvo1ni$3l14p$1@dont-email.me>
 <c09f468e8485c22150cedb12a9010b401f292054.camel@gmail.com>
 <vvo58a$3lnkd$1@dont-email.me>
 <dc76ef3215a83481dfddc40c466bb9ebc0e77341.camel@gmail.com>
 <vvo709$3m1oc$1@dont-email.me>
 <b503e969e23dd1b2a6201ba78c82c9ff7906eaae.camel@gmail.com>
 <vvo9e8$3m1oc$3@dont-email.me>
 <b9cec56c1d257e09fdf8043f02f123a4243de6e1.camel@gmail.com>
 <vvoife$3ofmu$1@dont-email.me>
 <09cea75db07408dc9203aca3fb74408ad3a095b4.camel@gmail.com>
 <vvoubl$3qtsi$1@dont-email.me>
 <bc4fb153ff914177dba706ce6e0dfb467e2126eb.camel@gmail.com>
 <vvp04i$3r5li$3@dont-email.me>
 <853816e160c7b3fe75c71f0728e72989d9fb2e41.camel@gmail.com>
 <vvp1fm$3r5li$4@dont-email.me>
 <b049926b61baa5d69d11655a8af06e537b7acd71.camel@gmail.com>
 <vvqga9$gldn$3@dont-email.me>
 <41e08841caf0d628beb5105bc78531a412eea440.camel@gmail.com>
 <vvql3p$gldn$15@dont-email.me> <vvsa1a$104j2$1@dont-email.me>
 <vvt2lo$14pca$5@dont-email.me> <vvt2pf$15ceh$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 12 May 2025 18:19:51 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="15cac720ddbb61c7f6586fe023932af8";
	logging-data="1205642"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18Lkv5j/CzLAYl2Fa1lbnfe"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:9F1jH3fcjFuFS4/jjwdPfp+kdD8=
X-Antivirus-Status: Clean
Content-Language: en-US
X-Antivirus: Norton (VPS 250512-4, 5/12/2025), Outbound message
In-Reply-To: <vvt2pf$15ceh$1@dont-email.me>
Bytes: 3416

On 5/12/2025 10:06 AM, dbush wrote:
> On 5/12/2025 11:04 AM, olcott wrote:
>> Termination analyzers compute the mapping from their
>> inputs to the behavior that these inputs actually specify.
> 
> False.  They compute the mapping from their input to the behavior of the 
> algorithm described by the input when executed directly, as per the 
> requirements:
> 

That is easily proven stupidly wrong.

If HHH could see that the direct execution of DDD()
does halt because HHH spots the repeating pattern
and aborts this simulation and HHH did not abort
on this basis then DDD() never halts, proving
that HHH was correct to abort.

Most people here seem to be complete morons about
hypothetical possibilities.

<MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>
     If simulating halt decider H correctly simulates its
     input D until H correctly determines that its simulated D
     *would never stop running unless aborted* then

     H can abort its simulation of D and correctly report that D
     specifies a non-halting sequence of configurations.
</MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>



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