Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: "Fred. Zwarts" Newsgroups: comp.theory Subject: Re: Simulation vs. Execution in the Halting Problem Date: Fri, 13 Jun 2025 11:11:22 +0200 Organization: A noiseless patient Spider Lines: 39 Message-ID: <102gpvq$3bhe0$1@dont-email.me> References: <102cg6f$246h5$1@dont-email.me> <822e204898d419545ca400a9088970f0b6a5107f.camel@gmail.com> <102ckje$25dg0$2@dont-email.me> <102cm0u$25dg0$3@dont-email.me> <610e2a54b66e8576b80bda3a0fe188d025b9798e.camel@gmail.com> <102cp0e$26clp$1@dont-email.me> <102crbv$26rt0$1@dont-email.me> <102ctbg$26rt0$2@dont-email.me> <102d082$28067$1@dont-email.me> <102d4fa$291mi$1@dont-email.me> <27181e2fc0e06453f53994e2a92e3a5c8808e581.camel@gmail.com> <102d6ge$29fp7$1@dont-email.me> <102d8bk$29pam$1@dont-email.me> <102e74m$2jopg$1@dont-email.me> <102et14$2ohps$8@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Fri, 13 Jun 2025 11:11:23 +0200 (CEST) Injection-Info: dont-email.me; posting-host="f54e121e79e26e1b3dd36e32fd2d3418"; logging-data="3524032"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1//Q2wKT+OVJMO5Gj4gmJA5" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:ZmjTQdao8Pm4XJHtH6pbiu3iQmY= In-Reply-To: <102et14$2ohps$8@dont-email.me> Content-Language: nl, en-GB Op 12.jun.2025 om 17:51 schreef olcott: > On 6/12/2025 4:37 AM, Fred. Zwarts wrote: >> Op 12.jun.2025 om 02:52 schreef olcott: >>> >>> If you don't understand the difference between object >>> instances of OOP classes and the classes themselves >>> then you might not understand. >>> >>> int main() >>> { >>>    D(); // calls H(D) and the parameter to this H(D) >>> }      // is not the caller of this instance of H(D) >>> >> The analyser should not decide about an instance, but about what is >> specified by the code. > void DDD() > { >   HHH(DDD); >   return; > } > > The input to HHH(DDD) specifies a sequence of configurations > that cannot possibly reach their own "return" statement > final halt state. The input is a pointer to code that includes the code to abort and halt. That HHH is not able to reach that part of the code is a failure of HHH, not a property of the program specified in the input. That HHH cannot reach it, does not change the specified code. The program aborts as world-class simulators en direct execution of exactly the same input prove. > > That you are insufficiently competent to see this is proven > by the fact that you have no rebuttal anchored in correct > reasoning. > Ad hominem attacks only prove your lack of counter-arguments.