Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: dbush Newsgroups: comp.lang.c Subject: Re: Proving the: Simulating termination analyzer Principle Date: Sat, 5 Apr 2025 17:31:04 -0400 Organization: A noiseless patient Spider Lines: 27 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 05 Apr 2025 23:31:03 +0200 (CEST) Injection-Info: dont-email.me; posting-host="43eaa133a904c8986c7a0672d25633a8"; logging-data="3417512"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19gVmOZTCzJ9MYqewu3qfxH" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:lbvdNq3QnkaWJSmQb2QYlnCr9Po= Content-Language: en-US In-Reply-To: Bytes: 1855 On 4/5/2025 5:29 PM, olcott wrote: > On 4/5/2025 4:15 PM, dbush wrote: >> On 4/5/2025 4:52 PM, olcott wrote: >>> *Simulating termination analyzer Principle* >>> It is always correct for any simulating termination >>> analyzer to stop simulating and reject any input that >>> would otherwise prevent its own termination. >>> >>> void DDD() >>> { >>>     HHH(DDD); >>>     return; >>> } >> >> Except when doing so would change the input, as is the case with HHH >> and DDD. >> >> Changing the input is not allowed. > > You may disagree that the above definition > of simulating termination analyzer is correct. > > It is self-evident that HHH must stop simulating > DDD to prevent its own non-termination. > Changing the input is not allowed.