| Deutsch English Français Italiano |
|
<vvtb81$15ceh$15@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: dbush <dbush.mobile@gmail.com> Newsgroups: comp.theory Subject: Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD) Date: Mon, 12 May 2025 13:30:42 -0400 Organization: A noiseless patient Spider Lines: 46 Message-ID: <vvtb81$15ceh$15@dont-email.me> References: <vv97ft$3fg66$1@dont-email.me> <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> <vvt736$14pca$16@dont-email.me> <vvt8bv$15ceh$9@dont-email.me> <vvt949$14pca$22@dont-email.me> <vvt9sb$15ceh$13@dont-email.me> <vvtae1$14pca$24@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 19:30:42 +0200 (CEST) Injection-Info: dont-email.me; posting-host="d587ba6f088c47ed8fd2ad250ebfd646"; logging-data="1225169"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+h4SEEBdLjk2gxNEzMh5gW" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:8J57EgYMjRbnnr7kKnp4msmgKUg= Content-Language: en-US In-Reply-To: <vvtae1$14pca$24@dont-email.me> On 5/12/2025 1:16 PM, olcott wrote: > On 5/12/2025 12:07 PM, dbush wrote: >> On 5/12/2025 12:54 PM, olcott wrote: >>> On 5/12/2025 11:41 AM, dbush wrote: >>>> On 5/12/2025 12:19 PM, olcott wrote: >>>>> 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. >>>> >>>> >>>> Category error. Definitions are not proven: >>>> >>> >>> Definitions that contradict other definitions are refuted. >>> >> >> >> And you haven't shown a conflict with the definition of a solution to >> the halting problem: >> > > That you keep ignoring it its not > a matter of me never providing it. > In other words, you agree that no algorithm exists that can compute the following mapping: Given any algorithm (i.e. a fixed immutable sequence of instructions) X described as <X> with input Y: A solution to the halting problem is an algorithm H that computes the following mapping: (<X>,Y) maps to 1 if and only if X(Y) halts when executed directly (<X>,Y) maps to 0 if and only if X(Y) does not halt when executed directly