Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: dbush Newsgroups: comp.theory Subject: Re: Turing Machine computable functions apply finite string transformations to inputs Date: Mon, 28 Apr 2025 12:54:45 -0400 Organization: A noiseless patient Spider Lines: 73 Message-ID: References: <0a2eeee6cb4b6a737f6391c963386745a09c8a01@i2pn2.org> <4818688e0354f32267e3a5f3c60846ae7956bed2@i2pn2.org> <65dddfad4c862e6593392eaf27876759b1ed0e69@i2pn2.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 28 Apr 2025 18:54:45 +0200 (CEST) Injection-Info: dont-email.me; posting-host="67af223ffcc413f8c29b457017b45374"; logging-data="3585230"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+2YrTC3+T3ptBsRR0b0vYS" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:tOb3ELAAkgOj2/FPVndiVUQTTRw= Content-Language: en-US In-Reply-To: On 4/28/2025 12:38 PM, olcott wrote: > On 4/28/2025 10:41 AM, dbush wrote: >> On 4/28/2025 11:35 AM, olcott wrote: >>> On 4/28/2025 10:18 AM, dbush wrote: >>>> On 4/28/2025 11:01 AM, olcott wrote: >>>>> On 4/28/2025 2:33 AM, Richard Heathfield wrote: >>>>>> On 28/04/2025 07:46, Fred. Zwarts wrote: >>>>>> >>>>>> >>>>>> >>>>>>> So we agree that no algorithm exists that can determine for all >>>>>>> possible inputs whether the input specifies a program that >>>>>>> (according to the semantics of the machine language) halts when >>>>>>> directly executed. >>>>>>> Correct? >>>>>> >>>>>> Correct. We can, however, construct such an algorithm just as long >>>>>> as we can ignore any input we don't like the look of. >>>>>> >>>>> >>>>> The behavior of the direct execution of DD cannot be derived >>>>> by applying the finite string transformation rules specified >>>>> by the x86 language to the input to HHH(DD). This proves that >>>> >>>> The assumption that an H exists that meets the below requirements is >>>> false, as shown by Linz and others: >>>> >>> >>> I have just proved that those requirements are stupidly wrong >> >> Category error.  The mapping exists > > Computable functions are the formalized analogue > of the intuitive notion of algorithms, in the > sense that a function is computable if there > exists an algorithm that can do the job of the > function, i.e. i.e. a computable function is a mathematical mapping for which an algorithm exists to compute in. And the halting function below is not a computable function: Given any algorithm (i.e. a fixed immutable sequence of instructions) X described as with input Y: A solution to the halting problem is an algorithm H that computes the following mapping: (,Y) maps to 1 if and only if X(Y) halts when executed directly (,Y) maps to 0 if and only if X(Y) does not halt when executed directly > *given an input of the function domain* > *it can return the corresponding output* > https://en.wikipedia.org/wiki/Computable_function > In other words, the algorithm, given an input in the domain of the mathematical function, returns the corresponding output of the mathematical function. > There is a mapping from the input to HHH(DD) by applying > the finite string transformation rules specified by the > x86 language to this DD input that derives: > *no correctly emulated DD ever reaches its final halt state* > In other words, the mathematical function that algorithm HHH is mapping is not the halting function, and therefore isn't a solution to the halting problem.