Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "Fred. Zwarts" Newsgroups: comp.theory Subject: Re: Indirect Reference Changes the Behavior of DDD() relative to DDD emulated by HHH Date: Sat, 7 Sep 2024 12:19:51 +0200 Organization: A noiseless patient Spider Lines: 50 Message-ID: References: <878qwn0wyz.fsf@bsb.me.uk> <87le0jzc8f.fsf_-_@bsb.me.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Sat, 07 Sep 2024 12:19:53 +0200 (CEST) Injection-Info: dont-email.me; posting-host="a1d6656c1a26d4db193354f7a3d64b24"; logging-data="1404868"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18E7DUyOkSq81YoeL7MgtEa" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:tnP3dOEWIv7a33Ff6CqqzcAucwY= Content-Language: en-GB In-Reply-To: Bytes: 4123 Op 06.sep.2024 om 13:31 schreef olcott: > On 9/6/2024 4:36 AM, Fred. Zwarts wrote: >> Op 05.sep.2024 om 15:48 schreef olcott: >>> >>> HHH MUST ABORT AFTER SOME FIXED NUMBER OF RECURSIVE EMULATIONS >>> AND THE OUTERMOST HHH ALWAYS SEE ONE MORE THAN THE NEXT INNER ONE. >> >> And the outer one, when aborting after two cycles , misses the >> behaviour of the inner one in the next cycle, where the inner one >> would see the 'special condition', abort, return to DDD, which would >> halt as well. >> That HHH misses the last part of the behaviour of the program, does >> not change the fact that this is the behaviour that was coded in the >> program >> >>> >>> If we have an infinite chain of people each waiting for >>> the next one down the line to do something then that thing >>> is never done. >> >> The infinite chain exists only in your dream. In fact there are only >> two recursions, so never more that a chain of three HHH in the >> simulation. >> HHH is incorrect in assuming the there is an infinite chain, but this >> incorrect assumption makes that it aborts and halts. This applies both >> to the simulating and the simulated HHH. > > The way it is encoded now there are only two recursions. > > If we encode it as you suggest the outermost directly > executed HHH would wait for the first emulated HHH which > would wait for the second which would wait for third > on and on... > What is olcott's problem with English? If one way is incorrect, he thinks that it suggests that another way must be correct. I never suggested to change HHH, because there is *no* correct way to do it. Every HHH that simulates itself is incorrect. No matter what clever code it includes. There are two types of HHH: a) that waits till the simulation halts, b) that does not wait but aborts and halts. The HHHa is correct when its input is based on HHHb, but does not halt if its input is based on HHHa. The HHHb is correct when its input is based on HHHa, but incorrect when its input is based on HHHb. HHH cannot possibly simulate *itself* correctly up to the end.