Path: ...!weretis.net!feeder6.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail From: Richard Damon Newsgroups: comp.theory Subject: Re: Categorically exhaustive reasoning applied to the decision to abort Date: Mon, 1 Apr 2024 19:18:28 -0400 Organization: i2pn2 (i2pn.org) Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Mon, 1 Apr 2024 23:18:28 -0000 (UTC) Injection-Info: i2pn2.org; logging-data="3972960"; mail-complaints-to="usenet@i2pn2.org"; posting-account="diqKR1lalukngNWEqoq9/uFtbkm5U+w3w6FQ0yesrXg"; User-Agent: Mozilla Thunderbird Content-Language: en-US In-Reply-To: X-Spam-Checker-Version: SpamAssassin 4.0.0 Bytes: 2845 Lines: 23 On 4/1/24 10:52 AM, olcott wrote: > Every element of the set of implementations of H(D,D) that simulates its > input either aborts this simulation or is wrong. Yes, every implementation of H(D,D) that does not abort is wrong. This does NOT mean that every implementation of H(D,D) that does abort is right. Since if H(D,D) aborts and returns to D, that D halts, that shows that H did not need to abort it simulation to reach an end statem. > It also must be the first directly executed element that performs > the abort or none of them do because all of the H elements in a > recursive simulation chain have the exact same machine code. But the BEHAVIOR of the MACHINE being SIMULATED (the actual machine, not its simulation) has been established BEFORE H even started its simulation, so H was just wrong when it made its FAULTY deduction that it needed to abort. You confuse the simulation of the input, with the factual establishment of its behavior, which occurs independently of the simulation, and preceeds it.